This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: target names and glibc versions on linux


On Tue, 2003-06-24 at 20:43, Jim Wilson wrote:
> Alex Hornby wrote:
> > I've been having a bit of trouble with the way that config.guess returns
> > the same string (i686-pc-linux-gnu) for glibc 2.0, 2.2 and 2.3 based
> > GNU/Linux systems.
> 
> What kind of trouble?  We can't help if we don't know what the problem is.

Hi Jim,

My starting point is that I have an NFS shared directory containing
various tools mounted on various linux machines of different vintages -
this has lead me to need to test which version of linux I am on when
setting up PATHs etc.

config.guess doesn't distinguish between them, so I end up doing things
like greping /etc/redhat-release or its distro equivalent.

On solaris I have the same situation, but I can use config.guess output
on which to base my decisions.  Of course with solaris there is just the
"OS release" version to consider. On linux I would argue that the glibc
version is the closest thing to the "OS release", as most user space
tools don't really care which kernel they are on, but will most
definitely need the correct glibc version for the dynamic linker to load
them.

Anyway - the basic point is that say, Redhat 9 and Debian Woody are
quite different systems (glibc, kernel etc etc), at least as different
as solaris 2.6 and 2.8, but config.guess doesn't give me any assistance
in distinguishing them, so I have to fall back to add-hoc methods of my
own.

Cheers,
Alex.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]