CODEWITHSUNDEEP
cgccglibc
my_question
my_question

Reputation: 3235

Why glibc configure complains gcc version?

I downloaded glibc 2.3.1 source code and tried compiling it, the compilation failed saying gcc and make are too old:

../glibc-2.3.1_src/configure  --prefix=/home/user/download/glibc-2.3.1/install

checking version of gcc... 9.4.0, bad
checking for gnumake... no
checking for gmake... no
checking for make... make
checking version of make... 4.2.1, bad
configure: error:
*** These critical programs are missing or too old: gcc make
*** Check the INSTALL file for required versions.

This is odd as INSTALL says gcc needs to be 3.2 or newer. Yet you can see from the above message that gcc is 9.4.

You see what is wrong? How to fix it?

Upvotes: 1

Views: 1466

Answers (2)

Bart
Bart

Reputation: 229

The configure script does not check for 'too new' versions.

Fix for 'too old' make, see comment in GLIBC install failed, programs are missing or too old

Fix for 'too old' gcc: search for missing gcc in configure. Then look a bit higher (near ac_prog_version) to see 4.[3-9].* | 4.[1-9][0-9].* | [5-9].* Put | 9.* after that (where 9 denotes the gcc version you want to use).

Upvotes: 0

Grady Player
Grady Player

Reputation: 14549

your specified glibc is ancient, released 20 years ago

2002-10-10 GLIBC 2.3.1

glibc probably has some problem recognizing or parsing versions from make and gcc that new (or the flags used to get the versions of make and gcc changed along the way)...

you are probably looking for 2020-02-01 GLIBC 2.31

Upvotes: 2

Related Questions