From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Standard build environment variables
Date: Mon, 29 Jun 2020 02:52:29 +1200 [thread overview]
Message-ID: <20200629025229.1aba405f@katipo2.lan> (raw)
In-Reply-To: <91a59b26-94e1-9494-3f2c-ca75e8ff1426@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
On Sun, 28 Jun 2020 08:18:23 -0400
Michael Orlitzky <mjo@gentoo.org> wrote:
> With LD set to something libtooly in the
> environment, the pari build fails. We can solve that by unsetting LD in
> the ebuild, but for that to be The Right Thing To Do, we should be
> expecting LD to contain something libtooly, and thus something
> inappropriate to be passed to the pari build.
>
> To avoid these issues, I suggest creating a list of "Gentoo environment
> variables" in the devmanual with descriptions of how they should be used
> and pointers to the references (for why we chose that meaning). That way
> a user can export LD, for example, and know that it will be used how he
> thinks it will be used.
That LD problem is not unique to Pari, ftr. Its a problem in *all* Perl
things that involve C parts.
Because Perl code expects "LD" to be a "CCLD", and passes flags a CCLD
would expect, which LD can't handle.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-28 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 12:18 [gentoo-dev] RFC: Standard build environment variables Michael Orlitzky
2020-06-28 14:52 ` Kent Fredric [this message]
2020-06-28 15:25 ` Mike Gilbert
2020-06-29 8:44 ` [gentoo-dev] " Agostino Sarubbo
2020-06-29 10:04 ` Ulrich Mueller
2020-06-30 16:22 ` [gentoo-dev] " Matthew Thode
2020-07-01 13:36 ` Michael Orlitzky
2020-07-01 19:04 ` Rich Freeman
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=20200629025229.1aba405f@katipo2.lan \
--to=kentnl@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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