Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/gobject-introspection/g-ir-scanner: do not set default compiler values
Date: Sun, 22 Mar 2020 22:53:44 +0100	[thread overview]
Message-ID: <20200322215344.GF22325@scaer> (raw)
In-Reply-To: <20200321214726.GN4290@scaer>

Adam, All,

On 2020-03-21 22:47 +0100, Yann E. MORIN spake thusly:
> On 2020-03-20 15:23 -0700, aduskett at gmail.com spake thusly:
> > From: Adam Duskett <Aduskett@gmail.com>
> > Commit 8b0aeafce2a22913e6a44818227f6a39e3225157 set 7 new variables in
> > g-ir-scanner.in:
> > 
> > export CPP="${CPP:-${HOST_DIR}/bin/@BASENAME_TARGET_CPP@}"
> > export CC="${CC:-${HOST_DIR}/bin/@BASENAME_TARGET_CC@}"
> > export CXX="${CXX:-${HOST_DIR}/bin/@BASENAME_TARGET_CXX@}"
> > CPPFLAGS="${CPPFLAGS:- at TARGET_CPPFLAGS@}"
> > CFLAGS="${CFLAGS:- at TARGET_CFLAGS@}"
> > CXXFLAGS="${CXXFLAGS:- at TARGET_CXXFLAGS@}"
> > LDFLAGS="${LDFLAGS:- at TARGET_LDFLAGS@}"
> > 
> > However, defaulting to CPP, CC, or CXX breaks some packages because they may
> > hard code CC to the system CC.
> > 
> > One such package is libostree which has the line
> > "INTROSPECTION_SCANNER_ENV = CC=gcc" in the Makefile.
> 
> But then, that's clearly a bug in libostree! They should not ever try to
> call a hard-coded compiler.
[--SNIP--]

Mu alternate proposal was just merged, so I've marked this series as
rejected. It anyway helped understand the actual problem, so it was
definitely not in vain. Thanks! :-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2020-03-22 21:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 22:23 [Buildroot] [PATCH 1/2] package/gobject-introspection/g-ir-scanner: do not set default compiler values aduskett at gmail.com
2020-03-20 22:23 ` [Buildroot] [PATCH 2/2] package/libostree: add introspection support aduskett at gmail.com
2020-03-22  9:31   ` Yann E. MORIN
2020-03-21 21:47 ` [Buildroot] [PATCH 1/2] package/gobject-introspection/g-ir-scanner: do not set default compiler values Yann E. MORIN
2020-03-22 21:53   ` Yann E. MORIN [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=20200322215344.GF22325@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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