Skip to Content.
Sympa Menu

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

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: George Sherwood <pilot AT beernabeer.com>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: [SM-Discuss] glibc 2.4 build failure
  • Date: Sat, 25 Nov 2006 14:14:03 +0400

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Both Phenax and I were seeing the same error when trying to build glibc
2.4. He also tried glibc 2.5 and got the same error. There error
looks like:

checking for grep that handles long lines and -e... Usage: grep
[OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.
configure: error: no acceptable grep could be found
in
/var/lib/sorcery/build:/sbin:/usr/sbin:/usr/local/sbin:/bin:/usr/bin:/usr/local/bin:/usr/games:/usr/local/games:/usr/bin/X11:/root/bin:.:/usr/lib/j2sdk/bin:/usr/xpg4/bin
make[1]: Failed to remake makefile
`/usr/src/glibc-2.4.bld/config.make'

I rebuilt grep and all dependencies and still had no luck. During the
initial configure, it was finding grep with no problems.
Comparing the compile logs from my two machines to successfully
build glibc 2.4 and the one with a problem I found that after the
initial configure, the problem machine was calling configure again in:

sysdeps/unix/sysv/linux/

This was then failing with the above error. The machines it was
working on did not call run that configure.

Looking at the BUILD I found:

# install x86_64 libraries to lib instead of lib64
sedit "s/| x86_64//" sysdeps/unix/sysv/linux/configure &&
sedit "s/| x86_64//" sysdeps/unix/sysv/linux/configure.in &&

It wasn't clear to me why those lines aren't part of the if statement
above it:
if [ "$GLIBC_NOLIB64" = "y" ]; then
# install x86_64 linker to lib instead of lib64

since I a building on a PIII. So I commented them out. The configure
now looked exactly the same and glibc 2.4 installed without any
problems. Phenax did the same and everything is now working for him
also.

Is this a bug in the spell or have I set myself up for more problems?

George Sherwood


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFaBdukVJnfkgKg60RAuueAJ9aOLCezB5SnREWuWTUorDkDZlGIACfX7Os
OnbeYpiNqhWKE614IaMOuFQ=
=Droo
-----END PGP SIGNATURE-----



Archive powered by MHonArc 2.6.24.

Top of Page