From: Matthias Klose <doko@ubuntu.com>
To: Gaius Mulley <gaius.mulley@southwales.ac.uk>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, Modula-2 (C/C++/D/F/Go/Jit)] (Register spec fn) (v2)
Date: Tue, 09 Jul 2019 13:24:00 -0000 [thread overview]
Message-ID: <2aa1013d-ee7c-efa5-52b6-36005e60c34d@ubuntu.com> (raw)
In-Reply-To: <87ef2zct5f.fsf@j228-gm.comp.glam.ac.uk>
On 09.07.19 14:02, Gaius Mulley wrote:
> Matthias Klose <doko@ubuntu.com> writes:
>
>>> - There are three letter libraries with pretty generic
>>> names installed into the system libdir: log, iso, cor,
>>> min, ulm. At least for log, you have a file conflict
>>> with another library. Shouldn't these libraries named
>>> mpre specific, like libgm2log?
>
>>> The installed tree:
>>
>>> ./usr/lib/gcc/x86_64-linux-gnu/9/m2/ulm/libulm.a
>>> ./usr/lib/x86_64-linux-gnu/libulm.a
>>
>> and all static libraries are installed twice, not just libulm.a. What is the
>> correct location?
>>
>> Matthias
>
> Hi Matthias,
>
> the libraries ./usr/lib/x86_64-linux-gnu/lib{ulm,pim,gm2,cor,iso,min}.a
> are not needed the correct locations of the static libraries are:
>
> ./usr/lib/gcc/x86_64-linux-gnu/9/m2/ulm/libulm.a
> ./usr/lib/gcc/x86_64-linux-gnu/9/m2/min/libmin.a
> ./usr/lib/gcc/x86_64-linux-gnu/9/m2/cor/libcor.a
> ./usr/lib/gcc/x86_64-linux-gnu/9/m2/pim/libgm2.a
> ./usr/lib/gcc/x86_64-linux-gnu/9/m2/log/liblog.a
> ./usr/lib/gcc/x86_64-linux-gnu/9/m2/iso/libiso.a
ok, then I assume that could be the place for the .so files as well (not the
.so.* files/links), if I don't want to install those in the system libdir.
next prev parent reply other threads:[~2019-07-09 13:19 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 [this message]
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
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=2aa1013d-ee7c-efa5-52b6-36005e60c34d@ubuntu.com \
--to=doko@ubuntu.com \
--cc=gaius.mulley@southwales.ac.uk \
--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).