From: Panagiotis Christopoulos <pxrist@gmail.com>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] Locating ar
Date: Tue, 29 Apr 2014 14:44:29 +0300 [thread overview]
Message-ID: <CAF2cyYPdSRPrd=yirzcc=N6X+yLOdWvoKNPjxhRozaVKBvT3Pw@mail.gmail.com> (raw)
In-Reply-To: <CAF2cyYPKzn9s+vBiuDv+1H903N2kEgh3fVMKLb7VG4bLC2kYMg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
On Tue, Apr 29, 2014 at 2:36 PM, Panagiotis Christopoulos
<pxrist@gmail.com>wrote:
> ...
>
> if you open the original sources (without eautoreconf), and go inside
> omalloc folder, you'll find the cause in line 120 of configure.ac and/or
> 12977 of configure. It's hardcoded there that the script should fail if
> $ac_cv_prog_AR is not "ar". Here, portage already passes (even without your
> tc-exports etc.) the correct environment to singular's build system but
> "x86_64-pc-linux-gnu-ar" is not "ar". You could remove that check at all
> but I'm not a toolchain expert and don't know why the check is there in
> first place. On my box ar just links to x86_64-pc-linux-gnu-ar so no big
> deal.
>
of course , name changes may affect program behariour ($0) so ar might have
different results if you invoke it as "ar" than "x86_64-pc-linux-gnu-ar".
I would remove or replace the configure check and would do some testing to
see what happens. Was omalloc and that test included on previous versions
too?
[-- Attachment #2: Type: text/html, Size: 1584 bytes --]
next prev parent reply other threads:[~2014-04-29 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 8:32 [gentoo-science] Locating ar Thomas Kahle
2014-04-29 11:23 ` François Bissey
2014-04-29 11:33 ` Thomas Kahle
2014-04-29 11:36 ` Panagiotis Christopoulos
2014-04-29 11:44 ` Panagiotis Christopoulos [this message]
2014-04-29 11:48 ` Thomas Kahle
2014-04-29 17:13 ` Panagiotis Christopoulos
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='CAF2cyYPdSRPrd=yirzcc=N6X+yLOdWvoKNPjxhRozaVKBvT3Pw@mail.gmail.com' \
--to=pxrist@gmail.com \
--cc=gentoo-science@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