From: Jeff Law <law@redhat.com>
To: Gerald Pfeifer <gerald@pfeifer.com>,
gcc@gcc.gnu.org, java@gcc.gnu.org,
David Malcolm <dmalcolm@redhat.com>
Subject: Re: GCC 5 fallout: libdata/pkgconfig/libgcj-5.0.pc
Date: Mon, 24 Nov 2014 16:28:00 -0000 [thread overview]
Message-ID: <54735CB3.8020104@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1411241700220.13258@tuna.site>
On 11/24/14 09:00, Gerald Pfeifer wrote:
> On Saturday 2014-08-23 12:38, Gerald Pfeifer wrote:
>> Packaging last week's GCC 5 snapshot, I ran into a couple of issues
>> due to the version number change.
>>
>> One is this: We are still creating libdata/pkgconfig/libgcj-5.0.pc
>> as we used to create libgcj-4.10.pc.
>>
>> Shouldn't that be libgcj-5.pc now?
>
> Ping.
>
> If it was 4.10 before, should it really not be just 5 now?
Yes. I wasn't even aware that we had a libgcj-<whatever>.pc
I guess I ought to eliminate my objection to bringing in pkg-config
dependencies into the JIT with that new knowledge. Though in the case
of libgcj we just install the file and don't, as far as I can tell,
actually depend on pkg-config.
jeff
prev parent reply other threads:[~2014-11-24 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-23 10:38 Gerald Pfeifer
2014-11-24 16:01 ` Gerald Pfeifer
2014-11-24 16:28 ` Jeff Law [this message]
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=54735CB3.8020104@redhat.com \
--to=law@redhat.com \
--cc=dmalcolm@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=java@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).