public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: IainS <developer@sandoe-acoustics.co.uk>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Where should libiberty.a be installed?
Date: Tue, 03 Jun 2008 15:25:00 -0000	[thread overview]
Message-ID: <25449091-873F-412F-81A7-134CF902EE8A@sandoe-acoustics.co.uk> (raw)
In-Reply-To: <e43ccaafe4aa34555bbaa0717bc947b3@kernel.crashing.org>


On 3 Jun 2008, at 15:30, Segher Boessenkool wrote:

>>>> libiberty.a ends up in /usr/lib (and the multilib in /usr/lib/ 
>>>> ppc64)
>>>
>>>> This appears to be ignoring the "--enable-version-specific- 
>>>> runtime-libs" flags (which is honored AFAICT by all the other  
>>>> libs).
>>>
>>> libiberty is not a runtime library.
>>
>> I appreciate this, however, libiberty *is* installed into the  
>> user's DESTDIR.
>
> Yes.  However, it (the installed libiberty.a) isn't used by any of the
> installed GCC binaries, so it doesn't cause problems there.
>
> OTOH, like I said, why is it installed at all by default?  Its header
> files are not, so this would seem pretty useless.

agreed,  either both lib/header or neither...

Note that (gcc) "make install-html" installs "libiberty.html" into  
the doc dirs which says (amongst other things):

-- that the library is used by "various GNU programs"

--  " Passing --enable-install-libiberty to the configure script when  
building libiberty causes the header files and archive library to be  
installed when make install is run. 
This option also takes an (optional) argument to specify the  
installation location, in the same manner as --prefix."

I've not used that configure argument to gcc [ it's not listed by  
(gcc) configure --help  or on  http://gcc.gnu.org/install/ 
configure.html  ] so presumably the html refers only to building the  
library as a separate project.

I'd add my £0.02 - and say if it's installed at all - it would make  
sense for it to be installed along with the other gcc-version- 
specific .a files in lib/gcc/X.Y.Z
That way the user can keep track of which version is being linked.

Iain

  reply	other threads:[~2008-06-03 15:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 19:30 IainS
2008-06-03  0:42 ` Segher Boessenkool
2008-06-03  6:55   ` IainS
2008-06-03 14:30     ` Segher Boessenkool
2008-06-03 15:25       ` IainS [this message]
2008-06-03 15:53         ` Brian Dessent
2008-06-03 16:22           ` IainS
2008-06-03 17:19           ` Where should libiberty.a be installed? (addendum) IainS

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=25449091-873F-412F-81A7-134CF902EE8A@sandoe-acoustics.co.uk \
    --to=developer@sandoe-acoustics.co.uk \
    --cc=gcc-help@gcc.gnu.org \
    --cc=segher@kernel.crashing.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).