installation of gcc failing, make error 2 and libstdc++ tests failing...

RetroGamerCX · 07-07-2022, 06:32 PM

hi, this is probably my last attempt on making an lfs, because i have come this far just to get errors: after not just one, but all of the libstdc++ tests failed, make gave error 2 on the makefile at line 2391. the last command i ran was copy and pasted from the book:
"su tester -c "PATH=$PATH make -k check".
i'm pretty sure there were no errors before running the command, and i dunno what the cause of this error is at all.

RetroGamerCX · 07-07-2022, 06:39 PM

well, i just read that it's known to the libstdc++ tests to fail, but i don't think the make is known to fail as well. i can't guess anything because i need further clarification about error 2.

RetroGamerCX · 07-07-2022, 08:14 PM

i'm so confused right now... after reading better my terminal, i saw that the error 2 came from libatomic, but libatomic isn't mentioned on the build log mentioned on the book...

derguteweka · 07-08-2022, 08:34 AM

Moin,

I'd try to proceed. Either it's just on of the usually failing tests or - if it's a real problem with your installation - you'll face it pretty soon again...

cheers,
WK

RetroGamerCX · 07-08-2022, 10:38 AM

Quote:

Originally Posted by derguteweka

Moin,

I'd try to proceed. Either it's just on of the usually failing tests or - if it's a real problem with your installation - you'll face it pretty soon again...

cheers,
WK

is make check that important, then?

hazel · 07-08-2022, 11:10 AM

Quote:

Originally Posted by RetroGamerCX

is make check that important, then?

Depends on the package. It's considered essential for binutils, glibc, gcc and its three internal libraries, and libstdc++. Not so much for the rest of the installation. And no tests at all should be run on the intermediate toolset, only on the final products.

But in any case the make error shows that something has gone badly wrong. No LFS build should break like that.

RetroGamerCX · 07-08-2022, 12:09 PM

yeah, do you know what causes error 2 on make?

derguteweka · 07-09-2022, 01:06 PM

Moin,

Quote:

Originally Posted by RetroGamerCX

is make check that important, then?

Yeah, on the one hand, it's important to give you a good feeling, if it tests ok.
On the other hand, if tests fail, and you have no idea why they fail, i'd just give it a try and ignore the failing tests.
You've nothing to lose. If anything is seriously wrong with your fresh compiler, you'll recognise it very soon. And if the tests failed for no serious reason, you're able to proceed.
Imho, proceeding doesn't harm or destroy anything valuable.

cheers,
WK

Keith Hedger · 07-11-2022, 06:47 AM

been building lfs for years I have NEVER run tests on libstdc++, but always run the sanity checks to make sure you are compiling and linking correctly, about half way down this page:
https://www.linuxfromscratch.org/lfs...ter08/gcc.html

Code:

echo 'int main(){}' > dummy.c
cc dummy.c -v -Wl,--verbose &> dummy.log
readelf -l a.out | grep ': /lib'

xlfs-0.2 · 11-23-2022, 02:35 AM

[QUOTE=RetroGamerCX;6366317]hi, this is probably my last attempt on making an lfs, because i have come this far just to get errors

I made a small LFS which has 0% build errors. It can run ff99 w/video sound (PC intelHD sound nvidia). but it's not "suited for laptops" and global distribution of all hardwares.

It is possible to build linux from scratch usably 0% failure. Somone told me "the point is learning if a script does it what is learned?"

Totally Built Linux Distro

https://sourceforge.net/projects/tot...t-linux-distro

xlfs-0.2 · 11-23-2022, 02:38 AM

You haven't posted the error for us to see!

Over like 250+ packages I build i GUARANTEE YOU most README admit that some tests will always fail.

You should do you own c++ test by compiling c++ programs and running them.

And for us: tell us what test fails don't be so vague. That's almost spam it's so vague.

hazel · 11-23-2022, 04:24 AM

When I first started building LFS, I religiously tested everything. Now I only test where the Book says you definitely must. And even if you do test everything, one or two test failures in a package don't count. A lot of failures in an essential build package do.

@Keith: surely you run tests on your final gcc, and that includes libstdc++. I agree that it's not worth testing the temporary libstdc++ that you build for your toolkit.

Keith Hedger · 11-23-2022, 07:20 AM

Hazel - Nope just the sanity test, I script it all so rarely have typos, did the full checks a couple of times on my 1st few builds, but never bothered since, never had a problem.

RetroGamerCX · 12-19-2022, 06:43 AM

hi, i'm back after 200 years to say i finally went ahead on my lfs, i ignored the errors as you guys told me to, and now i'm almost done! what happens now is that every time i boot my lfs, grub says:
"could not find a suitable video mode
Booting in blind mode
_"
then 1 second later, vmware says that the guest halted the cpu, and tells me to power off the vm. i think i have to make a different thread about this issue.

xlfs-0.2 · 12-26-2022, 12:21 AM

Nice.

Are you running lfs linux in a linux ubuntu VM host? In win11 VM host? Is that what is going on?

Did you enable linux kernel LVM support when you built the kernel? (specifically kvm video obvious)

Did you check your host VM's video options?

Did a GRUB BOOT menu come up? Is your VM a bootable grub image on GPT? Or are you using somekinda virtual system where GRUB isn't used?