Hallo,
> CC=$LFS_TGT-gcc
> I mean really on their own line, w/o the trailing '\' on each line.
you could solve that by exporting the variables. only exported variables are
visible in sub shells, or variables listed on the same command line in front of
the command invoked.
"CC=... make" would
On Thu, Jan 17, 2019 at 05:44:08PM -0500, jonetsu wrote:
> On Thu, 17 Jan 2019 10:36:33 -0500
> jonetsu wrote:
>
> > make: gcc: Command not found
>
> Confirmed. It now works. Two modifications were made since last
> time. One is about a gcc directory that did not get erased when
> supposed
On Thu, 17 Jan 2019 10:36:33 -0500
jonetsu wrote:
> make: gcc: Command not found
Confirmed. It now works. Two modifications were made since last
time. One is about a gcc directory that did not get erased when
supposed to. The other is about the gcc 2nd pass configure command
that had the
On Thu, 17 Jan 2019 14:46:33 -0600
Bruce Dubbs wrote:
> Typically the solution for errors like you describe is to start over
> and be more careful following the commands in the book.
Yes. This is why it's all scripted.
Doing some searches I found this quote in the mailing list, perhaps by
> And each
> command is followed by an error check and if there's an error, the
> script will bail out. It checks the error code with this:
>
> function check4errors()
> {
> if [ $? != 0 ]
> then
> [ "$1" != "" ] && logError $1 exit 1
> fi
> }
>
> It simply logs by writing to a file.
On 01/17/2019 02:33 PM, jonetsu wrote:
On Thu, 17 Jan 2019 21:06:24 +0100
Pierre Labastie wrote:
I think I've proposed a set of commands in my previous message.
Either you have not run them or you have run them and not sent the
result to us. In either case, I cannot help you.
Since there
On Thu, Jan 17, 2019 at 01:35:51PM -0500, jonetsu wrote:
> On Thu, 17 Jan 2019 19:06:18 +0100
> Pierre Labastie wrote:
>
> > So, IIUC gcc *is* in /tools/bin (and is executable) (what is the
> > ouput of ls -l /tools/bin/*gcc*).
>
You did not answer that.
> From the ch6 chroot, where it
On Thu, 17 Jan 2019 14:20:19 -0600
Bruce Dubbs wrote:
> In my experience, these types of errors result from not building
> Chapter 5 as user lfs or that the lfs user environment is wrong. One
> mistake is that the change to user lfs is done with 'su lfs' and not
> 'su - lfs'.
Do you know in
On 01/17/2019 02:06 PM, Pierre Labastie wrote:
On 17/01/2019 19:35, jonetsu wrote:
On Thu, 17 Jan 2019 19:06:18 +0100
Pierre Labastie wrote:
So, IIUC gcc *is* in /tools/bin (and is executable) (what is the
ouput of ls -l /tools/bin/*gcc*).
From the ch6 chroot, where it matters, the output
On 17/01/2019 19:35, jonetsu wrote:
> On Thu, 17 Jan 2019 19:06:18 +0100
> Pierre Labastie wrote:
>
>> So, IIUC gcc *is* in /tools/bin (and is executable) (what is the
>> ouput of ls -l /tools/bin/*gcc*).
>
> From the ch6 chroot, where it matters, the output of gcc is, when
> executed directly
On Thu, 17 Jan 2019 10:36:33 -0500
jonetsu wrote:
> make: gcc: Command not found
I should add that ldd (as chroot) gives:
lfs chroot) root:/tools/bin# ldd gcc
linux-vdso.so.1 (0x7ffeed749000)
libc.so.6 => /tools/lib/libc.so.6 (0x7f75b5b98000)
Hello,
I have rebuilt ch5 twice now. The 2nd time around I have scripted all
build commands so that there's a firm reliable base to work with. Each
package has its own build file. The build instructions can be compared
with the book and adjusted if necessary. Less guess work. And each
12 matches
Mail list logo
