From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@busybox.net,
"Guillaume W. Bres" <guillaume.bressaix@gmail.com>
Subject: Re: [Buildroot] [RFC v3 1/2] package/pkg-meson.mk: support fortran cross-compilation
Date: Tue, 9 Aug 2022 18:25:34 +0200 [thread overview]
Message-ID: <20220809162534.GE3168@scaer> (raw)
In-Reply-To: <20220808194708.GA524369@scaer>
Thomas, All,
On 2022-08-08 21:47 +0200, Yann E. MORIN spake thusly:
> On 2022-08-07 00:13 +0200, Thomas Petazzoni spake thusly:
> [--SNIP--]
> > Now, on to the open issue which explains why I have added Yann in Cc.
> > We are currently setting the C++ compiler and Fortran compiler path in
> > Meson's cross-compilation.conf unconditionally... even when the
> > toolchain has no C++ or Fortran support. So it means we're pointing to
> > compilers that don't exist.
> I think this is fine. They don't exist, so they can't be run, so meson
> will not inadvertently be able to build a C++/Fortran/... program and we
> will notice the issue.
>
> > Ideally, the cross-compilation.conf should be generated with no
> > reference to a C++ or Fortran compiler, or a /bin/false reference, and
> > ditto for the CXXFLAGS/FCFLAGS when there is no C++ or Fortran support.
>
> In the past, we used to use false as a C++ compiler (but not for meson
> specifically), and it turned out that that caused quite some
> hard-to-understand issues, see 4cd1ab15886a (core: alternate solution to
> disable C++).
>
> I'll ask the meson guys in irc://irc.oftc.net/#mesonbuild and se what
> they have to say and suggest.
So, @eliebrokeit there said, quoting:
If you don't have one defined, cross builds won't try to autodetect
one, IIRC...
[...] however setting it to /bin/false will result in it detecting
that that doesn't work
I guess the safest bet is to deliberately poison it with /bin/false
So, when we do not have a compiler for a specific language, we should
force it to /bin/false.
Guillaume, would you be willing to tackle that?
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. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-09 16:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 14:36 [Buildroot] [RFC v3 1/2] package/pkg-meson.mk: support fortran cross-compilation Guillaume W. Bres
2022-08-05 14:36 ` [Buildroot] [RFC v3 2/2] package/python-scipy: bump version to 1.9.0 Guillaume W. Bres
2022-08-05 14:46 ` Guillaume Bres
2022-08-08 20:58 ` Arnout Vandecappelle
2022-08-08 21:13 ` Thomas Petazzoni via buildroot
2022-08-09 8:37 ` Guillaume Bres
2022-08-27 9:11 ` Guillaume Bres
[not found] ` <CABL7CQjFbqaDd2ULBsPVyKM3cAEjCSHEdnY9vfxA=VMuRbdNjg@mail.gmail.com>
2022-09-01 19:43 ` Guillaume Bres
2022-08-06 22:13 ` [Buildroot] [RFC v3 1/2] package/pkg-meson.mk: support fortran cross-compilation Thomas Petazzoni via buildroot
2022-08-08 19:47 ` Yann E. MORIN
2022-08-09 16:25 ` Yann E. MORIN [this message]
2023-06-26 21:34 ` James Hilliard
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=20220809162534.GE3168@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
--cc=guillaume.bressaix@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.