Re: ntop
Can anyone launch the current version of ntop from the terminal without it immediately quitting? If so, what did you do to launch it? I haven't used it in awhile, but I put in a howto what I thought was the easiest way. http://homepage.mac.com/duling/halfdozen/ntop-Howto.html If it still dies, can you see in the terminal output what is the last thing it does before it dies? Also, look in /var/log/system for more info. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Installation problems with Expect
I am having the same problem, reported all over the web, with Macport installation of the program Expect, apparently because of a problem recognizing the current version of Tcl. Does someone have a work-around? Thanks. Joe Goddard This ticket is (unfortunately) still the current state of things: http://trac.macports.org/ticket/13827 I found a patch for using it with Tcl 8.5 and applied it. Please do a selfupdate to get revision 4 of expect and try again. Note also that OS X 10.4 and 10.5 have expect v5.42 included in case you weren't aware. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Postfix and cyrus in Macports bind to different saslauthd
Hi there, I am experimenting an extrange behaviour with saslauthd daemons. Macports port of Postfix seems to need Apple's builtin saslauthd daemon but Macports port of Cyrus needs macports version of saslauthd. I guess this is not normal... I don't mind using any of the versions of saslauthd as I don't need a special auth mech; just rimap which is built in both, but whould like to use just one of them. Now I have both saslauthd started. mux files ar in /opt/local/var/state/saslauthd/mux and /var/state/saslauthd/mux Anybody knows how can y make Macports ports of postfix or Cyrus Imaps use one or the other saslauthd daemons? Hi Ignacio, I haven't used postscript this way, but it is set to do that and it seems like it is building against the macports version of cyrus-sasl judging by the build messages. Can you give any information you see where it shows that it isn't -error messages, otool output or anything else? Thanks. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: nedi fails to build (on p5-math-pari)
On Fri, Nov 07, 2008 at 02:44:53PM -0800, [EMAIL PROTECTED] said:
p5-math-pari installs fine for me. So is the problem fetching the
tarball? If so, you can manually copy the tarball into
${prefix}/var/macports/distfiles/perl5 and then do the install.
If you are on an Intel-based Mac, did you try running 'make test' when it
built?
I am on an Intel box. I did a 'port configure p5-math-pari' and then a
'make test' in the source directory. It failed.
Compilation failed in require at t/zz_leak.t line 17.
BEGIN failed--compilation aborted at t/zz_leak.t line 17.
t/zz_leakdubious
Test returned status 2 (wstat 512, 0x200)
FAILED--15 test scripts could be run, alas--no output ever seen
Also, manual fetching doesn't work because the perl module, while
building, does the fetch itself so it won't look under ${prefix}.
I see that now. I didn't get that before. I wonder if there is a way to
turn that off by setting $(paridir) so the Makefile will see it.
$paridir = find_pari_dir() unless defined $paridir or $parisrc or
$force_download;
($paridir) = download_and_patch_pari($parisrc, $force_download)
if !$paridir or $force_download;
Mark
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Postfix's main.cf
$ sudo postfix start PATH/to/opt/etc/postfix/postfix-script: line 220: ls: command not found I get that too. It can't find the operating system's ls command. I modified postfix-script to print out the value of PATH when it's running. I get: /opt/local/bin:/usr/bin:/sbin:/usr/sbin So /bin, where ls resides, is not in the PATH. I don't know why postfix is excluding that vital path. There was a ticket on that. The other issues were already fixed. http://trac.macports.org/ticket/10644 I've never understood why it can't find 'ls'. But it seems since no better solution is available for this longstanding issue, I committed a hack to fix it in r41192, and then updated the port to 2.5.5 in a subsequent commit. Please try a selfupdate after a short wait and test 2.5.5. It should be fixed. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Nagios/Macports on PowerMac G5
Hi folks, I am running Nagios in several instances on Linux machines for a few years now, so I thought I give it a try on a Mac. I have installed Macports and with that nagios (3.03) on a PowerMac G5 Dual 1,8 GHz (2,5 GB RAM), have configured 3 hosts and around 100 services - which is not much. Now there is several problems that I do not find any way to get around: 1. Nagios uses 150 - 200 % of cpu (since it is a dual cpu system that makes sense) in normal operation. One of my other nagios instances on a linux box monitors 30 hosts with 400 services inside a virtual machine on a pentium III box without noticable cpu load. The rest of the machine (system, services) run on unimpressed with normal process behaviour (just a mailserver and the OS, nothing else). What is happening there? 2. Nagios simply stops every now and then; it is not launchd stopping nagios, but the nagios process itself seems to hang somehow. It simply does not do any checks any more. Or a sub process hangs while trying to send an email. These hangs are quite weird - top and other tools list these processes as normally working processes, but they stop in the middle of something and do not go on or never finish. launchd does not recognize nagios as failed then and does not restart it. I would be interested in looking very deep into this and spending quite some time, but I do not now where to look at. Any hint or help is appreciated. Dirk Hi Dirk, I maintain the nagios port, but I haven't used it for awhile, and not since version 3. In the past it was always very stable. Have you run Nagios v3 on Linux? It may be a bug in the source of v3. Could you ask the Nagios support list about this? I don't have a running installation of nagios right now so I couldn't answer any questions they might ask. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Is MacPort a valid term?
For a long time, I thought that when people were saying port, in this discussion, I thought the were referring to a port or a tcp/ip address. like localhost:80 Clarity is one of the reasons that in the past I frequently used the term MacPorts port (to distinguish it from FreeBSD and other port systems), but this is too cumbersome and inelegant when used a lot so I mostly curtailed that. Using the term MacPort would make the term clear, but is that really a valid term in current usage? It seems we're only comfortable with the plural form, and I think that is why we always fall back to the more generic port to express a single MacPorts port. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Is MacPort a valid term?
For a long time, I thought that when people were saying port, in this discussion, I thought the were referring to a port or a tcp/ip address. like localhost:80 Clarity is one of the reasons that in the past I frequently used the term MacPorts port (to distinguish it from FreeBSD and other port systems), but this is too cumbersome and inelegant when used a lot so I mostly curtailed that. Using the term MacPort would make the term clear, but is that really a valid term in current usage? It seems we're only comfortable with the plural form, and I think that is why we always fall back to the more generic port to express a single MacPorts port. Just like Apple doesn't want you to say I wrote an AppleScript (they want you to say I wrote an AppleScript script), I don't like hearing I installed a MacPort (I think I installed a MacPorts port is clearer). That's not to say I don't see your point too. MacPorts port (and AppleScript script) is long and sounds silly. Would be neat if we could come up with a new cute term for our ports. Ruby has gems, for instance. What entities could MacPorts have? Hmn. How about mport as shorthand for MacPorts port. MacPorts mport would never be used, since it is redundant. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Ports and their dependencies
All jokes aside, would it be helpful to take the great explanations you have all written and integrating them into chapter 5.4.1 of the MacPorts Guide http://guide.macports.org/#reference.dependencies.types? Is this something that would benefit the MacPorts Community (even though I might have been one of the first people to ask such questions explicitly)? I renamed non-port dependencies to file dependencies. See what you think of the revisions in r37493. It can be refined further if necessary. Thanks to Joshua and Ryan for the explanations. http://trac.macports.org/changeset/37493 Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Ports and their dependencies
This is not an error, but a different type of dependency. A port:foo
dependency means install the port named 'foo', whereas lib:foo:bar
means
check if the library 'foo' is present, and if not, install the port
named
'bar'. You can also use 'bin' or 'path' instead of 'lib' to make the
port
installation conditional on the absence of executables and arbitrary
files,
respectively.
This is only mentioned in passing in the guide:
[ http://guide.macports.org/#reference.dependencies.types
]http://guide.macports.org/#reference.dependencies.types. It's documented
a little better in the portfile(7) manual.
Most of the time dependencies should be of the port: variety, but
sometimes
it is better/easier to use software that Apple ships with OS X, a common
example being X11. You'll see lib:libX11.6:XFree86 in a lot of
portfiles.
How is it described better in the man page? Below is the text in the
guide. And don't forget that the guide is going to be the source for the
new man pages (1.7? 1.8?), so if the man pages are better in some
respect, the guide needs to be corrected in those respects.
http://guide.macports.org/#reference.dependencies.types
---
Port dependencies should be provided by MacPorts ports whenever possible,
however dependencies may be provided by vendor-supplied software when
satisfying a dependency by a port is not practical or desirable for a
special reason. Dependencies of this type are called non-port dependencies.
Non-port dependencies should only be used if the application or library
can be installed by multiple ports (for example stable and -devel version)
or if it can't be installed with MacPorts.
Port dependencies, the preferred type, are specified as shown in these
examples:
depends_lib port:rrdtool port:apache2
depends_build port:libtool
depends_run port:apache2 port:php5
Non-port dependencies are specified as shown in these examples:
depends_lib lib:libX11.6:xorg
depends_build bin:glibtool:libtool
depends_run path:${prefix}/lib/libltdl.a:libtool
--
Mark
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: ntop fials to build
Someone just proposed a fix for the port here: http://trac.macosforge.org/projects/macports/ticket/13610 Can someone verify or comment on this fix? Ihaven't had time to look at it. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: ntop fails to build
I just committed the patch as revision 1 to the port. The patch worked fine for me. In short order the new port should be updated for you after doing a selfupdate. Mark How do I patch this one? http://trac.macosforge.org/projects/macports/attachment/ticket/13610/ patch-globals-structtypes.h $ sudo patch -p0 ~/Dl/patch-globals-structtypes.h can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: --|--- globals-structtypes.h 2008-03-18 22:24:02.0 +1030 |+++ globals-structtypes.h.new 2008-03-18 22:23:51.0 +1030-- File to patch: ~/Dl/patch-globals-structtypes.h~/Dl/patch-globals-structtypes.h: No such file or directorySkip this patch? [y] ySkipping patch.1 out of 1 hunk ignored On Mar 20, 2008, at 2:04 AM, [EMAIL PROTECTED] wrote: Someone just proposed a fix for the port here: http://trac.macosforge.org/projects/macports/ticket/13610 Can someone verify or comment on this fix? Ihaven't had time to look at it. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
e: Install successful now trying to install ntop
Thanks to Adrian's help, I was able to complete the install of MacPorts.
My goal in installing MacPorts was to get a ntop installed. Checking
for installation instructions for ntop on macports.org wasn't helpful
at all; I couldn't find any instructions. Luckily, back at the old
darwinports.org there is a url for ntop, http://ntop/darwinports.org
that actually contains installation instructions:
cd /opt/local/bin/portslocation/dports/ntop
% sudo port install ntop
One problem here is that if /portslocation/dports/ntop doesn't exist,
then you must create it, cd to it and then sudo. Even thou the
instructions are clear, they should mention this to save newbies like
me.
Once the directories are created, sudo port install ntop works
wonderfully, installing all sorts files - that is until it gets to
libcap. Libcap can't be found in any of the following locations:
--- Fetching libpcap
--- Attempting to fetch libpcap-0.9.8.tar.gz from
http://www.tcpdump.org/release/
--- Attempting to fetch libpcap-0.9.8.tar.gz from
http://svn.macports.org/repository/macports/distfiles/libpcap
--- Attempting to fetch libpcap-0.9.8.tar.gz from
http://svn.macports.org/repository/macports/distfiles/general/
--- Attempting to fetch libpcap-0.9.8.tar.gz from
http://svn.macports.org/repository/macports/downloads/libpcap
--- Attempting to fetch libpcap-0.9.8.tar.gz from
http://svn.macports.org/repository/macports/distfiles/libpcap
--- Attempting to fetch libpcap-0.9.8.tar.gz from
http://svn.macports.org/repository/macports/distfiles/general/
--- Attempting to fetch libpcap-0.9.8.tar.gz from
http://svn.macports.org/repository/macports/downloads/libpcap
Error: Target org.macports.fetch returned: fetch failed
Since I it appears that libcap is required to build and install ntop,
what should I do from here?
ntop is broken on 10.5 and I don't know what the fix is yet. If someone
could ask the ntop support list it would be great. I've been too busy to
do it.
Right afterwards, cgilib failed to build since the terminal didn't
know what the command O3 was. Details below.
--- Building cgilib with target {}
Error: Target org.macports.build returned: shell command cd /opt/
local/var/macports/build/
_opt_local_var_macports_sources_rsync
.macports.org_release_ports_www_cgilib/work/cgilib-0.5 make
CFLAGS=-O3 -fPIC -I. returned error 2
Command output: O3 -fPIC -I. -c -o cgi.o cgi.c
make: O3: Command not found
make: [cgi.o] Error 127 (ignored)
O3 -fPIC -I. -c -o cookies.o cookies.c
make: O3: Command not found
make: [cookies.o] Error 127 (ignored)
ar rc libcgi.a cgi.o cookies.o
ar: cgi.o: No such file or directory
ar: cookies.o: No such file or directory
make: *** [libcgi.a] Error 1
Error: The following dependencies failed to build: rrdtool cgilib
libart_lgpl perl5.8 tcl
Error: Status 1 encountered during processing.
The last time I saw this happen, simply cleaning and reinstalling fixed it.
sudo port uninstall cgilib
sudo clean --all cgilib
sudo port install cgilib
Mark
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: logrotate deleting conf file
I recently upgraded logrotate and in doing so, my logrotate.conf file was deleted. Instead I got a shiny new logrotate-default. Fortunately I had a backup - but this is still a critical bug. I am unable to login to the trac and report the bug - the login process stalls. I thought the developers named the file with -default was so it would be renamed. But I renamed the file logrotate.conf.sample anyway. But it must be renamed from that after install or it will be overwritten on the next upgrade too. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: ntop failure to build (where is ticket #13648
Ntop is very broken and it is beyond my expertise to fix it. Someone needs to contact the developers and it will be a bit before I get to it. But all anyone can do is describe the symptoms and ask them. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: ntop fails to build
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 top/work/ntop-3.3 gnumake all returned error 2 Command output: gnumake all-recursive Making all in . /bin/sh ./libtool --tag=CC --mode=compile /usr/bin/gcc-4.0 - DHAVE_CONFIG_H -I. -I. -g -Os -DBUILD=112 - DMACOSX_DEPLOYMENT_TARGET=10.5 -F/System/Library/PrivateFrameworks/ -F/System/Library/Frameworks/ -pipe -Udarwin9 -Ddarwin9=darwin9 -I. -I/usr/local/include -I/opt/local/include -DDARWIN -I/usr/local/ include -g -no-cpp-precomp -O2 -I/opt/local/include -I/usr/local/ include -g -Wshadow -Wpointer-arith -Wmissing-prototypes -Wmissing- declarations -Wnested-externs -fno-common -DPIC -MT address.lo -MD -MP -MF .deps/address.Tpo -c -o address.lo address.c /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -g -Os -DBUILD=112 - DMACOSX_DEPLOYMENT_TARGET=10.5 -F/System/Library/PrivateFrameworks/ -F/System/Library/Frameworks/ -pipe -Udarwin9 -Ddarwin9=darwin9 -I. -I/usr/local/include -I/opt/local/include -DDARWIN -I/usr/local/ include -g -no-cpp-precomp -O2 -I/opt/local/include -I/usr/local/ include -g -Wshadow -Wpointer-arith -Wmissing-prototypes -Wmissing- declarations -Wnested-externs -fno-common -DPIC -MT address.lo -MD - MP -MF .deps/address.Tpo -c address.c -fno-common -DPIC -o .libs/ address.o In file included from ntop.h:484, from address.c:21: globals-structtypes.h:103: error: two or more data types in declaration specifiers globals-structtypes.h:103: warning: useless type name in empty declaration gnumake[2]: *** [address.lo] Error 1 gnumake[1]: *** [all-recursive] Error 1 gnumake: *** [all] Error 2 Error: Status 1 encountered during processing. I see this problem was reported 3 weeks ago but the maintainer hasn't commented on it yet. [ https://owa016.msoutlookonline.net/owa/redir.aspx?URL=http%3a%2f%2ftrac.macosforge.org%2fprojects%2fmacports%2fticket%2f13610 ]http://trac.macosforge.org/projects/macports/ticket/13610 I'll add you to the Cc list of that ticket so you're informed of its progress. I see you're running Mac OS X 10.5. Looks like the reporter of that ticket was too. And do you have Xcode 3? What version of MacPorts do you have, and what architecture is your processor? I note occurrences of /usr/local in your output above, and also in the filed ticket. What do you have in /usr/local? It can conflict with MacPorts ports, so we recommend not having anything in /usr/ local. Try renaming /usr/local to /usr/local-off and cleaning (sudo port clean --work ntop) and building (sudo port install ntop) ntop again. If it works, you'll know something in /usr/local conflicted, and you should install whatever you need using MacPorts instead of manually installing in /usr/local. Ntop started failing to build on leopard, and I don't know yet what the solution is. I tried renaming /usr/local just to be sure and it didn't help. I'll ask the ntop support list shortly and leave comments in the ticket later at least to show I've seen it. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Tripwire not installing
I have the latest version of MacPorts installed and am attempting to install Tripwire. I do not have sendmail installed, but do have postfix. Running Mac OS 10.4.10 Server. Here is the install Terminal window: HD:/opt/local/bin root# /opt/local/bin/port install tripwire --- Staging tripwire into destroot Error: Target org.macports.destroot returned: shell command cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_security_tripwire/work/tripwire-2.4.1.2-src make install DESTDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_security_tripwire/work/destroot returned error 2 Command output: make[3]: Nothing to be done for `install-data-am'. make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[2]: Nothing to be done for `install-exec-am'. make install-data-hook prefix=/opt/local sysconfdir=/opt/local/etc/tripwire \ path_to_vi=/usr/bin/vi path_to_sendmail= \ ./install/install.sh -n -f -s none -l none Installer program for: Tripwire(R) 2.4 Open Source Copyright (C) 1998-2000 Tripwire (R) Security Systems, Inc. Tripwire (R) is a registered trademark of the Purdue Research Foundation and is licensed exclusively to Tripwire (R) Security Systems, Inc. Using configuration file ./install/install.cfg Checking for programs specified in install configuration file *** No sendmail found. Edit install.cfg and set *** TWMAILPROGRAM to full path to sendmail, or *** change TWMAILMETHOD to SMTP and set SMTP *** settings appropriately. make[3]: *** [install-data-hook] Error 1 make[2]: *** [install-data-am] Error 2 make[1]: *** [install-am] Error 2 make: *** [install-recursive] Error 1 Error: Status 1 encountered during processing. The installer does not finish, so I'm not sure how I can change the TWMAILMETHOD to SMTP. Any help would be greatly appreciated. It installs fine for me on Leopard. Do you have a /usr/sbin/sendmail? That's where tripwire seems to look. checking for sendmail... /usr/sbin/sendmail Also, when you say you have postfix, do you mean you have MacPort's Postfix port installed? Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: NeDi Installation Failure
I have followed the instructions located here: [ https://owa016.msoutlookonline.net/owa/redir.aspx?URL=http%3a%2f%2fhomepage.mac.com%2fduling%2fhalfdozen%2fNeDi-Howto.html ]http://homepage.mac.com/duling/halfdozen/NeDi-Howto.html I've gotten to step 3, Install and Configure NeDi. Unfortunately, when I run the command sudo port install nedi it doesn't work. The debug output is Ok, so the error message is: Can't locate DynaLoader.pm in @INC (@INC contains: /opt/local/lib/ perl5/5.8.8/darwin-2level /opt/local/lib/perl5/5.8.8 /opt/local/lib/ perl5/site_perl/5.8.8/darwin-2level /opt/local/lib/perl5/site_perl/ 5.8.8 /opt/local/lib/perl5/site_perl /opt/local/lib/perl5/vendor_perl/ 5.8.8/darwin-2level /opt/local/lib/perl5/vendor_perl/5.8.8 /opt/local/ lib/perl5/vendor_perl .) at /opt/local/lib/perl5/5.8.8/ExtUtils/ Mkbootstrap.pm line 20. Chad, I just installed the NeDi port on 10.5 with no problems. Initiating a discovery run gave no problems either. So I can't see any problem at all. It must be that the install is failing on a dependency that is installed prior to installing the NeDi port. Please send me the full debug output so I can tell. BTW, I just updated the port to rc5. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
NeDi installation failure
I am out of town and can't test the problem until Monday. But it is hard
to believe that the error is happening at time of the port install. The
nedi port just copies stuff into ${prefix}. It sure sounds like a runtime
error running nedi.pl. I can test it all on Monday though (and I haven't
tried nedi on 10.5 yet) so drop me a line as a reminder if you don't hear
from me by Monday evening.
Mark
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Tripwire fails to install
I just took a couple of minutes to checkout the current stable Open Soure Tripwire(R) 2.4.1.2 on Mac OS X 10.4.11 PPC. I unpacked the source code, ran ./configure make make install. Tripwire configures and compiles without any problems using the tool chain that comes with 10.4 out of the box, I didn't even update to the latest XCode etc. This is the output of tripwire --version Open Soure Tripwire(R) 2.4.1.2 built for powerpc-apple-darwin8.11.0 The developer of the original code and/or files is Tripwire, Inc. Portions created by Tripwire, Inc. are copyright 2000 Tripwire, Inc. Tripwire is a registered trademark of Tripwire, Inc. All rights reserved. This program is free software. The contents of this file are subject to the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. You may redistribute it and/or modify it only in compliance with the GNU General Public License. This program is distributed in the hope that it will be useful. However, this program is distributed AS-IS WITHOUT ANY WARRANTY; INCLUDING THE IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Please see the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. Nothing in the GNU General Public License or any other license to use the code or files shall permit you to use Tripwire's trademarks, service marks, or other intellectual property without Tripwire's prior written consent. If you have any questions, please contact Tripwire, Inc. at either [EMAIL PROTECTED] or www.tripwire.org. --- cheers, Tobias W. Tobias, To install tripwire via MacPorts, you would use sudo port intall tripwire. What happens when you type that? It instals fine for me, but I don't use tripwire so I can't test its operation. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: selfupdate failing under Leopard
macports-users@lists.macosforge.org writes: Apple doesn't install things into /usr/local, you do. You had a bad copy of libreadline installed and it was causing problems. On 10.5, I see: /usr/local/include fuse fuse.h ulockmgr.h /usr/local/lib libfuse.0.0.0.dylib libfuse.la libulockmgr.dylib libfuse.0.dylib libulockmgr.0.0.0.dylib libulockmgr.la libfuse.a libulockmgr.0.dylib pkgconfig libfuse.dylib libulockmgr.a Has the possiblity of checking for the presence of trouiblesome stuff in /usr/local/bin lib/ and if so throwing up a terse warning that non-Apple software has been installed, likely problems that might occur because of it, and perhaps possible workarounds? I know forcing MP not to link against /usr/local is thought though possible right now. On the other hand, if a user installs stuff in /usr/local/ after installing MacPorts it wouldn't help unless selfupdate (and/or port) also checked those paths so maybe it isn't feasible. The Cisco VPN client uses /usr/local, though it causes no problems. Comments? Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: selfupdate failing under Leopard
On the other hand, if a user installs stuff in /usr/local/ after installing MacPorts it wouldn't help unless selfupdate (and/or port) also checked those paths so maybe it isn't feasible. The Cisco VPN client uses /usr/local, though it causes no problems. Comments? So the 'problem' is only when the user installs some library in /usr/ local that macports uses and either that install is broken somehow or the user removes it. It's good to make macports robust against mistakes, but at some point we probably have to realize that end-users are going to be able to configure their systems in ways that are broken, and we may or may not be able to do something about that specific broken-ness. I agree. Especially since the woes of manually installed OSS is one if the problems MacPorts is trying to overcome. :) Is readline the main offender? I want to document this problem and though I think any non-MP software could potentially be a problem, I might mention the worst offenders as examples. What are others? Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports on Xserve OSX server
BB [EMAIL PROTECTED] writes: I'm guessing your problem something simple, like you forgot to install X11 before installing Xcode. Be sure X11 is installed (look for /Applications/Utilities/X11.app) and once installed then go back to Xcode and install Xcode Tools X11 option. I didn't think X11 had to be installed to install the X11 SDK if you select it explicitly. If that is so, the new guide's install section order is wrong. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Macports on Xserve OSX server
BB [EMAIL PROTECTED] writes: I didn't think X11 had to be installed to install the X11 SDK if you select it explicitly. If that is so, the new guide's install section order is wrong. This (older) page indicates that X11 must be installed before the X11 SDK: http://developer.apple.com/opensource/tools/runningX11.html I've always installed X11 before Xcode, and therefore can't verify if X11 must be installed before the SDK. I wrote both of those. On the one hand it seemed natural to install X11 first since X11SDK would be automatically installed by Xcode Tools if X11 was present, but on the other it seemed like the first install item should be the most important one. I decided on the latter for the guide because I thought that forcing X11SDK (without X11) was possible. I think I tested it, but I'll recheck it when I get the chance. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: leopard install
Ryan Schmidt [EMAIL PROTECTED] writes: eoghan, have you installed Xcode 3? You'll need that. Yes, and I forgot to give the link to the new guide for some others install details you may need. http://geeklair.net/new_macports_guide/ Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: man port problem
Lefteris Tsintjelis [EMAIL PROTECTED] writes: I personally prefer the general settings as it works well for any user logged in as well as the general scripts running of the OS, if any. Can you restate your preferred way of fixing the problem? Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: man port problem
Luís Beça [EMAIL PROTECTED] writes: I just installed macports on a PPC iMac running Leopard 10.5.0 and ran into the following problem when doing 'man port' in the terminal: Cannot open the message catalog man for locale UTF-8 (NLSPATH=none) No manual entry for port On the other hand, if do 'man port' in xterm, it works fine. Why is this happening? I thought it might have something to do with encodings, so I disabled all encodings in the new terminal preferences, but still man port does not work. I see the same problem. I'm also on 10.5. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: installing error: xorg-proto
Soo-Hyun Choi [EMAIL PROTECTED] writes:
If I attache more detailed error message, it would something like:
[EMAIL PROTECTED]: ~ $ sudo port install xorg-proto
--- Fetching xorg-proto
--- Verifying checksum(s) for xorg-proto
--- Extracting xorg-proto
--- Configuring xorg-proto
--- Building xorg-proto with target all
--- Staging xorg-proto into destroot
--- Packaging tgz archive for xorg-proto 20070907_0
Error: Target org.macports.archive returned: error copying
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-proto/work/.macports.xorg-
proto.state to
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-proto/work/destroot/+STATE:
no such file or directory
Error: Status 1 encountered during processing.
[EMAIL PROTECTED]: ~ $
That port is supposed to do nothing but trigger dependencies.
fetch { }
checksum{ }
configure { }
build { }
destroot{ }
activate{ }
Is there another stage that needs to be eliminated? I'm not familiar with
ports like this.
Mark
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: apache2 MacPorts info message
Jochen Küpper [EMAIL PROTECTED] writes: I always wondered why my apache would not start at boot-time... Now I updgraded to MacPorts apache2 version 2.2.6 and take a quick look into it. Apparently one has to edit /opt/local/etc/LaunchDaemons/org.macports.apache2/ org.macports.apache2.plist and change the Disabled key to false? keyDisabled/keyfalse/ Is this true? If so, this should be documented in the info-message given upon installation of apache2 via MacPorts: ### # A startup item has been generated that will aid in # starting apache2 with launchd. It is disabled # by default. Execute the following command to start it, # and to cause it to launch at startup: # # sudo launchctl load -w /Library/LaunchDaemons/ org.macports.apache2.plist ### This message indicates, launchctl would take care of that stuff. It doesn't, at least not for me. If, however, the user has to do this manually, it should be said at that point. If I am overlooking something, I am happy to learn about it;) Hi Jochen, sudo launchctl load -w /Library/LaunchDaemons/org.macports.apache2.plist is intended to remove the Disabled tag, and always has for me. And unload will place it there again. I'm not sure why it wouln't do that for you though. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: installing error: xorg-proto
Sorry I wasn't clear, but I was hoping to spur comments by someone with
knowledge of the port. I could experiment and perhaps find the problem,
but there are others on the list more knowledgable that hopefully will
provide some insight.
Mark
Soo-Hyun Choi [EMAIL PROTECTED] writes:
Thanks for your reply. But I don't get what you are saying. Would you
kindly give some more information what should I do with that?
Regards,
Soo-Hyun
On 10/30/07, [ mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] [
mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Soo-Hyun Choi [ mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]
writes:
If I attache more detailed error message, it would something like:
[EMAIL PROTECTED]: ~ $ sudo port install xorg-proto
--- Fetching xorg-proto
--- Verifying checksum(s) for xorg-proto
--- Extracting xorg-proto
--- Configuring xorg-proto
--- Building xorg-proto with target all
--- Staging xorg-proto into destroot
--- Packaging tgz archive for xorg-proto 20070907_0
Error: Target org.macports.archive returned: error copying
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-proto/work/.macports.xorg-
proto.state to
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-proto/work/destroot/+STATE:
no such file or directory
Error: Status 1 encountered during processing.
[EMAIL PROTECTED]: ~ $
That port is supposed to do nothing but trigger dependencies.
fetch { }
checksum{ }
configure { }
build { }
destroot{ }
activate{ }
Is there another stage that needs to be eliminated? I'm not familiar with
ports like this.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: installing error: xorg-proto
Soo-Hyun Choi [EMAIL PROTECTED] writes:
Okay, I get errors when I do archive the port.
[EMAIL PROTECTED]: ~ $ sudo port fetch xorg-proto
[EMAIL PROTECTED]: ~ $ sudo port checksum xorg-proto
[EMAIL PROTECTED] : ~ $ sudo port configure xorg-proto
[EMAIL PROTECTED]: ~ $ sudo port build xorg-proto
[EMAIL PROTECTED]: ~ $ sudo port destroot xorg-proto
[EMAIL PROTECTED] : ~ $ sudo port archive xorg-proto
--- Packaging tgz archive for xorg-proto 20070907_0
Error: Target org.macports.archive returned: error copying
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-proto/work/.macports.xorg-
proto.state to
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-proto/work/destroot/+STATE:
no such file or directory
Error: Status 1 encountered during processing.
[EMAIL PROTECTED]: ~ $
Anyone got a clue why I'm getting this errors and how I can cure?
Based on Daniel's comment, the Porfile has a bug. It is missing the
statement archive {}. Do sudo port ed xorg-proto and add that
statement to the Portfile and try again. To so that you need to have a
statement like this in your ~/.profile file: export EDITOR=/usr/bin/nano
Mark
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: apache2 MacPorts info message
Jochen Küpper [EMAIL PROTECTED] writes: Yes, it does work as you describe for me as well. I was put off by the fact that it moved the flags somewhere else (before the array) inside the file. However, it does still not restart apache at boot-time. Is there more I have to do? I am still not moved to Mac OS X (from my Unix experience) in that respect and don't really know how all this is done here... Have you renamed httpd.conf.sample to httpd.conf? Also, you can start apache manually and you an see any error messages. sudo /opt/local/apache2/bin/apachectl start Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: c3270
Shawn Protsman [EMAIL PROTECTED] writes: I've installed x3270 but it doesn't include c3270. Is there any reason why c3270 is not included in the Macports x3270 package? You'll have to clue us in here. Isn't c3270 a different application, and therefore would be a separate port? If yes, the only reason we don't have a port for c3270 is that no one has yet contributed one Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: c3270
Shawn Protsman [EMAIL PROTECTED] writes: Hi Mark, If that is the case with FreeBSD then I'd suggest they be kept separate. The 'suite' contains other items I don't use. It would be simpler to have x3270 and c3270 ports. I'll consider the patching and get back to you. I need to read through some patch documentation and understand how Macports handle things in more depth. If you could point me to some documentation I'd appreciate it. --Shawn Shawn, It looks like there is a separate tarball. This is the download sirte for the freebsd port. http://x3270.bgp.nu/download/ It may be as simple as cloning the x3270 port and changing the port name, download file, and checksum. The documentation is kind of a mess right now because it is under development. But here it is: http://geeklair.net/new_macports_guide/ You can make a local portfile repository as shown in the docs, copy the x3270 portfile and modify it for c3270. If you can tell us how it installs manually, we can help you along if you want to try it. It is probably very easy. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: wxMaxima port
sbcl was updated recently and installed fine on my MacBook Pro. Hopefully moving or removing the stuff in /usr/local is all you need to do. Mark On Oct 18, 2007, at 10:43, John Doner wrote: I tried to port wxmaxima; it failed because I already had maxima installed (/usr/local/bin/maxima). Now the obvious solution would be to also use macports to install maxima. In fact, I did try this a couple of months ago, only to see it fail because it could not install the dependency sbcl. At the time, I just gave up on macports, installed sbcl and then maxima from the source. This worked out fine. Probably, I can do the same with wxmaxima. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Porting Postfix 2.4.5
In my spare time I've been working on getting Postfix 2.4.5 working with MacPorts, as well as getting TLS and SASL to work correctly (OpenSSL deps using system libraries instead of the ported version, leading to 0.9.7 vs 0.9.8 mismatch). The below portfile *works* correctly (with thanks to Mark Duling to helping me get this far!)-- the issue is that while I'm rather comfortable with Postifx, I'm quite certain I don't know enough about the MacPorts system to make it work in the proscribed manner. For instance, it isn't set up to use variants and whatnot, but the make arguments get passed correctly and it uses the proper dependencies. Can anyone lend a hand towards helping me polish this so that it can be published? The issues I see at the moment: jay-chandlers-computer:/opt/local/var/macports/sources/rsync.macports.org/release/ports/mail/postfix jay$ sudo postfix start postfix/postfix-script: warning: not owned by root: /opt/local/var/spool/postfix postfix/postfix-script: warning: not owned by group postdrop: /opt/local/var/spool/postfix/public postfix/postfix-script: warning: not owned by group postdrop: /opt/local/var/spool/postfix/maildrop postfix/postfix-script: warning: not owned by group postdrop: /opt/local/sbin/postqueue postfix/postfix-script: warning: not owned by group postdrop: /opt/local/sbin/postdrop postfix/postfix-script: warning: not set-gid or not owner+group+world executable: /opt/local/sbin/postqueue postfix/postfix-script: warning: not set-gid or not owner+group+world executable: /opt/local/sbin/postdrop postfix/postfix-script: starting the Postfix mail system That's simple enough to fix-- should just be a chown, I figure. I committed your update to 2.4.5. Please test it. Oct 14 11:57:25 jay-chandlers-computer postfix/master[29706]: daemon started -- version 2.4.5, configuration /etc/postfix The fact that it's pulling from /etc/postfix for its configuration is somewhat more puzzling. The patchfiles were ommitted from your update and some of them needed to be carried over from 2.3.8. I did that. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Tripwire fails to install
I opened ticket #12894 with a gizp'd tar file that contains an updated Portfile and updated patch files to allow Tripwire to install. Hopefully this helps. Fixed in r29963. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to specify a variant in 'depends_lib'
[EMAIL PROTECTED] writes: I am trying to write a portfile for some software but I want to make sure that a particular variant of a dependency is installed. Is there some way that I can specify the variant within the portfile that I want to use? WOuld something like: depends_lib port:otherport+variantname work? (I'm away from the computer that is doing this at the moment so I can't experiment). If not, then I'll have to think of some other way of achieving my goal. There is a characteristic of MacPorts base that can accomplish this, though it should be used with some care. Variants are passed to dependents, so if you install a port with a variant foo, and a dependency also has a variant foo, then the dependency will get installed with variant foo. This is fine for ports where a dependency is only used with a given port, or rarely used with anything else, or where the dependency is almost always installed using the variant anyway. Caveats are that if a dependency is already installed, it won't help a bit. Another is that if the conditions I mentioned do not hold, you may shield the user from having to learn something they'll only have to learn later anyway. But I've done this for a couple of ports where I thought it was warranted. See the comments in the server variant of the nedi port for an example. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: I cannot install help2man
It installed ok for me on 10.4 / Intel/ Xcode 2.4.1. What platform, OS version, and Scode do you have? Mark [EMAIL PROTECTED] writes: Hello, I cannot install help2man with macports 1.5 and OS X 10.4.10 ppc I have this : sudo port -dv install help2man Password: DEBUG: Found port in [ file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/help2man ]file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/help2man DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/help2man DEBUG: Requested variant powerpc is not provided by port help2man. DEBUG: Requested variant darwin is not provided by port help2man. DEBUG: Requested variant macosx is not provided by port help2man. DEBUG: Executing variant darwin_8 provides darwin_8 DEBUG: Found port in [ file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/perl5.8 ]file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/perl5.8 DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/perl5.8 DEBUG: Requested variant powerpc is not provided by port perl5.8. DEBUG: Requested variant macosx is not provided by port perl5.8. DEBUG: Executing variant darwin provides darwin DEBUG: Executing variant darwin_8 provides darwin_8 DEBUG: Searching for dependency: perl5.8 DEBUG: Found Dependency: receipt exists for perl5.8 DEBUG: Found port in [ file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/perl/p5-locale-gettext ]file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/perl/p5-locale-gettext DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/perl/p5-locale-gettext DEBUG: Requested variant powerpc is not provided by port p5-locale-gettext. DEBUG: Requested variant darwin is not provided by port p5-locale-gettext. DEBUG: Requested variant macosx is not provided by port p5-locale-gettext. DEBUG: Searching for dependency: p5-locale-gettext DEBUG: Found Dependency: receipt exists for p5-locale-gettext DEBUG: Found port in [ file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gettext ]file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gettext DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gettext DEBUG: Requested variant powerpc is not provided by port gettext. DEBUG: Requested variant darwin is not provided by port gettext. DEBUG: Requested variant macosx is not provided by port gettext. DEBUG: Searching for dependency: gettext DEBUG: Found Dependency: receipt exists for gettext DEBUG: Found port in [ file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv ]file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv DEBUG: Requested variant powerpc is not provided by port libiconv. DEBUG: Requested variant darwin is not provided by port libiconv. DEBUG: Requested variant macosx is not provided by port libiconv. DEBUG: Executing variant darwin_8 provides darwin_8 DEBUG: Searching for dependency: libiconv DEBUG: Found Dependency: receipt exists for libiconv DEBUG: Skipping completed org.macports.main (help2man) DEBUG: Skipping completed org.macports.fetch (help2man) DEBUG: Skipping completed org.macports.checksum (help2man) DEBUG: Skipping completed org.macports.extract (help2man) DEBUG: Skipping completed org.macports.patch (help2man) DEBUG: Skipping completed org.macports.configure (help2man) DEBUG: Skipping completed org.macports.build (help2man) --- Staging help2man into destroot . missing (directory not created: File exists) ./Applications missing (directory not created: File exists) ./Developer missing (directory not created: File exists) ./Library missing (directory not created: File exists) DEBUG: Executing org.macports.destroot (help2man) DEBUG: Environment: DEBUG: Assembled command: 'cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_help2man/work/help2man-1.36.4 make install DESTDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_help2man/work/destroot' ./mkinstalldirs /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_help2man/work/destroot/opt/local/bin ./mkinstalldirs /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_help2man/work/destroot/opt/local/lib ./mkinstalldirs /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_help2man/work/destroot/opt/local/share/man/man1 ./mkinstalldirs
Re: Error getting SSMTP
Scott Harper [EMAIL PROTECTED] writes: Thanks Mark, that is working now. One comment, the install didn't provide a copy of the ssmtp.conf file (it needs to go in /opt/local/etc/ssmtp along with the revaliases file). I'll attach a copy of the default file that is provided in some of the other Linux distros... The file is in the distro but the Makefile didn't copy it, so I have to port do it. Changes in revsion 1 will show up shortly. Port ssmtp contains: /opt/local/etc/ssmtp/revaliases /opt/local/etc/ssmtp/ssmpt.conf.sample /opt/local/sbin/ssmtp /opt/local/share/doc/ssmtp/COPYING /opt/local/share/doc/ssmtp/INSTALL /opt/local/share/doc/ssmtp/README /opt/local/share/man/man8/ssmtp.8.gz Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Error getting SSMTP
Scott Harper [EMAIL PROTECTED] writes: I'm not really in any position to comment on whether or not any of these other patches need to be applied... But beyond that, do you have any estimate of when the 2.61 port will be made available? I committed an update to 2.61 just now so give it a few hours and do a selfupdate. A port that installs is better than a broken one, and the patch problem will have to be worked on another day. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Error getting SSMTP
Jay Chandler [EMAIL PROTECTED] writes: I am trying to install the ssmtp port, but get the following error fetching. Any suggestions? $ port search ssmtp ssmtp mail/ssmtp 2.60.4 Sendmail alternative for small routers (outgoing mail only) $ sudo port install ssmtp --- Fetching ssmtp --- Attempting to fetch ssmtp_2.60.4.tar.gz from http://ftp.debian.org/debian/pool/main/s/ssmtp/ --- Attempting to fetch ssmtp_2.60.4.tar.gz from ftp://ftp.icm.edu.pl/pub/Linux/debian/pool/main/s/ssmtp/ --- Attempting to fetch ssmtp_2.60.4.tar.gz from http://svn.macports.org/repository/macports/distfiles/ssmtp --- Attempting to fetch ssmtp_2.60.4.tar.gz from http://svn.macports.org/repository/macports/distfiles/general/ --- Attempting to fetch ssmtp_2.60.4.tar.gz from http://svn.macports.org/repository/macports/downloads/ssmtp Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. Yeah, I show the same thing here. Same for installing PuTTY, incidentally... 2.61 is current and 2.60 is no longer available. I've got the port updated (but not committed), but I can't get the debian patchfile to behave. But looking at the FreeBSD port patches (with ssl related patching) I wonder if some of those should be applied too. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Postfix Port -- OpenSSL Issues
Jay Chandler [EMAIL PROTECTED] writes: So I've built Postfix on my MacBook Pro, and it starts correctly. However, when I try to relay mail via 587 submission to my colocated server, I get: warning: run-time library vs. compile-time header version mismatch: OpenSSL 0.9.8 may not be compatible with OpenSSL 0.9.7 Followed quickly by a network error from the server: Sep 17 14:08:20 kwisatz postfix/smtpd[7902]: warning: network_biopair_interop: error reading 5 bytes from the network: Connection reset by peer Sep 17 14:08:20 kwisatz postfix/smtpd[7902]: lost connection after EHLO from pool-MyIP.lsanca.dsl-w.verizon.net[MyIP] I suspect the problem is that the port builds with one OpenSSL, but runs with another; the issue is I require TLS encryption for my 587 submissions, so this is kind of a showstopper until I can get this resolved... And though it should go without saying, the colocated server is patched, current, and has no issues from other locations... I'd be grateful for any assistance anyone can lend... I see this has been reported before. http://lists.macosforge.org/pipermail/macports-dev/2006-September/70.html Perhaps the answer is here. See the next 2-3 messages in the thread. http://www.aet.tu-cottbus.de/pipermail/postfix_tls/2002/000314.html If someone can use this information to make a fix to the portfile we can commit it. The postfix port needs a maintainer; it is a little bit out-of-date now that 2.4 is out. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: libmng installation failure
David Moylan [EMAIL PROTECTED] writes: Still trying to figure out why libmng won't configure properly. No Makefile is created when ./configure is run. This is the output from sudo port -vd configure libmng Do the requested variant messages indicate the problem? DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/libmng DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/libmng DEBUG: Requested variant powerpc is not provided by port libmng. DEBUG: Requested variant darwin is not provided by port libmng. DEBUG: Requested variant macosx is not provided by port libmng. DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/jpeg DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/jpeg DEBUG: Requested variant powerpc is not provided by port jpeg. DEBUG: Requested variant darwin is not provided by port jpeg. DEBUG: Requested variant macosx is not provided by port jpeg. DEBUG: Searching for dependency: jpeg DEBUG: Found Dependency: receipt exists for jpeg DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/lcms DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/lcms DEBUG: Requested variant powerpc is not provided by port lcms. DEBUG: Requested variant darwin is not provided by port lcms. DEBUG: Requested variant macosx is not provided by port lcms. DEBUG: Searching for dependency: lcms DEBUG: Found Dependency: receipt exists for lcms DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/archivers/zlib DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/archivers/zlib DEBUG: Requested variant powerpc is not provided by port zlib. DEBUG: Requested variant darwin is not provided by port zlib. DEBUG: Requested variant macosx is not provided by port zlib. DEBUG: Searching for dependency: zlib DEBUG: Found Dependency: receipt exists for zlib DEBUG: Skipping completed org.macports.main (libmng) DEBUG: Skipping completed org.macports.fetch (libmng) DEBUG: Skipping completed org.macports.checksum (libmng) DEBUG: Skipping completed org.macports.extract (libmng) DEBUG: Skipping completed org.macports.patch (libmng) DEBUG: Skipping completed org.macports.configure (libmng) No, that looks normal. Also, automake and autoconf are build dependencies so they will show up later. It works fine for me, but this sounds like the same problem someone (or was it you?) had with esound. I never understood why that problem occured only for some. Mark Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: esound won't install
Lenore Horner [EMAIL PROTECTED] writes: I get the following message. I have emailed the maintainer and had no response (in 36 hours). Does anyone know how to work around this. I can't install Gimp until this works (as far as I know - Gimp installation keeps hanging here). I get this error both as part of the Gimp installation via MacPorts and attempting to install esound alone through MacPorts. I'm use OS X 10.4.10 and MacPorts 1.5. sudo port install esound --- Building esound 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_audio_e sound/work/esound-0.2.38 make all returned error 2 Command output: make: *** No rule to make target `all'. Stop. Error: Status 1 encountered during processing. Exit 1 It works for me. Try 'port clean --all esound' and try it again. Also make sure you have done a selfupdate if you haven't done it recently. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: esound won't install
David Moylan [EMAIL PROTECTED] writes: I posted this same error to the list. Who's the maintainer? Use 'port info esound' Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: faac and faad2 errors
AstroDrabb [EMAIL PROTECTED] writes: I am trying to install all the dependencies for avidemux2. The version in Macports is 2.0.x and the current source I can download is 2.4. I wanted to use MacPorts to install all the dependencies and then manually build and install avidemux. Avidemux has not been updated because the newer versions are very challenging to get compiled on OS X. You might want to try a binary. Hopefully later builds will shake out and someone will update the port. http://avidemux.org/admForum/viewtopic.php?id=3610p=1 Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
MacPorts Docs Strategy - Proposal
The work on the new guide is progressing steadily, but one thing has become apparent. We need to unify our documentation efforts. The manpages proceed on a separate path from the guide docs, and we on the doc team (Maun Suang , Simon Ruderich, and I) think that the man pages should be rewriten in DocBook and then xincluded into the guide reference section, thereby unifying the guide with the manpages. Simon has tested this method of inclusion to hte new guide and it works. Changes proposed: 1) Change macports.conf.5 man page to portconf.5 and include info for sources.conf and variants.conf, or create sources.conf and variants.conf man pages for consistency. 2) Create a trunk/doc/man directory to hold the DocBook man page sources. 3) Modify the guide to xinclude the rewritten man page xml sources. 4) Modify the guide Makefile as necessary, Simon has that mapped out already. 5) After ensuring that the guide and the wiki have within them all the notes from various text files within trunk, delete these legacy documents. base/doc/INTERNALS, trunk, base/HACKING, etc. The goal is one source for a given type of information, be it the guide or the wiki. I think as far as process, the major changes will be: 1) Man pages need to be rewritten 2) Man page formats will look slightly different, not exactly how we're used to seeing them. 3) People other than those on the doc team should make trac tickets against the documentation milestone, unless the changes are trivial. There are naturally exceptions, but similar rules should be followed as with other trunk modifications. This can all happen fairly quickly, as long as we can agree that this is the direction we need to go. Any objections? Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Installing Apache2, PHP5, and MySQL5 using PortAuthority
Ryan Schmidt [EMAIL PROTECTED] writes: I have no information about PortAuthority. I assume it's supposed to be able to do every MacPorts command you can do from the command line, but I've never used it and you'll have to consult its documentation or its author if you have questions about it. What you want is easy to do on the command line. Do you want to run a MySQL 5 server on your iBook, or just get PHP 5 compiled with the MySQL 5 libraries so that you can connect to another MySQL 5 server running somewhere? I assume you want to run a server yourself. To do so: sudo port install mysql5 +server (If you did not want a MySQL 5 server of your own, you can omit +server.) To get PHP 5 with MySQL 5 support and the Apache 2 libphp5.so module, and get the apache2 port installed as well: sudo port install php5 +apache2 +mysql5 To discover what variants a port has which might be interesting to you, do e.g.: port variants php5 But the ui_msgs for php5 are still not right. http://trac.macosforge.org/projects/macports/ticket/12108 So you might want to use these instructions in this NeDi howto. http://homepage.mac.com/duling/halfdozen/NeDi-Howto.html Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Tripwire fails to install
Tobias Weisserth [EMAIL PROTECTED] writes: the Tripwire port is broken and seemingly no longer maintained (as are a lot of macports :-( ). Show me a collection of thousands of ports on any platform, and I'll show you a lot of broken ones. ;) But the current stable version of Tripwire compiles on Mac OS X 10.4.10 PPC without any issue. Contact me privately if you need help. I've tried to fix this port in the past, but I think there were problems with it. If 2.4.1.2 installs cleanly, then updating the port should be very simple. Please send me exactly the steps you use to install tripwire manually on OS X (ports just mimic manual instal steps), and I'll update the port. Also, include any configuration steps you use to get it running (even if it is read file INSTALL) since we don't like to leave people clueless after the instal. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Uninstall not removing packages?
Have you tried uninstalling using the case-sensitive portname? I don't have time to look right now, but I think there is a bug filed on this. I think you can install without matching the case, but when you ininstall without matching the case it doesn't work correctly. Mark Troy Telford [EMAIL PROTECTED] writes: Simple enough: I uninstalled a couple of packages, in particular, TeTeX, and XeTeX. (port uninstall tetex port uninstall xetex) Port claimed to have uninstalled both without error, problems, etc. However, nothing was uninstalled. All of the files for both packages are still there. So, I tried re-installing both. That failed, because the same files were already in place. I next re-installed, using the '-f' switch to force it. Lots of file renames, and port re-installed the package. I deleted the renamed files. I then tried to uninstall the package. Same deal as before -- files which should have been deleted weren't. Has anybody seen this behavior and/or have an idea what I need to do to uninstall these packages? (the thought already occured to me to make a list of the 'renamed' files, edit the list so it's the original filenames, then 'cat list | xargs rm') But I'd rather macports do it properly. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Error stops installing gnome/dia
Martin Trejo [EMAIL PROTECTED] writes: I'm trying to install gnome/dia but I'm getting this error: --- Configuring xrender Error: Target org.macports.configure returned: configure failure: shell command cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xrender/work/libXrender- 0.9.0 ./configure --prefix=/opt/local returned error 1 Command output: checking if /usr/bin/gcc-4.0 supports -fno-rtti -fno-exceptions... no checking for /usr/bin/gcc-4.0 option to produce PIC... -fno-common checking if /usr/bin/gcc-4.0 PIC flag -fno-common works... yes checking if /usr/bin/gcc-4.0 supports -c -o file.o... yes checking whether the /usr/bin/gcc-4.0 linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... darwin8.8.5 dyld checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag CXX to libtool checking for ld used by /usr/bin/g++- 4.0... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... no checking whether the /usr/bin/g++-4.0 linker (/usr/bin/ld) supports shared libraries... yes checking for /usr/bin/g++-4.0 option to produce PIC... -fno-common checking if /usr/bin/g++-4.0 PIC flag -fno-common works... yes checking if /usr/bin/g++-4.0 supports -c -o file.o... yes checking whether the /usr/bin/g++-4.0 linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... darwin8.8.5 dyld checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes appending configuration tag F77 to libtool checking for pkg-config... /opt/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for X_CFLAGS... checking for X_LIBS... checking for X... no configure: error: X is required, but it was either disabled or not found. Error: The following dependencies failed to build: gtk2 pango Xft2 xrender cairo tiff jpeg libart_lgpl libxslt popt Error: Status 1 encountered during processing. I have X installed from Apple's media that might be a problem? Have you installed the X11 SDK? http://geeklair.net/new_macports_guide/#installing.x11 Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: (no subject)
David C Black [EMAIL PROTECTED] writes: I looked around the website and could find no definitive statement of what MacPorts is supposed to be. Lots of join us, but no this project is/does paragraphs. I would expect to find such a paragraph at the top of the HOME page. Using Mac since 1984. Unix since 1978. The website needs an overhaul and I think plans are in the works. The MacPorts Guide is brand new (in development and unfinished) and makes an attempt to say what it is/does. http://geeklair.net/new_macports_guide/ I think shortly we will link it on the current website. Critiques of the new guide are welcome. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Overwriting config files
Anders F Björklund [EMAIL PROTECTED] writes: If a port installs a foo.cf.sample it might want to copy foo.cf.sample to foo.cf iff foo.cf doesn't exist. This is probably common enough that the port author shouldn't be forced to write an on-install foo.cf.sample [ ! -f foo.cf ] cp foo.cf.sample foo.cf I don't understand what functionality requested by Brian cannot be met by MacPorts 1.5.2 as it is today. It's an enhancement alright, but I think that it would fit in great with the need of packages to signify which files are configuration ? In essence doing port install/uninstall and binary archives/packages have different needs, but I think it would be great to have features for both of them. And I do prefer simply listing the conffiles, rather than having to write any such install/uninstall scripts manually. I think having 'dodoc' and 'dobin' macros or some such like Gentoo would be very nice. I'm not sure what I 'doconf' would do but it could be useful. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem installing gnome-doc-utils
Anders F Björklund [EMAIL PROTECTED] writes: selfupdate is broken on some platforms, and sometimes a newer MacPorts release is broken itself, so user might prefer to just update the ports tree - without having to update base itself... It's possible to update base later, without using selfupdate. Yes I'm now convinced of the utility of sync due to the points made by Keith and yourself. And cross-platform issues regarding selfupdate is something I hadn't considered. I'll accomodate that in the docs when I add the writeup for port sync to keep it is general as possible. Thanks. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem installing gnome-doc-utils
Half an hour normally. Then use `sudo port sync` to update your ports tree and to get the newest updates. Then run the command. Are there good reasons not to do a selfupdate? I haven't even documented 'port sync' in the new guide because I'm still waiting for an argument for its utility. Can someone tell me why we tell people to do a 'port sync'? I don't understood that. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: gtk2 compiling problem
Michael [EMAIL PROTECTED] writes: I've wondered whether there might be a problem with a mismatch of the installed XCode and the version of MacPorts in play here - neither http://www.macports.org/ nor http://trac.macosforge.org/projects/macports/wiki/InstallingMacPorts are particularly helpful in sorting out the question of what 10.3.x needs/can use. I only installed 1.510 (specifically the 10.3 variant) because there appeared to be nothing to contradict doing so and using an earlier version appropriate to the installed XCode. I considered installing the X11 SDK from XCode 2.4.1, perhaps some other parts of it, too, but demurred; why complicate matters? Yes, the install docs don't cover 10.3. But 10.3 is not heavily used and it will soon not be among the most recent two releases, which is our target audience. It could be added though, it just wasn't the top priority because the docs were so lacking in commonly needed things. I'm also unclear on the syntax for using variants on the command line; http://trac.macosforge.org/projects/macports/wiki/UsingMacPortsQuickStart is muddy on this subject... Information is not bubbling to the surface. The QuickStart needs some work, or perhaps some parts can be removed that are handled in the new guide. See if it is better on the subject of variants; I added some on that topic just last night. http://geeklair.net/new_macports_guide/ Look in Using MacPorts. What isn't clear can be changed so let us know. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem installing gnome-doc-utils
Simon Ruderich [EMAIL PROTECTED] writes: I think for normal users there is no difference and you are right, it would be better to use selfupdate. I should have used that in the mail, thanks for the hint; will do next time. Oh I wasn't meaning to say you shouldn't tell people to use 'port sync', it was just my way of finding out why it is used. Personally I use sync because it's faster and I can be sure my port command is not updated (which would cause some problems in my setup). But for casual users selfupdate is indeed better. I see. Yeah that makes sense. I think both should be documented (because undocumented features are not so good) but the selfupdate should be marked clearly as the better thing to do. Yes I agree. I'll put it in as the lesser used option for those that want it the next chance I get. Thanks. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: gtk2 compiling problem
Michael [EMAIL PROTECTED] writes: There should be a bit more specificity about the assumptions made at your end, or the scope of what interests you. 10.3, implicitly does (at the moment), else there wouldn't be a version specific to it available. But there's a forgotten ignorance at play when macports.org sternly refers to installing XCode 2.4.x, which, it turns out, requires 10.4.2 or higher. One hand should know what the other is doing. Or phrase things in less absolute terms e.g. ideally,..., etc.. I still wonder whether various parts of the latter version of XCode (e.g. the X11 SDK) can be installed over that version supplied with XC 1.5... This describes a perfect world. In this one even the deep pockets puts less effort into products towards the end of their life cycles. The document you are referring to was only recently made, so the top priority for docs was our largest installed base. Now the top priority is completion of a comprehensive documentation (the new guide) , which happens to be common to all platforms. The news docs have been progressing steadily and may be mostly feature complete fairly soon. At that time tweaking them so they document 10.3 would be fine, though it may require some contributions from people still on 10.3 and that may not happen. But spending time trying to do it now would be negligent since it would make most of our users wait to have even feature completed rough documentation for a few users. If this weren't a volunteer projects priorities could be very different, but in fact they often aren't. Yes, the install docs don't cover 10.3. If you keep a last-but-one version (1.4, from what I can see at the moment), is it so hard to archive complete prior versions - docs and all - and make them available on a yer-on-yer-own basis? When we get docs that are even roughly feature complete that would be possible, but the fact is (at least in my opinion) that the Mac community is very, very agressive about upgrading. And I think this is a departure from the communities surrounding the other Unices. We also don't support intalling previous versions of ports and such for similar reasons I think. Our community is different than the others. I like the fact that our community spends more time on new stuff than old, and I happen to think this is a weakness of some of the other Unix communities. That's why our ports tree tend to have newer ports than the others, the reason I came to MacPorts in the first place. All these things supply context to be considered when one says how things should be. To perform that should requires not doing some things we are doing now. So should requires votes behind it before it carries any weight. :) A single locus of info would be a great improvement all around - ideally on a single site, but at least something that's been vetted by the same set of eyeballs, or managed, in toto, by one person or group with a stylesheet in mind! Check. The new guide is vetted by one group and has a single CSS stylesheet. The InstallingMacPorts Wiki page is actually unnceccessary now, but I'm waiting to see how we rearrange our web site. Or if that takes too long I'll delete the Wiki page and replace it with a link to the new guide that now contains all the information right at the top. Metastasizing FAQs don't help in an already complicated, detail-fussy matter. I'm hoping the info at the link above will eventually be everywhere, or the only there. All true. I don't like the current FAQs either. I hope many parts may be also deleted after the new guide is done, and the few remaining can be reformatted and clarified. After that, having a different look and feel for the FAQ is not a bad thing because people should know they are not reading official docs. So in the main, I think we'll get down to one guide, one FAQ on the Wiki, some news related stuff on the Wiki, and very little else. I'm heartened to see that the above link begins with a description of the 'what it is' variety - something that's very difficult to find, ironically, on the macports.org site. I think the what it is type of information is lacking in the whole Unix app world in general. I think it is fairly rare actually. And we know the MacPorts site needs work badly and we're actively seeking those who can redesign it. For free, of course, so it limits the prospective candidates a bit. :) Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: gtk2 compiling problem
Michael [EMAIL PROTECTED] writes: Not having applied a diff patch before, I'm at something of a loss. I do expect it to get hairy, though. I'll add instructions for how to apply patches manually to the Creating Patchfiles section of the new guide tonight. I see I didn't put in anything about applying patches manually. But all you have to is this: cd /path/to/file/to/patch patch /path/to/patchfile That's it. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: dsocks compile error
Boey Maun Suang [EMAIL PROTECTED] writes: --- Building dsocks with target all Warning: Object directory not changed from original /opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_net_d socks/work/dsocks-1.6 cc -g -Wall -O2 -nostdlib -flat_namespace -fno-common -undefined suppress-c dsocks.c -o dsocks.o In file included from dsocks.c:35: dsocks.h:13: error: parse error before uint8_t /snip Hmm, I'm the maintainer, but I'm afraid I don't currently have a Panther installation to test this build on to see what the problem is. If anybody else out there with a Panther installation could see if they can reproduce the problem, I'd appreciate it greatly. Here is what I get on 10.3: DEBUG: Assembled command: 'cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_dsocks/work/dsocks-1.6 bsdmake all' Warning: Object directory not changed from original /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_dsocks/work/dsocks-1.6 cc -g -Wall -O2 -nostdlib -flat_namespace -fno-common -undefined suppress -c dsocks.c -o dsocks.o In file included from dsocks.c:35: dsocks.h:13: error: parse error before uint8_t dsocks.h:13: warning: no semicolon at end of struct or union dsocks.h:14: warning: type defaults to `int' in declaration of `cd' dsocks.h:14: warning: data definition has no type or storage class dsocks.h:15: error: parse error before dport dsocks.h:15: warning: type defaults to `int' in declaration of `dport' dsocks.h:15: warning: data definition has no type or storage class dsocks.h:16: error: parse error before dst dsocks.h:16: warning: type defaults to `int' in declaration of `dst' dsocks.h:16: warning: data definition has no type or storage class dsocks.h:31: error: parse error before uint8_t dsocks.h:31: warning: no semicolon at end of struct or union dsocks.h:32: warning: type defaults to `int' in declaration of `nmeths' dsocks.h:32: warning: data definition has no type or storage class dsocks.h:33: error: parse error before method dsocks.h:33: warning: type defaults to `int' in declaration of `method' dsocks.h:33: warning: data definition has no type or storage class dsocks.h:37: error: parse error before uint8_t dsocks.h:37: warning: no semicolon at end of struct or union dsocks.h:38: warning: type defaults to `int' in declaration of `cmd' dsocks.h:38: warning: data definition has no type or storage class dsocks.h:39: error: parse error before rsv dsocks.h:39: warning: type defaults to `int' in declaration of `rsv' dsocks.h:39: warning: data definition has no type or storage class dsocks.h:40: error: parse error before atyp dsocks.h:40: warning: type defaults to `int' in declaration of `atyp' dsocks.h:40: warning: data definition has no type or storage class dsocks.h:41: error: parse error before dst dsocks.h:41: warning: type defaults to `int' in declaration of `dst' dsocks.h:41: warning: data definition has no type or storage class dsocks.h:42: error: parse error before dport dsocks.h:42: warning: type defaults to `int' in declaration of `dport' dsocks.h:42: warning: data definition has no type or storage class dsocks.c: In function `_sin_aton': dsocks.c:56: error: `uint32_t' undeclared (first use in this function) dsocks.c:56: error: (Each undeclared identifier is reported only once dsocks.c:56: error: for each function it appears in.) dsocks.c:56: error: parse error before ip dsocks.c:57: error: `uint16_t' undeclared (first use in this function) dsocks.c:62: error: `ip' undeclared (first use in this function) dsocks.c:63: error: `port' undeclared (first use in this function) dsocks.c: In function `_dsocks4_connect': dsocks.c:90: error: dereferencing pointer to incomplete type dsocks.c:94: error: dereferencing pointer to incomplete type dsocks.c:95: error: dereferencing pointer to incomplete type dsocks.c:96: error: dereferencing pointer to incomplete type dsocks.c:97: error: dereferencing pointer to incomplete type dsocks.c:98: error: dereferencing pointer to incomplete type dsocks.c:111: error: dereferencing pointer to incomplete type dsocks.c:113: error: dereferencing pointer to incomplete type dsocks.c: In function `_dsocks5_connect': dsocks.c:146: error: storage size of `auth' isn't known dsocks.c:147: error: storage size of `msg' isn't known dsocks.c:146: warning: unused variable `auth' dsocks.c:147: warning: unused variable `msg' dsocks.c: In function `_send_recv_timeout': dsocks.c:202: error: variable `tv' has initializer but incomplete type dsocks.c:202: warning: excess elements in struct initializer dsocks.c:202: warning: (near initialization for `tv') dsocks.c:202: warning: excess elements in struct initializer dsocks.c:202: warning: (near initialization for `tv') dsocks.c:202: error: storage size of `tv' isn't known dsocks.c:202: warning: unused variable `tv' *** Error code 1 ___
Re: Wireshark build fails on 10.4.10 MacBook Core Duo
Chip Warden [EMAIL PROTECTED] writes: I'm trying to build Wireshark from MacPorts 1.5.1 on a 1st generation MacBook running OS X 10.4.10 with the following port command: sudo port -v install wireshark +adns +ipv6 +net_snmp +pcre The final error is: cc1: warnings being treated as errors In file included from /opt/local/include/glib-2.0/glib/ gasyncqueue.h:30, from /opt/local/include/glib-2.0/glib.h:32, from wtap-int.h:30, from 5views.c:30: /opt/local/include/glib-2.0/glib/gthread.h: In function 'g_once_init_enter': /opt/local/include/glib-2.0/glib/gthread.h:335: warning: cast discards qualifiers from pointer target type make[3]: *** [libwiretap_la-5views.lo] Error 1 make[2]: *** [all] Error 2 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Warning: the following items did not execute (for wireshark): org.macports.activate org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing. Has anyone else seen this? I've attached the entire 'port -v' output. I just tried it and I see the same thing on my MacBook Pro. Someone should create a ticket for it or ask the wireshark support list to go the extra mile. I suspect they would know the answer. I'm also cc'ing the maintainer. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem with p5-xml-sax
Keith J. Schultz [EMAIL PROTECTED] writes: Due to a disk error I had to rebuild everything. While installing gnome port has not been able to fetch p5-xml-sax or at least part of it for two days now. See below for the error messages. Can anyone help. It can not be that so many site are down for so long. It looks like a typo in the port file for xml-sax. Not sure though. reagards Keith Excerpt from sudo port -d install gnome: DEBUG: Searching for dependency: gdbm DEBUG: Didn't find receipt, going to depspec regex for: gdbm DEBUG: Skipping completed org.macports.main (p5-xml-sax) --- Fetching p5-xml-sax DEBUG: Executing org.macports.fetch (p5-xml-sax) --- XML-SAX-0.15.tar.gz doesn't seem to exist in /opt/local/var/ macports/distfiles/perl5 --- Attempting to fetch XML-SAX-0.15.tar.gz from http:// ftp.ucr.ac.cr/Unix/CPAN/modules/by-module/XML p5-xml-sax is now at 0.16 because the delveloper removed 0.15. You need to do frequent selfupdates. Do a port selfupdate and try again and it should work fine. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: strange bug with python24+darwin_8, py-wxpython and xml parsing
Lorenz Schori [EMAIL PROTECTED] writes:
Date: Mon, 06 Aug 2007 22:36:25 +0200
From: Mark Asbach asbach at ient.rwth-aachen.de
when using py-xml together with py-wxpython, I get a reproductible
bus error whenever I try to use sax or minidom (both relying on
expat). Invoking the parsers crashes the application with a bus
error. The workaround I found is to import xml.parsers.pyexpat before
importing wx - but this is a workaround, not a bug fix.
backtrace clipped
Can someone comment on this? What could I do to narrow the bug?
Hi Mark,
* This problem may be caused by wxPython being built/linking against
older versions of libexpat than pyexpat is.
Hi
Apparently the wxwidgets Portfile is causing this error.
configure.ldflags
lacks -L${prefix}/lib and thus configure thinks that expat does not
exist in
the system and links to its own version of the library.
I think the Portfile's configure.ldflags should be
configure.ldflags-append. -L${prefix}/lib is is a default now, but if you
don't use -append it gets overwritten.
Mark
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: package request - tn5250
Shawn Protsman [EMAIL PROTECTED] writes: Can anyone tell me what the official means is to request a new package? We are an iSeries shop and I'd like to use tn5250 ( http:// tn5250.sourceforge.net/ ) on my Mac. I use it on my SLED workstation all the time. tn5250 is in FreeBSD ports so I'd assume it wouldn't be too difficult to get it into Macports. Any suggestions? When I can get some spare time I'll look into creating the port file. Shaun, This appears to be a really easy one. Can you test it? Drop the attached Portfile somewhere on your disk, cd to the same directory, and execute sudo port install. Let us know if the app works ok and if so we'll commit it. If you'd like to be the port maintainer that'd be great too. Mark Portfile Description: Binary data ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem installing ntop
Ryan Schmidt [EMAIL PROTECTED] writes: When trying to install ntop + server on OS10.4.10 on a G4 PPC I am getting these (see below) errors (a similar install on a MacBook(intel) 10.4.10 was without problems). I am just a user, not an expert, does anyone can give me some advice ? Is this a Macports problem or a ntop problem ? I do not know where the problem lies. Have you already contacted the port's maintainer? I'm Cc'ing him on this email. I just installed the current ntop 3.2 on a clean PPC Mac mini with no problems. Are you using the latest Xcode, currently 2.4.1? That was what I was going to ask too. I see ntop 3.3 has been released. Perhaps the portfile should be updated. I can't get ntop 3.3 to build so I can't update it yet. I'm going to ask the ntop list about it. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: was p5-perlmagick .. do we need bugzilla 2.22?
Robert A. Decker [EMAIL PROTECTED] writes: I would love to use a more current version of bugzilla. I am using mysql5 now. The version of PerlMagick that this package is tied to definitely has a bug in it. I was able to download the 6.32 version of ImageMagick (which has PerlMagick in it) from http://www.imagemagick.org/script/ download.php and was able to build that without a problem. I did a diff between the two versions but there's too many diffs for it to really be useful. That's weird, but neither FreeBSD nor Gentoo even have a separate perlmagick port so it must not be necessary. Have you re-installed imagemagick using +perl? (I still haven't figured out how to let port know that I successfully installed PerlMagick - it seems to try to build it again each time, and of course fails) So, how do I go about using your bugzilla portfile? I attached a portfile for 3.0. To use it see the section Local Portfile Respositories here: http://geeklair.net/new_macports_guide/ One thing I don't understand it that it isn't creating a localconfig file like the docs say it should. I can't understand why. Mark Portfile Description: Binary data ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Full db44 error
miles3 [EMAIL PROTECTED] writes:
I have been having a very frustrating time trying to install Apache2
+openldap. which you probably know by now is dependent on db4 and db44.
Turns out there is a misconfiguration of db packages in the MacPorts
repository...full details can be found here:
http://concise-software.blogspot.com/2007/07/howto-sudo-port-install-db4.html
What this link tells you is to edit as Admin:
/opt/local/var/macports/sources/rsync.macports.org/release/ports/databases/db4/Portfile
Change the line:
configure.args --enable-compat185 --enable-dump185 --enable-cxx \
TO
configure.args --enable-cxx \
Unfortunately that does not work for me, since there is nothing in
.release/ports/
The solution is to run the command:
sudo port edit db4
and then remove the offending command
Do the same for db44 and any other db{x} you need to make.
Who do I talk to about fixing the repository? Why is it almost two weeks
without the system being fixed?
The concise-software blog author chose not to have his discussion on a
MacPorts list where it might be useful so we didn't benefit. He chose to
document a supposed bug rather than contribute to fixing it. But there
isn't much we can do about lone rangers.
But otherwise, I suspect that openldap should use db44 (a newer version)
rather than db4. So please try this:
uninstall db4
install db44
Change the openldap Portfile like this:
--- Portfile.org2007-07-30 09:30:48.0 -0700
+++ Portfile2007-07-30 09:36:58.0 -0700
@@ -20,12 +20,13 @@
depends_libport:perl5.8 \
port:cyrus-sasl2 \
port:openssl \
- port:db4
+ port:db44
patchfiles patch-ltmain
configure.env-append LANG=C
-configure.cppflags-append -I${prefix}/include/db4
-I${prefix}/include/openssl -DBIND_8_COMPAT
+configure.cppflags-append -I${prefix}/include/db44
-I${prefix}/include/openssl -DBIND_8_COMPAT
+configure.cflags-append-L${prefix}/lib/db44
configure.args --mandir=${prefix}/share/man \
--localstatedir=${prefix}/var \
The db44 port still has the arguments --enable-compat185
--enable-dump185, but I see the FreeBSD port uses those too and I wonder
if mr blogger is correct about removing those. I just installed openldap
using db44; please report if you have success with this method so we can
tell the openldap port maintainer so he can fix it.
Mark
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Error compiling gtk-sharp
Marcus Vinicius Eiffle Duarte [EMAIL PROTECTED] writes: I am a newbie in MacOS X (been using it for almost a year now), with some Linux background. I am running MacOS X 10.4.10 on a Intel Core Duo MacBook Pro. I downloaded and installed MacPorts 1.5 in order to try and install MonoDevelop (I use Mono 1.2.4, installed from the binary provided at [ http://mono-project.org ]mono-project.org, which does not include gtk-sharp and applications that use it). So, after installing MacPorts 1.5.0, I ran 'sudo port -v selfupdate' and then installed a few apps to test MacPorts: Dia and Planner. Next, I tried installing Gtk#, running 'sudo port -v install gtk-sharp'. The connection to [ http://macports.org ]macports.org was closed a few times while fetching tarballs, but after some time, all the source was downloaded and compiled, until I got the error I copied at the end of my message. As I understand it, the code was compiled, but something failed during the activation phase. I thought it was something related to an improper path, but could not understand how to fix it. The file gapi_codegen.exe was built and lies at /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_gtk-sharp/work/gtk- sharp-1.0.10/generator/gapi_codegen.exe. Can somebody help me? Well I know nothing about gtk-sharp, but it seems like gtk-sharp 1.0.10 would be for GTK v1. It seems like it needs to be updated to v2.10.0. http://go-mono.com/sources-stable/ Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: what is an inactive port?
Yves de Champlain [EMAIL PROTECTED] writes: The link seems to have changed. http://geeklair.net/new_macports_guide/#id934418 Both links take me to the top of the page. Hmn. I guess the doc regen must change the link numbers. I thought they'd be consistent. Oh well, I was referring to section 6.3. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: creating ports - howto
Bakki Kudva [EMAIL PROTECTED] writes: Where is the documentation on how to create ports? I sort of have an idea by looking in existing port files etc but is there a canonical doc on this? I need the port wv which is broken. There is no maintainer for it so I thought I'd roll my own. Thanks for any pointers, The new guide is a work in progress, but it is here: http://geeklair.net/new_macports_guide/ The old guide is here: http://geeklair.net/macports_guide/ That's the best we have right now. I just installed the wv port; what it theproblem with it? Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: what is an inactive port?
Michael Thon [EMAIL PROTECTED] writes: Could someone explain to me what an inactive port is? This may help to explain why unactivated ports exist. http://geeklair.net/new_macports_guide/#id975763 So MacPorts does not assume you'll never want to use a deactivated port, even if most people never will. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: what is an inactive port?
Ryan Schmidt [EMAIL PROTECTED] writes: This may help to explain why unactivated ports exist. http://geeklair.net/new_macports_guide/#id975763 So MacPorts does not assume you'll never want to use a deactivated port, even if most people never will. There does not appear to be any id975763 anchor or id on that page so that just shows me the top of the guide. The link seems to have changed. http://geeklair.net/new_macports_guide/#id934418 Markmacp ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
apr 0.9.13 tarball removed on some mirrors - was Re: Hydra install
Mervyn [EMAIL PROTECTED] writes: Hi Macports gurus, I'm trying to install Hydra and got the following error. Any idea what is wrong? barcajax:~ barcajax$ sudo port install hydra --- Fetching apr0 --- Attempting to fetch apr-0.9.13.tar.bz2 from [Image] [ http://www.apache.org/dist/apr ]http://www.apache.org/dist/apr --- Attempting to fetch apr-0.9.13.tar.bz2 from [Image] [ http://apache.planetmirror.com.au/dist/apr ]http://apache.planetmirror.com.au/dist/apr --- Attempting to fetch apr-0.9.13.tar.bz2 from [ ftp://ftp.planetmirror.com/pub/apache/dist/apr ]ftp://ftp.planetmirror.com/pub/apache/dist/apr --- Attempting to fetch apr-0.9.13.tar.bz2 from [ ftp://ftp.is.co.za/Apache/dist/apr ]ftp://ftp.is.co.za/Apache/dist/apr --- Attempting to fetch apr-0.9.13.tar.bz2 from [ ftp://ftp.infoscience.co.jp/pub/net/apache/dist/apr ] ftp://ftp.infoscience.co.jp/pub/net/apache/dist/apr --- Attempting to fetch apr-0.9.13.tar.bz2 from [Image] [ http://svn.macports.org/repository/macports/distfiles/apr0 ]http://svn.macports.org/repository/macports/distfiles/apr0 --- Attempting to fetch apr-0.9.13.tar.bz2 from [Image] [ http://svn.macports.org/repository/macports/distfiles/general/ ]http://svn.macports.org/repository/macports/distfiles/general/ --- Attempting to fetch apr-0.9.13.tar.bz2 from [Image] [ http://svn.macports.org/repository/macports/downloads/apr0 ] http://svn.macports.org/repository/macports/downloads/apr0 Error: Target org.macports.fetch returned: fetch failed Error: The following dependencies failed to build: apr0 libssh Error: Status 1 encountered during processing. --- Attempting to fetch apr-0.9.13.tar.bz2 from ftp://ftp.infoscience.co.jp/pub/net/apache/dist/apr % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 839k 100 839k0 0 53761 0 0:00:15 0:00:15 --:--:-- 284k --- Verifying checksum(s) for apr0 DEBUG: Executing org.macports.checksum (apr0) --- Checksumming apr-0.9.13.tar.bz2 DEBUG: Correct (md5) checksum for apr-0.9.13.tar.bz2 It was found on the mirror above after failing on the previous ones for me. But it fails on the previous master_sites because it was replaced by 0.9.14. Do a port clean --all hydra and try it again. If it still fails you can download 0.9.13 from infoscience and put it in /opt/local/var/macports/distfiles/apr (don't clean after the fetch failure or apr/ will be gone). I'm ccing the port maintainer so he may update it if he wishes. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: A question about xpdf and t1lib
Martin Buchmann [EMAIL PROTECTED] writes: this post corresponds to a ticket opened by me (#12316). I tried to install xpdf on my new MacBook but it fails because the dependency t1lib wasn't installed because it couldn't be found. I tried to find it on the web but it seems that the version specified in the portfile is outdated and I could not find it either. I had never problems like these installing xpdf on my PowerMac G5 before. It seems that there is no active maintainer of t1lib and xpdf at the moment and I don't know how to fix the portfile. Would this be hard to learn? Can anyone tell me how to tell port where to find the recent version of t1lib? Martin, I just updated t1lib to 5.1.1. After a few hours do a selfupdate and try again. The MacPorts guide is still under construction, but even unfinished it may help to explain a little about making and modifing portfiles. http://geeklair.net/new_macports_guide/ Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Transmission Build Error
Daniel Laughlin [EMAIL PROTECTED] writes: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_transmission/work/Transmission-0.6.1/build/Transmission.build/Debug/libtransmission.build/Objects-normal/ppc/net.o error: couldn't exec /usr/bin/gcc-3.3: No such file or directory I don't know why it can't find gcc3, though I don't know why the app wants it either. But given that it wants it that may be the problem. Perhaps it uses gcc3 just for the transmission CLI for some bizarre reason. The transmission port is a little out of date also. so perhaps updateing it would fix it too. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Transmission Build Error
Daniel Laughlin [EMAIL PROTECTED] writes: I tried installing Transmission and I got the following error: --- Fetching transmission --- Attempting to fetch Transmission-0.6.1.tar.gz from [ http://download.m0k.org/transmission/files/ ]http://download.m0k.org/transmission/files/ --- Verifying checksum(s) for transmission --- Extracting transmission --- Configuring transmission --- Building transmission with target all --- Staging transmission into destroot Error: Target org.macports.destroot returned: xinstall: Cannot stat: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_transmission/work/Transmission-0.6.1/cli/transmissioncli, No such file or directory Error: Status 1 encountered during processing. Try using debug to get more information. If that file isn't there it must have failed to build so there should be an error earlier and it may have been suppressed. sudo port -v install transmission Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: X needed. What is this?
olivier SAINT-EVE [EMAIL PROTECTED] on Wednesday, July 18, 2007 at 8:08 AM -0800 wrote: Hello, when I try to install cairo, I have the following error message: checking for X_CFLAGS... checking for X_LIBS... checking for X... no configure: error: X is required, but it was either disabled or not found. After a re-installation, it's the first port I install. Do you know what is X, and where find it? thank you, It sounds like you haven't installed X11. See section 2.2 here: http://homepage.mac.com/duling/macports/guide.html Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: A newbie question
Jan Erik Moström [EMAIL PROTECTED] on Wednesday, July 18, 2007 at 8:29 AM -0800 wrote: I've just installed port and have installed apache2. Unfortunately, it doesn't seem to work when I try to connect to it (127.0.0.1 gives a can't connect message). I think it's running since I have a process: /opt/local/bin/daemondo --label=apache2 --start-cmd /opt/local/et And I can't really figure out where the config files etc are for the installation (I'm used to a standard linux installation), etc. So my question is: where do I find documentation of the different ports, for example where conf files are stored? 'port installed' will tell you where all files are stored. See if this helps: http://homepage.mac.com/duling/halfdozen/NeDi-Howto.html#d0e152 You may ignore the parts about PHP if you don't need it. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: portslocation
Denis Bueno [EMAIL PROTECTED] writes: As I understand it, darwinports.com is not to be trusted in general, and certainly not in particular with respect to Macports. (I am willing to be corrected; I got that impression from another thread on this mailing list.) Darwinports.com and macports.org are not affiliated. So whatever you read on there probably has no bearing to your macports installation If you'd like to see whether the gaim port is available on your system: sudo port search gaim Unfortunately for you, I don't think it is. Correct, anything not using the name MacPorts is not official. darwinports dot com is someone's attempt to provide 3rd party support, and it is not accurate. And a file called portslocation has never existed. There is a new guide under development here: http://homepage.mac.com/duling/macports/guide.html to tell you how to install ports. Looks like the gaim project has been renamed http://sourceforge.net/projects/gaim/ to pidgin. Try installing the pidgin port. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: After binding server to directory service lighttpd and mongrel won't start
Sterling Anderson [EMAIL PROTECTED] writes: I needed to bind my server to our organization's Active Directory domain today and after that now LightTPD and Mongrel refuse to start on reboot. I can unload, then load the LaunchDaemons for each item and things are fine, but obviously I'd rather not have to do that every time I reboot the server. I had the exact same issue last month with just LightTPD, you can see the thread here: http://lists.macosforge.org/pipermail/macports-users/2007-June/ 004009.html Now that I've added the AD to the mix I'm wondering if there is something I can try different. Any suggestions? Sterling, Can you be more specific? Did inserting this into the .plist file allow the LightTPD to startup at boot or not? string--restart-netchange/string Or did it work and now suddenly it fails to boot again after changing trying to authenticate against active directory? If it needs to wait after boot a bit to work, and I've seen some apps this way, you can use a wrapper shell script with a sleep 30 in it to introduce a 30s delay. See the snort port because it does this. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Upgrading from 10.3 to 10.4
Malcolm Fitzgerald [EMAIL PROTECTED] on Monday, July 16, 2007 at 5:30 PM -0800 wrote: I've just upgraded to 10.4. At this point everything seems to be running smoothly in X11. Is there anything that I should be or could be doing in MacPorts to facilitate this upgrade? If I'm not mistaken no one has responded, but I'm not sure what you are asking. Can you clarify your question? Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: qt3-mac
Giuseppe Di Matteo [EMAIL PROTECTED] on Saturday, July 14, 2007 at 11:29 AM -0800 wrote: I want to install LyX but I'm having problems with the dependency qt3-mac: There is a ticket on qt3-mac, but the problem seems to be different for you. http://trac.macosforge.org/projects/macports/ticket/11895 But the Lyx port is broken anyway. I'd take a crack at fixing it but I've hit a wall with qt3-mac also and so I haven't been able to. At teh Lyx ftp site there is an OS X binary so I'd use that for now. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Checked in the current draft of the new guide
Juan Manuel Palacios [EMAIL PROTECTED] on Thursday, July 12, 2007 at 5:24 PM -0800 wrote: First off, and even if it's just a first draft that we can improve as we learn from experience, I'd like to see a single all- encompassing guide too, with a users oriented first section and a developers section in which we can put all the Portfile reference stuff and others not geared for regular users. If this proves to be hard to manage and a lot of voices raise up asking for a simple and short user reference, I'm figuring we can always take the contents of the rewritten guide and split them up in two. My thoughts exactly. Though I did not end up dividing cleanly into users/developers parts, I personally think that since even newbies these days sometimes ask How do I modify a Portile?, that the guide is better sectioned functionally according MacPorts itself, rather than by hypothetical types of users. But still, more or less the first part is the using part, the middle part tends towards development, and the end is pretty advanced stuff. Not clear lines, but I think the sections make the guide fairly intuitive nonetheless. At least I hope, and others are certainly free to disagree or suggest changes. We spoke about committing to svn and you expressed your thoughts and concerns about it, but I didn't manage to reply at the moment due to a lack of time. In a nutshell, I'd really love to see your work in our tree so that all those willing to contribute can do it in a more timely fashion (I know I would have already contributed three or four fixes if I had access to the sources ;-). But I understand that since you're not amending what we have but actually rewriting it, you prefer to keep from committing until your sources become an actual drop in replacement for what's already there. So how's the following: you write up the new guide up to the point where it can replace to a good extent what we have, even leaving empty certain sections/areas if you have to because you don't have enough information to write it up on your own, and you commit that? Once that's in all of us can dive in and help you complete it. I'm even thinking that for the sections you can't rewrite, but what's in the old guide suffices for them to whatever extent, you can simply copy paste that into the new sources and write up a marker saying THIS IS OLD, NEEDS REWRITING! for contributors to notice. More over, we can all agree to nominate Maun Suang and you Guide Masters: rather than simply diving in and committing patches to the sources in svn, we instead upload them to tickets in the Documentation milestone and you guys, governing that milestone, review them and decide when/how to commit them, rewriting them if need be. Sounds like a decent plan to me. I just committed what I have so far. xml/newguide.xml http://trac.macosforge.org/projects/macports/browser/trunk/doc/guide/xml/newguide.xml?rev=26949 resources/newdocbook.css http://trac.macosforge.org/projects/macports/browser/trunk/doc/guide/resources/newdocbook.css?rev=26950 Hack away! Needs work in the reference sections, among others. 6.2 and 6.3 have placeholders for keywords and Tcl primitives respectively. Full comments in the svn checkout logs. See the the updated copy with a slightly different stylesheet at my .mac page for those wanting a peek at the draft of the new guide. Colors are awful! You have been warned! http://homepage.mac.com/duling/macports/guide.html Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Checked in the current draft of the new guide
Juan Manuel Palacios [EMAIL PROTECTED] on Friday, July 13, 2007 at 10:23 AM -0800 wrote: I cleaned up some of our documentation tickets up on trac: *) renamed the doc component to guide *) relocated most of the old doc component tickets I could find to more appropriate components, of course leaving there the ones that belong. What I intended with these changes is the following: we now have a documentation milestone and two documentation related components, base and guide, the former for stuff like our man pages (and maybe doxygen like in source documentation in the future) and the latter being self explanatory; any new documentation related tickets should be filed under the appropriate milestone and its component flagged accordingly. I believe this split gives us nicely, fine- grained enough (but not too much) organizational choices. Please feel free to suggest something different if you believe this will not suite us (but if you do, you're gonna have to help me through trac adapting tickets as needed! :-P) These changes sound sensible to me. So, moving forward, I skimmed over the new guide sources and filed my first ticket: http://trac.macports.org/projects/macports/ticket/12284 Guide Masters, start your engines! I just committed it. Thanks! Once the new guide properly replaces the old one we're gonna have to think about removing the latter and adapting the Makefile targets and GuideRegen.sh script to build the new one. Mark, how are you currently building the new guide? Any automation put into that? (hint: base/portmgr/GuideRegen.sh) No automation yet. I'm using a GUI tranform tool, XFC from XMlmind. I'm a poor excuse for a geek. :) I'm going to examine the GuideRegen.sh to learn how to do it via terminal commands. I'm hoping you guys can give us a heads-up when you believe we're ready to flip the coin and make this change (I'm figuring at that point the trunk/doc/guide/xml/newguide.xml file will have to be renamed to something more appropriate). I'll be interested in seeing: 1) the response from the community as far as how usable they think it is. 2) whether developers are interested in populating the reference sections so that the guide becomes a true reference guide. And we desperately need someone to give the sylesheet some CSS love and make it blend with the overall MacPorts site. I really want to keep the TOC sidebar; that's my baby, but the colors and other look/feel items need someone less artistically challenged. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts 1.5.0 and binary packaging / New improved Guide
Boey Maun Suang [EMAIL PROTECTED] on Thursday, July 12, 2007 at 10:16 AM -0800 wrote: Comments still welcome on the Guide so far. I haven't been through it in detail, but it looks good to me. I haven't thought too clearly about what, if anything, should become of the old guide (I don't know if a separate technical reference is warranted, which seems to be what the old guide leans towards). Perhaps we can post them somewhere and solicit feedback from users as to what they find easiest to understand and use, and what they think ought to be included or restructured. I really wanted the new guide to serve as technical reference also, at least for now. I wanted the Portfile Reference section to be more or less exhaustive. If that should turn out too large then it could be split out into a separate reference, but I'm not sure it will be that large. My two goals for he new guide was 1) better organization, and 2) more or less exhaustive Using MacPorts and Portfile Reference sections. The latter to give us a place to stick all the helpful information about keywords and commands that we exchange on the list now, and often forget. Those things should go in the guide but the old guide had no structure to contain them, and I don't think a FAQ is adequate. As for the source of your guide, which I understand is a DocBook article, would be able to put it into the doc/ part of the repository so that we can look at it? I understand if you'd like to hang onto control of it yourself (saves me some work, for a start :P), but I think it'd be helpful if the source was somewhere that all those interested in the working on documentation could see it. Here's where I need some advice. I did the new guide as an article and in one XML file because that was more familiar to me. Should I switch to a book and/or split the XML into multiple files? Anders has reminded me that the copyright information frm the old guide needs to be added back in and I haven't got there yet. Other than that those questions I'm willing to commit it to svn. And I can't fill in the reference sections fully by myself anyway so it does need to be committed very soon. Let me know your thoughts on that. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
MacPorts 1.5.0 and binary packaging / New improved Guide
Juan Manuel Palacios [EMAIL PROTECTED] on Monday, July 9, 2007 at 11:54 PM -0800 wrote: 2) Even though still not complete, extensive work on the generation of rpm's off MacPorts Portfiles has pushed forward our ability to generate real binary packages, improving both the building of the rpm tool itself on Mac OS X and the rpm MacPorts target (renamed from rpmpackage) that creates the corresponding rpm files/packages. These packages still need to be generated by users off their own MacPorts installations (port rpm port), and flawless functionality for each of them is still not guaranteed, unfortunately. For instance, one long standing shortcoming still with us is that rpm installed software (even if the package is generated through MacPorts) is separate from MacPorts installed software, they are still two different universes that don't talk to each other even if installed into the same /opt/local prefix. However, strong developer momentum on the packaging front raises our hope that the goal of providing fully working and ironed out binary packages will be reached eventually! I am progressing on the new Guide. I mispoke when I called the new Guide minimalist, because that implies stuff will be left out. I only intended to streamline and rewrite it (some explanations were verbose and redundant) but leave no material out. I just added all the sections that I think need to be in it and I inserted the contents of MacPorts Internals stuff from the old guide too. Shouldn't be long now that all the data will be mined from the old guide. Not that the work is over since improvments will still be needed, but at least we can look forward to those rather than looking backwards and trying to capture what used to be. http://homepage.mac.com/duling/macports/guide.html Comments still welcome on the Guide so far. It needs some color css work and other css formatting, but I'm focusing on content and readability. I don't feel competant to write Section 7, Packaging Ports into Binaries. Can anyone who understands the packaging process throw some text at me on this topic? Doesn't have to be much or pretty, I can rewrite it but I just something more or less technically accurate to start with. Or point me to a similar section in another package manager if that is possible. I'm just not that familiar with the whole topic and the manpage doesn't say that much. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts 1.5.0 and binary packaging / New improved Guide
Anders F Björklund [EMAIL PROTECTED] on Tuesday, July 10, 2007 at 5:41 AM -0800 wrote: There are some common typos in it like OS X (Mac OS X) and Xwindows (X Window System) and it should probably be less Apple/Mac OS X centric (i.e. should mention explicitly that 2.1-2.5 applies to Mac OS X, and say something instead of Apple-supplied - like vendor-supplied, etc etc...) It would also be nice if it could mention open source and free software, instead of just saying open source Unix software and not mentioning GNU ? This is IMHO also another reason why it is important to get License metadata into the ports, as it is now you'll have to dig through homepages/licenses. You can look at the old guide for some hints, it uses third party software and has much more info on the common heritage with the BSD Ports/collections. A MacPorts for people used to *BSD Ports section might even be a good idea. Besides regular Mac OS X, MacPorts is also usable on FreeBSD (with GNUstep). All good points. I haven't yet got to that level of detail yet, but I agree with you it needs to be done. I'll hang onto these suggestions and address them the best I can after getting all the raw data I can from the old guide. I will try to be of some assistance about those, we can take either in the regular guide xml or if you're doing some kind of parallel guide we can discuss it here on these mailing lists or on some Wiki page... As it is now we have two kinds of binaries: ARCHIVES (.tgz, .tbz, etc) and PACKAGES (.pkg, .rpm, etc). Eventually these might both be able to use the same XAR archive, but as of now they're still separate... The archives are created with port archive or by enabling archivemode. They can (confusingly!) be found under /opt/local/var/macports/packages with subdirectories for each platform (e.g. darwin) and arch (e.g. i386) The packages are created with something like port pkg or port rpm and are found in either the work directory or /opt/local/src/macports. Since .pkg is a dir bundle, it is converted to one file with port dmg. The main differences is that the archives are used within the port system, to avoid having to rebuild a port from source, and that the packages are used outside the port system, without even needing MacPorts installed. Besides the binary packages, we also have source packages. These consist of the Portfile and all needed files/ (patches and other supporting files), and they come in either .portpkg (XAR) or .nosrc.rpm (SRPM) flavors. Normally there is not much need to use source packages, since the binary packages can be built directly from the ports tree (whether rsync or svn) but they are useful for port submissions or for storage of older versions. In order to build a new binary from a source package, all the corresponding distfiles are also needed. Normally these are only kept around as checksums, but can be mirrored locally - or even included in the case of .src.rpm. When building packages, all dependencies must be installed from ports or archives - installations made from packages do not help and must be redone. This is because the binary packages are *not* registered within MacPorts. Hopefully that should be enough to start, and let me know if I am mistaken... I'll have to look at your descriptions later tonight (I hope) and write something up and send it back to the list for more peer review. BTW, I don't want a parallel guide; I'd like to get the new one replaced and I'm willing to go take whatever suggestions, contributions, or changes the community thinks necessary to make a new guide official. I just think the modifying the old guide is too difficult if we want very much improvement. Thanks very much for your help! Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts 1.5.0 and binary packaging / New improved Guide
Anders F Björklund [EMAIL PROTECTED] on Tuesday, July 10, 2007 at 2:32 PM -0800 wrote: Don't get me wrong here, I don't think there is anything wrong whatsoever with using Apple and Mac terms to describe how you install MacPorts on Apple Mac OS X. But everywhere? Nah. we're talking about something minor like changing Installing MacPorts to Installing MacPorts on Mac OS X and avoiding limiting the entire system to just the Apple Macs. Don't see how Mac OS X and other platforms or Apple or other vendors would hurt anything. Unless the project clearly defines that it will remove all old code for Darwin and for FreeBSD. I think that writing the guide so it is has enough generality to accomodate other operating systems is a good idea; it just wasn't one of the major things in my mind since my main goal to start with was/is conceptual clarity of the overall system. For the OS question, I woulld like to use this approach: 1) Make the guide as platform agnostic as possible without confusing OS X users. 2) Mention what alternative OSs are likely to work in the introduction. 3) If alternative OS instructions are desired or needed, put them in a doc sandbox (separate guide section, or MP wiki, etc). If we stick to that philosophy I think it would minimize how much we need to revisit the do these guide mods/additions make sense for OS X and BSD questions as time goes on. And leave the question of what alternative OSs we support to the people writing and contributing to the code over time. Thoughts are welcome. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Draft of a minimalist MacPorts Guide
I think the structure of the original guide is fundamentally flawed. I cooked up a draft of a minimalist approach. What do y'all think? http://homepage.mac.com/duling/macports/guide.html I used the stylesheet from another document I had handy, so don't mind the format or the fact that it isn't chunked. The colors and text of the original guide make it look more professional I think but I didn't have time to mess with the stylesheet, especially since I don't know if people will really like this approach anyway. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: [tsocks] : Unresolved symbol: close
Sylvain [EMAIL PROTECTED] on Wednesday, July 4, 2007 at 9:27 AM -0800 wrote: I'm using tsocks, it works well, but when I use it, whenever it starts, before doing anything, it outputs: : Unresolved symbol: close I don't like it when there are errors, even though it seems to work pretty well. Do you know how to fix this? I would file a ticket in Trac, or at least contact the maintainer on this one. I say this because it has an active maintainer, and this app required some serious patching. Sometimes, if a user is willing, it is more helpful to contact the app's programmer so they can suggest a fix or patch and send the information to the port maintainer. But because of the heavy patching required of this port, I think the best option is to file a ticket and assign it to the port maintainer (and put his email in the cc field). Let us know if you need help with trac or anything. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Tripwire fails to install
Tripwire is way out of date and needs to be updated. But it looks to me like this app may take a lot of modification, so someone will need to take on the challenge to figure out the installation method of the the latest version and update the port. Mark Tobias Weisserth [EMAIL PROTECTED] on Tuesday, July 3, 2007 at 7:03 AM -0800 wrote: I'm running the latest MacPorts on a PPC G4 PowerBook with Max OS X 10.4.10. When running sudo port selfupdate sudo port install tripwire I get errors after tripwire finishes building and tries to run the install.sh shell script: --- Fetching tripwire --- Verifying checksum(s) for tripwire --- Extracting tripwire --- Applying patches to tripwire --- Configuring tripwire --- Building tripwire with target all --- Staging tripwire into destroot Error: Target com.apple.destroot returned: shell command cd /opt/ local/var/db/dports/build/ _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dp orts_security_tripwire/work/tripwire-2.3.1-2 make install DESTDIR=/opt/local/var/db/dports/build/ _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dp orts_security_tripwire/work/destroot returned error 2 Command output: /usr/bin/install -c twadmin /opt/local/var/db/ dports/build/ _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dp orts_security_tripwire/work/destroot/opt/local/sbin/twadmin make[3]: Nothing to be done for `install-data-am'. Making install in siggen /bin/sh ../../mkinstalldirs /opt/local/var/db/dports/build/ _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dp orts_security_tripwire/work/destroot/opt/local/sbin /usr/bin/install -c siggen /opt/local/var/db/dports/build/ _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dp orts_security_tripwire/work/destroot/opt/local/sbin/siggen make[3]: Nothing to be done for `install-data-am'. Making install in tripwire /bin/sh ../../mkinstalldirs /opt/local/var/db/dports/build/ _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dp orts_security_tripwire/work/destroot/opt/local/sbin /usr/bin/install -c tripwire /opt/local/var/db/dports/build/ _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dp orts_security_tripwire/work/destroot/opt/local/sbin/tripwire make[3]: Nothing to be done for `install-data-am'. make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[2]: Nothing to be done for `install-exec-am'. make install-data-hook prefix=/opt/local sysconfdir=/opt/local/etc/tripwire \ path_to_vi=/usr/bin/vi path_to_sendmail=/usr/sbin/ sendmail \ ./install/install.sh Installer program for: Tripwire(R) 2.3 Open Source Copyright (C) 1998-2000 Tripwire (R) Security Systems, Inc. Tripwire (R) is a registered trademark of the Purdue Research Foundation and is licensed exclusively to Tripwire (R) Security Systems, Inc. Say 'sh install.sh', not 'sh install.sh' make[3]: *** [install-data-hook] Error 1 make[2]: *** [install-data-am] Error 2 make[1]: *** [install-am] Error 2 make: *** [install-recursive] Error 1 Error: Status 1 encountered during processing. What's wrong? thanks for any hints, ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: installing ARTS
KURAAKU Deibiddo [EMAIL PROTECTED] on Friday, June 29, 2007 at 9:18 AM -0800 wrote: --- Verifying checksum(s) for arts Error: Checksum (md5) mismatch for arts-1.1.2.tar.bz2 Error: Target com.apple.checksum returned: Unable to verify file checksums Error: Status 1 encountered during processing. Is there any way around it, short of one of the maintainers or devs fixing the checksum for this package? (Note: I am running the current version of MacPorts, have run clean on it, and have done multiple syncs.) There is a ticket on that. The package is out of date and it requires more than the usual update version/checksum sort of thing. so unfortunately it needs someone who knows the app well to fix it I think. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: [MySQL] Install difficulties : Can't connect to local MySQL server through
I confess I haven't been follwing this thread as closely as I could have, but I really don't understand what the problem is. I have several howtos on the net that use mysql5 and the instructions are quite short, simple, and work fine by all accounts. I've never thought much about what the file hierarchy is, and I don't see why anyone would care. http://homepage.mac.com/duling/halfdozen/NeDi-Howto.html#d0e94 However, I do think that having a +server variant is pointless and adds needless hassle, and probably the result of a paranoid standpoint on security. As soon as 1.5 comes out the startupitem is disabled by default (as my instructions assume, and as it was supposed to be from the start), and I really think enough grief and confusion has been encountered over this that it really should be terminated with extreme prejudice. I think those arguing for keeping the server variant should list the reasons and let us debate them point-by-point. And I'm going to frown on because someone will commit a mysql5-server port any time now anyway because that one's a bit old by now. Mark Bill Hernandez [EMAIL PROTECTED] on Monday, June 25, 2007 at 2:55 PM -0800 wrote: The reason for using MacPorts in the first place is to simplify the whole unix thing, with that in mind, why over-complicate the hierarchy. I screwed around with the MacPorts version of MySQL for about a week off and on, and couldn't get it running... NOTE : While I was waiting for a reply to this problem I downloaded the MySQL for OSX from http://www.MySQL.com, followed the simple instructions and got it running in about 20 minutes, and within a brief time after that I had imported all my data. They use a simple hierarchy that works with simple instructions. I even ran the secure install using : $ /usr/local/mysql/bin/mysql_secure_installation and it all worked the first time... For some reason, MacPorts uses an OVER-COMPLICATED HIERARCHY for MySQL, yet it uses a simple and great hierarchy for APACHE2. You can go to the MacPorts Apache2 folder and find everything you could possibly need all in one place. The shame is that these guys that volunteer to do all this work are spending a great deal of time and effort to do all this, and I almost feel like a terrible ingrate for mentioning the fact that the user experience is probably now what they intended... ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Launchd not starting lighttpd - startupitem.requires
Sterling Anderson [EMAIL PROTECTED] on Wednesday, June 20, 2007 at 8:38 PM -0800 wrote: Nothing in the console at all. I am stumped. No error messages at all. The wrapper has the correct syntax. Manually loading and unloading the launchd file works properly. I just don't get why it's not working on boot. Ah, then it must be a timinig issue. I just found an feature that isn't documented in the manpage: startupitem.requires. Theoretically that could be used to delay execution until some other functions are started. See the radmind portfile for an example. However, 10.3 also had that keyword for the systemstarter, but I never had any luck with that. I ended up using a start script with a sleep command in it. See the Snort port. But I didn't know about startupitem.requires on 10.4 so I didn't try that. I will sometime. Try editing the portfile and using startup.requires as the radmind port does and let us know if it works. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: x11 install
eoghan [EMAIL PROTECTED] on Tuesday, June 19, 2007 at 5:02 AM -0800 wrote: Im reading the instructions from the wiki for installing X11.. i have my tiger dvd in and i dont seem to see a package named Additional Software to install X11... i searched the dvd and dont see it... is it called something different? Oops. It is called Optional Installs. It is on install disk 1 on my MacBook Pro disks. Scroll down in the finder window toward the bottom. I'm fixing the wiki now. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Install gimp-user-manual fails
But the gimp-user-manual port should not have this problem, and I didn't.
Have you done a selfupdate so that gimp-user-manual-0.12 is available? Is
docbook-xml-4.1.2 installed? Does the file ${prefix}/etc/xml/catalog
exist?
Mark
Baz [EMAIL PROTECTED] on Monday, June 11, 2007 at 7:50 AM -0800
wrote:
I/O error : Attempt to load network entity
http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl
warning: failed to load external entity
http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl;
compilation error: file
I just had this same problem in another thread... the solution is set
XML_CATALOG_FILES=/opt/local/etc/xml/catalog
in your environment.
Maun Suang has raised an issue about it:
http://trac.macports.org/projects/macports/ticket/12106
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: interspersed and cut off
Hi Pete, There are some problems with the user messages in the php5 port. It occurrs when you specify neither the apache nor the apache2 variant. This is a perfectly legitimate use of php, but did you intend to install it without Apache support? I attached a patch to the php5 port for the maintainer to evaluate that I think straightens out the messages. If you did intend to install Apache support, you must reinstall the port and specify a variant. Either +apache or +apache2. And until the user message fixes get applied to the port, here are instructions you may use: http://homepage.mac.com/duling/halfdozen/NeDi-Howto.html#d0e134 Mark Pete Gontier [EMAIL PROTECTED] on Monday, June 11, 2007 at 8:57 AM -0800 wrote: I've just installed PHP5 on a Panther box. At the end of the progress messages, I see: --- Installing php5 5.2.3_0+darwin_7+macosx If this is your first install, you might want --- Activating php5 5.2.3_0+darwin_7+macosx --- Cleaning php5 This is not a misquote; it really does look interspersed and cut off like that. I can probably grep for If this is your first install, you might want and find the rest of the text, though I have not yet tried that. I suppose it might be relevant that I got this in interactive mode. I'm going to file a bug report, but in the meantime, can anybody offer any better hints as to how to proceed? Pete Gontier [ http://www.pete.gontier.org/ ]http://www.pete.gontier.org/ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Install gimp-user-manual fails
Ok, I just tried to reinstall it and I'm getting the same error now. I
don't understand that I reopened the ticket.
http://trac.macosforge.org/projects/macports/ticket/11429
Mark
David Rowe [EMAIL PROTECTED] on Monday, June 11, 2007 at 9:32 AM
-0800 wrote:
But the gimp-user-manual port should not have this problem, and I
didn't.
Have you done a selfupdate so that gimp-user-manual-0.12 is available?
Is
docbook-xml-4.1.2 installed? Does the file ${prefix}/etc/xml/catalog
exist?
Mark
The answer is yes to all questions
I have just done a selfupdate and gimp-user-manual-0.12 is what I am
trying to install.
docbook-xml-4.1.2 is installed and active
the file /opt/local/etc/xml/catalog does exist. ls -l gives:
-rw-r--r-- 1 root admin 911 Jun 9 16:31 catalog.
I am trying out PortAuthority and as far as I can see all the Build
dependencies are present - except that I had gimp activated rather than
gimp2. I fixed that but it still made no difference
I also tried Baz's suggestion of setting
XML_CATALOG_FILES=/opt/local/etc/xml/catalog
but I still get the same error reports:
sudo port install gimp-user-manual
Password:
--- Building gimp-user-manual with target all
Error: Target com.apple.build returned: shell command cd
/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_graphics_gimp-user-manual/work/gimp-help-2-0.12
make all returned error 2
Command output: -- Building HTML for cs
I/O error : Attempt to load network entity
http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl
warning: failed to load external entity
http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl;
compilation error: file
/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_graphics_gimp-user-manual/work/gimp-help-2-0.12/stylesheets/plainhtml.xsl
line 7 element import
xsl:import : unable to load
http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl
make: *** [stamps/html.cs.stamp] Error 5
---
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Install gimp-user-manual fails
http://trac.macosforge.org/projects/macports/ticket/11429 With the recent updates to the docbook-xsl port, this patch shouldn't even be necessary anymore. I've added a patch to the Trac ticket above that does the job instead. Yves said he was without MacPorts now so I committed the fix, along with an update to 0.12. Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
