mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Sandy Patterson <apatterson@sightlogix.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] problem using custom host compiler
Date: Fri, 27 Oct 2017 08:57:18 -0400	[thread overview]
Message-ID: <CABCGj3aO8GZXV16hwRZ1maucw7YuDSCZJrye0BWCMFbhu-UBGQ@mail.gmail.com> (raw)
In-Reply-To: <20171027123227.p3xp2pqjq3yjtart@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 925 bytes --]

Ahh, it seems as very much didn't understand. The Namespace.make sets
HOSTCC to gcc for prepare, but then during compile, the path starts with
that wrapper/real folder and on the command line you see just gcc. If I run
gcc --version I get the correct 4.8.

I also spaced and didn't realize that the symlinks in wrapper/real were
relative for cc and c++ so they all point to the 4.8 versions
...
lrwxrwxrwx 1 apatterson apatterson  3 Oct 27 08:20 c++ -> g++
lrwxrwxrwx 1 apatterson apatterson  3 Oct 27 08:20 cc -> gcc
lrwxrwxrwx 1 apatterson apatterson 16 Oct 27 08:20 cpp -> /usr/bin/cpp-4.8
lrwxrwxrwx 1 apatterson apatterson 16 Oct 27 08:20 g++ -> /usr/bin/g++-4.8
lrwxrwxrwx 1 apatterson apatterson 16 Oct 27 08:20 gcc -> /usr/bin/gcc-4.8

I think the console output compile command starting with gcc without the
4.8 confused me, but it was using the path and symlinks to get to the
correct one.

Thanks,
Sandy Patterson

[-- Attachment #1.2: Type: text/html, Size: 1123 bytes --]

[-- Attachment #2: Type: text/plain, Size: 91 bytes --]

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2017-10-27 12:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 19:48 Sandy Patterson
2017-10-27 12:32 ` Michael Olbrich
2017-10-27 12:57   ` Sandy Patterson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABCGj3aO8GZXV16hwRZ1maucw7YuDSCZJrye0BWCMFbhu-UBGQ@mail.gmail.com \
    --to=apatterson@sightlogix.com \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox