problem with ldconfig and xorg libraries

From: Chuck Robey (chuckr_at_chuckr.org)
Date: 06/27/05

  • Next message: Remington L: "buildkernel woes"
    Date: Mon, 27 Jun 2005 02:12:27 +0000
    To: FreeBSD-current@FreeBSD.org
    
    

    I have to recover from a particularly dumb thing that I did. It's an
    entertaining problem, so I'll see if I can lay it all out to you.

    I run FreeBSD on two machine, "April" and July". They are both 2
    processor smp machines; April is i386, and the July machine is amd64. I
    often use x11 cross mounts, so I have to keep in mind what's my current
    machine, else I will do what I just did. In pkg_add, there's a
    variable, PACKAGESITE, that lets you vector the place you get your
    packages from, and I use this to set the ARCH. I screwed up , mis-set
    it to i386 just before beginning to bring in a lot of KDE upgrade
    ports. Oops.

    OK, I used "file" to locate i386 libraries, and I rebuilt (from sources,
    the ports directly) very nearly everything. FreeBSD is *SO* darned
    stable, I have really only hit just thing single really killer problem ...

    The problem?? Can't start X11. When I try a startx, I get about a done
    lines, but they're really just all copies of one of these two lines:

    /libexec/ld-elf.so.1: /usr/X11R6/lib/libX11.so.6: unsupported file layout
    /libexec/ld-elf.so.1: /usr/X11R6/lib/libXau.so.0: unsupported file layout

    july:chuckr:/usr/X11R6/lib:#27>file libX11.so.6 libXau.so.0
    libX11.so.6: ELF 64-bit LSB shared object, AMD x86-64, version 1
    (FreeBSD), not stripped
    libXau.so.0: ELF 64-bit LSB shared object, AMD x86-64, version 1
    (FreeBSD), not stripped

    These happen to be precisely what all the other X11 libraries are
    reporting, too. OK, these are all of the more obvious hints. If you
    can think up any other ones, I'd very much appreciate a note to me.
    Being as candid as I can be, I'm actually enjoying doing this, running
    down these problems.
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  • Next message: Remington L: "buildkernel woes"

    Relevant Pages

    • xfce4 & networking
      ... I just installed FreeBSD 5.3-RELEASE doing the prepackaged User+X11 ... make install clean). ... displays an error message (in X11, not on the terminal) that says, " ...
      (freebsd-questions)
    • Re: FreeBSD Security Advisory FreeBSD-SA-08:05.openssh
      ... For general information regarding FreeBSD Security Advisories, ... server and forwarding any connections which are made to that port. ... use X11 will connect to the IPv4 port, even though it had not been ...
      (FreeBSD-Security)
    • [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-08:05.openssh
      ... For general information regarding FreeBSD Security Advisories, ... including descriptions of the fields above, security branches, and the ... server and forwarding any connections which are made to that port. ... use X11 will connect to the IPv4 port, even though it had not been ...
      (freebsd-announce)
    • FreeBSD Security Advisory FreeBSD-SA-08:05.openssh
      ... For general information regarding FreeBSD Security Advisories, ... including descriptions of the fields above, security branches, and the ... server and forwarding any connections which are made to that port. ... use X11 will connect to the IPv4 port, even though it had not been ...
      (FreeBSD-Security)
    • FreeBSD Security Advisory FreeBSD-SA-08:05.openssh
      ... For general information regarding FreeBSD Security Advisories, ... including descriptions of the fields above, security branches, and the ... server and forwarding any connections which are made to that port. ... use X11 will connect to the IPv4 port, even though it had not been ...
      (Bugtraq)