From: Sandy Patterson <apatterson@sightlogix.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] problem using custom host compiler
Date: Thu, 26 Oct 2017 15:48:46 -0400 [thread overview]
Message-ID: <CABCGj3bkT2VW+vqR8S90ztRHkuWOto7-GujNvbNySDXgHR7TRw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1251 bytes --]
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.
Thanks,
Sandy Patterson
--- ptxdist-2015.02.0-orig/rules/other/Namespace.make 2017-10-26
15:20:35.925028016 -0400
+++ ptxdist-2015.02.0/rules/other/Namespace.make 2017-10-26
15:21:19.248999794 -0400
@@ -19,8 +19,8 @@
PTXCONF_COMPILER_PREFIX := $(call remove_quotes,
$(PTXCONF_COMPILER_PREFIX))
COMPILER_PREFIX := $(PTXCONF_COMPILER_PREFIX)
-HOSTCC := gcc
-HOSTCXX := g++
+HOSTCC := $(call remove_quotes, $(PTXCONF_SETUP_HOST_CC))
+HOSTCXX := $(call remove_quotes, $(PTXCONF_SETUP_HOST_CXX))
PTXCONF_ARCH_STRING := $(call remove_quotes, $(PTXCONF_ARCH_STRING))
PTXCONF_KERNEL_ARCH_STRING := $(call remove_quotes,
$(PTXCONF_KERNEL_ARCH_STRING))
[-- Attachment #1.2: Type: text/html, Size: 2047 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2017-10-26 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 19:48 Sandy Patterson [this message]
2017-10-27 12:32 ` Michael Olbrich
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=CABCGj3bkT2VW+vqR8S90ztRHkuWOto7-GujNvbNySDXgHR7TRw@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