Glad to hear that it seems to be working now. I really don't know what
was wrong, but obviously there was some bug with the info command on
10.3. The recent changes mean we no longer rely on the 'info commands'
behaviour, so we should be good.
-Kevin Ballard
On Jan 7, 2008, at 12:56 AM,
Hi Adam,
I just saw that there is a new Qt port available.
It contains several small improvements, but for sqlite I retracted,
for now, to your workaround to use Qt's shipped sqlite.
Does that mean that you got this problem figured out?
No, not yet.
I also, again, don't have much time
On Fri, Jan 04, 2008 at 12:05:14PM -0600, Ryan Schmidt wrote:
On Jan 4, 2008, at 09:41, Charlse Darwin wrote:
On Dec 26, 2007, at 8:14 AM, Ryan Schmidt wrote:
This bug has already been reported:
http://trac.macosforge.org/projects/macports/ticket/13583
# I installed ocaml from
Hello Guido and all others interested ...
I have amended Ticket numbers: 13182 and 11755 per this thread.
Thanks,
T.M.
On 1/6/08, Tabitha McNerney [EMAIL PROTECTED] wrote:
Guido,
I can confirm that your solution that you eloquently described
aforementioned works perfectly -- the namespace
For anyone who might be interested, I just filed a new bug report, Ticket
#13855 http://trac.macports.org/projects/macports/ticket/13855 regarding
building the enscript port (quite popular if I recall correctly when used
with Trac), as it doesn't want to build on my system (MacPorts 1.6.0 and
Tabitha McNerney wrote:
Can anyone with the appropriate editorial authority in the Trac system (
maybe Ryan or Jordan?) delete Ticket #13857 since that ticket is an
accidental duplicate whereby the file was not accepted?
Marked it as duplicate and closed the ticket.
Rainer
For anyone who might be interested, I added a bug report as Ticket
#13858https://trac.macosforge.org/projects/macports/ticket/13858with
regard to the Kaffe port not building / installing on Leopard Server.
I made a mistake at first by trying to upload as an attachment to this
original ticket
On 1/7/08, Rainer Müller [EMAIL PROTECTED] wrote:
Tabitha McNerney wrote:
Can anyone with the appropriate editorial authority in the Trac system (
maybe Ryan or Jordan?) delete Ticket #13857 since that ticket is an
accidental duplicate whereby the file was not accepted?
Marked it as
Hallo, i've a problem after installing macports 1.600
When i tring to install my first package (Midnight Commander), this was
the output:
ibook-g4-di-*-:~ *$ sudo port install mc
Password:
--- Extracting libiconv
Error: Target org.macports.extract returned:
On 2008-01-06 , at 22:56 , Boey Maun Suang wrote:
Just out of curiosity, Kevin, any idea as to exactly why we were
getting
this problem? I wonder if there was a bug fixed between the tcl on
10.3.9
(which appears to be 8.4.4 [1], Chris can confirm this by running
`info
patchlevel` in
On 2008-01-07 , at 01:05 , Kevin Ballard wrote:
Glad to hear that it seems to be working now. I really don't know
what was wrong, but obviously there was some bug with the info
command on 10.3. The recent changes mean we no longer rely on the
'info commands' behaviour, so we should be
I have also tried exporting DYLD_LIBRARY_PATH, expat is not found.
On Sun, Jan 06, 2008 at 06:30:00PM -0500, George Georgalis wrote:
I'm not sure what the problem is here, expat is installed
(subversion, at least, is using it) but p5-xml-parser won't go
in because it cannot find it. I've tried
possible useful info from uni-porting list;
Begin forwarded message:
From: Martin Costabel [EMAIL PROTECTED]
Date: December 30, 2007 8:12:57 AM EST
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Beginner question -- how to resolve dependent dylib's
when linking
Peter O'Gorman
Hello
I want to install LyX on my MacBook Pro Leopard 10.5.1 and did as
follows
sudo port install LyX
then by building the dependencies port wants to configure qt3-mac and
fails.
Error: The following dependencies failed to build: qt3-mac
Error: Status 1 encountered
--- Building libpcap with target all
Error: Target org.macports.build returned: shell command
cd
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_libpcap/work/libpcap-0.9.8
make all returned error 2
Command output: rm -f libpcap.dylib
Well - we're getting closer, but something is still not right.
I am trying to install all of the ports that are on my production
server. Some work, some don't
house54 25 # sudo port -vd install analog
DEBUG: Found port in file:///opt/local/var/macports/sources/
[Resending to post to list; sorry to muffetta for the extra copy]
On 07 Jan, 2008, at 7:48, muffetta66 wrote:
ibook-g4-di-*-:~ *$ sudo port
install mc
Password:
--- Extracting libiconv
Error: Target org.macports.extract returned: shell command cd /
This looks similar to the problem with mod_python on Leopard (the lack
of a command name):
http://trac.macports.org/projects/macports/ticket/13856
-Bill
On Jan 7, 2008, at 9:19 AM, Chris Pickel wrote:
[Resending to post to list; sorry to muffetta for the extra copy]
On 07 Jan, 2008, at
port selfupdate is not appropriate anymore simply because it will
overwrite your self-built copy of macports with the latest released
version (well, it actually won't do this until the latest released
version is a higher version number than what you currently have
installed). I mean, if
Yes, the analog port needs updating. The cd command was removed, but
some ports still use it.
I've just gone ahead and fixed the analog port (the updated Portfile
is available in svn now and will be available through `port sync
`within 12 hours). Any other ports that complain about invalid
[EMAIL PROTECTED] sudo port install ntop
--- Building ntop with target all
Error: Target org.macports.build returned: shell command cd
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_ntop/work/ntop-3.3
gnumake all returned error 2
Command
Hi,
Since MacOS X officially supports IPv6, it would be nice if programs that
provide an IPv6 build option could either have IPv6 specified in the default
port, or at the very least as a variant. Hopefully everyone is ok with this
enhancement request.
I don't plan on testing the ports for
On Jan 7, 2008, at 08:49, George Georgalis wrote:
I have also tried exporting DYLD_LIBRARY_PATH, expat is not found.
That should not be necessary.
I have p5-xml-parser and expat installed. Never seen this problem.
The obvious difference I see is that your MacPorts prefix is /usr/
On Jan 7, 2008, at 12:49, Jay Chandler wrote:
[EMAIL PROTECTED] sudo port install ntop
--- Building ntop with target all
Error: Target org.macports.build returned: shell command cd /opt/
local/var/macports/build/
_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_n
On Jan 7, 2008, at 09:48, Leo Studer wrote:
I want to install LyX on my MacBook Pro Leopard 10.5.1 and did as
follows
sudo port install LyX
then by building the dependencies port wants to configure qt3-mac
and fails.
Error: The following dependencies failed to build: qt3-mac
On Jan 7, 2008, at 05:58, Tabitha McNerney wrote:
For anyone that may be interested, I filed a bug report, Ticket
#13856, regarding attempts to build the mod_python port for use
with Apache 2 on a fresh system of MacPorts 1.6.0 on Leopard Server
10.5.1
I've assigned the ticket to the
On Jan 7, 2008, at 09:14, William Davis wrote:
possible useful info from uni-porting list;
Begin forwarded message:
From: Martin Costabel [EMAIL PROTECTED]
Date: December 30, 2007 8:12:57 AM EST
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Beginner question -- how to resolve
On Jan 7, 2008, at 04:32, Joerg van den Hoff wrote:
On Fri, Jan 04, 2008 at 12:05:14PM -0600, Ryan Schmidt wrote:
On Jan 4, 2008, at 09:41, Charlse Darwin wrote:
On Dec 26, 2007, at 8:14 AM, Ryan Schmidt wrote:
This bug has already been reported:
just migrated tiger -- leopard: clean install. i'm copying stuff
over by hand and had hoped i could do an rsync of my /opt tree on
tiger to leopard. this seems to have work as at least many things are
working. however, just tried to port install iterm and got:
ld: library not found for
Hi,
I've tested the patch and the update, it works, please submit it.
Gruss Olaf
---BeginMessage---
#13845: UPDATE: darkstat 3.0.707
--+-
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type:
I see we have a ticket on this already:
http://trac.macosforge.org/projects/macports/ticket/13802
I'll add you to the Cc list so you'll be informed of its progress.
Any help you can provide in resolving the problem would of course
also be appreciated.
On Jan 7, 2008, at 10:20, Stefmit
On Jan 7, 2008, at 15:38, ara howard wrote:
just migrated tiger -- leopard: clean install. i'm copying stuff
over by hand and had hoped i could do an rsync of my /opt tree on
tiger to leopard. this seems to have work as at least many things
are working. however, just tried to port
On Jan 7, 2008, at 4:03 PM, Ryan Schmidt wrote:
On Jan 7, 2008, at 09:14, William Davis wrote:
possible useful info from uni-porting list;
Begin forwarded message:
From: Martin Costabel [EMAIL PROTECTED]
Date: December 30, 2007 8:12:57 AM EST
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Hi Olaf,
On Tue, January 8, 2008 8:51 am, Olaf Foellinger wrote:
Hi,
I've tested the patch and the update, it works, please submit it.
Done in r32564 [1]. Thanks!
Kind regards,
Maun Suang
[1] http://trac.macosforge.org/projects/macports/changeset/32564
--
Boey Maun Suang
Email: [EMAIL
I was seduced by the libtool-devel port (v. 1.9f), which caused me to
deactivate the libtool port (v 1.5.24) in favor of it. As it turns out, the
automake folks told me 1.9f is pretty old.
The other kicker which got me to try libtool-devel was that the libtool port
doesn't actually install
Per http://trac.macosforge.org/projects/macports/changeset/32564 it seems that
I have the right Portfile:
$less
/opt/local/var/macports/sources/rsync.macports.org/release/ports/net/darkstat/Portfile
PortSystem 1.0
namedarkstat
version 3.0.707
categories
Andre-John Mas wrote:
Hi,
Hi,
Since MacOS X officially supports IPv6, it would be nice if programs that
provide an IPv6 build option could either have IPv6 specified in the default
port, or at the very least as a variant. Hopefully everyone is ok with this
enhancement request.
I don't
Stefmit wrote:
$ sudo port upgrade outdated
--- Building libpcap with target all
Error: Target org.macports.build returned: shell command
cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_libpcap/work/libpcap-0.9.8
make all returned error
I am sorry - followed the wrong thread, thus patch - of course it is libpcap,
I just reported it earlier ... long Monday, sorry for the screw-up :(
Stefan
On Monday 07 January 2008 20:36:33 Rainer Müller wrote:
Stefmit wrote:
$ sudo port upgrade outdated
--- Building libpcap with target
On 1/7/08, Ryan Schmidt [EMAIL PROTECTED] wrote:
On Jan 7, 2008, at 05:58, Tabitha McNerney wrote:
For anyone that may be interested, I filed a bug report, Ticket
#13856, regarding attempts to build the mod_python port for use
with Apache 2 on a fresh system of MacPorts 1.6.0 on Leopard
On Jan 7, 2008, at 21:22, Tabitha McNerney wrote:
Thank you for the reminder about the best way to file a ticket.
What happens when a MacPort doesn't have a maintainer? For example,
I filed a Ticket for the Kaffe port but the kaffe port doesn't have
a maintainer according to:
$ port
Regarding ticket #13845:
On Jan 7, 2008, at 15:51, Olaf Foellinger wrote:
I've tested the patch and the update, it works, please submit it.
boeyms committed the patch and closed the ticket.
___
macports-users mailing list
On Jan 7, 2008, at 18:51, [EMAIL PROTECTED] wrote:
I was seduced by the libtool-devel port (v. 1.9f), which caused me to
deactivate the libtool port (v 1.5.24) in favor of it. As it turns
out, the
automake folks told me 1.9f is pretty old.
libtool-devel is unmaintained so it wouldn't
On Jan 7, 2008, at 20:10, George Georgalis wrote:
On Mon, Jan 07, 2008 at 02:23:05PM -0600, Ryan Schmidt wrote:
On Jan 7, 2008, at 08:49, George Georgalis wrote:
I have also tried exporting DYLD_LIBRARY_PATH, expat is not found.
That should not be necessary.
I have p5-xml-parser and
On Jan 7, 2008, at 20:33, Rainer Müller wrote:
Since MacOS X officially supports IPv6, it would be nice if
programs that provide an IPv6 build option could either have IPv6
specified in the default port, or at the very least as a variant.
Hopefully everyone is ok with this enhancement
Given the naive view that a larger version number implies something a
bit more current and -devel implies something a bit more
development- oriented, shouldn't the libtool-devel port either be
renamed or deleted altogether?
Ryan The -devel suffix indicates a development
On Jan 7, 2008, at 21:58, [EMAIL PROTECTED] wrote:
Given the naive view that a larger version number implies
something a
bit more current and -devel implies something a bit more
development- oriented, shouldn't the libtool-devel port either be
renamed or deleted altogether?
The -devel
On Mon, Jan 07, 2008 at 09:46:26PM -0600, Ryan Schmidt wrote:
On Jan 7, 2008, at 20:10, George Georgalis wrote:
On Mon, Jan 07, 2008 at 02:23:05PM -0600, Ryan Schmidt wrote:
On Jan 7, 2008, at 08:49, George Georgalis wrote:
I have also tried exporting DYLD_LIBRARY_PATH, expat is not found.
On Jan 7, 2008, at 22:30, George Georgalis wrote:
On Mon, Jan 07, 2008 at 09:46:26PM -0600, Ryan Schmidt wrote:
On Jan 7, 2008, at 20:10, George Georgalis wrote:
On Mon, Jan 07, 2008 at 02:23:05PM -0600, Ryan Schmidt wrote:
On Jan 7, 2008, at 08:49, George Georgalis wrote:
I have also
49 matches
Mail list logo
