From: Titus von Boxberg <titus@v9g.de>
To: crossgcc@sourceware.org
Cc: yann.morin.1998@anciens.enib.fr
Subject: [PATCH 2 of 6] configure: require libtoolize, create wrapper to it
Date: Mon, 22 Aug 2011 07:49:00 -0000 [thread overview]
Message-ID: <f9bee81aabe252b001ff.1313999264@mikulin.boxberg.lan> (raw)
In-Reply-To: <patchbomb.1313999262@mikulin.boxberg.lan>
# HG changeset patch
# User Titus von Boxberg <titus@v9g.de>
# Date 1313998831 -7200
# Node ID f9bee81aabe252b001ff70d40c0c061811011c05
# Parent b1be254591e7b524a0b06a2247a9331ebe0faf1d
configure: require libtoolize, create wrapper to it
libtoolize must be checked_for and there needs to be a wrapper
that points to GNU libtoolize since that may be installed
as glibtoolize.
This fixes a problem with building Cloog/PPL that was
Reported-by: "Pierrick Brossin"
Signed-off-by: "Titus von Boxberg" <titus@v9g.de>
diff -r b1be254591e7 -r f9bee81aabe2 Makefile.in
--- a/Makefile.in Mon Aug 22 09:41:35 2011 +0200
+++ b/Makefile.in Mon Aug 22 09:40:31 2011 +0200
@@ -50,16 +50,17 @@
LOCAL := @@LOCAL@@
# Paths found by ./configure
-install:= @@install@@
-bash := @@bash@@
-grep := @@grep@@
-make := @@make@@
-sed := @@sed@@
-libtool:= @@libtool@@
-objcopy:= @@objcopy@@
-objdump:= @@objdump@@
-readelf:= @@readelf@@
-patch := @@patch@@
+install := @@install@@
+bash := @@bash@@
+grep := @@grep@@
+make := @@make@@
+sed := @@sed@@
+libtool := @@libtool@@
+libtoolize:= @@libtoolize@@
+objcopy := @@objcopy@@
+objdump := @@objdump@@
+readelf := @@readelf@@
+patch := @@patch@@
# config options to push down to kconfig
KCONFIG:= @@KCONFIG@@
@@ -183,6 +184,7 @@
echo "export make=$(make)"; \
echo "export sed=$(sed)"; \
echo "export libtool=$(libtool)"; \
+ echo "export libtoolize=$(libtoolize)"; \
echo "export objcopy=$(objcopy)"; \
echo "export objdump=$(objdump)"; \
echo "export readelf=$(readelf)"; \
diff -r b1be254591e7 -r f9bee81aabe2 configure
--- a/configure Mon Aug 22 09:41:35 2011 +0200
+++ b/configure Mon Aug 22 09:40:31 2011 +0200
@@ -491,6 +491,10 @@
var=libtool \
ver='\(GNU libtool.*\) (2[[:digit:]]*\.|1\.6[[:digit:]]*\.|1\.5\.[2-9][[:digit:]]+)' \
err="'libtool' 1.5.26 or above was not found"
+has_or_abort prog=libtoolize \
+ var=libtoolize \
+ ver='\(GNU libtool.*\) (2[[:digit:]]*\.|1\.6[[:digit:]]*\.|1\.5\.[2-9][[:digit:]]+)' \
+ err="'libtoolize' 1.5.26 or above was not found"
has_or_abort prog=stat
has_or_abort prog="curl wget"
has_or_abort prog=patch
diff -r b1be254591e7 -r f9bee81aabe2 docs/C - Misc. tutorials.txt
--- a/docs/C - Misc. tutorials.txt Mon Aug 22 09:41:35 2011 +0200
+++ b/docs/C - Misc. tutorials.txt Mon Aug 22 09:40:31 2011 +0200
@@ -71,11 +71,12 @@
4) run ct-ng's configure with the following tool configuration
(assuming you have installed the tools via macports in /opt/local):
- ./configure --with-sed=/opt/local/bin/gsed \
- --with-libtool=/opt/local/bin/glibtool \
- --with-objcopy=/opt/local/bin/gobjcopy \
- --with-objdump=/opt/local/bin/gobjdump \
- --with-readelf=/opt/local/bin/greadelf \
+ ./configure --with-sed=/opt/local/bin/gsed \
+ --with-libtool=/opt/local/bin/glibtool \
+ --with-libtoolize=/opt/local/bin/glibtoolize \
+ --with-objcopy=/opt/local/bin/gobjcopy \
+ --with-objdump=/opt/local/bin/gobjdump \
+ --with-readelf=/opt/local/bin/greadelf \
[...other configure parameters as you like...]
5) proceed as described in standard documentation
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2011-08-22 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 7:49 [PATCH 0 of 6] reworked patch series Titus von Boxberg
2011-08-22 7:49 ` [PATCH 6 of 6] debug/ltrace: Fix HOST_OS and ar Titus von Boxberg
2011-08-22 7:49 ` Titus von Boxberg [this message]
2011-08-22 7:49 ` [PATCH 1 of 6] configure: fix --with-prog=[...] Titus von Boxberg
2011-08-22 7:49 ` [PATCH 3 of 6] libc/uClibc: portability fixes to install_headers Titus von Boxberg
2011-08-22 7:49 ` [PATCH 5 of 6] debug/gdb: correct compilation error when stpcpy is a define Titus von Boxberg
2011-08-22 7:56 ` [PATCH 4 of 6] docs: Document usage with Xcode 4.1 Titus von Boxberg
2011-08-22 15:26 ` [PATCH 0 of 6] reworked patch series Yann E. MORIN
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=f9bee81aabe252b001ff.1313999264@mikulin.boxberg.lan \
--to=titus@v9g.de \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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).