Can't compile/Make 1.5.0 on a MacBook (was Re: MacPorts 1.5.0 released)
(reposting... I sent this 5 days ago but no replies) On Jul 10, 2007, at 2:54 AM, Juan Manuel Palacios wrote:
I am glad to announce that we've finally finished the 1.5.0 edition of MacPorts, readily available through all our regular distribution means:
-) binary installer for both 10.4 (Universal) and 10.3, http:// svn.macports.org/repository/macports/downloads/MacPorts-1.5.0/ -) source tarballs, both gz and bz2 formats, same location as above; -) selfupdate.
Using http://svn.macosforge.org/repository/macports/downloads/ MacPorts-1.5.0/MacPorts-1.5.0.tar.bz2 which I downloaded and unarchived. $ ./configure && make checking build system type... configure: error: /bin/sh ./config.sub - apple-darwin8.10.1 failed configure: WARNING: Cache variable ac_cv_build contains a newline. zsh: 10685 exit 1 ./configure Running 10.4.10 on a MacBook 2Ghz Core Duo
Hi Why don't you download: MacPorts-1.5.0-10.4.dmg at: http://svn.macports.org/repository/macports/downloads/MacPorts-1.5.0/ then just follow the instruction at: http://trac.macosforge.org/projects/macports/wiki/InstallingMacPorts You're making it more complicated than it really is :) Hope it helps. On Sat, 2007-07-14 at 10:48 -0400, TjL wrote:
(reposting... I sent this 5 days ago but no replies)
On Jul 10, 2007, at 2:54 AM, Juan Manuel Palacios wrote:
I am glad to announce that we've finally finished the 1.5.0 edition of MacPorts, readily available through all our regular distribution means:
-) binary installer for both 10.4 (Universal) and 10.3, http:// svn.macports.org/repository/macports/downloads/MacPorts-1.5.0/ -) source tarballs, both gz and bz2 formats, same location as above; -) selfupdate.
Using http://svn.macosforge.org/repository/macports/downloads/ MacPorts-1.5.0/MacPorts-1.5.0.tar.bz2
which I downloaded and unarchived.
$ ./configure && make checking build system type... configure: error: /bin/sh ./config.sub - apple-darwin8.10.1 failed configure: WARNING: Cache variable ac_cv_build contains a newline. zsh: 10685 exit 1 ./configure
Running 10.4.10 on a MacBook 2Ghz Core Duo
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
-- Frederic Soulier <frederic@wallaby.uklinux.net> OpenPGP key available on http://www.keyserver.net 1024D/BA6700ED 49A6 8E8E 4230 8D41 1ADE B649 3203 1DD2 BA67 00ED
On Jul 19, 2007, at 9:51 AM, Frederic Soulier wrote:
Why don't you download: MacPorts-1.5.0-10.4.dmg
at: http://svn.macports.org/repository/macports/downloads/ MacPorts-1.5.0/
then just follow the instruction at: http://trac.macosforge.org/projects/macports/wiki/ InstallingMacPorts
You're making it more complicated than it really is :)
I assumed that the precompiled versions would not be optimized for my MacBook, whereas if I compiled my own they would be. Is this a faulty assumption?
TjL wrote:
On Jul 19, 2007, at 9:51 AM, Frederic Soulier wrote:
Why don't you download: MacPorts-1.5.0-10.4.dmg
at: http://svn.macports.org/repository/macports/downloads/MacPorts-1.5.0/
then just follow the instruction at: http://trac.macosforge.org/projects/macports/wiki/InstallingMacPorts
You're making it more complicated than it really is :)
I assumed that the precompiled versions would not be optimized for my MacBook, whereas if I compiled my own they would be.
Is this a faulty assumption?
The DMG is a universal binary--it should run fine/natively on your MacBook. ----- Kevin Walzer PortAuthority: The GUI for MacPorts http://www.codebykevin.com/portauthority.html
On Jul 19, 2007, at 9:59 AM, Kevin Walzer wrote:
You're making it more complicated than it really is :) I assumed that the precompiled versions would not be optimized for my MacBook, whereas if I compiled my own they would be. Is this a faulty assumption?
The DMG is a universal binary--it should run fine/natively on your MacBook.
That much I knew. I thought gcc did further optimizations based on the specific processor of the machine in which it was compiled on. I may be wrong, I have only a vague understanding of things at that level. Still, in any event, why doesn't it compile "out of the box" (for those who want to)? TjL
TjL wrote:
The DMG is a universal binary--it should run fine/natively on your MacBook.
That much I knew. I thought gcc did further optimizations based on the specific processor of the machine in which it was compiled on.
gcc isn't magic--it compiles based on whatever instructions are given to it. If you tell it to compile for a single architecture only, it will do that. If you tell it to compile as a universal binary and you have the appropriate libraries/SDK installed, it will do that instead.
Still, in any event, why doesn't it compile "out of the box" (for those who want to)?
I don't know, it worked for me on 10.4.10 Intel. I did things a bit differently than you--I ran "configure" and then "make" in two steps. Try that and see if it works. --- Kevin Walzer PortAuthority: The GUI for MacPorts http://www.codebykevin.com/portauthority.html
On 19 Jul, 2007, at 10:05, TjL wrote:
On Jul 19, 2007, at 9:59 AM, Kevin Walzer wrote:
I assumed that the precompiled versions would not be optimized for my MacBook, whereas if I compiled my own they would be. Is this a faulty assumption?
The DMG is a universal binary--it should run fine/natively on your MacBook.
That much I knew. I thought gcc did further optimizations based on the specific processor of the machine in which it was compiled on.
Well, there are compiler flags that can be passed to gcc that instruct it to do processor-specific optimizations, but you wouldn't have been using any. In any case, although the dmg probably would get MacPorts installed fine, you would likely run into similar problems if you tried to 'selfupdate' because this is just what it does behind the scenes. Now, I think the problem you're having is that your build type is coming up as "-apple-darwin8.10.1" when it should be "i686-apple- darwin8.10.1". This is figured out by config.guess, so a couple of commands to try (with their output on my system) would be: % cd MacPorts-1.5.0 % ./config.guess i686-apple-darwin8.10.1 % uname -a Darwin sauvagine.local 8.10.1 Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386 i386 i386 % machine i486 % arch i386 Chris
On Jul 14, 2007, at 10:48 AM, TjL wrote:
(reposting... I sent this 5 days ago but no replies)
On Jul 10, 2007, at 2:54 AM, Juan Manuel Palacios wrote:
I am glad to announce that we've finally finished the 1.5.0 edition of MacPorts, readily available through all our regular distribution means:
-) binary installer for both 10.4 (Universal) and 10.3, http:// svn.macports.org/repository/macports/downloads/MacPorts-1.5.0/ -) source tarballs, both gz and bz2 formats, same location as above; -) selfupdate.
Using http://svn.macosforge.org/repository/macports/downloads/ MacPorts-1.5.0/MacPorts-1.5.0.tar.bz2
which I downloaded and unarchived.
$ ./configure && make checking build system type... configure: error: /bin/sh ./ config.sub -apple-darwin8.10.1 failed configure: WARNING: Cache variable ac_cv_build contains a newline. zsh: 10685 exit 1 ./configure
Running 10.4.10 on a MacBook 2Ghz Core Duo
In a more recent post you claimed you don't have much understanding of things at this level. OK, but then: did you manually switch from the default bash shell to zsh? I wonder what else is different in your system (and that you might not be aware of) that could be making the system type check fail... Regards,... -jmpp
On Jul 19, 2007, at 11:29 AM, Juan Manuel Palacios wrote:
$ ./configure && make checking build system type... configure: error: /bin/sh ./ config.sub -apple-darwin8.10.1 failed configure: WARNING: Cache variable ac_cv_build contains a newline. zsh: 10685 exit 1 ./configure
Running 10.4.10 on a MacBook 2Ghz Core Duo
In a more recent post you claimed you don't have much understanding of things at this level. OK, but then: did you manually switch from the default bash shell to zsh? I wonder what else is different in your system (and that you might not be aware of) that could be making the system type check fail...
Sorry for the confusion. At the shell/commandline level, I know my way around a lot. Been doing that for 12+ years. On the gcc/programming/compiling level, I know "configure" and "make" and "make install".... if that doesn't work, I'm hosed. Sorta like being a good driver but having no idea what to do under the hood of a car :-) I started using zsh back in the day because I had a friend who was a programmer who taught me how to do a lot with it back when t/csh was what most people were using and I was trying to write scripts, etc. Have used it ever since. TjL
On Jul 19, 2007, at 11:01 AM, Chris Pickel wrote:
Now, I think the problem you're having is that your build type is coming up as "-apple-darwin8.10.1" when it should be "i686-apple- darwin8.10.1". This is figured out by config.guess, so a couple of commands to try (with their output on my system) would be:
% cd MacPorts-1.5.0 % ./config.guess i686-apple-darwin8.10.1
-apple-darwin8.10.1 There's the problem I bet.
% uname -a Darwin sauvagine.local 8.10.1 Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386 i386 i386
Darwin MacBook.local 8.10.1 Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386 i386 unknown MacBook1,1 Darwin (Note the word "unknown" where you have i386!)
% machine i486
ditto
% arch i386
ditto Here's my $PATH /Users/luomat/bin:/opt/local/bin:/sw/bin:/usr/local/bin:/bin:/usr/ X11R6/bin:/usr/bin:/sbin:/usr/sbin I have also installed the gnu coreutils (neither from Fink nor MacPorts, I believe) which I know adds their own commands such as 'ls' to /usr/local/bin/ I wonder.... (Switches to Terminal.app) $ wh -a uname /usr/local/bin/uname /usr/bin/uname $ uname --version uname (coreutils) 5.2.1 Written by David MacKenzie. Copyright (C) 2004 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO $ sudo mv -i /usr/local/bin/uname /usr/local/bin/guname $ rehash; uname -a Darwin MacBook.local 8.10.1 Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386 i386 i386 A-HA! That's what the problem was. GNU stuck its own 'uname' program into the $PATH w/o being smart enough to identify the system. After that, ./configure ran fine. Thank you for helping me figure out the solution. While I could have simply used the DMG (and may still do so), having solved this problem now will probably avoid problems in the future. (I will also try to remember to watch what gets installed with coreutils next time. This isn't the first time one of their programs has been not-Mac-OS-X aware and caused problems.) And next time someone reports a compile problem, we'll know one more thing to suggest. Q: "I tried to run ./configure on my Mac but it failed with this error:" checking build system type... configure: error: /bin/sh ./config.sub - apple-darwin8.10.1 failed A: This can happen if you have installed a different version of 'uname' such as is found in the GNU 'coreutils' package. From the commandline, type "uname -p" and if the response is "unknown" then you have an incompatible version of uname installed on your machine. From the commandline, type "which uname" and if you get anything other than "/usr/bin/uname" (such as /usr/local/bin/uname) try renaming it % mv -i /usr/local/bin/uname /usr/local/bin/guname % rehash And then try ./configure again
participants (5)
-
Chris Pickel
-
Frederic Soulier
-
Juan Manuel Palacios
-
Kevin Walzer
-
TjL