From: Andreas Rottmann <a.rottmann@gmx.at>
To: David Pirotte <david@altosw.be>
Cc: guile-devel@gnu.org
Subject: Re: no more *.la files in libgc-dev
Date: Thu, 30 Jun 2011 11:27:41 +0200 [thread overview]
Message-ID: <87sjqrvfci.fsf@rotty.yi.org> (raw)
In-Reply-To: <20110629232723.01dbf84c@rascar> (David Pirotte's message of "Wed, 29 Jun 2011 23:27:23 -0300")
David Pirotte <david@altosw.be> writes:
> Le Sun, 26 Jun 2011 22:15:23 +0200,
> Andreas Rottmann <a.rottmann@gmx.at> a écrit :
>
> ...
>> The solution (other than just removing the offending .la files) would be to
>> re-build and re-install all software depending on libgc-dev, including
>> g-wrap, as to get rid of the stale references to libgc's .la file.
>>
>> [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625187
>>
>> Regards, Rotty
>
> Hello Andreas,
>
> Thanks your explanation. Though I just uninstalled rebuilt/installed g-wrap
> [v1.9.13-13-geeb1aae for guile-gnome-platform compatibility issues] and
> 'it' did build/install .la files: missing something?
>
No, that's expected: .la files are still built and installed by the
(upstream) G-Wrap, it's just that the corresponding Debian package
doesn't contain them anymore -- getting rid of .la files is a Debian
packaging thing, no change to upstream code or build system is made.
Regards, Rotty
--
Andreas Rottmann -- <http://rotty.yi.org/>
prev parent reply other threads:[~2011-06-30 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 17:00 no more *.la files in libgc-dev David Pirotte
2011-06-26 20:15 ` Andreas Rottmann
2011-06-28 14:49 ` Ludovic Courtès
2011-06-30 2:27 ` David Pirotte
2011-06-30 9:27 ` Andreas Rottmann [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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sjqrvfci.fsf@rotty.yi.org \
--to=a.rottmann@gmx.at \
--cc=david@altosw.be \
--cc=guile-devel@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).