From: ulf at uclibc.org <ulf@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/libmad
Date: Tue, 30 Oct 2007 23:40:36 -0700 (PDT) [thread overview]
Message-ID: <20071031064036.F3C42A65D5@busybox.net> (raw)
Author: ulf
Date: 2007-10-30 23:40:36 -0700 (Tue, 30 Oct 2007)
New Revision: 20347
Log:
update ltmain.sh in libmad by running libtoolize during build
Modified:
trunk/buildroot/package/libmad/libmad.mk
Changeset:
Modified: trunk/buildroot/package/libmad/libmad.mk
===================================================================
--- trunk/buildroot/package/libmad/libmad.mk 2007-10-31 06:38:59 UTC (rev 20346)
+++ trunk/buildroot/package/libmad/libmad.mk 2007-10-31 06:40:36 UTC (rev 20347)
@@ -36,8 +36,13 @@
)
touch $@
+# This rule runs 'libtoolize' since the ltmain.sh which comes in the tarball
+# is unsuitable with new libtool versions (causing shared libraries to build
+# without the .so extension).
+
$(LIBMAD_DIR)/libmad.la: $(LIBMAD_DIR)/.configured
rm -f $@
+ (cd $(LIBMAD_DIR); libtoolize --force)
$(MAKE) -C $(LIBMAD_DIR)
$(STAGING_DIR)/usr/lib/libmad.so: $(LIBMAD_DIR)/libmad.la
next reply other threads:[~2007-10-31 6:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 6:40 ulf at uclibc.org [this message]
2007-10-31 6:50 ` [Buildroot] svn commit: trunk/buildroot/package/libmad Hans-Christian Egtvedt
2007-10-31 7:03 ` Ulf Samuelsson
-- strict thread matches above, loose matches on Subject: below --
2007-11-27 21:44 ulf at uclibc.org
2007-11-27 21:40 ulf at uclibc.org
2007-11-02 22:37 ulf at uclibc.org
2007-08-28 19:35 ulf at uclibc.org
2007-08-28 19:33 ulf at uclibc.org
2007-08-01 22:34 ulf at uclibc.org
2007-07-28 17:09 ulf at uclibc.org
2007-07-28 16:49 ulf at uclibc.org
2007-07-23 7:57 ulf at uclibc.org
2007-05-10 8:10 jacmet at uclibc.org
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=20071031064036.F3C42A65D5@busybox.net \
--to=ulf@uclibc.org \
--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