This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc 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: AC_TRY_LINK

From: Dan Kegel <dank at kegel dot com>
To: Anton Blanchard <anton at samba dot org>
Cc: Roland McGrath <roland at redhat dot com>, libc-alpha at sources dot redhat dot com
Date: Tue, 20 Jan 2004 08:51:23 -0800
Subject: Re: AC_TRY_LINK
References: <20040120033540.GH3620@krispykreme> <200401200557.i0K5vScp012177@magilla.sf.frob.com> <20040120115323.GN3620@krispykreme>

Anton Blanchard wrote:

Those tests are necessary to ensure that you have everything you need for
libpthread to work right.  If you need to get around them for bootstrapping
purposes, you can hand-prime a config.cache file to preempt the test.  You
only have to do this in the very first glibc build.  After that you should
be able to have enough installed for a vanilla configure and build to work
right.

Assuming a non NPTL build will continue to work (either no threads or
linuxthreads), we could make the first pass use it. Still, it would be
nice to fix those 2 NPTL tests to not requiring linking.


I haven't seen the problem you're talking about when building
gcc/glibc cross-toolchains with http://kegel.com/crosstool
Does it only show up when building a ppc64 toolchain?  If so,
I'll give that a whirl.  Do I need glibc cvs for that?
- Dan

References:
- AC_TRY_LINK
  - From: Anton Blanchard
- Re: AC_TRY_LINK
  - From: Roland McGrath
- Re: AC_TRY_LINK
  - From: Anton Blanchard

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