From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: Experimenting with reduced gcc-lib
Date: Mon, 19 Dec 2022 22:14:26 +0100 [thread overview]
Message-ID: <87ili7cczx.fsf@gnu.org> (raw)
In-Reply-To: <3059C8A7-7F80-406A-84F0-DAE02D7D6D75@lepiller.eu> (Julien Lepiller's message of "Thu, 15 Dec 2022 17:59:38 +0100")
Hi!
Julien Lepiller <julien@lepiller.eu> skribis:
> Le 15 décembre 2022 15:34:02 GMT+01:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
>>> (outputs '("out" ;commands, etc. (60+ MiB)
>>> - "lib" ;libgcc_s, libgomp, etc. (15+ MiB)
>>> + "shared-lib" ;libgcc_s, libgomp, etc. (5+ MiB)
>>> + "static-lib" ;object code libraries and internal data files of GCC. (10+ MiB)
>>
>>The convention is to use “lib” for shared libraries and “static” for
>>static libraries.
>
> But using lib introduces a --libdir argument which is used to install static libs…
I see. Then maybe we should override the ‘configure’ phase, or repeat
‘--libdir’ in the hope that the second one wins?
>>Is libgomp in “lib”? Is it found when linking with ‘-fopenmp’?
>
> Well, shared-lib should be renaimed into libgcc, because it's the only library there.
OK.
> Libgomp amd all other libs are in static-lib (which is not well named either ^^'). It will be found I think but not tested (it find libstdc++ in the same directory).
Heh. :-)
I think it would be great to have all the .a in a separate output.
Thanks,
Ludo’.
prev parent reply other threads:[~2022-12-19 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 21:32 Experimenting with reduced gcc-lib Julien Lepiller
2022-12-15 14:34 ` Ludovic Courtès
2022-12-15 16:59 ` Julien Lepiller
2022-12-19 21:14 ` Ludovic Courtès [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ili7cczx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).