Bryan Blackburn wrote:
On Mon, Dec 08, 2008 at 03:25:19PM -0500, Jay Levitt said:
I know this isn't a great bug report, because I already overwrote the fail
case; sorry about that.
I upgraded from a DMG-installed 1.6.0 to a built-from-source 1.7.0 beta 1.
I then updated a bunch of ports
Joshua Root wrote:
Could the wrong libcurl be picked up if there is something like
LDFLAGS=-L/opt/local/lib in the environment? If that's what happened to
Jay, it shouldn't be a problem with selfupdate because the environment
is sanitised.
I do, in fact, have that:
CPATH=/opt/local/include
I know this isn't a great bug report, because I already overwrote the fail
case; sorry about that.
I upgraded from a DMG-installed 1.6.0 to a built-from-source 1.7.0 beta 1.
I then updated a bunch of ports, but I don't think libcurl was one of them.
(Is there a log? I don't think there is.)
]; then
PATH=
eval `/usr/libexec/path_helper -s`
fi
3. Create /etc/paths.d/000-macports
And now you've got an easily-ordered paths.d.
Jay Levitt
[1] As discovered by
http://www.softec.st/en/OpenSource/DevelopersCorner/MasteringThePathHelper.html
to be
coupled with some type of continuous-integration build farm so that
platform-specific bugs don't get (further) introduced.
Jay Levitt
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi
Ryan Schmidt wrote:
On Sep 22, 2008, at 9:22 AM, Jay Levitt wrote:
I have a developer who lives in a rural area, with no broadband access.
(OK, stop laughing.) Worse, his 28.8K dialup ISP has an 8-hour max
session time, so anything signifcantly large just can't be downloaded,
period.
Oh
, but doesn't say how to create them. Neither
does the man page.
Is there any documentation on creating source packages?
Jay Levitt
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports
