I can't seem to find the download page for the macport binary. The above url is an error 404... Any idea where the binaries are ? Jean-Christophe Helary
On Dec 13, 2006, at 20:44, Jean-Christophe Helary wrote:
I can't seem to find the download page for the macport binary.
The above url [http://www.macports.org/downloads/] is an error 404...
Where is that URL advertised?
Any idea where the binaries are ?
From http://www.macports.org/, click "Source Code," for some reason. Get the relevant .dmg file from here: http://svn.macports.org/repository/macports/downloads/DarwinPorts-1.3.1/ Then do a "sudo port selfupdate" to get you to the latest version.
Ryan, Thanks for the reply.
On Dec 13, 2006, at 20:44, Jean-Christophe Helary wrote:
I can't seem to find the download page for the macport binary.
The above url [http://www.macports.org/downloads/] is an error 404...
Where is that URL advertised?
http://darwinports.opendarwin.org/docs/ch01s03.html#getting_dports I could not find the download info on macports so I searched it on darwinports.
Any idea where the binaries are ?
From http://www.macports.org/, click "Source Code," for some reason. Get the relevant .dmg file from here:
http://svn.macports.org/repository/macports/downloads/ DarwinPorts-1.3.1/
It would definitely help if the info was right on the top page :) Jean-Christophe
http://svn.macports.org/repository/macports/downloads/ DarwinPorts-1.3.1/
Then do a "sudo port selfupdate" to get you to the latest version.
After I install the package, I do "sudo port selfupdate" but get the following message:
$ port install Pextlib can't find package Pextlib 1.0 while executing "package_native require Pextlib 1.0" ("eval" body line 1) invoked from within "eval package_native $args" (procedure "package" line 14) invoked from within "package require Pextlib 1.0" (procedure "dportinit" line 311) invoked from within "dportinit ui_options global_options global_variations" Error: /opt/local/bin/port: Failed to initialize ports system, can't find package Pextlib 1.0
Anything I missed on the way ? Jean-Christophe
On 14 déc. 06, at 13:25, Jean-Christophe Helary wrote:
http://svn.macports.org/repository/macports/downloads/ DarwinPorts-1.3.1/
Then do a "sudo port selfupdate" to get you to the latest version.
After I install the package, I do "sudo port selfupdate" but get the following message:
$ port install Pextlib can't find package Pextlib 1.0 while executing "package_native require Pextlib 1.0" ("eval" body line 1) invoked from within "eval package_native $args" (procedure "package" line 14) invoked from within "package require Pextlib 1.0" (procedure "dportinit" line 311) invoked from within "dportinit ui_options global_options global_variations" Error: /opt/local/bin/port: Failed to initialize ports system, can't find package Pextlib 1.0
Anything I missed on the way ?
I've tried re-installing with 1.2.1 and I get the same problem. Will try with older packages... JC
On Dec 13, 2006, at 22:25, Jean-Christophe Helary wrote:
http://svn.macports.org/repository/macports/downloads/ DarwinPorts-1.3.1/
Then do a "sudo port selfupdate" to get you to the latest version.
After I install the package, I do "sudo port selfupdate" but get the following message:
$ port install Pextlib can't find package Pextlib 1.0 while executing "package_native require Pextlib 1.0" ("eval" body line 1) invoked from within "eval package_native $args" (procedure "package" line 14) invoked from within "package require Pextlib 1.0" (procedure "dportinit" line 311) invoked from within "dportinit ui_options global_options global_variations" Error: /opt/local/bin/port: Failed to initialize ports system, can't find package Pextlib 1.0
Anything I missed on the way ?
I have seen several people report that. I do not understand it. There is this bug report: http://trac.macports.org/projects/macports/ticket/10682 Does anything in that ticket help you?
On Dec 13, 2006, at 22:10, Jean-Christophe Helary wrote:
On Dec 13, 2006, at 20:44, Jean-Christophe Helary wrote:
I can't seem to find the download page for the macport binary.
The above url [http://www.macports.org/downloads/] is an error 404...
Where is that URL advertised?
http://darwinports.opendarwin.org/docs/ch01s03.html#getting_dports
Indeed. 1. Since we have advertised the URL www.darwinports.org/downloads, and everything under www.darwinports.org now redirects to www.macports.org, could whoever is responsible for www.macports.org please arrange that www.macports.org/downloads redirects to the place where MacPorts can be downloaded? 2. Why do we still have darwinports.opendarwin.org active? I feel that since we have some time ago changed names to MacPorts and the URL macports.org, anything that used to be at darwinports.org or darwinports.opendarwin.org should now be available somewhere under macports.org. What do we need to do to make that happen?
After I install the package, I do "sudo port selfupdate" but get the following message:
$ port install Pextlib can't find package Pextlib 1.0 while executing "package_native require Pextlib 1.0" ("eval" body line 1) invoked from within "eval package_native $args" (procedure "package" line 14) invoked from within "package require Pextlib 1.0" (procedure "dportinit" line 311) invoked from within "dportinit ui_options global_options global_variations" Error: /opt/local/bin/port: Failed to initialize ports system, can't find package Pextlib 1.0
Anything I missed on the way ?
I've tried re-installing with 1.2.1 and I get the same problem. Will try with older packages...
I manage to install 1.0 but selfupdate does not work. So I took the DarwinPorts-1.3.2-archive.tar.bz2 package and decided to install it. After typing "./configure" I get a list of checks and eventually:
checking whether tclsh was compiled with threads... no configure: error: tcl wasn't compiled with threads enabled
And of course, the following "make" won't work... JC
After I install the package, I do "sudo port selfupdate" but get the following message:
$ port install Pextlib can't find package Pextlib 1.0 while executing
<snip>
Error: /opt/local/bin/port: Failed to initialize ports system, can't find package Pextlib 1.0
Anything I missed on the way ?
I have seen several people report that. I do not understand it. There is this bug report:
http://trac.macports.org/projects/macports/ticket/10682
Does anything in that ticket help you?
I'm currently downloading XCode 2.4.1 (close to 1gb...) I'll report when I'm done. JC
After I install the package, I do "sudo port selfupdate" but get the following message:
$ port install Pextlib can't find package Pextlib 1.0 while executing
<snip>
Error: /opt/local/bin/port: Failed to initialize ports system, can't find package Pextlib 1.0
Anything I missed on the way ?
I have seen several people report that. I do not understand it. There is this bug report: http://trac.macports.org/projects/macports/ticket/10682 Does anything in that ticket help you?
I'm currently downloading XCode 2.4.1 (close to 1gb...) I'll report when I'm done.
I've installed XCode 2.4.1, reboot, re-downloaded MacPorts 1.3.1 for OSX 10.4, installed seemingly successfully but a "sudo port selfupdate" still produces the same error. Besides, I've tried the "./configure" command for the tar package and I still get a "tcl has been compiled with the nothread option" error message that aborts the configuration. So I am left with no way whatsoever to run macports... JC
Le 14 déc. 06 à 15:30, Jean-Christophe Helary a écrit :
I've installed XCode 2.4.1, reboot, re-downloaded MacPorts 1.3.1 for OSX 10.4, installed seemingly successfully but a "sudo port selfupdate" still produces the same error.
Besides, I've tried the "./configure" command for the tar package and I still get a "tcl has been compiled with the nothread option" error message that aborts the configuration.
So I am left with no way whatsoever to run macports...
Could you please do: * which tclsh * tclsh then $ array get tcl_platform * /usr/bin/tclsh then $ array get tcl_platform and report the result here. Thanks. I'm guessing that configure is picking another tclsh that doesn't have threaded support built-in. On a 10.4.8 MacMini with all software updates and Xcode but nothing else, the built-in tclsh has threaded support built-in. Besides, I think your default tclsh cannot load Pextlib, either because it doesn't like Pextlib (seems to be the problem that was solved by upgrading Xcode on Intel machines) or because it doesn't load libraries the way MacOS X's default tcl loads them. Paul
Paul, Thank you very much for your followup. Here is what I get:
$ which tclsh /sw/bin/tclsh [15:57:36][suzume@bilbo:~] $ tclsh % array get tcl_platform osVersion 8.8.1 byteOrder littleEndian machine i386 platform unix os Darwin user suzume wordSize 4 % [15:58:21][suzume@bilbo:~] $ /usr/bin/tc tclsh tclsh8.4 tclsh8.4.7 tclsh8.5 tcopy [15:58:21][suzume@bilbo:~] $ /usr/bin/tclsh % array get tcl_platform osVersion 8.8.1 byteOrder bigEndian threaded 1 machine {Power Macintosh} platform unix os Darwin user suzume wordSize 4
So, the tclsh from fink is what seems to be interacting with the whole process... I just purged tcltk and all the related packages from fink and the "./ configure", "make", "sudo make install" worked flawlessly:
Congratulations, you have successfully installed the DarwinPorts system.
To get the Portfiles and update the system run:
sudo port selfupdate
Please read README_RELEASE1 and port(1).
Now, I tried "sudo port selfupdate" but I get same Pextlib message :( JC On 14 déc. 06, at 15:42, Paul Guyot wrote:
Le 14 déc. 06 à 15:30, Jean-Christophe Helary a écrit :
I've installed XCode 2.4.1, reboot, re-downloaded MacPorts 1.3.1 for OSX 10.4, installed seemingly successfully but a "sudo port selfupdate" still produces the same error.
Besides, I've tried the "./configure" command for the tar package and I still get a "tcl has been compiled with the nothread option" error message that aborts the configuration.
So I am left with no way whatsoever to run macports...
Could you please do: * which tclsh * tclsh then $ array get tcl_platform * /usr/bin/tclsh then $ array get tcl_platform
and report the result here.
Thanks.
I'm guessing that configure is picking another tclsh that doesn't have threaded support built-in. On a 10.4.8 MacMini with all software updates and Xcode but nothing else, the built-in tclsh has threaded support built-in.
Besides, I think your default tclsh cannot load Pextlib, either because it doesn't like Pextlib (seems to be the problem that was solved by upgrading Xcode on Intel machines) or because it doesn't load libraries the way MacOS X's default tcl loads them.
Paul
JC I ran into this same problem and was finally able to fix it... The pkgIndex.tcl file in /opt/local/share/darwinports/pextlib1.0 (as well as in darwintrace1.0) is missing the following line: package ifneeded Pextlib 1.0 [list load [file join $dir Pextlib.dylib]] The Pextlib.dylib file is also not universal. I opened the DarwinPorts-1.3.1.pkg, extracted the Archive.pax.gz file, extracted the contents and copied the proper dylib file from there... I tried many other things trying to fix the problem, but I believe this was the actual cure for the problem. Chuck On Dec 14, 2006, at 12:30 AM, Jean-Christophe Helary wrote:
After I install the package, I do "sudo port selfupdate" but get the following message:
$ port install Pextlib can't find package Pextlib 1.0 while executing
<snip>
Error: /opt/local/bin/port: Failed to initialize ports system, can't find package Pextlib 1.0
Anything I missed on the way ?
I have seen several people report that. I do not understand it. There is this bug report: http://trac.macports.org/projects/macports/ticket/10682 Does anything in that ticket help you?
I'm currently downloading XCode 2.4.1 (close to 1gb...) I'll report when I'm done.
I've installed XCode 2.4.1, reboot, re-downloaded MacPorts 1.3.1 for OSX 10.4, installed seemingly successfully but a "sudo port selfupdate" still produces the same error.
Besides, I've tried the "./configure" command for the tar package and I still get a "tcl has been compiled with the nothread option" error message that aborts the configuration.
So I am left with no way whatsoever to run macports...
JC _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Chuck,
I ran into this same problem and was finally able to fix it...
The pkgIndex.tcl file in /opt/local/share/darwinports/pextlib1.0 (as well as in darwintrace1.0) is missing the following line:
package ifneeded Pextlib 1.0 [list load [file join $dir Pextlib.dylib]]
I don't have a pkgIndex.tcl file in /opt/local/share/darwinports/ pextlib1.0, the directory seems to be actually: /opt/local/share/darwinports/Tcl/pextlib1.0/
The Pextlib.dylib file is also not universal. I opened the DarwinPorts-1.3.1.pkg, extracted the Archive.pax.gz file, extracted the contents and copied the proper dylib file from there...
jeeeez :) _THAT_ worked :) Thank you very much, Ryan, Paul and Chuck for your hints. Now, I think that deserves some kind of explanation of the top page of MacPorts, don't you think ? JC
Oops...forgot the Tcl in the path when typing it... Chuck :-) On Dec 14, 2006, at 1:26 AM, Jean-Christophe Helary wrote:
Chuck,
I ran into this same problem and was finally able to fix it...
The pkgIndex.tcl file in /opt/local/share/darwinports/pextlib1.0 (as well as in darwintrace1.0) is missing the following line:
package ifneeded Pextlib 1.0 [list load [file join $dir Pextlib.dylib]]
I don't have a pkgIndex.tcl file in /opt/local/share/darwinports/ pextlib1.0, the directory seems to be actually:
/opt/local/share/darwinports/Tcl/pextlib1.0/
The Pextlib.dylib file is also not universal. I opened the DarwinPorts-1.3.1.pkg, extracted the Archive.pax.gz file, extracted the contents and copied the proper dylib file from there...
jeeeez :)
_THAT_ worked :)
Thank you very much, Ryan, Paul and Chuck for your hints.
Now, I think that deserves some kind of explanation of the top page of MacPorts, don't you think ?
JC _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
On Dec 14, 2006, at 01:26, Jean-Christophe Helary wrote:
The Pextlib.dylib file is also not universal. I opened the DarwinPorts-1.3.1.pkg, extracted the Archive.pax.gz file, extracted the contents and copied the proper dylib file from there...
jeeeez :)
_THAT_ worked :)
Thank you very much, Ryan, Paul and Chuck for your hints.
Now, I think that deserves some kind of explanation of the top page of MacPorts, don't you think ?
No, I think MacPorts needs to work properly without requiring such ridiculous fiddling. I don't know the MacPorts internals, but can someone who does please comment on WTF is going on here? Why can most people install MacPorts just fine, but some people experience this problem that is so cumbersome to fix? How do we fix it in MacPorts so nobody needs to muck with it like this to get it to work?
On 15 déc. 06, at 02:28, Ryan Schmidt wrote:
On Dec 14, 2006, at 01:26, Jean-Christophe Helary wrote:
The Pextlib.dylib file is also not universal. I opened the DarwinPorts-1.3.1.pkg, extracted the Archive.pax.gz file, extracted the contents and copied the proper dylib file from there...
jeeeez :)
_THAT_ worked :)
Thank you very much, Ryan, Paul and Chuck for your hints.
Now, I think that deserves some kind of explanation of the top page of MacPorts, don't you think ?
No, I think MacPorts needs to work properly without requiring such ridiculous fiddling. I don't know the MacPorts internals, but can someone who does please comment on WTF is going on here? Why can most people install MacPorts just fine, but some people experience this problem that is so cumbersome to fix? How do we fix it in MacPorts so nobody needs to muck with it like this to get it to work?
What you suggest is the ideal. But the fact is that looking on the web did not help me find the info to fix my problem. So this info, even if it is a temporary solution, _must_ be placed in a position where people will actually find it, _while_ the bug is being fixed. Also, it is reasonable to expect a system to work flawlessly, but the fact is that thanks to Chuck and Paul, I actually learned something about my system. Jean-Christophe Helary
participants (4)
-
Chuck Ferril
-
Jean-Christophe Helary
-
Paul Guyot
-
Ryan Schmidt