crosstool-ng on Mac OS X 10.6.2 (Snow Leopard) and issue with mpfr

[Uwe Papengut <uwe dot papengut at t-online dot de>]

Hello Titus, hello all,

thanks for the quick help. In past if I build ct-ng I got the uname-warning and then an error with
the filesystem, because my file-system wasn't complete case sensitiv. I fixed this problem.

My new problem is with build-command is "mpfr":

----------------------------------------------------------------------------------------

mac-mini:ct-ng uwepapengut$ ct-ng -d build
GNU Make 3.81
Copyright (C) 2006  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

This program built for i386-apple-darwin10.0
Reading makefiles...
Reading makefile `/Volumes/ct-ng/x-tool/bin/ct-ng'...
Reading makefile `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/paths.mk' (search path) (no ~ expansion)...
Reading makefile `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/config/config.mk' (search path) (no ~ expansion)...
Reading makefile `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/kconfig/kconfig.mk' (search path) (no ~ expansion)...
Reading makefile `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/steps.mk' (search path) (no ~ expansion)...
Reading makefile `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/samples/samples.mk' (search path) (no ~ expansion)...
Reading makefile `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/scripts/scripts.mk' (search path) (no ~ expansion)...
Updating makefiles....
 Considering target file `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/scripts/scripts.mk'.
  Looking for an implicit rule for `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/scripts/scripts.mk'.
  No implicit rule found for `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/scripts/scripts.mk'.
  Finished prerequisites of target file `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/scripts/scripts.mk'.
 No need to remake target `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/scripts/scripts.mk'.
 Considering target file `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/samples/samples.mk'.
  Looking for an implicit rule for `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/samples/samples.mk'.
  No implicit rule found for `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/samples/samples.mk'.
  Finished prerequisites of target file `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/samples/samples.mk'.
 No need to remake target `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/samples/samples.mk'.
 Considering target file `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/steps.mk'.
  Looking for an implicit rule for `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/steps.mk'.
  No implicit rule found for `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/steps.mk'.
  Finished prerequisites of target file `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/steps.mk'.
 No need to remake target `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/steps.mk'.
 Considering target file `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/kconfig/kconfig.mk'.
  Looking for an implicit rule for `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/kconfig/kconfig.mk'.
  No implicit rule found for `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/kconfig/kconfig.mk'.
  Finished prerequisites of target file `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/kconfig/kconfig.mk'.
 No need to remake target `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/kconfig/kconfig.mk'.
 Considering target file `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/config/config.mk'.
  Looking for an implicit rule for `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/config/config.mk'.
  No implicit rule found for `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/config/config.mk'.
  Finished prerequisites of target file `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/config/config.mk'.
 No need to remake target `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/config/config.mk'.
 Considering target file `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/paths.mk'.
  Looking for an implicit rule for `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/paths.mk'.
  No implicit rule found for `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/paths.mk'.
  Finished prerequisites of target file `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/paths.mk'.
 No need to remake target `/Volumes/ct-ng/x-tool/lib/ct-ng-1.6.0/paths.mk'.
 Considering target file `/Volumes/ct-ng/x-tool/bin/ct-ng'.
  Looking for an implicit rule for `/Volumes/ct-ng/x-tool/bin/ct-ng'.
  No implicit rule found for `/Volumes/ct-ng/x-tool/bin/ct-ng'.
  Finished prerequisites of target file `/Volumes/ct-ng/x-tool/bin/ct-ng'.
 No need to remake target `/Volumes/ct-ng/x-tool/bin/ct-ng'.
Updating goal targets....
Considering target file `build'.
 File `build' does not exist.
  Considering target file `.config'.
   Finished prerequisites of target file `.config'.
  No need to remake target `.config'.
 Finished prerequisites of target file `build'.
