Hi,
I am getting a "Cannot find compiler message" from a configure script
yet I know gcc ( I know as it wasn't by default and I had to install
it later) is there -- how can I tell the script where it is.
THis seems to be the relevant part of the script.
Many TIA
F
#
# $CXX
#
$echo 'Checking C++ compiler... \c';
cat <<EOF >$tmp_file.C;
#include
On Thursday 05 September 2002 17:18, Francesco Scaglioni wrote:
Hi,
I am getting a "Cannot find compiler message" from a configure script yet I know gcc ( I know as it wasn't by default and I had to install it later) is there -- how can I tell the script where it is. THis seems to be the relevant part of the script.
It is the relevant part of the configure script, but what you should be looking at is config.log that should have been created in the source directory. That will give you the actual compilation error that caused teh configure script to deduce that the compiler wasn't working. As a rough guess I'd say you've installed gcc, which is the gnu C compiler. The package gpp has the C++ compiler. But only the config.log file will say for certain. //Anders
Thanks -- no config.log was created but when get a chance I shall install the gpp package and try again. THanks again Francesco
Francesco Scaglioni
Thanks -- no config.log was created but when get a chance I shall install the gpp package and try again.
Just remember that libgpp (or was it gpplib?) is also needed. Philipp -- Philipp Thomas work: pthomas@suse.de Development SuSE Linux AG private: pth@t-link.de
Greetings from New York City! I recently removed a hard drive and now I can't get SuSE Linux 8.0 to boot from the Windows 2000 Boot Manager. I've changed hardware before and successfully copied the first 512 bytes of the Linux bootsector to the W2K partition, so I could add the correct entry to Windows' boot.ini file. But this time, all I get is lot of "01"s when I select the SuSE boot option from Windows 2000. If I boot from the SuSE DVD I can boot my existing Linux partition (from the installation routine, not the "Boot installed OS" from that boot menu). My hardware is a DPT 3865 SCSI controller connected to a Seagate Cheetah disk that boots Windows 2000. SuSE Linux 8.0 is installed on an 18GB UDMA IDE drive connected to an on-motherboard ATA-100 controller, with the system BIOS set to boot SCSI first. The motherboard is an Asus A7V-133 with an Athlon 1200 CPU and 512MB RAM. The Linux drive is identified as /dev/hde and there are two partitions: hde1 is a 1GB swap; hde2 is a17GB ReiserFS native partition. LILO is installed on hde2. I had a second 8GB SCSI hard drive (one big extended partion formatted FAT32 for swapping files between W2K and Linux), but the drive was getting noisy and running way too hot, so I figured it was best to remove it before it died and took some data with it. After removing the dying drive Linux would no longer boot from the W2K boot loader, so I booted from the SuSE DVD, booted my installed Linux system, logged in as root, removed the mount point for the missing drive from fstab, ran /sbin/lilo, then did the "dd..." trick to get the first 512bytes from the Linux boot sector into a file (after running df to make sure I was hitting the right partition). I ftp'd the file to a temporary place, booted W2K, downloaded the boot sector file from the ftp site, modified boot.ini and rebooted. And that's when I get nothing but a screenful of "01 01 01 01..." FWIW, hde2 is marked as Active (Bootable) with fdisk. I looked around the SuSE KB web site, read the Docs on my Linux drive, but I can't see what I've done wrong--which means it's probabaly something simple and stupid! Any ideas? Thanks! -- __________________________________________________________ Another Message From... L. Mark Stone Email: LMStone@LMStone.com Web: http://www.lmstone.com
The only time I ever saw that happen, was on an old Comcrap, err compaq, deskpro. It was caused by the bios being software, rather then a hardware chip. Apparently, I put LILO in the MBR (like I always do), but becuase the bios was in the first sectors of the harddrive, LILO overwrote the bios info. To fix this, I had to go to compaq website and d/l the bios utility and install that, then reinstall Linux, and put LILO on floppy. : -----Original Message----- : From: L. Mark Stone [mailto:LMStone@LMStone.com] : Sent: Sunday, September 15, 2002 9:54 PM : To: suse-linux-e@suse.com : Subject: [SLE] LILO Dual Boot Error 01 01 01 01... : : : : Greetings from New York City! : : I recently removed a hard drive and now I can't get SuSE Linux 8.0 to : boot from the Windows 2000 Boot Manager. : : I've changed hardware before and successfully copied the first 512 bytes : of the Linux bootsector to the W2K partition, so I could add the : correct entry to Windows' boot.ini file. But this time, all I get is : lot of "01"s when I select the SuSE boot option from Windows 2000. : : If I boot from the SuSE DVD I can boot my existing Linux partition (from : the installation routine, not the "Boot installed OS" from that boot : menu). : : My hardware is a DPT 3865 SCSI controller connected to a Seagate Cheetah : disk that boots Windows 2000. SuSE Linux 8.0 is installed on an 18GB : UDMA IDE drive connected to an on-motherboard ATA-100 controller, with : the system BIOS set to boot SCSI first. The motherboard is an Asus : A7V-133 with an Athlon 1200 CPU and 512MB RAM. : : The Linux drive is identified as /dev/hde and there are two partitions: : hde1 is a 1GB swap; hde2 is a17GB ReiserFS native partition. LILO is : installed on hde2. : : I had a second 8GB SCSI hard drive (one big extended partion formatted : FAT32 for swapping files between W2K and Linux), but the drive was : getting noisy and running way too hot, so I figured it was best to : remove it before it died and took some data with it. : : After removing the dying drive Linux would no longer boot from the W2K : boot loader, so I booted from the SuSE DVD, booted my installed Linux : system, logged in as root, removed the mount point for the missing : drive from fstab, ran /sbin/lilo, then did the "dd..." trick to get the : first 512bytes from the Linux boot sector into a file (after running df : to make sure I was hitting the right partition). I ftp'd the file to a : temporary place, booted W2K, downloaded the boot sector file from the : ftp site, modified boot.ini and rebooted. : : And that's when I get nothing but a screenful of "01 01 01 01..." : : FWIW, hde2 is marked as Active (Bootable) with fdisk. : : I looked around the SuSE KB web site, read the Docs on my Linux drive, : but I can't see what I've done wrong--which means it's probabaly : something simple and stupid! : : Any ideas? : : Thanks! : : -- : : __________________________________________________________ : Another Message From... L. Mark Stone : : Email: LMStone@LMStone.com : Web: http://www.lmstone.com : : : : -- : Check the headers for your unsubscription address : For additional commands send e-mail to suse-linux-e-help@suse.com : Also check the archives at http://lists.suse.com : Please read the FAQs: suse-linux-e-faq@suse.com : :
"L. Mark Stone" schrieb:
And that's when I get nothing but a screenful of "01 01 01 01..."
FWIW, hde2 is marked as Active (Bootable) with fdisk.
I looked around the SuSE KB web site, read the Docs on my Linux drive, but I can't see what I've done wrong--which means it's probabaly something simple and stupid!
Any ideas?
Thanks!
Look into BIOS for the section on HD adressing. LBA/CHS? -- *º¤.,___,.¤º*¨¨¨*¤ =Oliver@home= *º¤.,¸¸¸,.¤º*¨¨*¤ I / __|__ http://www.bmw-roadster.de/Friends/Olli/olli.html I I / / |_/ http://www.bmw-roadster.de/Friends/friends.html I I \ \__|_\ http://groups.yahoo.com/group/VGAP-93 I I \___| mailto:VGAP-93-subscribe@yahoogroups.com I
Telek0ma iBBMS - moving house, but online! +49....TRSi1 <<<
Oliver Ob wrote:
"L. Mark Stone" schrieb:
And that's when I get nothing but a screenful of "01 01 01 01..."
Any ideas?
Thanks!
Look into BIOS for the section on HD adressing. LBA/CHS?
I am a little puzzled at the responses to this post. All the replies are talking about bios but it seems that the problem is elsewhere. The original poster said that he just removed a drive which means that the remaining drives already worked with his bios. The problem is that devices change. To fix this problem, one will have to boot the rescue system and tamper with /etc/lilo.conf and /etc/fstab to show the new devices. I have had to do this before and this procedure has worked for me. Damon Register
Damon Register schrieb:
Oliver Ob wrote:
"L. Mark Stone" schrieb:
And that's when I get nothing but a screenful of "01 01 01 01..."
Any ideas?
Thanks!
Look into BIOS for the section on HD adressing. LBA/CHS?
I am a little puzzled at the responses to this post. All the replies are talking about bios but it seems that the problem is elsewhere. The original poster said that he just removed a drive which means that the remaining drives already worked with his bios. The problem is that devices change. To fix this problem, one will have to boot the rescue system and tamper with /etc/lilo.conf and /etc/fstab to show the new devices. I have had to do this before and this procedure has worked for me.
Damon Register
Absolutely NOT, the problem is HOW the bios addresses its boot device ! Either LBA or CHS - fiddle with it and you will see. I solved it that way! -- *º¤.,___,.¤º*¨¨¨*¤ =Oliver@home= *º¤.,¸¸¸,.¤º*¨¨*¤ I / __|__ http://www.bmw-roadster.de/Friends/Olli/olli.html I I / / |_/ http://www.bmw-roadster.de/Friends/friends.html I I \ \__|_\ http://groups.yahoo.com/group/VGAP-93 I I \___| mailto:VGAP-93-subscribe@yahoogroups.com I
Telek0ma iBBMS - moving house, but online! +49....TRSi1 <<<
Oliver Ob wrote:
Absolutely NOT, the problem is HOW the bios addresses its boot device ! Either LBA or CHS - fiddle with it and you will see. Perhaps I am a little slow but could you please explain how this issue applies to a secondary, data only drive that was removed? Didn't the original poster say that the 2 devices containing W2K and SuSE were still the same?
Damon Register
I also had this problem, and I noticed afterwards that tools like fdisk saw partition sizes of over 800 GIG's (the size is 27 GB). Is there any remedy for this problem? Seems that the partition table is corrupted or something like that. Regards, Marco Teeuwen On Tue, Sep 17, 2002 at 09:11:38PM +0200, Oliver Ob wrote:
Absolutely NOT, the problem is HOW the bios addresses its boot device ! Either LBA or CHS - fiddle with it and you will see.
I solved it that way!
Damon, I'm the original poster and I agree with you that removing a non-bootable device shouldn't have caused this problem, as long as I cleaned up fstab (which I did) and reinstalled LILO exactly where it was before. It's baffling for sure! Especially when the SuSE DVD can boot the installed system just fine! But I took the BFI way out (Brute Force and Ignorance) and just reinstalled Linux. But this time, I created a small /boot partition, well within the first 1024 cylinders and installed LILO there. On Tuesday, September 17, 2002 11:48 am, Damon Register wrote:
Oliver Ob wrote:
"L. Mark Stone" schrieb:
And that's when I get nothing but a screenful of "01 01 01 01..."
Any ideas?
Thanks!
Look into BIOS for the section on HD adressing. LBA/CHS?
I am a little puzzled at the responses to this post. All the replies are talking about bios but it seems that the problem is elsewhere. The original poster said that he just removed a drive which means that the remaining drives already worked with his bios. The problem is that devices change. To fix this problem, one will have to boot the rescue system and tamper with /etc/lilo.conf and /etc/fstab to show the new devices. I have had to do this before and this procedure has worked for me.
Damon Register
-- _________________________________________________________ Another Message From... L. Mark Stone Email: LMStone@LMStone.com Web: http://www.lmstone.com
"L. Mark Stone" wrote:
Damon,
I'm the original poster and I agree with you that removing a non-bootable device then I am convinced that Oliver is wrong. Though he maybe right about
shouldn't have caused this problem, as long as I cleaned up fstab (which I did) and reinstalled LILO exactly where it was before. but did you edit lilo.conf? You almost certainly will have to edit
what he said, you confirmed that it was not a boot device that was removed. What does LBA or CHS have to do with this if the booting device never changed. lilo.conf to shuffle the devices there. Did you change the disk= section in lilo.conf? Because you removed a drive, the other drives that were after it will have a different bios number.
But I took the BFI way out (Brute Force and Ignorance) and just reinstalled Linux. Too bad. Now I will never know if what I am thinking is correct. I have exactly (almost) the same situation here. In my case the second scsi drive is an HP optical drive.
Damon Register
participants (8)
-
Anders Johansson -
Damon Register -
Francesco Scaglioni -
Jeric -
L. Mark Stone -
Marco Teeuwen -
Oliver Ob -
Philipp Thomas