Re: [lfs-support] GCC build first pass: mpc build looks for libgmp.la in the wrong place
On Thu, 05 Dec 2013 18:08:56 +
lf...@cruziero.com (akhiezer) wrote:
Sanity-checks:
---
* your host-os (Slackware 14.0) is 64-bit (what does 'uname -a' show)?
x86_64 as expected.
* _prior_ to your creation of the symlink that you note below, did
'/usr/lib64/libgmp.la' exist in the host-os?
No, it doesn't, though /usr/lib/libmpfr.la does.
* you mention in a later post, that it is a customised version of the
host-os. At the time of getting the compile-fail below, did you have
any of mpfr, mpc, gmp installed in the host-os? What do you get from:
$ ls
-latrF /var/log/{packages,{removed_,}scripts}/{gmp,libmpc,mpfr}*
-rw-r--r-- 1 root root 986 Jul 4 16:41 packages/libmpc-0.8.2-x86_64-2
-rw-r--r-- 1 root root 1532 Jul 4 16:42 packages/mpfr-3.1.0-x86_64-1
-rwxr-xr-x 1 root root 180 Jul 4 16:41 scripts/libmpc-0.8.2-x86_64-2*
-rwxr-xr-x 1 root root 186 Jul 4 16:42 scripts/mpfr-3.1.0-x86_64-1*
Nothing was found in any of the removed_ directories because I
haven't uninstalled any libraries.
* did you ever have any of mpfr, mpc, gmp installed in the host-os,
and then uninstalled/moved/changed them at all; if so, by what
methods?
Once I had enough software installed to make the package management
system work, I used it exclusively. But I clearly don't have libgmp
installed. This was very much an educational project and my policy was
to install only:
a) programs I knew I wanted
b) libraries, etc. that installed programs wouldn't work without.
* At the time of the build below, what was LD_LIBRARY_PATH ?
There wasn't one. I was working as the lfs user, strictly by the book,
and checked my environment periodically to ensure that it didn't include
anything but the specified variables.
In the book it says that these libraries may not be included in your
host distribution, so why did it make a difference in my case?
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] LFS 7.4 / 6.9 - Glibc - how to tell if error messages are benign or critical?
root:/sources/glibc-build# grep Error glibc-check-log make[2]: *** [/sources/glibc-build/math/ test-float.out] Error 1 make[2]: *** [/sources/glibc-build/math/test-ldouble.out] Error 1 make[2]: *** [/sources/glibc-build/math/test-ildoubl.out] Error 1 make[2]: *** [/sources/glibc-build/math/test-ifloat.out] Error 1 I would want to dig into the tests to see what is failing. They all look related and my first reaction is that there are hardware issues, but I haven't seen these particular errors before. Thanks for your reply, Bruce. Is there any way for a relatively novice user like myself to better determine what these errors are before continuing, as you suggested? I suppose the only other route for me to take is to forge ahead and hope for the best. As mentioned before, it's a relatively older system (Athlon XP 3200+) which doesn't have SSE2 or other newer instruction extensions. Could that be the cause of the errors? Any advice or suggestions are welcome. Thanks. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS 7.4 / 6.9 - Glibc - how to tell if error messages are benign or critical?
frozen tuesday wrote: root:/sources/glibc-build# grep Error glibc-check-log make[2]: *** [/sources/glibc-build/math/ test-float.out] Error 1 make[2]: *** [/sources/glibc-build/math/test-ldouble.out] Error 1 make[2]: *** [/sources/glibc-build/math/test-ildoubl.out] Error 1 make[2]: *** [/sources/glibc-build/math/test-ifloat.out] Error 1 I would want to dig into the tests to see what is failing. They all look related and my first reaction is that there are hardware issues, but I haven't seen these particular errors before. Is there any way for a relatively novice user like myself to better determine what these errors are before continuing, as you suggested? I suppose the only other route for me to take is to forge ahead and hope for the best. Look at the contents of /sources/glibc-build/math/test-*.out. Sometimes tracing the sources through the test suite can be quite challenging. On the other hand, sometimes errors may be indicated by an off-by-one issue in the least significant digit. Unless you are doing really heavy math, that probably is something you can live with. As mentioned before, it's a relatively older system (Athlon XP 3200+) which doesn't have SSE2 or other newer instruction extensions. Could that be the cause of the errors? That's possible, but I'd think it would have been handled in the code. If it should be and isn't, then it does need to be brought up upstream. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] GCC build first pass: mpc build looks for libgmp.la in the wrong place
Date: Thu, 05 Dec 2013 18:08:56 +
From: lf...@cruziero.com (akhiezer)
To: LFS Support List lfs-support@linuxfromscratch.org
Subject: Re: [lfs-support] GCC build first pass: mpc build looks for
libgmp.la in the wrong place
.
.
I have tried two experimental builds. In the first, I used two
additional configuration parameters in the hope that they would tell the
compiler the correct place to look for information on gmp:
--with_gmp_include=$(pwd)/gmp and --with_gmp_lib=$(pwd)/gmp/.libs. But
this did not have any effect on the error.
Just to check: did you use underscores there - i.e. in the above
--with_gmp_include=$(pwd)/gmp and --with_gmp_lib=$(pwd)/gmp/.libs
; or did you use hyphens/dashes thus:
--with-gmp-include=$(pwd)/gmp --with-gmp-lib=$(pwd)/gmp/.libs
?
Hazel, did you have any info on the above query re underscores?
lfs-6.7 and lfs-6.8 both use './configure ...' options:
--with-gmp-include=$(pwd)/gmp --with-gmp-lib=$(pwd)/gmp/.libs
; and they don't use any mpfr/mpc stuff.
And lfs-7.0 thru lfs-7.4 uses (I've replaced the gcc version numbers with the
literal string '${GCC_VERNUM}'):
--with-mpfr-include=$(pwd)/../gcc-${GCC_VERNUM}/mpfr/src \
--with-mpfr-lib=$(pwd)/mpfr/src/.libs
; and they don't use any gmp/mpc stuff.
Had a brief look at trac to see why the switchover at 6.8 - 7.0 , and why
wanting/needing to specify those options to './configure ...' explicitly; but
nothing obvious in the time spent.
Will leave the above remarks here, as likely to return to it.
For the second try, I simply put a symbolic link into /usr/lib64
pointing to /mnt/lfs/sources/gcc-build/gmp/.libs/libgmp.la. Then the
build was successful.
.
.
There are quite a few problems reported over recent years, with folks - one
way or another - having some trouble in getting mpfr/gmp/mpc picked up
properly automatically in the way intended; and often 'needing' to tell
'./configure' explicitly (not always with complete success), or resort to
other measures.
rgds,
akh
--
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
