From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] problem using custom host compiler
Date: Fri, 27 Oct 2017 14:32:27 +0200 [thread overview]
Message-ID: <20171027123227.p3xp2pqjq3yjtart@pengutronix.de> (raw)
In-Reply-To: <CABCGj3bkT2VW+vqR8S90ztRHkuWOto7-GujNvbNySDXgHR7TRw@mail.gmail.com>
On Thu, Oct 26, 2017 at 03:48:46PM -0400, Sandy Patterson wrote:
> I am attempting to specify a host compiler via the file
> ~/.ptxdist/ptxdistrc-2015.02
>
> PTXCONF_SETUP_HOST_CPP="cpp-4.8"
> PTXCONF_SETUP_HOST_CC="gcc-4.8"
> PTXCONF_SETUP_HOST_CXX="g++-4.8"
> PTXCONF_SETUP_HOST_MAKE="make"
>
> I think this is ptxdist setup developer options.
>
> I expected ptxdist to use these compilers to build host-* packages, but
> instead it is using gcc and g++.
>
> I'm including a patch which behaves more the way I expect below. Would you
> guys care to comment on how I should have done this? I would like to build
> my firmware on different ubuntu versions which come with different
> compilers.
It should work as is. The 'gcc' from HOSTCC should be
platform-XXX/sysroot-host/lib/wrapper/gcc. That's a script that will add
extra options and then call platform-XXX/sysroot-host/lib/wrapper/real/gcc.
This should be a symlink to ${PTXCONF_SETUP_HOST_CC}.
Where exactly does it use the wrong compiler?
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-10-27 12:32 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 [this message]
2017-10-27 12:57 ` Sandy Patterson
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=20171027123227.p3xp2pqjq3yjtart@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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