| View previous topic :: View next topic |
| Author |
Message |
pindar
Apprentice
Joined: 30 Apr 2004
Posts: 220
|
 Posted: Fri Aug 27, 2004 9:46 am Post subject: errors compiling for OS X [solved] |
 |
|
Is anyone else seeing these errors?
| Code: |
11:41AM:pindar@pindar's-Computer: ~ % ACCEPT_KEYWORDS="~macos" sudo emerge -D nano Calculating dependencies ...done!
>>> emerge (1 of 1) app-editors/nano-1.3.4 to /
>>> Downloading http://gentoo.osuosl.org/distfiles/nano-1.3.4.tar.gz
######################################################################## 100.0%
>>> md5 src_uri ;-) nano-1.3.4.tar.gz
>>> Unpacking source...
>>> Unpacking nano-1.3.4.tar.gz to /var/tmp/portage/nano-1.3.4/work
* Applying 1.3.4-nanobrack.patch... [ ok ]
>>> Source unpacked.
[snip]
checking build system type... configure: error: /bin/sh ./config.sub -apple-darwin7.5.0 failed
!!! ERROR: app-editors/nano-1.3.4 failed.
!!! Function econf, Line 426, Exitcode 1
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message. |
Not quite sure, but is this related to the 10.3.5 update? I'm kind of clueless here. Tried with other nano versions, got the same error.
Last edited by pindar on Tue Sep 21, 2004 3:35 pm; edited 1 time in total |
|
| Back to top |
|
 |
gnuageux
Veteran
Joined: 17 Apr 2004
Posts: 1201
|
|
| Back to top |
|
|
pindar
Apprentice
Joined: 30 Apr 2004
Posts: 220
|
| Posted: Fri Aug 27, 2004 1:16 pm Post subject: |
|
|
| Yup, couldn't find anything appropriate. As far as I can see, nano is not the only ebuild affected, there are a couple more. |
|
| Back to top |
|
|
pindar
Apprentice
Joined: 30 Apr 2004
Posts: 220
|
| Posted: Mon Sep 20, 2004 3:43 pm Post subject: |
|
|
| OK, I have kind of fixed this particular bug: it seems that my version of uname did not return the expected result (found this out googling for "darwin-unknown darwin-powerpc," and lo and behold, there was a discussion somewhere on a mailing list). I copied over the original version of uname from another mac, and now things compile fine. The only question is: this new (and broken) version of uname must have been installed by an ebuild - does anyone have an idea which one that could have been? Might help other users, too. |
|
| Back to top |
|
|
JoseJX
Retired Dev
Joined: 28 Apr 2002
Posts: 2774
|
| Posted: Tue Sep 21, 2004 2:28 pm Post subject: |
|
|
| If you installed coreutils without using collision-protect then your version of uname would have been replaced. A new version of coreutils has been written to address this and should be available soon. |
|
| Back to top |
|
|
pindar
Apprentice
Joined: 30 Apr 2004
Posts: 220
|
| Posted: Tue Sep 21, 2004 3:35 pm Post subject: |
|
|
| Good to know, thanks! I was under the impression that collision-protect was enabled by default, I can't remember disabling it, but maybe I did. Well, on second thought, I must have, because I just saw that my version of rsync was replaced, too (i had the one with hfs-support, and after emerging coreutils, I was left with the vanilla one). |
|
| Back to top |
|
|
|
Gentoo for Mac OS X (Portage for Mac OS X)
