From: Gaius Mulley <gaius.mulley@southwales.ac.uk>
To: Matthias Klose <doko@ubuntu.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, Modula-2 (C/C++/D/F/Go/Jit)] (Register spec fn) (v2)
Date: Wed, 10 Jul 2019 20:49:00 -0000 [thread overview]
Message-ID: <87y315vct8.fsf@j228-gm.comp.glam.ac.uk> (raw)
In-Reply-To: <8681ab8d-1b67-7ee6-1cd2-d8cbb8ca937b@ubuntu.com> (Matthias Klose's message of "Wed, 10 Jul 2019 18:53:32 +0200")
Matthias Klose <doko@ubuntu.com> writes:
>>> - The internal tools in the gcclibdir are installed twice, with
>>> both vanilla names and prefixed/suffixed names.
>>> The installed tree:
>>>
>>> ./usr/bin
>>> ./usr/bin/x86_64-linux-gnu-gm2-9
>>> ./usr/bin/x86_64-linux-gnu-gm2m-9
>>> ./usr/lib/gcc/x86_64-linux-gnu
>>> ./usr/lib/gcc/x86_64-linux-gnu/9
>>> ./usr/lib/gcc/x86_64-linux-gnu/9/cc1gm2
>>> ./usr/lib/gcc/x86_64-linux-gnu/9/gm2l
>>> ./usr/lib/gcc/x86_64-linux-gnu/9/gm2lcc
>>> ./usr/lib/gcc/x86_64-linux-gnu/9/gm2lgen
>>> ./usr/lib/gcc/x86_64-linux-gnu/9/gm2lorder
>>> ./usr/lib/gcc/x86_64-linux-gnu/9/x86_64-linux-gnu-cc1gm2-9
>>> ./usr/lib/gcc/x86_64-linux-gnu/9/x86_64-linux-gnu-gm2l-9
>>> ./usr/lib/gcc/x86_64-linux-gnu/9/x86_64-linux-gnu-gm2lcc-9
>>> ./usr/lib/gcc/x86_64-linux-gnu/9/x86_64-linux-gnu-gm2lgen-9
>>> ./usr/lib/gcc/x86_64-linux-gnu/9/x86_64-linux-gnu-gm2lorder-9
>>> ./usr/lib/gcc/x86_64-linux-gnu/9/x86_64-linux-gnu-gm2m-9
>>
>> With a fresh build, configured with
>>
>> --program-suffix=-9
>> --program-prefix=x86_64-linux-gnu-
>>
>> the latter set of internal binaries is installed, while I would expect just the
>> un-pre/post-fixed tool names.
>
> fixed by the attached patch.
Hi Matthias,
thank you - I think we were both working on the same code at the same
time! I've checked in some fixes to both the master gm2/Make-lang.in
(and 9.1.0 branch). I've culled gm2m from /usr/bin and relegated it to
libexecsubdir,
regards,
Gaius
next prev parent reply other threads:[~2019-07-10 20:45 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 13:10 Gaius Mulley
2019-06-29 10:15 ` Richard Sandiford
2019-06-29 12:52 ` Richard Biener
2019-06-29 20:29 ` Gaius Mulley
2019-06-29 18:08 ` Segher Boessenkool
2019-07-02 0:18 ` Gaius Mulley
2019-07-03 8:41 ` Rainer Orth
2019-07-08 15:20 ` Gaius Mulley
2019-07-08 15:31 ` Rainer Orth
2019-07-09 9:25 ` Rainer Orth
2019-07-09 11:41 ` Gaius Mulley
2019-07-10 11:50 ` Rainer Orth
2019-07-08 15:41 ` Gaius Mulley
2019-07-08 21:21 ` Matthias Klose
2019-07-09 6:37 ` Matthias Klose
2019-07-09 19:50 ` Gaius Mulley
2019-07-09 21:35 ` Matthias Klose
2019-07-10 17:56 ` Matthias Klose
2019-07-10 20:18 ` Gaius Mulley
2019-07-10 20:38 ` Matthias Klose
2019-07-10 21:16 ` Gaius Mulley
2019-07-09 9:56 ` Matthias Klose
2019-07-09 12:14 ` Gaius Mulley
2019-07-09 13:24 ` Matthias Klose
2019-07-09 13:49 ` Gaius Mulley
2019-07-09 16:23 ` Matthias Klose
2019-07-09 17:22 ` Gaius Mulley
2019-07-09 12:31 ` Rainer Orth
2019-07-09 15:57 ` Gaius Mulley
2019-07-09 17:32 ` Matthias Klose
2019-07-10 20:45 ` Gaius Mulley
2019-07-10 12:11 ` Rainer Orth
2019-07-09 21:36 ` Matthias Klose
2019-07-10 17:11 ` Matthias Klose
2019-07-10 20:49 ` Gaius Mulley [this message]
2019-07-11 7:57 ` Matthias Klose
2019-07-11 12:12 ` Gaius Mulley
2019-07-11 16:40 ` Segher Boessenkool
2019-07-11 17:26 ` Gaius Mulley
2019-07-12 15:41 ` Segher Boessenkool
2019-07-12 18:35 ` Gaius Mulley
2019-07-18 20:15 ` Matthias Klose
2019-11-20 10:10 ` Gaius Mulley
2019-07-19 14:22 ` Matthias Klose
2019-07-20 21:41 ` 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=87y315vct8.fsf@j228-gm.comp.glam.ac.uk \
--to=gaius.mulley@southwales.ac.uk \
--cc=doko@ubuntu.com \
--cc=gcc-patches@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).