Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1711] New: Should libtool package install ltmain.sh into staging ?
Date: Thu,  6 May 2010 15:45:07 +0000 (UTC)	[thread overview]
Message-ID: <bug-1711-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=1711

           Summary: Should libtool package install ltmain.sh into staging
                    ?
           Product: buildroot
           Version: 2010.02
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: nick at leverton.org
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 1669
  --> https://bugs.busybox.net/attachment.cgi?id=1669
Patch to copy ltmain.sh to the staging area.

I'm no libtool expert and I'm struggling to adapt a couple of packages which
use it to Buildroot.  Instead trying to find the incompatibilities and then to
generate patches which mung the package's existing ltmain.sh, and which may
well break when the package is updated, I'd like to be able to copy in the
latest ltmain.sh, as is already done by gnuconfig for config.{guess,sub}.

At present I am doing this when required with a PACKAGE_POST_PATCH_HOOKS
target.  So there is no need to add extra Buildroot config items, potentially 
breaking other packages, as long as ltmain.sh is available in a known place.

If there's some reason why this is silly or otherwise not the best way to work,
I'd welcome any advice.  Otherwise please would you consider the attached patch
to add ltmain.sh to the libtool staging files ?

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2010-05-06 15:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06 15:45 bugzilla at busybox.net [this message]
2010-06-07 14:48 ` [Buildroot] [Bug 1711] Should libtool package install ltmain.sh into staging ? bugzilla at busybox.net
2010-06-07 22:04 ` bugzilla at busybox.net
2011-09-18 10:00 ` bugzilla at busybox.net

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=bug-1711-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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