Date: Wed, 2 Sep 1998 13:08:05 +1000 From: David Dawes <dawes@rf900.physics.usyd.edu.au> To: freebsd-current@FreeBSD.ORG Subject: Re: XFree86 and ELF Message-ID: <19980902130805.B21469@rf900.physics.usyd.edu.au> In-Reply-To: <19980902004140.A17784@keltia.freenix.fr>; from Ollivier Robert on Wed, Sep 02, 1998 at 12:41:40AM %2B0200 References: <199809011809.UAA16527@yacht.domestic.de> <19980902004140.A17784@keltia.freenix.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 02, 1998 at 12:41:40AM +0200, Ollivier Robert wrote: >According to Joachim Kuebart: >> The information to build XFree86 is incomplete: >> >> You need to separately "make configure" and then edit >> work/xc/config/cf/xf86site.def to include the line >> >> #define UseElfFormat YES > >There is a better way I think. I've completed a "make World" of X11R6.3, >using a merge of all posted patches (Doug's & yours) and some mine. The >various X servers/lib/programs linked successfully and seems to run fine. > >> This is due to the fact that I am unaware of a portable way to check >> if we're on an ELF system. Bear in mind it might be a prehistoric >> -stable version, so it isn't just a question of `objformat`. > >XFree86 has only releases to consider and 3.0 will be ELF so it is safe IMO >to assume that "objformat" will return "elf". Anyway, when you run an ELF >FreeBSD, __ELF__ is defined by the preprocessor... > >Supporting both 3.0/aout and 3.0/ELF may be too complicated. I don't know what you want to do with your ports, but speaking for XFree86, I'd like to see both formats supported in the medium term. It would be good from an XFree86 point of view to add code to imake to figure out the default binary format to use at runtime and have that set DefaultBinaryType internally. >-=-=- > >ldd seems to display some libraries (the one in the path specified with >"-rpath" and "-rpath-link"). Is it expected ? > >-=-=- >programs/xdpyinfo/xdpyinfo: > libXtst.so.6 => /usr/X11R6/lib/libXtst.so.6 (0x28056000) > libXIE.so.6 => /usr/X11R6/lib/libXIE.so.6 (0x2805b000) > libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x28065000) > libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x2806c000) > libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x28076000) > libm.so.2 => /usr/lib/libm.so.2 (0x28109000) > libc.so.3 => /usr/lib/libc.so.3 (0x28123000) > libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x2806c000) > libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x28076000) > libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x28076000) > libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x2806c000) > libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x28076000) > libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x28076000) >-=-=- I recall seeing this reported for Linux/ELF some time ago. I'm not sure how they dealt with that. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980902130805.B21469>