This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: report and queries on building 64bit + 32bit bi-arch amd64/i686 multilib glibc-2.8.90+ with gcc-4.2.4 on x86_64 AMD-TL64 linux-2.6.26+ GNU Linux
- From: Jason Vas Dias <jvdias at research dot att dot com>
- To: libc-help at sourceware dot org
- Date: Sun, 8 Jun 2008 16:31:55 -0400
- Subject: Re: report and queries on building 64bit + 32bit bi-arch amd64/i686 multilib glibc-2.8.90+ with gcc-4.2.4 on x86_64 AMD-TL64 linux-2.6.26+ GNU Linux
- Organization: at&t labs research inc.
- References: <200806072236.29923.jvdias@research.att.com> <20080608.205236.343159294.mrs@localhost.localdomain>
- Reply-to: jvdias at research dot att dot com
On Sunday 08 June 2008 15:52:36 Mark Seaborn wrote:
> Jason Vas Dias <jason.vas.dias@gmail.com> wrote:
>
> > When I attempt to build the HEAD branch after
>
> If you check out glibc from CVS with this command:
>
> > cvs -d:pserver:anoncvs@sources.redhat.com:/cvs/glibc co libc
>
> you will likely get this:
>
> > configure: error:
> > *** It seems that you're using an old `crypt' add-on. crypt is now
> > *** part of glibc and using the old add-on will not work with this
> > *** release. Start again with fresh sources and without the old
> > *** `crypt' add-on.
>
> You need to use cvs's -P flag, otherwise cvs will create empty
> directories which confuse glibc's configure script.
>
> i.e. check out with
>
> cvs -d:pserver:anoncvs@sources.redhat.com:/cvs/glibc -P co libc
>
> or do
>
> cvs update -dP
>
> The instructions on http://sourceware.org/glibc/ are not entirely correct.
> They would only work if you have put "update -dP" in your ~/.cvsrc.
>
> Mark
>
Thanks Mark - my CVS experience is a bit out-of-context for me at the moment -
your suggestion got rid of complaints about ../crypt and ../localedata -
but the i686 on x86_64 issues still remain.
I think streamlining a dual-architecture '--enable-multilib' / '--enable-targets='
feature for the GNU non-distro-specific build is a must-have for glibc going forward .
I'm rolling my own, and will post to libc-alpha when I get good results.
Regards,
Jason