From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 01/14] toolchain/toolchain-common.in: add BR2_TOOLCHAIN_HAS_LIBQUADMATH hidden symbol
Date: Mon, 4 Jul 2016 16:22:16 +0200 [thread overview]
Message-ID: <20160704162216.272f1883@free-electrons.com> (raw)
In-Reply-To: <7e95119d-44a7-dbf5-bc60-95b8a5bab77f@mind.be>
Hello,
On Mon, 4 Jul 2016 11:16:08 +0200, Arnout Vandecappelle wrote:
> > +# - libquadmath is not needed/available on all architectures (but gcc
> > +# correctly handles this already).
> > +# - At least, libquadmath is available on:
> > +# - i*86
> > +# - x86_64
> > +# - When available, libquadmath requires wchar support.
> > +config BR2_TOOLCHAIN_HAS_LIBQUADMATH
> > + bool
> > + default y if BR2_i386 || BR2_x86_64
>
> Wouldn't it make more sense to add here:
>
> depends on BR2_USE_WCHAR
>
> (and remove it from the .mk file)?
We thought about this, and discussed it with Samuel, but we had a good
reason not to do it. It was yesterday so I already forgot why.
Ah, there it is. Look at this option:
config BR2_TOOLCHAIN_BUILDROOT_FORTRAN
bool "Enable Fortran support"
+ # on architecture building libquadmath, wchar is required
+ depends on !BR2_TOOLCHAIN_HAS_LIBQUADMATH || \
+ (BR2_TOOLCHAIN_HAS_LIBQUADMATH && BR2_USE_WCHAR)
How would express the dependency of Fortran is
BR2_TOOLCHAIN_HAS_LIBQUADMATH handles the BR2_USE_WCHAR dependency?
libquadmath is only available on i386 and x86_64, and in *this* case
wchar is needed for Fortran support.
So, we want to show the Fortran option if:
* We are on an architecture that does not need libquadmath
or
* We are on an architecture that does need libquadmath, in which case
we also need wchar.
Do you see a better solution ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-04 14:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 13:47 [Buildroot] [PATCH v3 00/14] Fortran support for all toolchains Samuel Martin
2016-07-03 13:47 ` [Buildroot] [PATCH v3 01/14] toolchain/toolchain-common.in: add BR2_TOOLCHAIN_HAS_LIBQUADMATH hidden symbol Samuel Martin
2016-07-04 9:16 ` Arnout Vandecappelle
2016-07-04 14:22 ` Thomas Petazzoni [this message]
2016-07-03 13:47 ` [Buildroot] [PATCH v3 02/14] package/gcc: complete the logic on libquadmath Samuel Martin
2016-07-03 13:47 ` [Buildroot] [PATCH v3 03/14] package/gcc: fix fortran support Samuel Martin
2016-07-03 13:47 ` [Buildroot] [PATCH v3 04/14] toolchain: add hidden symbol for fortran support in the toolchain Samuel Martin
2016-07-03 13:47 ` [Buildroot] [PATCH v3 05/14] docs/manual: document dependency on fortran Samuel Martin
2016-07-03 13:47 ` [Buildroot] [PATCH v3 06/14] package/gcc: select BR2_TOOLCHAIN_HAS_FORTRAN when appropriate Samuel Martin
2016-07-03 13:47 ` [Buildroot] [PATCH v3 07/14] pkg-cmake.mk: export the fortran compiler path in the CMake toolchain file Samuel Martin
2016-07-03 13:47 ` [Buildroot] [PATCH v3 08/14] toolchain/helpers: add fortran check Samuel Martin
2016-07-03 13:47 ` [Buildroot] [PATCH v3 09/14] toolchain/toolchain-external: enable fortran check when it is selected Samuel Martin
2016-07-03 13:47 ` [Buildroot] [PATCH v3 10/14] toolchain/toolchain-external: add libgfortran and libquadmath to the TOOLCHAIN_EXTERNAL_LIBS list Samuel Martin
2016-07-03 13:47 ` [Buildroot] [PATCH v3 11/14] toolchain/toolchain-external: add knob for fortran support Samuel Martin
2016-07-03 13:47 ` [Buildroot] [PATCH v3 12/14] toolchain/toolchain-external: update external toolchain configuration with BR2_TOOLCHAIN_HAS_FORTRAN Samuel Martin
2016-07-03 13:47 ` [Buildroot] [PATCH v3 13/14] package/fftw: add fortran support Samuel Martin
2016-07-03 13:47 ` [Buildroot] [PATCH v3 14/14] package/lapack: new package Samuel Martin
2016-07-03 15:02 ` [Buildroot] [PATCH v3 00/14] Fortran support for all toolchains Thomas Petazzoni
2016-07-04 22:56 ` Samuel Martin
2016-07-05 6:33 ` Thomas Petazzoni
2016-07-05 6:48 ` Samuel Martin
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=20160704162216.272f1883@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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