Must remake target `build'.
Putting child 0x100121ab0 (build) PID 7268 on the chain.
Live child 0x100121ab0 (build) PID 7268 
[INFO ]  Performing some trivial sanity checks
[INFO ]  Build started 20100207.111226
[INFO ]  Building environment variables
[00:01] / uname: illegal option -- o
usage: uname [-amnprsv]
[WARN ]  You did not specify the build system. That's OK, I can guess...
[INFO ]  =================================================================
[INFO ]  Retrieving needed toolchain components' tarballs
[ERROR]    Could not retrieve 'mpfr-2.4.1'.
[04:29] / Reaping losing child 0x100121ab0 PID 7268 
make: *** [build] Error 1
Removing child 0x100121ab0 PID 7268 from chain.
mac-mini:ct-ng uwepapengut$ 


----------------------------------------------------------------------------------------
I run the "build-mpfr-on-darwin.patch" succesfully and I used mpfr-2.4.2 and mpfr-2.4.1 and got the same error.

Can anyone help me again, please?

Best Regards,
Uwe



> 
> An: crossgcc@sourceware.org
> Betreff: crosstool-ng on Mac OS X 10.6.2 (Snow Leopard) and issue with uname
> 
> 
> 
> Hello,
> 
> I used the description from titus to build toolchain on Mac OS X SL. I used crosstool-ng 1.6.0.
> 
> Everything worked fine until I start "ct-ng build" on my case sensitive file-system.
> I got this output:
> 
> mac-mini:dxdx uwepapengut$ ct-ng build
> [INFO ]  Performing some trivial sanity checks
> [INFO ]  Build started 20100204.190640
> [INFO ]  Building environment variables
> [00:01] / uname: illegal option -- o
> usage: uname [-amnprsv]
> 
> In which file can I found the wrong command "uname -o..."?
> 
> Best Regards,
> Uwe
> 
> 
> 
> 
> 
> Von: Khem Raj <raj.khem@gmail.com>
> Datum: 4. Februar 2010 21:34:39 MEZ
> An: Uwe Papengut <uwe.papengut@t-online.de>
> Kopie: crossgcc@sourceware.org
> Betreff: Re: crosstool-ng on Mac OS X 10.6.2 (Snow Leopard) and issue with uname
> 
> 
> On Thu, Feb 4, 2010 at 10:12 AM, Uwe Papengut <uwe.papengut@t-online.de> wrote:
>> 
>> Hello,
>> 
>> I used the description from titus to build toolchain on Mac OS X SL. I used crosstool-ng 1.6.0.
>> 
>> Everything worked fine until I start "ct-ng build" on my case sensitive file-system.
>> I got this output:
>> 
>> mac-mini:dxdx uwepapengut$ ct-ng build
>> [INFO ]  Performing some trivial sanity checks
>> [INFO ]  Build started 20100204.190640
>> [INFO ]  Building environment variables
>> [00:01] / uname: illegal option -- o
>> usage: uname [-amnprsv]
>> 
>> In which file can I found the wrong command "uname -o..."?
> 
> kconfig/kconfig.mk:ifeq ($(shell uname -o 2>/dev/null || echo unknown),Cygwin)
> scripts/crosstool-NG.sh.in:CT_SYS_OS=$(uname -o || echo "Unknown
> (maybe MacOS-X)")
> 
> 
> may be uname -s would be better because -s option exist in BSD version
> of uname as well as coreutils version.
> alternatively you can install coreutils from ports and use it on your mac
> 
>> 
>> Best Regards,
>> Uwe
>> 
>> 
>> 
>> --
>> For unsubscribe information see http://sourceware.org/lists.html#faq
>> 
>> 
> 
> 
> 
> Von: tvb377@gmx.de
> Datum: 5. Februar 2010 01:33:37 MEZ
> An: Uwe Papengut <uwe.papengut@t-online.de>, crossgcc@sourceware.org
> Betreff: Re: crosstool-ng on Mac OS X 10.6.2 (Snow Leopard) and issue with uname
> 
> 
>> Everything worked fine until I start "ct-ng build" on my case sensitive
>> file-system.
>> I got this output:
>> 
>> mac-mini:dxdx uwepapengut$ ct-ng build
>> [INFO ]  Performing some trivial sanity checks
>> [INFO ]  Build started 20100204.190640
>> [INFO ]  Building environment variables
>> [00:01] / uname: illegal option -- o
>> usage: uname [-amnprsv]
>> 
>> In which file can I found the wrong command "uname -o..."?
> Hello Uwe, all,
> 
> the message is only spam.
> The command is actually `uname -o || uname -s` to keep it
> compatible with GNU.
> So the correct command gets executed, anyway.
> 
> Regards
> Titus
> 
> 












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