Try selfupdate with Leopard => Error md5.h is missing
Hi, I have tried a new installation on Leopard. I have installed XCode and the Unix SDK. When I try sudo port selfupdate (I have a version 1.5 installed), I receive this error message: configure: Please install the BSD SDK package from the Xcode Developer Tools CD. configure: error: libmd was found, but md5.h is missing. Well the file md5.h exists (spotlight find it in crypto and sys ...)? Can someone help? Thanks // Jph
Hi, I don´t find a way to install macports from scratch on leopard. I mean you can download and install the dmg file for 10.5 But after this port selfupdate does not work... So the solution was to copy a tiger installation and it seems to work. Regards // Jph Le 30 oct. 07 à 13:13, Jean-Philippe Humbert a écrit :
Hi,
I have tried a new installation on Leopard. I have installed XCode and the Unix SDK.
When I try sudo port selfupdate (I have a version 1.5 installed), I receive this error message: configure: Please install the BSD SDK package from the Xcode Developer Tools CD. configure: error: libmd was found, but md5.h is missing.
Well the file md5.h exists (spotlight find it in crypto and sys ...)?
Can someone help?
Thanks // Jph
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
On Nov 1, 2007, at 13:34, Jean-Philippe Humbert wrote:
Le 30 oct. 07 à 13:13, Jean-Philippe Humbert a écrit :
I have tried a new installation on Leopard. I have installed XCode and the Unix SDK.
When I try sudo port selfupdate (I have a version 1.5 installed), I receive this error message: configure: Please install the BSD SDK package from the Xcode Developer Tools CD. configure: error: libmd was found, but md5.h is missing.
Well the file md5.h exists (spotlight find it in crypto and sys ...)?
Can someone help?
I don´t find a way to install macports from scratch on leopard. I mean you can download and install the dmg file for 10.5 But after this port selfupdate does not work...
So the solution was to copy a tiger installation and it seems to work.
That's not a solution, that's a workaround. Has anybody else been able to selfupdate on Leopard?
On Nov 1, 2007, at 4:24 PM, Ryan Schmidt wrote:
On Nov 1, 2007, at 13:34, Jean-Philippe Humbert wrote:
Le 30 oct. 07 à 13:13, Jean-Philippe Humbert a écrit :
I have tried a new installation on Leopard. I have installed XCode and the Unix SDK.
When I try sudo port selfupdate (I have a version 1.5 installed), I receive this error message: configure: Please install the BSD SDK package from the Xcode Developer Tools CD. configure: error: libmd was found, but md5.h is missing.
Well the file md5.h exists (spotlight find it in crypto and sys ...)?
Can someone help?
I don´t find a way to install macports from scratch on leopard. I mean you can download and install the dmg file for 10.5 But after this port selfupdate does not work...
So the solution was to copy a tiger installation and it seems to work.
That's not a solution, that's a workaround. Has anybody else been able to selfupdate on Leopard?
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
I have had no problem doing port selfupdate on Leopard William Davis
On Nov 1, 2007, at 4:24 PM, Ryan Schmidt wrote:
On Nov 1, 2007, at 13:34, Jean-Philippe Humbert wrote:
Le 30 oct. 07 à 13:13, Jean-Philippe Humbert a écrit :
I have tried a new installation on Leopard. I have installed XCode and the Unix SDK.
When I try sudo port selfupdate (I have a version 1.5 installed), I receive this error message: configure: Please install the BSD SDK package from the Xcode Developer Tools CD. configure: error: libmd was found, but md5.h is missing.
Well the file md5.h exists (spotlight find it in crypto and sys ...)?
Can someone help?
I don´t find a way to install macports from scratch on leopard. I mean you can download and install the dmg file for 10.5 But after this port selfupdate does not work...
So the solution was to copy a tiger installation and it seems to work.
That's not a solution, that's a workaround. Has anybody else been able to selfupdate on Leopard?
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
opps selfupdate ok with 1.52 have you tried doing sudo port -duf upgrade MacPorts?
On Nov 1, 2007, at 16:02, William Davis wrote:
On Nov 1, 2007, at 4:24 PM, Ryan Schmidt wrote:
On Nov 1, 2007, at 13:34, Jean-Philippe Humbert wrote:
Le 30 oct. 07 à 13:13, Jean-Philippe Humbert a écrit :
I have tried a new installation on Leopard. I have installed XCode and the Unix SDK.
When I try sudo port selfupdate (I have a version 1.5 installed), I receive this error message: configure: Please install the BSD SDK package from the Xcode Developer Tools CD. configure: error: libmd was found, but md5.h is missing.
Well the file md5.h exists (spotlight find it in crypto and sys ...)?
Can someone help?
I don´t find a way to install macports from scratch on leopard. I mean you can download and install the dmg file for 10.5 But after this port selfupdate does not work...
So the solution was to copy a tiger installation and it seems to work.
That's not a solution, that's a workaround. Has anybody else been able to selfupdate on Leopard?
opps selfupdate ok with 1.52
have you tried doing sudo port -duf upgrade MacPorts?
What the heck is that -- I mean the port called "MacPorts"?
On Nov 1, 2007, at 5:02 PM, Ryan Schmidt wrote:
On Nov 1, 2007, at 16:02, William Davis wrote:
On Nov 1, 2007, at 4:24 PM, Ryan Schmidt wrote:
On Nov 1, 2007, at 13:34, Jean-Philippe Humbert wrote:
Le 30 oct. 07 à 13:13, Jean-Philippe Humbert a écrit :
I have tried a new installation on Leopard. I have installed XCode and the Unix SDK.
When I try sudo port selfupdate (I have a version 1.5 installed), I receive this error message: configure: Please install the BSD SDK package from the Xcode Developer Tools CD. configure: error: libmd was found, but md5.h is missing.
Well the file md5.h exists (spotlight find it in crypto and sys ...)?
Can someone help?
I don´t find a way to install macports from scratch on leopard. I mean you can download and install the dmg file for 10.5 But after this port selfupdate does not work...
So the solution was to copy a tiger installation and it seems to work.
That's not a solution, that's a workaround. Has anybody else been able to selfupdate on Leopard?
opps selfupdate ok with 1.52
have you tried doing sudo port -duf upgrade MacPorts?
What the heck is that -- I mean the port called "MacPorts"?
well, I dont mean to teach the Pope catechism but! MacPorts is the name of the "port" portfile. someone must be maintaining it because it now has a varrant +darwin_9_i386 :) macintosh:~ frstan$ port list MacPorts MacPorts @1.5.0 sysutils/MacPorts macintosh:~ frstan$ port info MacPorts MacPorts 1.5.0, sysutils/MacPorts (Variants: universal, darwin_7, darwin_8, darwin_8_powerpc, darwin_8_i386, darwin_9, darwin_9_powerpc, darwin_9_i386) http://www.macports.org MacPorts provides the infrastructure that allows easy installation and management of freely available software on Mac OS X 10.3 or newer systems. Platforms: darwin freebsd Maintainers: macports-mgr@lists.macosforge.org macintosh:~ frstan$
On Nov 1, 2007, at 2:16 PM, William Davis wrote:
have you tried doing sudo port -duf upgrade MacPorts?
What the heck is that -- I mean the port called "MacPorts"?
well, I dont mean to teach the Pope catechism but! MacPorts is the name of the "port" portfile. someone must be maintaining it because it now has a varrant +darwin_9_i386 :)
The MacPorts port is a PortFile that is used to create the dmg files that we release when we release a binary version of MacPorts. It just treats MacPorts itself like any other port. James
James Berry <jberry@macports.org> writes:
The MacPorts port is a PortFile that is used to create the dmg files that we release when we release a binary version of MacPorts. It just treats MacPorts itself like any other port.
I think that port's description should be updated so it's purpose is more clear. Mark
On Nov 1, 2007, at 16:30, markd@macports.org wrote:
James Berry <jberry@macports.org> writes:
The MacPorts port is a PortFile that is used to create the dmg files that we release when we release a binary version of MacPorts. It just treats MacPorts itself like any other port.
I think that port's description should be updated so it's purpose is more clear.
A bit weird that this functionality is implemented as a port, isn't it? And getting back on track: then the "MacPorts" port can't have anything to do with the original poster's problem.
On Nov 1, 2007, at 7:03 PM, Ryan Schmidt wrote:
On Nov 1, 2007, at 16:30, markd@macports.org wrote:
James Berry <jberry@macports.org> writes:
The MacPorts port is a PortFile that is used to create the dmg files that we release when we release a binary version of MacPorts. It just treats MacPorts itself like any other port.
I think that port's description should be updated so it's purpose is more clear.
A bit weird that this functionality is implemented as a port, isn't it?
And getting back on track: then the "MacPorts" port can't have anything to do with the original poster's problem.
I didnt say it did have to do with his problem. :) but it is how I downloaded and built from the source........ and I could then do selfupdate on Leopard --- which is what he asked about and what made me think it might have something to do with the *answer* to his problem...... but what do I know? only that I can selfupdate on Leopard..... ymmv
Hi, I have found a solution: I have cleaned /usr/local. there was a lot of old headers and libraries into this directory. Sorry, it was only a local problem on my computer. // Jph Le 2 nov. 07 à 00:32, William Davis a écrit :
On Nov 1, 2007, at 7:03 PM, Ryan Schmidt wrote:
On Nov 1, 2007, at 16:30, markd@macports.org wrote:
James Berry <jberry@macports.org> writes:
The MacPorts port is a PortFile that is used to create the dmg files that we release when we release a binary version of MacPorts. It just treats MacPorts itself like any other port.
I think that port's description should be updated so it's purpose is more clear.
A bit weird that this functionality is implemented as a port, isn't it?
And getting back on track: then the "MacPorts" port can't have anything to do with the original poster's problem.
I didnt say it did have to do with his problem. :) but it is how I downloaded and built from the source........ and I could then do selfupdate on Leopard --- which is what he asked about and what made me think it might have something to do with the *answer* to his problem......
but what do I know? only that I can selfupdate on Leopard.....
ymmv
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
participants (5)
-
James Berry
-
Jean-Philippe Humbert
-
markd＠macports.org
-
Ryan Schmidt
-
William Davis