public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Uwe Papengut <uwe.papengut@t-online.de>
To: tvb377@gmx.de
Cc: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>,
	 crossgcc@sourceware.org
Subject: Building toolchain with crosstool-ng on Mac OS X 10.6.2 (SL) - libtool error
Date: Tue, 02 Feb 2010 15:18:00 -0000	[thread overview]
Message-ID: <1997A397-80B0-4ABE-86FA-00A504527153@t-online.de> (raw)
In-Reply-To: <20100201022556.48790@gmx.net>

[-- Attachment #1: Type: text/plain, Size: 352 bytes --]

Hi Titus, Yann and all,

I wrote a short script for MacOS SL and crosstool-ng-1.6.0. I got an error with libtool, because the crosstool-ng/configure wrote:

  Checking for 'libtool'... no
  libtool 1.5.26 or above was not found

I used the newest version of libtool 2.2.6b_0. Script and log-file see attachment.

Can anyone please help me?


[-- Attachment #2: MacOS_SL --]
[-- Type: application/octet-stream, Size: 851 bytes --]

echo "1.Update Port."
echo "=============="
sudo port -v selfupdate
sudo port upgrade outdated
echo " "
echo "2. Change to Source-Directory."
echo "=============================="
cd /Users/uwepapengut/Desktop/Crosstool/crosstool-ng-1.6.0
echo " "
echo "3. Install ports crosstool-ng."
echo "==============================="
sudo port install lzmautils
sudo port install libtool
sudo port install binutils
sudo port install gsed
sudo port install gawk
echo " "
echo "4. Show versions."
echo "================="
port installed
echo " "
echo "5. Configure crosstool_ng."
echo "=========================="
./configure --prefix=/Users/uwepapengut/Desktop/Crosstool/XXX --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

[-- Attachment #3: MacOS_SL.log --]
[-- Type: application/octet-stream, Size: 2795 bytes --]

1.Update Port.
==============
--->  Updating the ports tree
Synchronizing local ports tree from rsync://rsync.macports.org/release/ports/
receiving file list ... done
archivers/lzmautils/
devel/binutils/
devel/libtool/
lang/gawk/
textproc/gsed/

sent 66 bytes  received 432006 bytes  66472.62 bytes/sec
total size is 28020898  speedup is 64.85
--->  Updating MacPorts base sources using rsync
receiving file list ... done

sent 36 bytes  received 6893 bytes  2771.60 bytes/sec
total size is 4023490  speedup is 580.67
MacPorts base version 1.8.2 installed,
MacPorts base version 1.8.2 downloaded.
--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you should run
  port upgrade outdated
 
2. Change to Source-Directory.
==============================
 
3. Install ports crosstool-ng.
===============================
--->  Computing dependencies for lzmautils
--->  Cleaning lzmautils
--->  Computing dependencies for libtool
--->  Cleaning libtool
--->  Computing dependencies for binutils
--->  Cleaning binutils
--->  Computing dependencies for gsed
--->  Cleaning gsed
--->  Computing dependencies for gawk
--->  Cleaning gawk
 
4. Show versions.
=================
The following ports are currently installed:
  autoconf @2.65_0
  autoconf @2.65_1 (active)
  automake @1.11.1_0 (active)
  binutils @2.20_1 (active)
  expat @2.0.1_0 (active)
  gawk @3.1.7_0 (active)
  gettext @0.17_4 (active)
  gperf @3.0.4_0 (active)
  gsed @4.2.1_0 (active)
  help2man @1.37.1_1 (active)
  libiconv @1.13_0
  libiconv @1.13.1_0 (active)
  libidn @1.15_0 (active)
  libtool @2.2.6b_0 (active)
  lzmautils @4.32.7_1 (active)
  m4 @1.4.13_0 (active)
  ncurses @5.7_0+darwin_10 (active)
  ncursesw @5.7_0+darwin_10 (active)
  openssl @0.9.8l_0+darwin (active)
  p5-locale-gettext @1.05_0
  p5-locale-gettext @1.05_2 (active)
  perl5 @5.8.9_0 (active)
  perl5.8 @5.8.9_3 (active)
  wget @1.12_0 (active)
  zlib @1.2.3_3
  zlib @1.2.3_4 (active)
 
5. Configure crosstool_ng.
==========================
Checking for 'grep'... /usr/bin/grep
Checking whether '/usr/bin/grep' supports -E... yes
Checking for 'sed'... /opt/local/bin/gsed (cached)
Checking for 'bash'... /bin/bash
Checking for 'cut'... /usr/bin/cut
Checking for 'install'... /usr/bin/install
Checking for 'make'... /usr/bin/make
Checking for 'gcc'... /usr/bin/gcc
Checking for 'awk'... no
Checking for 'gawk'... /opt/local/bin/gawk
Checking for 'bison'... /usr/bin/bison
Checking for 'flex'... /usr/bin/flex
Checking for 'makeinfo'... /usr/bin/makeinfo
Checking for 'automake'... /opt/local/bin/automake
Checking for 'libtool'... no

libtool 1.5.26 or above was not found

Either you are missing entirely the needed tool,
or the version you have is too old.

configure: Bailing out...

[-- Attachment #4: Type: text/plain, Size: 2578 bytes --]



Best Regards,
Uwe




Am 01.02.2010 um 03:25 schrieb tvb377@gmx.de:

>>> I recently made a patch for using crosstool-ng on mac and freebsd.
>>> I will rework the cosmetics according to Yann's comments this month.
>> 
>> Titus, I think you are the one that can handle this stuff, as you have a
> 
> Uwe, Yann, all
> 
> here is the reworked patch for crosstool-ng on FreeBSD and MacOS against a current (31 January 23:00 CET) version.
> And two new READMEs (instead of docs/MacOS-X.txt).
> 
> Almost all patch parts revolve around GNU/BSD incompatibilities.
> I try to explain what I did:
> - enlarge the list of configurable tools that ctng uses (for usage of GNU tools).
> - also make sure that the configured tools actually get used.
> - make all calls to stat(1) dependent to `uname -s` or replace the call.
> - replace all calls to readlink(1GNU) with compatible variants.
>  This makes the usage of wrapper.c mandatory on MacOS because there is no way known to me emulating readlink -m without a lengthy shell script.
> - uname -o is not portable. use -s when -o fails
> - a bug in the sed-expression that sets the nanoseconds to 0 for a date(1) not handling %N
> 
> Notable other reasons besides GNU/BSD are:
> - have to compile mpfr with --disable-thread-safe on darwin.
> - "You did not specify the build system. That's OK, I can guess...":
>  Under MacOS 10.6 gcc reports itself as "i686-apple-..."
>  However, it's default behaviour is to generate 64bit objects.
>  This clashes with some configure scripts that require "x86_64-..." for configuring for a 64bit host.
>  Using CT_DoConfigGuess does the job correctly.
>  Why not use that in general?
> BTW, the above two changes are the only changes actually for BUILDING the toolchain, and not for porting ctng itself.
> - the compiler command line options for compiling wrapper.c crashes gcc on MacOS (and IMHO were a little bit overdone for the complexity of wrapper.c).
> - you should not link statically on MacOS (wrapper.c command line again)
> - under Darwin, use DYLD_LIBRARY_PATH in wrapper.c
> - added printenv to the build.log (I found that helpful).
> 
> I can now compile gcc4.4.2 for powerpc for linux/glibc under Linux, BSD, and MacOS.
> I only shortly grepped through scripts not necessary for this configuration, so more incompatibilities may arise. However, they should be easy to fix in this manner.
> 
> Hope this helps.
> Further comments are welcome.
> 
> Regards
> Titus
> <ct-ng-bsdpatch.txt><README.freebsd><README.macos>










[-- Attachment #5: Type: text/plain, Size: 71 bytes --]

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2010-02-02 15:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01  2:26 Help with Building toolchain with crosstool-ng on Mac OS X 10.6.2 (Snow Leopard) tvb377
2010-02-02 15:18 ` Uwe Papengut [this message]
2010-02-02 20:02   ` Building toolchain with crosstool-ng on Mac OS X 10.6.2 (SL) - libtool error Titus von Boxberg
2010-02-02 18:16 ` Help with Building toolchain with crosstool-ng on Mac OS X 10.6.2 (Snow Leopard) 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=1997A397-80B0-4ABE-86FA-00A504527153@t-online.de \
    --to=uwe.papengut@t-online.de \
    --cc=crossgcc@sourceware.org \
    --cc=tvb377@gmx.de \
    --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).