public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Please review: function epunt_la_files for eutils.eclass
Date: Sun, 9 Nov 2008 17:48:39 +0100	[thread overview]
Message-ID: <20081109164839.GM23310@gentoo.org> (raw)
In-Reply-To: <200811091734.35331.loki_val@gentoo.org>

On 09-11-2008 18:34:31 +0200, Peter Alfredsen wrote:
> On Sunday 09 November 2008, Fabian Groffen wrote:
> > On 09-11-2008 18:04:05 +0200, Peter Alfredsen wrote:
> > > +	# If this is a non-ELF system, chances are good that the .la
> > > files will be needed. +	if type -P scanelf &> /dev/null
> >
> > I think this is a not so cool way to check for an ELF system.
> 
> Indeed, I think it's a horrid way. Please find a better one.

% uname -a
Darwin tefnut.cheops.ods.org 8.11.0 Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC Power Macintosh powerpc PowerMac8,2 Darwin
% scanelf --version
pax-utils-0.1.18_pre0004: scanelf.c compiled Oct 19 2008
$Id: scanelf.c,v 1.194 2008/09/29 06:05:55 vapier Exp $
scanelf written for Gentoo by <solar and vapier @ gentoo.org>
% scanmacho --version
pax-utils-0.1.18_pre0004: scanmacho.c compiled Oct 19 2008
$Id: scanmacho.c,v 1.5 2008/10/19 18:11:59 grobian Exp $
scanmacho written for Gentoo by <solar, vapier and grobian @ gentoo.org>

You could identify ELF a bit more reliable by running file on e.g.
"${ROOT}/bin/bash", or just by building a list of CHOSTs that you know
are ELF systems.

> > > +		debug-print "scanelf not found, this appears to be a non-ELF
> > > system." +		debug-print "non-ELF systems are likely to need .la
> > > files." +		debug-print ".la files not removed from ${TARGET}"
> >
> > rationale?
> 
> "I've been told" that .la files are really only needed on non-ELF 
> systems and with plugin systems that use dlopen. I actually have no way 
> of knowing that the .la files are needed on those arches, but I had 
> your archs in mind when doing the patch.

Ok.  What worries me though is that this would result in some systems
having libtool files whereas the majority does not.  E.g. removing them
apparently fixes a problem that then crops up on those systems or
something.  Can't think of any atm.


-- 
Fabian Groffen
Gentoo on a different level



  reply	other threads:[~2008-11-09 16:48 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-09 16:04 [gentoo-dev] Please review: function epunt_la_files for eutils.eclass Peter Alfredsen
2008-11-09 16:10 ` Fabian Groffen
2008-11-09 16:34   ` Peter Alfredsen
2008-11-09 16:48     ` Fabian Groffen [this message]
2008-11-09 17:46       ` Peter Alfredsen
2008-11-09 17:53         ` Fabian Groffen
2008-11-12 13:41     ` Mart Raudsepp
2008-11-12 14:40       ` Peter Alfredsen
2008-11-12 16:14         ` Rémi Cardona
2008-11-12 17:16           ` Peter Alfredsen
2008-11-13  6:21             ` Donnie Berkholz
2008-11-14 10:35             ` Gilles Dartiguelongue
2008-11-14 17:28               ` Marius Mauch
2008-11-14 14:25             ` Alexis Ballier
2008-11-14 14:35               ` Rémi Cardona
2008-11-16  8:44                 ` Michael Haubenwallner
2008-11-16 22:21                   ` Rémi Cardona
2008-11-14 22:31               ` Donnie Berkholz
2008-11-14 22:33                 ` Ciaran McCreesh
2008-11-14 22:44               ` David Leverton
2008-11-12 16:53         ` Mart Raudsepp
2008-11-12 17:31           ` Peter Alfredsen
2008-11-13 18:49             ` [gentoo-dev] " Ryan Hill
2008-11-14  4:14             ` Ryan Hill
2008-11-14 23:05               ` Peter Alfredsen
2008-11-14 23:25                 ` Ciaran McCreesh
2008-11-15  0:26                 ` Mart Raudsepp
2008-11-15  6:44                   ` Duncan
2008-11-17 19:19                 ` [gentoo-dev] " Steve Long
2008-11-12 15:52     ` [gentoo-dev] " Donnie Berkholz
2008-11-12 16:24       ` Peter Alfredsen
2008-11-13  6:23         ` Donnie Berkholz

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=20081109164839.GM23310@gentoo.org \
    --to=grobian@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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