[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: comiling error in exec
From: |
Alfred M. Szmidt |
Subject: |
Re: comiling error in exec |
Date: |
Fri, 13 Feb 2004 12:21:09 +0100 (MET) |
Honestly, I would prefer that we just require pretty darn new libc
for use with hurd. But if that is really an imposition, using
#ifdef is fine for this. There is no great loss in just disabling
the new functionality.
I don't see any problems with this, the Hurd and glibc are quite
tightly linked in more ways then one. What one can do is to add a
config check to autoconf that will barf if you try to compile the Hurd
with a older glibc. And then maybe have a --enable-old-glibc switch
to override it. This would also clean up a bit in
[hurd]/configure.in.
Not sure how one would detect the version of glibc in a sane manner
though. __GLIBC_PREREQ only cares about major and minor versions; we
would need some kind of a mini-version check.
Anyway, what do you think about doing something like that?
Cheers.
- comiling error in exec, Dmitry V. Zhulanov, 2004/02/12
- Re: comiling error in exec, Dmitry V. Zhulanov, 2004/02/12
- Re: comiling error in exec, Alfred M. Szmidt, 2004/02/12
- Re: comiling error in exec, Roland McGrath, 2004/02/12
- Re: comiling error in exec,
Alfred M. Szmidt <=
- Re: comiling error in exec, Roland McGrath, 2004/02/13
- Re: comiling error in exec, Alfred M. Szmidt, 2004/02/13
- Re: comiling error in exec, Roland McGrath, 2004/02/13
- Re: comiling error in exec, Alfred M. Szmidt, 2004/02/13
- Re: comiling error in exec, Michael Banck, 2004/02/13
- Re: comiling error in exec, Alfred M. Szmidt, 2004/02/13
Re: comiling error in exec, M. Gerards, 2004/02/12