Opened 15 years ago
Closed 15 years ago
#21255 closed defect (invalid)
MacPorts won't install in 10.6.
Reported by: | brian.postow@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 1.7.1 |
Keywords: | Cc: | ||
Port: |
Description
When I try to install from the install package, the installed binary says:
Brians-mini$ sudo ./port -d selfupdate can't find package Pextlib 1.0 while executing "package require Pextlib 1.0" (file "./port" line 40)
When I try to compile from source, the make works fine, but the make install says:
. . . /usr/bin/tclsh src/upgrade_sources_conf_default.tcl /opt/local /usr/bin/tclsh src/dep_map_clean.tcl /Library/Tcl can't find package Pextlib 1.0 while executing "package require Pextlib 1.0" (file "/opt/local/share/macports/Tcl/registry1.0/receipt_flat.tcl" line 37) invoked from within "source /opt/local/share/macports/Tcl/registry1.0/receipt_flat.tcl" ("package ifneeded receipt_flat 1.0" script) invoked from within "package require receipt_flat 1.0" (file "/opt/local/share/macports/Tcl/registry1.0/registry.tcl" line 35) invoked from within "source /opt/local/share/macports/Tcl/registry1.0/registry.tcl" ("package ifneeded registry 1.0" script) invoked from within "package require registry 1.0" (file "src/dep_map_clean.tcl" line 10) make: *** [install] Error 1
is this a bug? or am I doing something wrong? thanks.
Attachments (1)
Change History (12)
comment:1 Changed 15 years ago by blb@…
comment:3 follow-up: 4 Changed 15 years ago by jmroot (Joshua Root)
Component: | ports → base |
---|
Version: 1.7.1? If that's accurate, that's your problem. Snow Leopard needs 1.8.
comment:4 Changed 15 years ago by brian.postow@…
Replying to jmr@…:
Version: 1.7.1? If that's accurate, that's your problem. Snow Leopard needs 1.8.
I was initially using the pkg version, which is 1.7, and the released tarball which is 1.7. I just tried the 1.8.beta tarball and still get:
gcc -dynamiclib -g -O2 -W -Wall -pedantic -Wl,-single_module Pextlib.o strsed.o fgetln.o md5cmd.o setmode.o xinstall.o fs-traverse.o strcasecmp.o vercomp.o filemap.o sha1cmd.o curl.o rmd160cmd.o readline.o uid.o tracelib.o tty.o readdir.o pipe.o flock.o system.o -o Pextlib.dylib -L/System/Library/Frameworks/Tcl.framework/Versions/8.5 -ltclstub8.5 -lcurl -lssl -lcrypto -Wl,-weak-lldap -dynamic -Os -pipe -g0 -Wno-system-headers -Wl,-search_paths_first -Wl,-weak-lgssapi_krb5 -Wl,-weak-lkrb5 -Wl,-weak-lk5crypto -Wl,-weak-lcom_err -Wl,-weak-lresolv -lssl -lcrypto -lz -lz -lcrypto -lreadline warning: error while loading Pextlib.dylib: dlopen(./Pextlib.dylib, 10): no suitable image found. Did find: make[2]: *** [pkgIndex.tcl] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1
comment:5 Changed 15 years ago by brian.postow@…
Ok, Added information: When I run make on 1.8 beta, I get:
warning: error while loading MacPorts.dylib: dlopen(./MacPorts.dylib, 10): no suitable image found. Did find:
I run make again, not doing anything else and get:
warning: error while loading Pextlib.dylib: dlopen(./Pextlib.dylib, 10): no suitable image found. Did find:
3rd time and get
warning: error while loading registry.dylib: dlopen(./registry.dylib, 10): no suitable image found. Did find:
4th time it actually compiles!
I sudo make install and get:
can't find package Pextlib 1.0 while executing "package require Pextlib 1.0" (file "/opt/local/share/macports/Tcl/registry1.0/receipt_flat.tcl" line 37) invoked from within "source /opt/local/share/macports/Tcl/registry1.0/receipt_flat.tcl" ("package ifneeded receipt_flat 1.0" script) invoked from within "package require receipt_flat 1.0" (file "/opt/local/share/macports/Tcl/registry1.0/registry.tcl" line 35) invoked from within "source /opt/local/share/macports/Tcl/registry1.0/registry.tcl" ("package ifneeded registry 1.0" script) invoked from within "package require registry 1.0" (file "src/dep_map_clean.tcl" line 10) make: *** [install] Error 1
I run make install from src, and it runs. I run make install then from the macports dir, and it still fails.
comment:6 follow-up: 7 Changed 15 years ago by jmroot (Joshua Root)
Why the beta and not the final release? And how did you even install the 10.5 pkg on 10.6? Could you attach a full log of a fresh attempt to build 1.8.0 from source? And while you're at it, what's the output of
ls -l `which gcc`
comment:7 Changed 15 years ago by brian.postow@…
Replying to jmr@…:
Why the beta and not the final release? And how did you even install the 10.5 pkg on 10.6?
The package to download on the site is 1.7. And I don't see a tarball of a 1.8 final release. The only 1.8 I see is in the testing section and listed as 1.MacPorts-1.8.0-beta1
Could you attach a full log of a fresh attempt to build 1.8.0 from source? And while you're at it, what's the output of
ls -l `which gcc`
lrwxr-xr-x 1 root wheel 7 Sep 9 14:44 /usr/bin/gcc@ -> gcc-4.0
does it need 4.2? I set it to 4.0 because some other programs (The things that I'm going to compile with the libraries that I download with macports) will needto be run on 10.4 machines... I can swap back and forth if needed, I guess.
log is attached.
comment:8 Changed 15 years ago by jmroot (Joshua Root)
I don't know if you're seeing a stale cached copy or what, but http://www.macports.org/install.php has definitely featured version 1.8.0 for a couple weeks now.
I don't know if using gcc 4.0 could be responsible for the problem you're seeing, but I'd definitely recommend using 4.2 since it's the default for the platform and is what we built the 10.6 pkg with.
comment:9 Changed 15 years ago by tobypeterson
"config.status: src/config.h is unchanged" indicates that it wasn't a clean build, anyway.
comment:10 Changed 15 years ago by brian.postow@…
ok. Umm, for some reason I was looking at DarwinPorts and not MacPorts? Did the name change between 1.7 and 1.8?
This version seems to work. thanks!
comment:11 Changed 15 years ago by jmroot (Joshua Root)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Ugh. That domain squatter again. As the page you apparently inadvertently wiki-linked to explains, we've been called MacPorts since 2006...
Did you upgrade to 10.6 and already had MacPorts installed? If so, see the Migration page (the DMG to install MacPorts can be found on the install page).