On 17/01/2019 21:33, jonetsu wrote:
> On Thu, 17 Jan 2019 21:06:24 +0100
> Pierre Labastie <[email protected]> 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 are two very different contexts of execution (ch5 and ch6,
> eg. login and chroot), and one of them being at fault, and since you
> haven't specified in which context the gcc commands had to be executed,
> I have assumed the most important context which is ch6, the chroot.
> 
> With that assumption I have posted twice, initially and as a reply, the
> output of gcc, which was, again:
> 
> ./gcc: Command not found
> 
> Not once, but twice.
> 

But I haven't asked you to run "./gcc", but to run "./gcc -v". That makes a
big difference: gcc is just a wrapper which calls other programs sequentially
(normal sequence: cpp, cc1 (compiler), as, and collect2 (itself a wrapper to
ld). Some of those programs are (at this stage) located in
/tools/libexec/gcc/x86_64-pc-linux-gnu/8.2.0 (cc1, collect2), some are in the
path (cpp, as). That's why I asked you to run ./gcc -v, which tells what
command would be run to call those programs, but does not run them (since
there is nothing to compile). Alsso the "gcc -print-something' does not try to
call the other programs, and just prints information.

What seems to have happenned is that one of those programs could not be found,
but gcc itself could be run. Glad it works now anyway.

The missing asm-goto issue could come from a similar error (not using \
continuation) in binutils pass 2...

Pierre

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Reply via email to