public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [RFC] Removing .la files from x86
Date: Wed, 03 Aug 2016 09:19:00 -0000	[thread overview]
Message-ID: <062647ee-734c-d868-589b-a5d32c6d4515@gmail.com> (raw)
In-Reply-To: <20160803080043.GA7388@calimero.vinschen.de>

On 03/08/2016 10:00, Corinna Vinschen wrote:
> On Aug  2 22:09, Yaakov Selkowitz wrote:
>> Libtool .la files are generally a waste of time and space.  They slow down
>> linking of other libraries with libtool, and they cause otherwise
>> unnecessary private dependencies to be pulled in by -devel packages.
>> Therefore, the major distros generally remove them from their packages
>> unless they are really necessary.
>>
>> When we first enabled Cygwin for x86_64, as we had no backwards
>> compatibility to worry about, I made removing all .la files the default.
>> AFAIK this has worked well, and any missing link libraries that the presence
>> thereof would have masked have already been fixed.
>>
>> In order to do the same for x86 without breaking builds of other packages,
>> AFAICS we would need a perpetual postinstall script which will continually
>> remove them.  The downside is that (unless the script is made a *LOT* more
>> complicated) a number of -devel packages will show up as "Incomplete" until
>> such time they are rebuilt with a new version of cygport.
>>
>> Any objections?
>
> User confusion about incomplete packages?
>
> What I wonder is, if cygport builds don't create/install .la files
> anymore, don't we end up without them at one point anyway?  Isn't it
> sufficient if they go away over time?
>
>
> Corinna

I prefer just the change in cygport behaviour.

Please note we have still some *.la files on x86_64
for other reasons and we can not run an indiscriminate prune
on x86.

  $ ls -1 /usr/lib/*.la
/usr/lib/libguilereadline-v-17.la
/usr/lib/libguilereadline-v-18.la
/usr/lib/libguile-srfi-srfi-13-14-v-3.la
/usr/lib/libguile-srfi-srfi-1-v-3.la
/usr/lib/libguile-srfi-srfi-4-v-3.la
/usr/lib/libguile-srfi-srfi-60-v-2.la
/usr/lib/libltdl.la
/usr/lib/libntl.la

Regards
Marco

  reply	other threads:[~2016-08-03  9:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03  3:11 Yaakov Selkowitz
2016-08-03  4:16 ` Warren Young
2016-08-03  8:00 ` Corinna Vinschen
2016-08-03  9:19   ` Marco Atzeri [this message]
2016-08-03 15:58     ` Yaakov Selkowitz

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=062647ee-734c-d868-589b-a5d32c6d4515@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin-apps@cygwin.com \
    /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).