Re: [lfs-support] GCC build first pass: mpc build looks for libgmp.la in the wrong place
On Mon, 2 Dec 2013 12:01:38 + (UTC) Thomas Kupper wrote: > G'day, > > I was coming across that error while trying to cross compile mpc for > later use with gcc using Optware building system (nothing to do with > LFS I agree). In my case it was mpc which did complain but mpfr was > the one causing it. In the libmpfr.la there was the path > to /opt/lib/libgmp.la (/opt/lib in my case cause of Optware). MPC > seems to look at the libmpfr.la (and libgmp.la) I assume. > > --- --- > ... > # Libraries that this one depends upon. > dependency_libs=' -L opt/lib/libgmp.la' > ... > --- > > I still don't know the source of the problem but I simply did sed the > /opt/lib/*.la out of the libmpfr.la file and mpc and gcc compiled > fine. And I may add that "/opt/lib/libgmp.la" is is not in > 'dependency_libs the libmpfr.la file right after compilation > in ./src/.libs/libmpfr.la and ./src/libmpfr.la. Instead the complete > path to were it really gets copied. It seems to happen during the > "$make install" phase. > > Maybe that a) helps someone else too - as did your post me - and b) > maybe someone with deeper knowledge of libs/libtool and compiling > knows what's the source of the problem is. The method with linking to > - in my case - /opt/lib would be a bit more work since I do cross > compile for i686 and x86_64 bit. > > Additionally, in libmpc.la the two paths to /opt/lib/libgmp.la and > /opt/lib/libmpfr.la appear again but gcc seems not to mind and > compiles fine anyway. > > Below the sed I used, although probaly obvious: > $ sed -i 's%^\(dependency_libs=.*\) \(/opt/lib/.*la\)%/\1%g' \ > > /home/jane/Projects/slug/optware/asustor-i686/staging/opt/lib/libmpfr.la > > System involved: > - Ubuntu 12.04 32-bit, 4 logical CPU's, 4GB RAM (Parallels VM) > - cross compiler : gcc 4.6.3 > - latest Optware and latest GMP,MPFR and MPC > > I was also able to trace the problem back to a bad dependency line in a libtool archive file. But in my case it can't be an install problem because in LFS, you don't actually install these libraries in your /tools tree. You just unpack their sources inside the gcc source directory and let Make build and use them. In the end, after hitting the same wall several times, I just used a redirecting link as no one was prepared to suggest anything better. In the second-pass build of gcc everything went smoothly, so the problem must lie with my host compiler. I have a "home-rolled" minimalist system based on Slackware packages and something is probably missing in my setup. -- 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: Wed, 4 Dec 2013 11:40:23 + > From: Hazel Russman > To: lfs-support@linuxfromscratch.org > Subject: Re: [lfs-support] GCC build first pass: mpc build looks for > libgmp.la in the wrong place > . . > I was also able to trace the problem back to a bad dependency line in a > libtool archive file. But in my case it can't be an install problem What was the bad-dep line? > because in LFS, you don't actually install these libraries in > your /tools tree. You just unpack their sources inside the gcc source > directory and let Make build and use them. In the end, after hitting > the same wall several times, I just used a redirecting link as no one > was prepared to suggest anything better. > > In the second-pass build of gcc everything went smoothly, so the > problem must lie with my host compiler. I have a "home-rolled" > minimalist system based on Slackware packages and something is probably > missing in my setup. > - we've built lfs74 on several machines using full-install Slackware 14.1 here - yes, yours is 14.0 - and no problems at all. Similarly for lfs68/blfs68 built on full-install Slackware 13.37 - all completely OK. But just have never built from 14.0 - no partic reason: I'd expect/wager that a full(er) install - as recommended by PV et al - of 14.0, and not "home-rolled" too much away from its upstream intended function, would go just fine. Anyway, good you got past the roadblock. rgds, akh > > -- > http://linuxfromscratch.org/mailman/listinfo/lfs-support > FAQ: http://www.linuxfromscratch.org/lfs/faq.html > Unsubscribe: See the above information page > -- -- 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
On Wed, 04 Dec 2013 11:57:14 + lf...@cruziero.com (akhiezer) wrote: > > Date: Wed, 4 Dec 2013 11:40:23 + > > From: Hazel Russman > > To: lfs-support@linuxfromscratch.org > > Subject: Re: [lfs-support] GCC build first pass: mpc build looks for > > libgmp.la in the wrong place > > > . > . > > I was also able to trace the problem back to a bad dependency line > > in a libtool archive file. But in my case it can't be an install > > problem > > > What was the bad-dep line? The errant file is gcc-build/mpc/src/libmpc.la, which contains the line: dependency_libs=' /usr/lib64/libmpfr.la /usr/lib64/libgmp.la /mnt/lfs/sources/gcc-build/./gmp/.libs/libgmp.la -lm' There is no other file in either gcc-4.8.1 or gcc-build that contains the string "/usr/lib64" > > - we've built lfs74 on several machines using full-install Slackware > 14.1 here - yes, yours is 14.0 - and no problems at all. Similarly > for lfs68/blfs68 built on full-install Slackware 13.37 - all > completely OK. But just have never built from 14.0 - no partic > reason: I'd expect/wager that a full(er) install - as recommended by > PV et al - of 14.0, and not "home-rolled" too much away from its > upstream intended function, would go just fine. > > > Anyway, good you got past the roadblock. > > > rgds, > > akh > > > > > > -- > > http://linuxfromscratch.org/mailman/listinfo/lfs-support > > FAQ: http://www.linuxfromscratch.org/lfs/faq.html > > Unsubscribe: See the above information page > > > > > -- -- If any members of GCHQ are reading this, shame on you! I fought for your right to belong to a trade union and now you are taking away my right to privacy? H Russman -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Configuring 3.10.10 for quad-core processor
I was slogging through dmesg in my new LFS system and didn't find more than one CPU loaded. I have an AMD-10-5745M processor which has a quad-core. I tried to reconfigure the kernel to support it but it wouldn't boot. Am reverting back to the one I know works. Can anyone suggest the .config settings to enable this in 3.10.10? I've also heard that in addition to enhanced Radeon graphics support, kernel 3.12 has enhanced support for AMD processors, but I can't verify this. When I configured 3.10.10, I set GENERIC_x86_64=y and have been looking for support for this particular processor. Any other knowledge? Thanks, Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Configuring 3.10.10 for quad-core processor
On Dec 4, 2013, at 1:49 PM, Dan McGhee wrote: > AMD-10-5745M Have you used the powernow-k8 driver and have SMP enabled? http://cateee.net/lkddb/web-lkddb/X86_POWERNOW_K8.html Sincerely, WIlliam Harrington -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Configuring 3.10.10 for quad-core processor
On Wed, Dec 04, 2013 at 02:46:47PM -0600, William Harrington wrote: > > On Dec 4, 2013, at 1:49 PM, Dan McGhee wrote: > > > AMD-10-5745M > > Have you used the powernow-k8 driver and have SMP enabled? > > http://cateee.net/lkddb/web-lkddb/X86_POWERNOW_K8.html > > Sincerely, > > WIlliam Harrington Powernow is for cpufreq (a good thing to use, IMHO, but not mentioned in LFS) and not used anymore for K10 and newer CPUs (the support is now in acpi-cpufreq). From memory, the initial K10 was the athlon64xII. My git-foo isn't good enough to identify which release that happened in, but the indications are that it was well before 3.10. SMP is the key. If Dan is building only for that machine (and doesn't intend to use the system to boot any replacement machine when the time comes) then optimizing for the specific processor family, i.e. AMD x86_64 (Opteron/Athlon/Hammer/K8 : this is CONFIG_MK8 but works on K10 ;-) might gain a little, as might Multi-Core Scheduler support. ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Shadow tar file
I noticed that the debian site can't be reached anymore and therefore the newest shadow tar can't be reached - if any. Does anybody knows where the latest shadow tar's can be found - beside the LFS site. Regards, Frans. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Configuring 3.10.10 for quad-core processor
On Dec 4, 2013, at 3:36 PM, Ken Moffat wrote: > CONFIG_MK8 but works on K10 Ah was trying to find the exact configure option. It works with my A4 3400, as well. SIncerely, William Harrington -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Configuring 3.10.10 for quad-core processor
Ken Moffat wrote: > On Wed, Dec 04, 2013 at 02:46:47PM -0600, William Harrington wrote: >> >> On Dec 4, 2013, at 1:49 PM, Dan McGhee wrote: >> >>> AMD-10-5745M >> >> Have you used the powernow-k8 driver and have SMP enabled? >> >> http://cateee.net/lkddb/web-lkddb/X86_POWERNOW_K8.html >> >> Sincerely, >> >> WIlliam Harrington > > Powernow is for cpufreq (a good thing to use, IMHO, but not > mentioned in LFS) and not used anymore for K10 and newer CPUs (the > support is now in acpi-cpufreq). From memory, the initial K10 was > the athlon64xII. My git-foo isn't good enough to identify which > release that happened in, but the indications are that it was well > before 3.10. > > SMP is the key. > > If Dan is building only for that machine (and doesn't intend to use > the system to boot any replacement machine when the time comes) then > optimizing for the specific processor family, i.e. AMD x86_64 > (Opteron/Athlon/Hammer/K8 : this is CONFIG_MK8 but works on K10 ;-) > might gain a little, as might Multi-Core Scheduler support. I hate to mention the obvious, but is CONFIG_X86_64_SMP set in the kernel? Other possibilities: CONFIG_USE_GENERIC_SMP_HELPERS=y CONFIG_GENERIC_SMP_IDLE_THREAD=y CONFIG_SMP=y CONFIG_HAVE_TEXT_POKE_SMP=y -- 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] Shadow tar file
Frans de Boer wrote: > I noticed that the debian site can't be reached anymore and therefore > the newest shadow tar can't be reached - if any. > > Does anybody knows where the latest shadow tar's can be found - beside > the LFS site. http://ftp.de.debian.org/debian/pool/main/s/shadow/ -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] 7.4 5.15. Ncurses-5.9 fails to make
Hi Group,
Things seemed to be going well and according to the book until ncurses.
My host is Ubuntu 13.10 the rest of my info is below.
Any ideas what is wrong?
Thanks,
Ron
The error I got was: unterminated #ifdef. It happened here:
gcc -o make_hash -DHAVE_CONFIG_H -I../ncurses -I. -I./../include
-I../include -DUSE_BUILD_CC -DHAVE_CONFIG_H -I../ncurses -I. -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -DNDEBUG -I. -I../include -I/tools/include -O2
--param max-inline-insns-single=1200 ./tinfo/make_hash.c
In file included from ./../include/ncurses_cfg.h:177:0,
from ../ncurses/build.priv.h:53,
from ./tinfo/make_hash.c:40:
./../include/ncurses_def.h:5:0: error: unterminated #ifndef
#ifndef NC_DEFINE_H
__
the file in question looks exactly like some others I found on the web!
lfs@ron-Studio-1737:/mnt/lfs/sources/ncurses-5.9$ cat
../ncurses-5.9/include/ncurses_def.h
/*
* This file is generated by ./MKncurses_def.sh
*/
#ifndef NC_DEFINE_H
#define NC_DEFINE_H 1
lfs@ron-Studio-1737:/mnt/lfs/sources/ncurses-5.9$
_
full configure and make
lfs@ron-Studio-1737:/mnt/lfs/sources/ncurses-5.9$ ./configure
--prefix=/tools --with-shared \
> --without-debug --without-ada --enable-overwrite
checking for egrep... grep -E
Configuring NCURSES 5.9 ABI 5 (Wed Dec 4 20:06:19 EST 2013)
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
Configuring for linux-gnu
checking for prefix... /tools
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking version of gcc... 4.8.1
checking how to run the C preprocessor... gcc -E
checking whether gcc needs -traditional... no
checking whether gcc understands -c and -o together... yes
checking for POSIXized ISC... no
checking for gcc option to accept ANSI C... -DCC_HAS_PROTOS
checking for ldconfig... /sbin/ldconfig
checking if you want to ensure bool is consistent with C++... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for g++... /tools/bin/g++
checking version of g++... 4.8.1
checking if you want to build C++ binding and demo... yes
checking if you want to build with Ada95... no
checking if you want to install manpages... yes
checking if you want to build programs such as tic... yes
checking if you want to build test-programs... yes
checking if you wish to install curses.h... yes
checking for mawk... mawk
checking for egrep... (cached) grep -E
checking for a BSD compatible install... /usr/bin/install -c
checking for tdlint... no
checking for lint... no
checking for alint... no
checking for splint... no
checking for lclint... no
checking whether ln -s works... yes
checking if ln -s -f options work... yes
checking for long file names... yes
checking if you want to use pkg-config... yes
checking for pkg-config... /usr/bin/pkg-config
checking if we should install .pc files for /usr/bin/pkg-config... no
checking if we should assume mixed-case filenames... auto
checking if filesystem supports mixed-case filenames... yes
checking whether make sets ${MAKE}... yes
checking for exctags... no
checking for ctags... no
checking for exetags... no
checking for etags... no
checking for ctags... no
checking for etags... no
checking for makeflags variable...
checking for ranlib... ranlib
checking for ld... ld
checking for ar... ar
checking for ar... (cached) ar
checking for options to update archives... -curv
checking if you have specified an install-prefix...
checking if libtool -version-number should be used... yes
checking if you want to build libraries with libtool... no
checking if you want to build shared libraries... yes
checking if you want to build static libraries... yes
checking if you want to build debug libraries... no
checking if you want to build profiling libraries... no
checking for specified models... shared normal
checking for default model...
checking if you want to build a separate terminfo library... no
checking if you want to build a separate tic library... no
checking if you want to link with the GPM mouse library... maybe
checking for gpm.h... no
checking for default loader flags...
checking for an rpath option... -Wl,-rpath,
checking if release/abi version should be used for shared libs... auto
checking which gcc option to use... -fPIC
checking if you wish to install ncurses overwriting curses... yes
checking if external terminfo-database is used... yes
checking which terminfo source-file will be installed...
${top_srcdir}/misc/terminfo.src
checking whether to u
Re: [lfs-support] 7.4 5.15. Ncurses-5.9 fails to make
Ron Hartikka wrote: > Hi Group, > > > Things seemed to be going well and according to the book until ncurses. > My host is Ubuntu 13.10 the rest of my info is below. > Any ideas what is wrong? Not really. include/ncurses_def.h is definitely wrong. That's a generated file. The host requirements look OK, but I do see that configure is picking up mawk anyway. My log shows: AWK=gawk sh ./MKncurses_def.sh ./ncurses_defs >ncurses_def.h You may want to mv mawk to mawk.sav and try again. -- 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] Configuring 3.10.10 for quad-core processor
On 12/04/2013 04:02 PM, Bruce Dubbs wrote: > Ken Moffat wrote: >>Powernow is for cpufreq (a good thing to use, IMHO, but not >> mentioned in LFS) and not used anymore for K10 and newer CPUs (the >> support is now in acpi-cpufreq). From memory, the initial K10 was >> the athlon64xII. My git-foo isn't good enough to identify which >> release that happened in, but the indications are that it was well >> before 3.10. >> >>SMP is the key. >> >>If Dan is building only for that machine (and doesn't intend to use >> the system to boot any replacement machine when the time comes) then >> optimizing for the specific processor family, i.e. AMD x86_64 >> (Opteron/Athlon/Hammer/K8 : this is CONFIG_MK8 but works on K10 ;-) >> might gain a little, as might Multi-Core Scheduler support. > I hate to mention the obvious, but is CONFIG_X86_64_SMP set in the > kernel? Other possibilities: > > CONFIG_USE_GENERIC_SMP_HELPERS=y > CONFIG_GENERIC_SMP_IDLE_THREAD=y > CONFIG_SMP=y > CONFIG_HAVE_TEXT_POKE_SMP=y > > Mentioning the obvious always helps--the old "forest and trees." In this case, however, even with that particular option doesn't seem to be present. But, I discovered much to my embarassment that CONFIG_SMP was not set. Rats. Ken, are K10 and A10 the same? I suppose I could set it and if I didn't need it wouldn't hurt anything. I also suppose that I could "google around" to see if they are separate families or are somehow related. Some of the documentation I found today referred to "increased support" for AMD processors, including A10. I don't know how to go to 'kernel.org' and slog through the patches. I wouldn't even know where to start. I was, however, really distracted by my thunderbird build, which was ultimately successful, and maybe I'll be able to search more systematically tomorrow. But someone could just tell me so I wouldn't have to look. 8-) Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] 7.4 5.15. Ncurses-5.9 fails to make
> You may want to mv mawk to mawk.sav and try again. > >-- Bruce That did it. :) Configure checks for mawk first. It was mawk 1.3.3-17ubuntu1 Thanks again Bruce. Ron Hartikka -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Configuring 3.10.10 for quad-core processor
On Wed, 2013-12-04 at 20:33 -0600, Dan McGhee wrote: > Mentioning the obvious always helps--the old "forest and trees." In this > case, however, even with that particular > option doesn't seem to be present. But, I discovered much to my > embarassment that CONFIG_SMP was not set. Rats. Yeah, I got burned that way, when I built my first multicore system a few years ago. You'd think that these days, it'd be a reasonable default... > Ken, are K10 and A10 the same? Nope. K10 refers to a generation of AMD processors from about 3 years ago (including the Phenom II in my current desktop box). A10 is a specific model of their current A-series processors. It's possible they're similar enough that K10 optimisations and stuff will work, but they might not be too... Simon. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
