RE: FC3 SMP builds do NOT contain ext3 drivers in the build!!!!
by Fred Skrotzki
ok this is out of order but it belongs here.
If you "hack" the fstab and change ext3 to ext2 and reboot it will still have ext3 errors because the mkinitrd uses the /etc/fstab at build time to determine modules. So to get it to load ext2 instead of ext3 you need to change fstab then do a new initrd so that it knows the changes and loads the right drivers for the partition.
-----Original Message-----
From: fedora-list-bounces(a)redhat.com
[mailto:fedora-list-bounces@redhat.com]On Behalf Of Terry Polzin
Sent: Thursday, December 02, 2004 2:27 PM
To: For users of Fedora Core releases
Subject: Re: FC3 SMP builds do NOT contain ext3 drivers in the build!!!!
On Thursday 02 December 2004 14:14, Fred Skrotzki wrote:
> # grub.conf generated by anaconda
> #
> # Note that you do not have to rerun grub after making changes to this file
> # NOTICE: You have a /boot partition. This means that
> # all kernel and initrd paths are relative to /boot/, eg.
> # root (hd0,0)
> # kernel /vmlinuz-version ro root=/dev/sda2
> # initrd /initrd-version.img
> #boot=/dev/sda
> default=1
> timeout=5
> splashimage=(hd0,0)/grub/splash.xpm.gz
> hiddenmenu
> title Fedora Core (2.6.9-1.681_FC3)
> root (hd0,0)
> kernel /vmlinuz-2.6.9-1.681_FC3 ro root=LABEL=/1
> initrd /initrd-2.6.9-1.681_FC3.img
> title Fedora Core (2.6.9-1.681_FC3smp)
> root (hd0,0)
> kernel /vmlinuz-2.6.9-1.681_FC3smp ro root=LABEL=/1
> initrd /initrd-2.6.9-1.681_FC3smp.img
> title Fedora Core (2.6.9-1.667smp)
> root (hd0,0)
> kernel /vmlinuz-2.6.9-1.667smp ro root=LABEL=/1
> initrd /initrd-2.6.9-1.667smp.img
> title Fedora Core-up (2.6.9-1.667)
> root (hd0,0)
> kernel /vmlinuz-2.6.9-1.667 ro root=LABEL=/1
> initrd /initrd-2.6.9-1.667.img
>
> -----Original Message-----
> From: fedora-list-bounces(a)redhat.com
> [mailto:fedora-list-bounces@redhat.com]On Behalf Of Terry Polzin
> Sent: Thursday, December 02, 2004 2:07 PM
> To: For users of Fedora Core releases
> Subject: Re: FC3 SMP builds do NOT contain ext3 drivers in the build!!!!
>
> On Thursday 02 December 2004 14:02, Fred Skrotzki wrote:
> > Drive was low level formatted and verified before and after 3 builds. It
> > boots and works fine under single proc. I even build it on another drive
> > just to be sure.
> >
> > BOX is a full blown server class system. hot swap drives, etc...
> > HP LP2000r dual 1.0 Ghz P4
> > 1 gig ram
> >
> > here is the drive config
> > Device Boot Start End Blocks Id System
> > /dev/sda1 * 1 13 104391 83 Linux
> > /boot ext3 /dev/sda2 14 1548 12329887+ 83 Linux
> > / ext3 /dev/sda3 1549 1809 2096482+ 82 Linux
> > swap swap /dev/sda4 1810 4427 21029085 5
> > Extended
> > /dev/sda5 1810 2070 2096451 83 Linux
> > /var/log ext3
> >
> > fstab
> > LABEL=/1 / ext3 defaults 1
> > 1 LABEL=/boot /boot ext3 defaults
> > 1 2 none /dev/pts devpts
> > gid=5,mode=620 0 0 none /dev/shm tmpfs
> > defaults 0 0 none /proc
> > proc defaults 0 0 none /sys
> > sysfs defaults 0 0 LABEL=/var/log1 /var/log
> > ext3 defaults 1 2 LABEL=SWAP-sda3 swap
> > swap defaults 0 0
> >
> > Here is what is left on the screen when booting using SMP:
> >
> > ext3: unknown symbol journal_get_write_access
> > ext3: unknown symbol journal_undo_access
> > ext3: unknown symbol journal_create_access
> > ext3: unknown symbol journal_destroy
> > ext3: unknown symbol journal_clear_error
> > ext3: unknown symbol journal_stop
> > ext3: unknown symbol journal_init_inode
> > ext3: unknown symbol journal_start
> > ext3: unknown symbol log_wait_command
> > ext3: unknown symbol journal_release_buffer
> > ext3: unknown symbol journal_check_available_features
> > ext3: unknown symbol journal_abort
> > ext3: unknown symbol journal_restart
> > insmod: error inserting '/lib/ext2.ko": -1 unknown symbol in module
> > ERROR: /sbin/udevstart exited abnormally
> > creating root drive
> > umount /sys failed: 16
> > Mounting root file system
> > mount: error 19 mounting ext3
> > mount: error 2 mounting none
> > switching to new root
> > switchroot: mount failed: 22
> > umount /initrd/dev failed: 2
> > Kernel panic - not syncing......
>
> Would you send on a copy of your grub.conf.
Like Ed Wilts suggested, doctor the fs tab and make the root partition ext2
and boot smp. Sounds like the journal is hosed.
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
19 years, 6 months
Cannot install skype
by Bayrouni
Hello all,
I tried to install skype 0.92 using:
rpm -Uvh skype-0.92.0.12-fc2.i386.rpm
the output from here is:
erreur: Dépendances requises:--> 'error: dedpendencies requiered'
libstdc++.so.5 est nécessaire pour skype-0.92.0.12-fc2.i386
libstdc++.so.5(CXXABI_1.2) est nécessaire pour
skype-0.92.0.12-fc2.i386
libstdc++.so.5(GLIBCPP_3.2) est nécessaire pour
skype-0.92.0.12-fc2.i386
then I search which libstdc is installed on my FC3.
find / -name libstdc++.so.*
the result is:
/usr/lib/libstdc++.so.6
/usr/lib/libstdc++.so.6.0.3
At the end I created a symlink to /usr/lib/libstdc++.so.6
ln -s /usr/lib/libstdc++.so.6 /usr/lib/libstdc++.so.5
and the find command outputs now
find / -name libstdc++.so.* -exec ls -l {} \;
lrwxrwxrwx 1 root root 23 déc 1 11:03 /usr/lib/libstdc++.so.5 ->
/usr/lib/libstdc++.so.6
lrwxrwxrwx 1 root root 18 nov 30 23:34 /usr/lib/libstdc++.so.6 ->
libstdc++.so.6.0.3
-rwxr-xr-x 1 root root 811744 oct 26 10:48 /usr/lib/libstdc++.so.6.0.3
But I still have the same eror as at the beginning
Any idea please
Thanks
19 years, 6 months
RE: FC3 SMP builds do NOT contain ext3 drivers in the build!!!!
by Fred Skrotzki
well none of mine match.
ll initrd*smp*
-rw-r--r-- 1 root root 496401 Dec 1 16:22 initrd-2.6.9-1.667smp.img
-rw-r--r-- 1 root root 494295 Dec 2 12:37 initrd-2.6.9-1.681_FC3smp.img
md5sum initrd*smp*
8423d673cc5cd6172bdc4ac793c2cf99 initrd-2.6.9-1.667smp.img
a4fcf890e395fa4bf0d85c8c933dc7b2 initrd-2.6.9-1.681_FC3smp.img
Yours look to not be compressed based on the size.
-----Original Message-----
From: fedora-list-bounces(a)redhat.com
[mailto:fedora-list-bounces@redhat.com]On Behalf Of Terry Polzin
Sent: Thursday, December 02, 2004 2:35 PM
To: For users of Fedora Core releases
Subject: Re: FC3 SMP builds do NOT contain ext3 drivers in the build!!!!
On Thursday 02 December 2004 14:22, William Hooper wrote:
> Fred Skrotzki said:
> > I've even run up2date and using the latest 2.6.9-1.681_FC3 it still
> > panics when booting. Thanks to the lack of ext3 drivers being built in.
>
> Ext3 has never been built in. The module is loaded as part of the initrd.
You do have a point here that I also tried to make, if the initrd is bad the
mods aren't going to load right. Here's the sizes and md5sums of my initrd
files.
ll initrd*smp*
-rw-r--r-- 1 root root 1065392 Nov 15 08:36 initrd-2.6.9-1.667smp.img
-rw-r--r-- 1 root root 1065514 Nov 17 13:03 initrd-2.6.9-1.678_FC3smp.img
-rw-r--r-- 1 root root 1064459 Nov 22 08:19 initrd-2.6.9-1.681_FC3smp.img
md5sum initrd*smp*
63e5a7024d015fe15ffefb9806102589 initrd-2.6.9-1.667smp.img
fbcd978df7311bd866fb3ec27e22761f initrd-2.6.9-1.678_FC3smp.img
ebe0beb1e8e48030db035f3f74d80aad initrd-2.6.9-1.681_FC3smp.img
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
19 years, 6 months
RE: FC3 SMP builds do NOT contain ext3 drivers in the build!!!!
by Fred Skrotzki
they look like they are being built at install time.
-----Original Message-----
From: fedora-list-bounces(a)redhat.com
[mailto:fedora-list-bounces@redhat.com]On Behalf Of Robin Bowes
Sent: Thursday, December 02, 2004 2:51 PM
To: fedora-list(a)redhat.com
Subject: Re: FC3 SMP builds do NOT contain ext3 drivers in the build!!!!
Fred Skrotzki wrote:
> well none of mine match.
> ll initrd*smp*
> -rw-r--r-- 1 root root 496401 Dec 1 16:22 initrd-2.6.9-1.667smp.img
> -rw-r--r-- 1 root root 494295 Dec 2 12:37 initrd-2.6.9-1.681_FC3smp.img
>
> md5sum initrd*smp*
> 8423d673cc5cd6172bdc4ac793c2cf99 initrd-2.6.9-1.667smp.img
> a4fcf890e395fa4bf0d85c8c933dc7b2 initrd-2.6.9-1.681_FC3smp.img
>
> Yours look to not be compressed based on the size.
Mine look like this:
[root@dude boot]# ls -l init*smp*
-rw-r--r-- 1 root root 439802 Dec 1 14:49 initrd-2.6.9-1.667smp.img
-rw-r--r-- 1 root root 439861 Dec 1 15:33 initrd-2.6.9-1.681_FC3smp.img
[root@dude boot]# md5sum init*smp*
86061cc6c2de5eb38f4ec9da0c01990b initrd-2.6.9-1.667smp.img
2e84fb3a5c0bc28983c2c27d10ca5817 initrd-2.6.9-1.681_FC3smp.img
Should these be the same or are they build dynamically at install time?
R.
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
19 years, 6 months
RE: FC3 SMP builds do NOT contain ext3 drivers in the build!!!!
by Fred Skrotzki
-----Original Message-----
From: fedora-list-bounces(a)redhat.com
[mailto:fedora-list-bounces@redhat.com]On Behalf Of Terry Polzin
Sent: Thursday, December 02, 2004 2:27 PM
To: For users of Fedora Core releases
Subject: Re: FC3 SMP builds do NOT contain ext3 drivers in the build!!!!
On Thursday 02 December 2004 14:14, Fred Skrotzki wrote:
> # grub.conf generated by anaconda
> #
> # Note that you do not have to rerun grub after making changes to this file
> # NOTICE: You have a /boot partition. This means that
> # all kernel and initrd paths are relative to /boot/, eg.
> # root (hd0,0)
> # kernel /vmlinuz-version ro root=/dev/sda2
> # initrd /initrd-version.img
> #boot=/dev/sda
> default=1
> timeout=5
> splashimage=(hd0,0)/grub/splash.xpm.gz
> hiddenmenu
> title Fedora Core (2.6.9-1.681_FC3)
> root (hd0,0)
> kernel /vmlinuz-2.6.9-1.681_FC3 ro root=LABEL=/1
> initrd /initrd-2.6.9-1.681_FC3.img
> title Fedora Core (2.6.9-1.681_FC3smp)
> root (hd0,0)
> kernel /vmlinuz-2.6.9-1.681_FC3smp ro root=LABEL=/1
> initrd /initrd-2.6.9-1.681_FC3smp.img
> title Fedora Core (2.6.9-1.667smp)
> root (hd0,0)
> kernel /vmlinuz-2.6.9-1.667smp ro root=LABEL=/1
> initrd /initrd-2.6.9-1.667smp.img
> title Fedora Core-up (2.6.9-1.667)
> root (hd0,0)
> kernel /vmlinuz-2.6.9-1.667 ro root=LABEL=/1
> initrd /initrd-2.6.9-1.667.img
>
> -----Original Message-----
> From: fedora-list-bounces(a)redhat.com
> [mailto:fedora-list-bounces@redhat.com]On Behalf Of Terry Polzin
> Sent: Thursday, December 02, 2004 2:07 PM
> To: For users of Fedora Core releases
> Subject: Re: FC3 SMP builds do NOT contain ext3 drivers in the build!!!!
>
> On Thursday 02 December 2004 14:02, Fred Skrotzki wrote:
> > Drive was low level formatted and verified before and after 3 builds. It
> > boots and works fine under single proc. I even build it on another drive
> > just to be sure.
> >
> > BOX is a full blown server class system. hot swap drives, etc...
> > HP LP2000r dual 1.0 Ghz P4
> > 1 gig ram
> >
> > here is the drive config
> > Device Boot Start End Blocks Id System
> > /dev/sda1 * 1 13 104391 83 Linux
> > /boot ext3 /dev/sda2 14 1548 12329887+ 83 Linux
> > / ext3 /dev/sda3 1549 1809 2096482+ 82 Linux
> > swap swap /dev/sda4 1810 4427 21029085 5
> > Extended
> > /dev/sda5 1810 2070 2096451 83 Linux
> > /var/log ext3
> >
> > fstab
> > LABEL=/1 / ext3 defaults 1
> > 1 LABEL=/boot /boot ext3 defaults
> > 1 2 none /dev/pts devpts
> > gid=5,mode=620 0 0 none /dev/shm tmpfs
> > defaults 0 0 none /proc
> > proc defaults 0 0 none /sys
> > sysfs defaults 0 0 LABEL=/var/log1 /var/log
> > ext3 defaults 1 2 LABEL=SWAP-sda3 swap
> > swap defaults 0 0
> >
> > Here is what is left on the screen when booting using SMP:
> >
> > ext3: unknown symbol journal_get_write_access
> > ext3: unknown symbol journal_undo_access
> > ext3: unknown symbol journal_create_access
> > ext3: unknown symbol journal_destroy
> > ext3: unknown symbol journal_clear_error
> > ext3: unknown symbol journal_stop
> > ext3: unknown symbol journal_init_inode
> > ext3: unknown symbol journal_start
> > ext3: unknown symbol log_wait_command
> > ext3: unknown symbol journal_release_buffer
> > ext3: unknown symbol journal_check_available_features
> > ext3: unknown symbol journal_abort
> > ext3: unknown symbol journal_restart
> > insmod: error inserting '/lib/ext2.ko": -1 unknown symbol in module
> > ERROR: /sbin/udevstart exited abnormally
> > creating root drive
> > umount /sys failed: 16
> > Mounting root file system
> > mount: error 19 mounting ext3
> > mount: error 2 mounting none
> > switching to new root
> > switchroot: mount failed: 22
> > umount /initrd/dev failed: 2
> > Kernel panic - not syncing......
>
> Would you send on a copy of your grub.conf.
Like Ed Wilts suggested, doctor the fs tab and make the root partition ext2
and boot smp. Sounds like the journal is hosed.
I did and got the same results and exact same errors attempting SMP kernel (Yep changed ext3 to ext2 in all three lines in fstab). but boots fine in Single be it doctored as ext2 or set back to ext3.
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
19 years, 6 months
FC3 SMP builds do NOT contain ext3 drivers in the build!!!!
by Fred Skrotzki
I've even run up2date and using the latest 2.6.9-1.681_FC3 it still panics when booting. Thanks to the lack of ext3 drivers being built in.
Not the greatest distro. If you are lazy, in a hurry and let it automatically configure the drive(s)for you, it of course defaults to ext3. Which then makes your build in FC3 under SMP USELESS..
Or does somebody have it working and know a trick to get around this. I can of course select the non SMP build and it boots fine but then I'm wasting the second processor which we need.
-----Original Message-----
From: fedora-list-bounces(a)redhat.com
[mailto:fedora-list-bounces@redhat.com]On Behalf Of Fred Skrotzki
Sent: Wednesday, December 01, 2004 5:49 PM
To: fedora-list(a)redhat.com
Subject: FC3 ext3 and SMP kernel errors.
Hardware: HP Lp2000r dual 1.0 Ghz procs, 1 Gig ram, Single 36 gig drive.
I just built a clean install (for the third time to be sure) on the above hardware. (FC2 runs perfectly on identical hardware).
Can anybody confirm this?
I'm going to rebuild again using ext2 to get by this problem.
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
19 years, 6 months
RE: FC3 SMP builds do NOT contain ext3 drivers in the build!!!!
by Fred Skrotzki
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda2
# initrd /initrd-version.img
#boot=/dev/sda
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.9-1.681_FC3)
root (hd0,0)
kernel /vmlinuz-2.6.9-1.681_FC3 ro root=LABEL=/1
initrd /initrd-2.6.9-1.681_FC3.img
title Fedora Core (2.6.9-1.681_FC3smp)
root (hd0,0)
kernel /vmlinuz-2.6.9-1.681_FC3smp ro root=LABEL=/1
initrd /initrd-2.6.9-1.681_FC3smp.img
title Fedora Core (2.6.9-1.667smp)
root (hd0,0)
kernel /vmlinuz-2.6.9-1.667smp ro root=LABEL=/1
initrd /initrd-2.6.9-1.667smp.img
title Fedora Core-up (2.6.9-1.667)
root (hd0,0)
kernel /vmlinuz-2.6.9-1.667 ro root=LABEL=/1
initrd /initrd-2.6.9-1.667.img
-----Original Message-----
From: fedora-list-bounces(a)redhat.com
[mailto:fedora-list-bounces@redhat.com]On Behalf Of Terry Polzin
Sent: Thursday, December 02, 2004 2:07 PM
To: For users of Fedora Core releases
Subject: Re: FC3 SMP builds do NOT contain ext3 drivers in the build!!!!
On Thursday 02 December 2004 14:02, Fred Skrotzki wrote:
> Drive was low level formatted and verified before and after 3 builds. It
> boots and works fine under single proc. I even build it on another drive
> just to be sure.
>
> BOX is a full blown server class system. hot swap drives, etc...
> HP LP2000r dual 1.0 Ghz P4
> 1 gig ram
>
> here is the drive config
> Device Boot Start End Blocks Id System
> /dev/sda1 * 1 13 104391 83 Linux /boot
> ext3 /dev/sda2 14 1548 12329887+ 83 Linux /
> ext3 /dev/sda3 1549 1809 2096482+ 82 Linux
> swap swap /dev/sda4 1810 4427 21029085 5
> Extended
> /dev/sda5 1810 2070 2096451 83 Linux
> /var/log ext3
>
> fstab
> LABEL=/1 / ext3 defaults 1 1
> LABEL=/boot /boot ext3 defaults 1 2
> none /dev/pts devpts gid=5,mode=620 0 0
> none /dev/shm tmpfs defaults 0 0
> none /proc proc defaults 0 0
> none /sys sysfs defaults 0 0
> LABEL=/var/log1 /var/log ext3 defaults 1 2
> LABEL=SWAP-sda3 swap swap defaults 0 0
>
> Here is what is left on the screen when booting using SMP:
>
> ext3: unknown symbol journal_get_write_access
> ext3: unknown symbol journal_undo_access
> ext3: unknown symbol journal_create_access
> ext3: unknown symbol journal_destroy
> ext3: unknown symbol journal_clear_error
> ext3: unknown symbol journal_stop
> ext3: unknown symbol journal_init_inode
> ext3: unknown symbol journal_start
> ext3: unknown symbol log_wait_command
> ext3: unknown symbol journal_release_buffer
> ext3: unknown symbol journal_check_available_features
> ext3: unknown symbol journal_abort
> ext3: unknown symbol journal_restart
> insmod: error inserting '/lib/ext2.ko": -1 unknown symbol in module
> ERROR: /sbin/udevstart exited abnormally
> creating root drive
> umount /sys failed: 16
> Mounting root file system
> mount: error 19 mounting ext3
> mount: error 2 mounting none
> switching to new root
> switchroot: mount failed: 22
> umount /initrd/dev failed: 2
> Kernel panic - not syncing......
Would you send on a copy of your grub.conf.
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
19 years, 6 months
"yum update" won't work
by Trevor Smith
I keep trying to run "yum update" and I get this problem:
Resolving dependencies
.Package newpg needs libksba.so.0, this is not available.
OK, I have newpg installed and I have libksba installed:
[root@laptop trevor]# rpm -q newpg
newpg-0.9.4-0.fdr.2.2
[root@laptop trevor]# rpm -q libksba
libksba-0.4.7-0.fdr.1.2
So what is the problem that yum is having and what can I do to fix it?
--
Trevor Smith // trevor(a)haligonian.com
19 years, 6 months
FC3: kernel panic on first boot
by Robin Bowes
Hi,
First some system details:
Epox EP-D3VA motherboard
dual 1Ghz PIII processors
1.5GB RAM
2 x Promise SATA150 TX4 controllers
6 x Maxtor Maxline II 250GB SATA HDDs (3 per controller)
The drives are all partitioned identically with two partitions: 1.5GB +
248.5GB. The partitions are configured in raid arrays as follows:
/dev/md0: /dev/sd[ad]1 / (root filesystem)
/dev/md1: /dev/sd[be]1 swap
/dev/md2: /dev/sd[cf]1 swap
/dev/md5: /dev/sd[abcdef]2 lvm2 volume
/home, /usr, and /var are mounted as lvm2 logical volumnes on the
/dev/md5 array.
I was running FC2. I then decided to upgrade to FC3.
I booted from the DVD (the media check completed OK) and went through
the system upgrade.
All seemed to go well and I rebooted.
However, the boot process halted with the following message:
Loading ext3.ko module
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Creating root device
Mounting root filesystem
EXT3-fs: unable to read superblock
mount: error 22 mounting ext3
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
This is with the default 2.6.9-1.667smp kernel.
I booted into rescue mode and chrooted into the upgraded system - all
seems fine, i.e. all the filesystems are OK.
I then upgraded all the packages using "yum upgrade" within the chroot
environment. This installed kernel-2.6.9-1.681_FC3smp.
I rebooted and got the same error as above. I also tried "downgrading"
to a 2.6.8 kernel but got the same error.
Am I hitting the known bug [1] with SATA drives in the 2.6.9 kernel ? Or
is this some other problem?
[1] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140367
Can anyone shed any light on this problem?
Thanks,
R.
--
http://robinbowes.com
19 years, 6 months
is it a bug that glibc won't build with gcc4?
by Robert P. J. Day
given that FC3 ships with a preview gcc4, should it be considered a
bug that glibc-2.3.3 can't be configured with that compiler? the
relevant excerpt from glibc-2.3.3/configure:
ac_prog_version=`$CC -v 2>&1 | sed -n 's/^.*version
\([egcygnustpi-]*[0-9.]*\).*$/\1/p'`
case $ac_prog_version in
'') ac_prog_version="v. ?.??, bad"; ac_verc_fail=yes;;
3.[2-9]*)
ac_prog_version="$ac_prog_version, ok"; ac_verc_fail=no;;
*) ac_prog_version="$ac_prog_version, bad"; ac_verc_fail=yes;;
esac
in short, if it ain't 3.2.x -> 3.9.x, glibc configure fails. bug?
feature? safeguard?
rday
19 years, 6 months