Does glibc x86_64 build really depend on linux kernel's autoconf.h ?

[Andreas Jaeger]

"Shivram U" <shivaram.upadhyayula@wipro.com> writes:
>  It seems that in the x86_64 build page.h is included which in turn includes
> config.h, which included autoconf.h. Touching the autoconf.h file just
> before the build works fine. Generating the autoconf.h via a make
> config/oldconfig works fine too. The problem however is not reproducible for
> a native build on an i686 machine.
>
>  Does the x86_64 glibc build really depend on definitions in the autoconf.h
> ? Would touching the autoconf.h be a safe way of getting around this problem
> ?

It only depends on the <linux/aout.h> header but that one depends on
this file.  glibc directly does not depend on autoconf.h.  So touching
the file should work from glibc's part,

Andreas
-- 
 Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
  SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20030829/9b636a3d/attachment.sig>