From: Matthias Klose <doko@ubuntu.com>
To: Meador Inge <meadori@codesourcery.com>
Cc: Richard Biener <richard.guenther@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] gcc-{ar,nm,ranlib}: Find binutils binaries relative to self
Date: Wed, 19 Jun 2013 12:03:00 -0000 [thread overview]
Message-ID: <51C19E16.5040305@ubuntu.com> (raw)
In-Reply-To: <50B502F9.8020901@codesourcery.com>
Am 27.11.2012 19:14, schrieb Meador Inge:
> On 11/26/2012 09:05 AM, Richard Biener wrote:
>
>> On Wed, Nov 7, 2012 at 10:51 PM, Meador Inge <meadori@codesourcery.com> wrote:
>>> Ping ^ 4.
>>
>> Ok.
>
> Thanks for the review. Committed to trunk.
This did break gcc-ar and gcc-nm; now a regression on the 4.8 branch.
$ gcc-ar-4.8 -h
gcc-ar-4.8: Cannot find plugin 'liblto_plugin.so'
the plugin is *not* installed with x permission flags (which seems to be the
standard for shared libraries). You did change the code to use find_a_file
which searches only for files with the x bit set.
Work around is to install the plugin with the x bits set, or use some helper
function which doesn't look for the x bits. I assume that wasn't catched,
because the plugin then was found in another location?
Matthias
next prev parent reply other threads:[~2013-06-19 12:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 20:46 Meador Inge
2012-10-10 2:47 ` Meador Inge
2012-10-18 15:39 ` Meador Inge
2012-10-18 19:08 ` Bernhard Reutner-Fischer
2012-10-19 21:55 ` Meador Inge
2012-10-19 22:26 ` Meador Inge
2012-10-29 16:10 ` Meador Inge
2012-11-07 21:51 ` Meador Inge
2012-11-26 15:06 ` Richard Biener
2012-11-27 18:14 ` Meador Inge
2013-06-19 12:03 ` Matthias Klose [this message]
2013-06-19 12:10 ` Jakub Jelinek
2013-06-19 15:29 ` Matthias Klose
2013-06-19 17:47 ` Jakub Jelinek
2013-06-19 20:58 ` Matthias Klose
2013-06-19 12:20 ` Matthias Klose
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=51C19E16.5040305@ubuntu.com \
--to=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meadori@codesourcery.com \
--cc=richard.guenther@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).