Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] glibc 2.4 build failure

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: seth AT swoolley.homeip.net
  • To: George Sherwood <pilot AT beernabeer.com>
  • Cc: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] glibc 2.4 build failure
  • Date: Sat, 25 Nov 2006 16:04:49 -0800

On Sat, Nov 25, 2006 at 10:18:56PM +0400, George Sherwood wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sat, 25 Nov 2006 08:44:09 -0800
> seth AT swoolley.homeip.net wrote:
>
> > If you read the past email discussions on multilib you'll see why they
> > aren't all in if statements. Portions were made optional and some
> > were made required based on discussion.
> >
> > I'd like to see a diff -Nua between the old and new configure scripts
> > if you can, so I can see why that sed script causes errors for you.
> >
> > Seth
>
> Here is the diff, but from looking at it, it isn't the change that is
> causing the problem, it is the fact that the change itself is causing
> configure to be run in that directory. That is what is failing in the
> glibc build. At least that is my guess from spending a few hours
> trying to get glibc 2.4 installed.
>
> - --- configure.withsedit 2006-11-25 22:08:50.000000000 +0400
> +++ configure.withoutsedit 2006-11-25 22:12:06.000000000 +0400
> @@ -229,7 +229,7 @@
> # and libc_cv_localedir.
> test -n "$libc_cv_slibdir" || \
> case $machine in
> - - sparc/sparc64 | powerpc/powerpc64 | s390/s390-64)
> + sparc/sparc64 | x86_64 | powerpc/powerpc64 | s390/s390-64)
> libc_cv_slibdir="/lib64"
> if test "$libdir" = '${exec_prefix}/lib'; then
> libdir='${exec_prefix}/lib64';
>
>
> Since I don't have a 64 bit machine, I didn't pay much attention to the
> multilib discussions. I am sure there were great reasons for doing it
> that way, I was just passing along that it was causing problems for me
> and one other user not on a 64 bit machine.

My code makes the change to configure.in also, so that when it's
reautotooled it will work too. Your #sourcemage-dump output indicates that
it simply re-ran autoconf, but you didn't paste the rest of the break.

I suspect you updated autoconf to a version those version of glibc doesn't
like.

Perhaps paste the rest of the error and some build system tool versions...

...so we have something to go on. ;)

Seth




Archive powered by MHonArc 2.6.24.

Top of Page