This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

dealing with newer version numbers in glibc "configure"


  i'm having to, ever so slightly, hack the newest glibc's configure
script to accept the latest snapshots of binutils.  in that configure
script, you find the version checking:

=====
if test -z "$AS"; then
  ac_verc_fail=yes
else
  # Found it, now check the version.
  echo "$as_me:$LINENO: checking version of $AS" >&5
echo $ECHO_N "checking version of $AS... $ECHO_C" >&6
  ac_prog_version=`$AS --version 2>&1 | sed -n 's/^.*GNU assembler.*
\([0-9]*\.[0-9.]*\).*$/\1/p'`
  case $ac_prog_version in
    '') ac_prog_version="v. ?.??, bad"; ac_verc_fail=yes;;
    2.1[3-9]*)
       ac_prog_version="$ac_prog_version, ok"; ac_verc_fail=no;;
    *) ac_prog_version="$ac_prog_version, bad"; ac_verc_fail=yes;;
=====

  where, you can see, the configure script is pretty picky about what
it things is an acceptable version of "as" (the current version of
"2.15" is clearly acceptable).  the same thing holds for "ld" as well.
note that this clearly won't accept the versions of those programs
from what i'm testing with, which is binutils-041205.  when you run
the generated versions of those two programs with "--version", you
get:

...
GNU assembler 041205 20041205
...
GNU ld version 041205 20041205

which, as you can see, will fail the version test when glibc is
configured:

...
checking version of
/home/rob/ct/results/sh3eb-unknown-linux-gnu/gcc-4.0-20041205-glibc-20041204/lib/gcc/sh3eb-unknown-linux-gnu/4.0.0/../../../../sh3eb-unknown-linux-gnu/bin/as...
v. ?.??, bad
...
checking version of
/home/rob/ct/results/sh3eb-unknown-linux-gnu/gcc-4.0-20041205-glibc-20041204/lib/gcc/sh3eb-unknown-linux-gnu/4.0.0/../../../../sh3eb-unknown-linux-gnu/bin/ld...
v. ?.??, bad
...

  a quick patch will handle this, of course, but it's annoying that
it's glibc snapshot version 20041204 that's doing this.  you'd think
that the snapshots of the GNU utils would have been updated to be
compatible with the other snapshots. :-(

rday

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


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