> Dont mix the things. LFS_TG was set in both trials. As I said, no
> errors. I was just telling you, that in my effort to check the line
> you wanted to see, I repeated, not chrooted, a ./compile, as root or
> as lfs or I do not know more what. Forgett it.
Hi, Edgar, may I help? My career was i
On Thu, 23 Jun 2016 14:28:10 +0200
Edgar Alwers wrote:
> But another comment: it should be the same if I enter the four line
> commands
>
> CC=$LFS_TGT-gcc
> CXX=$LFS_TGT-g++
> AR=$LFS_TGT-ar
> RANLIB=$LFS_TGT-ranlib
>
> as single commands and then enter the .compile one or if I give the comp
On 23/06/2016 14:42, Edgar Alwers wrote:
Am 23.06.2016 um 12:10 schrieb Pierre Labastie:
Do you mean that you type:
CC=$LFS_TGT-gcc\
CXX=$LFS_TGT-g++ \
...
then "enter" then ../configure ... ?
If so, that is the problem: this is one big instruction start
> From: Edgar Alwers
> Date: Thu, 23 Jun 2016 14:28:10 +0200
> Subject: Re: [lfs-support] 6.7 Linux-4.6 API headers make mrproper fails
>
> Am 23.06.2016 um 10:14 schrieb akhiezer:
> >> From: Edgar Alwers
> >> Date: Wed, 22 Jun 2016 22:18:09 +0200
> >>
Am 23.06.2016 um 12:10 schrieb Pierre Labastie:
Do you mean that you type:
CC=$LFS_TGT-gcc\
CXX=$LFS_TGT-g++ \
...
then "enter" then ../configure ... ?
If so, that is the problem: this is one big instruction starting at
CC= and ending at disable-libgomp.
Am 23.06.2016 um 10:14 schrieb akhiezer:
From: Edgar Alwers
Date: Wed, 22 Jun 2016 22:18:09 +0200
Subject: Re: [lfs-support] 6.7 Linux-4.6 API headers make mrproper fails
Am 22.06.2016 um 18:35 schrieb Pierre Labastie:
Did you type the CC=... CXX=... etc lines? They are needed (with
On 22/06/2016 22:18, Edgar Alwers wrote:
Yes. As user lfs i did as the book says.
CC=$LFS_TGT-gcc\
CXX=$LFS_TGT-g++
...
Then compilation as indicated in the book:
../configure \ --prefix=/tools \ --with-local-prefix=/tools \
--with-native-system-header-dir=/to
> From: Edgar Alwers
> Date: Wed, 22 Jun 2016 22:18:09 +0200
> Subject: Re: [lfs-support] 6.7 Linux-4.6 API headers make mrproper fails
>
>
> Am 22.06.2016 um 18:35 schrieb Pierre Labastie:
> > Did you type the CC=... CXX=... etc lines? They are needed (with
>
> >> Now that you mention it Pierre, I think the following would be better
> >> because it is far easier to read and understand.
> >>
> >>
> >> sed -e 's@/lib../ld@/tools&@g'
> >>
> >> where the '.' matches any character.
> >
> > Not completely sure, but I think we need to be able to match /lib/ld
Edgar Alwers wrote:
I hope, the book can be changed to include 32 bit ;-)
We will change it if we find out what needs to be changed, but I did a
jhalfs build on a 32-bit system with no problems.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfroms
Am 22.06.2016 um 18:35 schrieb Pierre Labastie:
Did you type the CC=... CXX=... etc lines? They are needed (with
backslash as continuation character) to get the behavior I
described... Maybe LFS_TGT is not set? Or $LFS_TGT-gcc is not found in
the PATH? To be clear, you can unpack gcc outside
On 22/06/2016 17:20, Edgar Alwers wrote:
Am 22.06.2016 um 15:08 schrieb Pierre Labastie:
You may try (outside chroot):
echo 'int main(){}' > dummy.c
/tools/bin/i686-lfs-linux-gnu-gcc dummy.c
readelf -l a.out | grep ': /tools'
[Requesting program interpreter: /tools/lib/ld-linux.so.2]
Also,
Am 22.06.2016 um 15:08 schrieb Pierre Labastie:
You may try (outside chroot):
echo 'int main(){}' > dummy.c
/tools/bin/i686-lfs-linux-gnu-gcc dummy.c
readelf -l a.out | grep ': /tools'
[Requesting program interpreter: /tools/lib/ld-linux.so.2]
Also, another check:
ls -i /tools/bin/i686-pc-l
On 21/06/2016 22:03, Edgar Alwers wrote:
Am 21.06.2016 um 18:21 schrieb Pierre Labastie:
Actually, what version of LFS were you building? SVN?
The place where /tools/ is added before /lib is in 5.10, GCC Pass 2.
it is the long sequence of instructions starting with "for file in".
Have you
On 21/06/2016 21:12, Bruce Dubbs wrote:
Pierre Labastie wrote:
The place where /tools/ is added before /lib is in 5.10, GCC Pass 2.
it is
the long sequence of instructions starting with "for file in". Have you
pasted those instructions from the book, or did you recopy them by hand?
Make sure y
Am 21.06.2016 um 18:21 schrieb Pierre Labastie:
Actually, what version of LFS were you building? SVN?
The place where /tools/ is added before /lib is in 5.10, GCC Pass 2.
it is the long sequence of instructions starting with "for file in".
Have you pasted those instructions from the book, or
Pierre Labastie wrote:
The place where /tools/ is added before /lib is in 5.10, GCC Pass 2. it is
the long sequence of instructions starting with "for file in". Have you
pasted those instructions from the book, or did you recopy them by hand?
Make sure you have the line
sed -e
On 21/06/2016 16:44, Edgar Alwers wrote:
Am 14.06.2016 um 07:21 schrieb Bruce Dubbs:
Edgar, I'd suggest trying jhalfs. It is really a tool for
developers, but it's not that hard to use. You need subversion and
the tools uses to build the book (libxml2, libxslt, DocBook, and
tidy). If you n
Am 14.06.2016 um 07:21 schrieb Bruce Dubbs:
Edgar, I'd suggest trying jhalfs. It is really a tool for developers,
but it's not that hard to use. You need subversion and the tools uses
to build the book (libxml2, libxslt, DocBook, and tidy). If you need
help getting it to run properly, I'll
I'll check my Tualatin, 1.4Ghz Pentium-3, today. I could try it there
if
necessary.
p.s. Correction to a previous post: I stopped compiling after "check"
not "install", of course.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally
Bruce Dubbs wrote:
Bruce Dubbs wrote:
Dr.-Ing. Edgar Alwers wrote:
$ ldd /tools/bin/gcc
linux-vdso.so.1 (0x7ffdf9d09000)
libm.so.6 => /tools/lib/libm.so.6 (0x7f0813de7000)
libc.so.6 => /tools/lib/libc.so.6 (0x7f0813a46000)
/tools/lib64/ld-li
I have stopped my build with the gcc-build as is at the end of the "make
install", with tee'd logs of the configure, make, and install phases.
I'm very willing to search for any clues to what's causigng the failure
which anybody can suggest, given that I'm just a LFS/Linux user, not a C
programmer
Douglas R. Reno wrote:
On June 13, 2016 3:59:27 PM CDT, Bruce Dubbs
wrote:
I tried to fire up my P6 yesterday but there seemed to be a
power issue. I left it plugged in and today I noticed some LEDs
flashing. I tried to restart it and it worked. Curious. It's like a
battery needed to be r
On June 13, 2016 3:59:27 PM CDT, Bruce Dubbs wrote:
>Bruce Dubbs wrote:
>> Dr.-Ing. Edgar Alwers wrote:
>
$ ldd /tools/bin/gcc
linux-vdso.so.1 (0x7ffdf9d09000)
libm.so.6 => /tools/lib/libm.so.6 (0x7f0813de7000)
libc.so.6 => /tools/lib/libc.
Thomas Trepl wrote:
Am Montag, den 13.06.2016, 15:59 -0500 schrieb Bruce Dubbs:
Bruce Dubbs wrote:
Dr.-Ing. Edgar Alwers wrote:
$ ldd /tools/bin/gcc linux-vdso.so.1 (0x7ffdf9d09000)
libm.so.6 => /tools/lib/libm.so.6 (0x7f0813de7000)
libc.so.6 => /tools/lib/libc.so.6 (0x7f0813a460
Am Montag, den 13.06.2016, 15:59 -0500 schrieb Bruce Dubbs:
> Bruce Dubbs wrote:
> > Dr.-Ing. Edgar Alwers wrote:
>
> > > > $ ldd /tools/bin/gcc
> > > > linux-vdso.so.1 (0x7ffdf9d09000)
> > > > libm.so.6 => /tools/lib/libm.so.6
> > > > (0x7f0813de7000)
> > > >
BTW, I did search for GCC-4.9.2 i686 regression test/patch and found
some, but they seemed to mostly be dealing with particular distros
packaging. On GNU I found a report of a successful regression test
build. Can't attest to a very thorough search.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers'
> Just use grep's '-E' - e.g.:
>
> grep -iE 'fail|error|unexpected' "${MKCHK_LG_FP}" ;
>
> ?
Thanks, AK.
--
Paul Rogers
paulgrog...@fastmail.fm
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)
--
http://www.fastm
> No its not. Too bad that well running machines are thrown away
> just because there newer ones. The current behavier in Linux even
> forces that.
I obviously agree.
> Back to on-topic: I also have trouble atm with building on a 32-bit-
> machine. Currently, there is a jhalfs build running on
Bruce Dubbs wrote:
Dr.-Ing. Edgar Alwers wrote:
$ ldd /tools/bin/gcc
linux-vdso.so.1 (0x7ffdf9d09000)
libm.so.6 => /tools/lib/libm.so.6 (0x7f0813de7000)
libc.so.6 => /tools/lib/libc.so.6 (0x7f0813a46000)
/tools/lib64/ld-linux-x86-64.so.2 (0x0
William Harrington wrote:
On Sun, June 12, 2016 20:32, Bruce Dubbs wrote:
Paul Rogers wrote:
I admit I have not tested a 32-bit system is several months. They
really
are obsolete.
That's OK, so is all my hardware! I'm retired living on a fixed income.
You can't afford a one time $89?
Ap
On Sun, June 12, 2016 20:32, Bruce Dubbs wrote:
> Paul Rogers wrote:
>>> I admit I have not tested a 32-bit system is several months. They
>>> really
>>> are obsolete.
>>
>> That's OK, so is all my hardware! I'm retired living on a fixed income.
>
> You can't afford a one time $89?
>
Apparently y
> From: Paul Rogers
> Date: Sun, 12 Jun 2016 18:29:09 -0700
> Subject: Re: [lfs-support] 6.7 Linux-4.6 API headers make mrproper fails
>
> [...] I did a few greps
> with line numbers on the "make check" log, so I could sort them into
> order. [...]
Just use
Am Sonntag, den 12.06.2016, 12:56 -0700 schrieb Paul Rogers:
> >
> > I admit I have not tested a 32-bit system is several months. They
> > really
> > are obsolete.
>
> That's OK, so is all my hardware! ...
> --
> Paul Rogers
>
No its not. Too bad that well running machines are thrown away ju
Reporting on the failure of my Ch6 GCC-4.9.2 rebuild from scratch for
i686. It went through the headers fine this time. I did a few greps
with line numbers on the "make check" log, so I could sort them into
order. I didn't see mush in the way of specific identifications. I'm
not sure this is ve
Paul Rogers wrote:
I admit I have not tested a 32-bit system is several months. They really
are obsolete.
That's OK, so is all my hardware! I'm retired living on a fixed income.
You can't afford a one time $89?
http://www.ebay.com/sch/i.html?_from=R40&_trksid=p2047675.m570.l1311.R5.TR12.TR
> I admit I have not tested a 32-bit system is several months. They really
> are obsolete.
That's OK, so is all my hardware! I'm retired living on a fixed income.
If I had all the bucks to keep up with the latest and greatest maybe I'd
have a recent version of that other software that keeps mak
Dr.-Ing. Edgar Alwers wrote:
ls -l /tools/bin/*gcc*' from outside chroot in my case
---
-rwxr-xr-x 3 root root 894420 11. Jun 10:28 /tools/bin/gcc
-rwxr-xr-x 2 root root 24160 11. Jun 10:28 /tools/bin/gcc-ar
and the same, chrooted:
Hallo all,
thank you very much for your e-mails
On Saturday 11 June 2016 16:01:26 Bruce Dubbs wrote:
> What about 'ls -l /tools/bin/*gcc*' from outside chroot.
>
> I admit I have not tested a 32-bit system is several months. They really
> are obsolete.
>
> I have:
>
> -rwxr-xr-x 3 lfs lfs 434
On Sunday 12 June 2016 07:30:51 William Harrington wrote:
> The interpreter is probably wrong. From the host run "readelf -e
> /tool/bin/gcc | grep interpreter"
>
> You may find it is linked to the host OS.
Hi William,
"readelf -e /tools/bin/gcc | grep interpreter" delivers
[Requesting program
On Sat, June 11, 2016 15:25, Edgar Alwers wrote:
> Hi Bruce, hi all,
>
> I am building the LFS Version SVN-20160527, up to chapter 6.7 everythink
> went OK.
>
> Now, starting the API Headers section with "make mrproper", I get an error
>
> make: gcc: Command not found
>
> followed by ./scripts/gcc-
> While I can't say anything about helping, I will note that you are the
> third person to report this issue in the past few days. I think this
> prompts an investigation.
>
> What do you use as a host system? What architecture (i686/x86_64)?
I'm doing LFS-7.7, march=i686, hosted on an i7 with L
Edgar Alwers wrote:
Am 11.06.2016 um 18:46 schrieb Bruce Dubbs:
Make sure you have the virtual file systems mounted.
I think the virtual file system is mounted. I can access every virtual
file e.g. cdrom and floppy in /media
> Inside chroot can you do:
< echo 'int main(){}' > dummy.c
> g
Edgar Alwers wrote:
Am 11.06.2016 um 18:28 schrieb Ken Moffat:
How about ldd /tools/bin/gcc ?
delivers /tools/bin/ldd: line 125: /tools/bin/gcc: No such file or directory
But that is not true. /tools/bin/gcc exists !
I have followed step by step the book instructions, and I have already
buil
Am 11.06.2016 um 18:46 schrieb Bruce Dubbs:
Make sure you have the virtual file systems mounted.
I think the virtual file system is mounted. I can access every virtual
file e.g. cdrom and floppy in /media
> Inside chroot can you do:
< echo 'int main(){}' > dummy.c
> gcc dummy.c
Yes, the
Am 11.06.2016 um 18:06 schrieb Douglas R. Reno:
What do you use as a host system? What architecture (i686/x86_64)?
I have a self compiled linux systemd-system as host.: linux 4.0.5, KDE
4.14.1, built some months ago. i 386 architecture. This host system
works smootly, is my main system.
Edg
Am 11.06.2016 um 18:28 schrieb Ken Moffat:
How about ldd /tools/bin/gcc ?
delivers /tools/bin/ldd: line 125: /tools/bin/gcc: No such file or directory
But that is not true. /tools/bin/gcc exists !
I have followed step by step the book instructions, and I have already
built more than a dozen
Edgar Alwers wrote:
Hi Bruce, hi all,
I am building the LFS Version SVN-20160527, up to chapter 6.7 everythink
went OK.
Now, starting the API Headers section with "make mrproper", I get an error
make: gcc: Command not found
followed by ./scripts/gcc-version.sh: line 25: /tools/bin/gcc: no suc
On June 11, 2016 10:25:10 AM CDT, Edgar Alwers wrote:
>Hi Bruce, hi all,
>
>I am building the LFS Version SVN-20160527, up to chapter 6.7
>everythink
>went OK.
>
>Now, starting the API Headers section with "make mrproper", I get an
>error
>
>make: gcc: Command not found
>
>followed by ./scripts/g
On Sat, Jun 11, 2016 at 05:25:10PM +0200, Edgar Alwers wrote:
> Hi Bruce, hi all,
>
> I am building the LFS Version SVN-20160527, up to chapter 6.7 everythink
> went OK.
>
> Now, starting the API Headers section with "make mrproper", I get an error
>
> make: gcc: Command not found
>
> followed
50 matches
Mail list logo