From viren.patel at emory.edu Thu Oct 1 05:16:29 2009 From: viren.patel at emory.edu (Viren Patel) Date: Thu, 01 Oct 2009 08:16:29 -0400 Subject: Apache + php + gd not working at all - PARTIAL SUCCESS In-Reply-To: <37D92A60-48AA-4E6A-92A3-33C40474735F@macports.org> References: <4AC39366.1090600@emory.edu> <37D92A60-48AA-4E6A-92A3-33C40474735F@macports.org> Message-ID: <4AC49D9D.5000500@emory.edu> Yes, I did follow all the steps. The only difference I noticed was in the phpinfo() test file. Whereas I originally had , the MAMP instructions specify . The MAMP test file works. I don't know if this a new feature or a bug. I have also installed the php5-gd package but do not see the gd5 module listed in the phpinfo() output. Are there special instructions for getting that capability? Thanks to all for your input. VP Ryan Schmidt wrote: > On Sep 30, 2009, at 12:20, Viren Patel wrote: > >> Apache starts and runs fine and server html pages. However when >> loading >> test.php containing , I get a blank page. No error >> messages in the logs. Page source shows and nothing >> else. > > Did you follow all the steps shown in the how-to? > > https://trac.macports.org/wiki/howto/MAMP#php > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: viren_patel.vcf Type: text/x-vcard Size: 345 bytes Desc: not available URL: From ryandesign at macports.org Thu Oct 1 05:17:13 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 1 Oct 2009 07:17:13 -0500 Subject: Apache + php + gd not working at all - PARTIAL SUCCESS In-Reply-To: <4AC49D9D.5000500@emory.edu> References: <4AC39366.1090600@emory.edu> <37D92A60-48AA-4E6A-92A3-33C40474735F@macports.org> <4AC49D9D.5000500@emory.edu> Message-ID: <0295D4C7-3911-48C5-9D7F-5A1D54C84B6A@macports.org> On Oct 1, 2009, at 07:16, Viren Patel wrote: > Yes, I did follow all the steps. The only difference I noticed was in > the phpinfo() test file. Whereas I originally had , the > MAMP instructions specify . The MAMP test file > works. > I don't know if this a new feature or a bug. If you want "" to work, turn on short open tags in your php.ini. > I have also installed the php5-gd package but do not see the gd5 > module > listed in the phpinfo() output. Are there special instructions for > getting that capability? Does your php.ini contain a line beginning with "extension_dir"? If so, remove it; it prevents the extensions from loading properly. From viren.patel at emory.edu Thu Oct 1 05:44:56 2009 From: viren.patel at emory.edu (Viren Patel) Date: Thu, 01 Oct 2009 08:44:56 -0400 Subject: Apache + php + gd not working at all - PARTIAL SUCCESS In-Reply-To: <0295D4C7-3911-48C5-9D7F-5A1D54C84B6A@macports.org> References: <4AC39366.1090600@emory.edu> <37D92A60-48AA-4E6A-92A3-33C40474735F@macports.org> <4AC49D9D.5000500@emory.edu> <0295D4C7-3911-48C5-9D7F-5A1D54C84B6A@macports.org> Message-ID: <4AC4A448.4020800@emory.edu> The extensions_dir line in php.ini is commented out... ... ; Directory in which the loadable extensions (modules) reside. ; http://php.net/extension-dir ; extension_dir = "./" ; On windows: ; extension_dir = "ext" ... Ryan Schmidt wrote: > On Oct 1, 2009, at 07:16, Viren Patel wrote: > >> Yes, I did follow all the steps. The only difference I noticed was in >> the phpinfo() test file. Whereas I originally had , the >> MAMP instructions specify . The MAMP test file >> works. >> I don't know if this a new feature or a bug. > > If you want "" to work, turn on short open tags in your > php.ini. > > >> I have also installed the php5-gd package but do not see the gd5 >> module >> listed in the phpinfo() output. Are there special instructions for >> getting that capability? > > Does your php.ini contain a line beginning with "extension_dir"? If > so, remove it; it prevents the extensions from loading properly. > > -------------- next part -------------- A non-text attachment was scrubbed... Name: viren_patel.vcf Type: text/x-vcard Size: 345 bytes Desc: not available URL: From ryandesign at macports.org Thu Oct 1 06:05:26 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 1 Oct 2009 08:05:26 -0500 Subject: Apache + php + gd not working at all - PARTIAL SUCCESS In-Reply-To: <4AC4A448.4020800@emory.edu> References: <4AC39366.1090600@emory.edu> <37D92A60-48AA-4E6A-92A3-33C40474735F@macports.org> <4AC49D9D.5000500@emory.edu> <0295D4C7-3911-48C5-9D7F-5A1D54C84B6A@macports.org> <4AC4A448.4020800@emory.edu> Message-ID: On Oct 1, 2009, at 07:44, Viren Patel wrote: > Ryan Schmidt wrote: >> On Oct 1, 2009, at 07:16, Viren Patel wrote: >>> I have also installed the php5-gd package but do not see the gd5 >>> module >>> listed in the phpinfo() output. Are there special instructions for >>> getting that capability? >> >> Does your php.ini contain a line beginning with "extension_dir"? If >> so, remove it; it prevents the extensions from loading properly. > > The extensions_dir line in php.ini is commented out... Ok, then that should be fine. I do see gd information in my phpinfo: $ php -r 'phpinfo();' | grep gd /opt/local/var/db/php5/gd.ini, gd gd.jpeg_ignore_warning => 0 => 0 And the gd functions are present: $ php -r 'echo (int)function_exists("imagecreate")."\n";' 1 Do you see the same? I just updated the php5 port to 5.3.0_3; once this update gets mirrored to the rsync server (about half an hour), please "sudo port selfupdate" and "sudo port upgrade php5" to see if that helps. From viren.patel at emory.edu Thu Oct 1 08:24:28 2009 From: viren.patel at emory.edu (Viren Patel) Date: Thu, 01 Oct 2009 11:24:28 -0400 Subject: Apache + php + gd not working at all - SUCCESS In-Reply-To: References: <4AC39366.1090600@emory.edu> <37D92A60-48AA-4E6A-92A3-33C40474735F@macports.org> <4AC49D9D.5000500@emory.edu> <0295D4C7-3911-48C5-9D7F-5A1D54C84B6A@macports.org> <4AC4A448.4020800@emory.edu> Message-ID: <4AC4C9AC.70702@emory.edu> Yes I do... and now I do see the gd module listed as well in the phpinfo() output. I didn't change anything so I must have just not seen it initially... something about hiding in plain sight ;-) Thanks! VP Ryan Schmidt wrote: > On Oct 1, 2009, at 07:44, Viren Patel wrote: >> Ryan Schmidt wrote: >>> On Oct 1, 2009, at 07:16, Viren Patel wrote: >>>> I have also installed the php5-gd package but do not see the gd5 >>>> module >>>> listed in the phpinfo() output. Are there special instructions for >>>> getting that capability? >>> Does your php.ini contain a line beginning with "extension_dir"? If >>> so, remove it; it prevents the extensions from loading properly. >> The extensions_dir line in php.ini is commented out... > > Ok, then that should be fine. > > > I do see gd information in my phpinfo: > > $ php -r 'phpinfo();' | grep gd > /opt/local/var/db/php5/gd.ini, > gd > gd.jpeg_ignore_warning => 0 => 0 > > And the gd functions are present: > > $ php -r 'echo (int)function_exists("imagecreate")."\n";' > 1 > > Do you see the same? > > > I just updated the php5 port to 5.3.0_3; once this update gets > mirrored to the rsync server (about half an hour), please "sudo port > selfupdate" and "sudo port upgrade php5" to see if that helps. > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: viren_patel.vcf Type: text/x-vcard Size: 345 bytes Desc: not available URL: From dcarpeneto at yahoo.com Thu Oct 1 10:47:22 2009 From: dcarpeneto at yahoo.com (David Carpeneto) Date: Thu, 1 Oct 2009 10:47:22 -0700 (PDT) Subject: Inkscape-bin crash: was "Re: Inkscape crazy slow" In-Reply-To: <400CB38E-708D-4720-B512-EB40E197ED89@macports.org> References: <451774.2566.qm@web88303.mail.re4.yahoo.com> <7F7E039C-770C-482B-B5B6-4A26169EFB67@wright.edu> <400CB38E-708D-4720-B512-EB40E197ED89@macports.org> Message-ID: <615442.78694.qm@web88308.mail.re4.yahoo.com> > Your original performance issue is a known issue in pango. The URL to bug reports has been posted to this list in the last few emails. Thanks - sorry I did not see this earlier -------------- next part -------------- An HTML attachment was scrubbed... URL: From talklists at newgeo.com Thu Oct 1 11:29:52 2009 From: talklists at newgeo.com (Scott Haneda) Date: Thu, 1 Oct 2009 11:29:52 -0700 Subject: Apache + php + gd not working at all - PARTIAL SUCCESS In-Reply-To: <4AC49D9D.5000500@emory.edu> References: <4AC39366.1090600@emory.edu> <37D92A60-48AA-4E6A-92A3-33C40474735F@macports.org> <4AC49D9D.5000500@emory.edu> Message-ID: <94DFD1A4-A2A9-4775-BEA8-081F619740A0@newgeo.com> Your using short tags. Depending on your php.ini settings those may not be on by default any longer. They should be off by default. If you need them, turn then on per vhost or per .htaccess with php admin value. I have not seen a short tag ( versus ) in years. "For portable, redistributable code, be sure not to use short tags.? Php5 has a few other areas to keep an eye on. The location in the date section of your php.ini should be set, no longer trusting the system for time zones. It will mark a verbose note in phpinfo on where to look. In order to get GD to work you probably have to enable it. That was probably mentioned in a message when you installed it. If you installed with -d (debug) you may have missed it. You can always issue "port edit php5-whatever" to look at the port instruction file. Look for the ui messages which are what print notes to stdout when you install. A patch to php5 was just released. I feel an important one as it leads to config data exposure and segfaulting if not handled. I'm not sure if this patch is in the wild yet, but do look to apply this patch via a php5 rebuild as soon as possible. -- Scott Iphone says hello. On Oct 1, 2009, at 5:16 AM, Viren Patel wrote: > Yes, I did follow all the steps. The only difference I noticed was in > the phpinfo() test file. Whereas I originally had , the > MAMP instructions specify . The MAMP test file > works. > I don't know if this a new feature or a bug. > > I have also installed the php5-gd package but do not see the gd5 > module > listed in the phpinfo() output. Are there special instructions for > getting that capability? > > Thanks to all for your input. > > VP > > Ryan Schmidt wrote: >> On Sep 30, 2009, at 12:20, Viren Patel wrote: >> >>> Apache starts and runs fine and server html pages. However when >>> loading >>> test.php containing , I get a blank page. No error >>> messages in the logs. Page source shows and nothing >>> else. >> >> Did you follow all the steps shown in the how-to? >> >> https://trac.macports.org/wiki/howto/MAMP#php >> >> >> > > begin:vcard fn:Viren Patel n:Patel;Viren org:Emory University School > of Medicine;Department of Human Genetics adr:;;615 Michael Street, > Ste. 301;Atlanta;GA;30322;USA email;internet:viren.patel at emory.edu > title:Application Developer/Analyst Sr. tel;work:(404) 727-9447 x- > mozilla-html:FALSE url:http://www.genetics.emory.edu version:2.1 > end:vcard > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From talklists at newgeo.com Thu Oct 1 11:30:46 2009 From: talklists at newgeo.com (Scott Haneda) Date: Thu, 1 Oct 2009 11:30:46 -0700 Subject: Apache + php + gd not working at all - PARTIAL SUCCESS In-Reply-To: <0295D4C7-3911-48C5-9D7F-5A1D54C84B6A@macports.org> References: <4AC39366.1090600@emory.edu> <37D92A60-48AA-4E6A-92A3-33C40474735F@macports.org> <4AC49D9D.5000500@emory.edu> <0295D4C7-3911-48C5-9D7F-5A1D54C84B6A@macports.org> Message-ID: <1CED0DA1-5ED1-41EA-BEA8-DDBFD56A3BC6@newgeo.com> Ugh. Sorry for the post reply. Looks like you covered it. -- Scott Iphone says hello. On Oct 1, 2009, at 5:17 AM, Ryan Schmidt wrote: > > On Oct 1, 2009, at 07:16, Viren Patel wrote: > >> Yes, I did follow all the steps. The only difference I noticed was in >> the phpinfo() test file. Whereas I originally had , >> the >> MAMP instructions specify . The MAMP test file >> works. >> I don't know if this a new feature or a bug. > > If you want "" to work, turn on short open tags in > your php.ini. > > >> I have also installed the php5-gd package but do not see the gd5 >> module >> listed in the phpinfo() output. Are there special instructions for >> getting that capability? > > Does your php.ini contain a line beginning with "extension_dir"? If > so, remove it; it prevents the extensions from loading properly. > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From talklists at newgeo.com Thu Oct 1 11:36:35 2009 From: talklists at newgeo.com (Scott Haneda) Date: Thu, 1 Oct 2009 11:36:35 -0700 Subject: Php 64 ... Was Re: Apache + php + gd not working at all - PARTIAL SUCCESS In-Reply-To: References: <4AC39366.1090600@emory.edu> <37D92A60-48AA-4E6A-92A3-33C40474735F@macports.org> <4AC49D9D.5000500@emory.edu> <0295D4C7-3911-48C5-9D7F-5A1D54C84B6A@macports.org> <4AC4A448.4020800@emory.edu> Message-ID: <9ACF4D54-7AEB-48DB-8C35-D3E8067A18D3@newgeo.com> What do you think about using this patch as opportunity to rebuild php5 in 64 bit mode on PPC dual G5? I'm inclined not to for fear more things may be broken. Though I really could use 64 bit ints in JSON. Do I have to change macports.conf to do so as per the previous suggestions to the list, or can I just ...upgrade +universal and get this one at 64 bit? Thanks for the rapid patch. I assume it built clean and runs for you? Were you able to get the random error messages and garbage string data as test, then have that go away post patch? -- Scott Iphone says hello. On Oct 1, 2009, at 6:05 AM, Ryan Schmidt wrote: > I just updated the php5 port to 5.3.0_3; once this update gets > mirrored to the rsync server (about half an hour), please "sudo port > selfupdate" and "sudo port upgrade php5" to see if that helps. From tjb at unh.edu Thu Oct 1 11:49:32 2009 From: tjb at unh.edu (Thomas Baker) Date: Thu, 1 Oct 2009 14:49:32 -0400 Subject: gpsbabel usb problems on snow leopard? Message-ID: I've got snow leopard installed on my MBP/intel and a macports 1.8.1 fresh install. I installed gpsbabel but I get USB errors with it that I didn't have with my old macports tree: gpsbabel -t -i garmin -f usb: -o gpx -F all.gpx Bad cmdsend r -1 sz 12 usb_bulk_write failed. 'usb_bulk_write: An error occured during write (see messages above)' My old macports tree was based on leopard though I did have similar errors if I tried to run a version of gpsbabel newer than 1.3.5. (I tried it every once in a while when a dependency was updated but then would just reactivate the old version.) My old tree still works but since it had a bunch of stuff I no longer use, I wanted to start over with a clean tree. Anyone else having any luck with gpsbabel and snow leopard? Thanks, tjb -- ======================================================================= | Thomas Baker email: tjb at unh.edu | | Systems Programmer | | Research Computing Center voice: (603) 862-4490 | | University of New Hampshire fax: (603) 862-1761 | | 332 Morse Hall | | Durham, NH 03824 USA http://wintermute.sr.unh.edu/~tjb | ======================================================================= From macports at tprfct.net Thu Oct 1 12:06:25 2009 From: macports at tprfct.net (Kastus Shchuka) Date: Thu, 1 Oct 2009 12:06:25 -0700 Subject: tmux upgrad problem Message-ID: <97408717-D9C4-4D0C-B4CC-48DA86DEE185@tprfct.net> A new version of tmux showed up after port sync: tmux 1.0_0 < 1.0_3 When trying to upgrade tmux I encouter this error: sudo port -d upgrade tmux Password: DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/sysutils/tmux DEBUG: epoch: in tree: 0 installed: 0 DEBUG: tmux 1.0_3 exists in the ports tree DEBUG: tmux 1.0_0 is the latest installed DEBUG: tmux 1.0_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/sysutils/tmux DEBUG: OS Platform: darwin DEBUG: OS Version: 9.8.0 DEBUG: Mac OS X Version: 10.5 DEBUG: System Arch: powerpc DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre- existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/ sources/rsync.macports.org/release/ports/_resources/port1.0/ variant_descriptions.conf DEBUG: Requested variant powerpc is not provided by port tmux. DEBUG: Requested variant darwin is not provided by port tmux. DEBUG: Requested variant macosx is not provided by port tmux. DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncurses DEBUG: epoch: in tree: 0 installed: 0 DEBUG: ncurses 5.7_0 exists in the ports tree DEBUG: ncurses 5.7_0 is the latest installed DEBUG: ncurses 5.7_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/devel/ncurses DEBUG: OS Platform: darwin DEBUG: OS Version: 9.8.0 DEBUG: Mac OS X Version: 10.5 DEBUG: System Arch: powerpc DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre- existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/ rsync.macports.org/release/ports/_resources/port1.0/group/ muniversal-1.0.tcl DEBUG: Reading variant descriptions from /opt/local/var/macports/ sources/rsync.macports.org/release/ports/_resources/port1.0/ variant_descriptions.conf DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant powerpc is not provided by port ncurses. DEBUG: Requested variant darwin is not provided by port ncurses. DEBUG: Requested variant macosx is not provided by port ncurses. DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncursesw DEBUG: epoch: in tree: 0 installed: 0 DEBUG: ncursesw 5.7_0 exists in the ports tree DEBUG: ncursesw 5.7_0 is the latest installed DEBUG: ncursesw 5.7_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/devel/ncursesw DEBUG: OS Platform: darwin DEBUG: OS Version: 9.8.0 DEBUG: Mac OS X Version: 10.5 DEBUG: System Arch: powerpc DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre- existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/ rsync.macports.org/release/ports/_resources/port1.0/group/ muniversal-1.0.tcl DEBUG: Reading variant descriptions from /opt/local/var/macports/ sources/rsync.macports.org/release/ports/_resources/port1.0/ variant_descriptions.conf DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant powerpc is not provided by port ncursesw. DEBUG: Requested variant darwin is not provided by port ncursesw. DEBUG: Requested variant macosx is not provided by port ncursesw. DEBUG: No need to upgrade! ncursesw 5.7_0 >= ncursesw 5.7_0 DEBUG: No need to upgrade! ncurses 5.7_0 >= ncurses 5.7_0 ---> Computing dependencies for tmux DEBUG: Searching for dependency: ncurses DEBUG: Found Dependency: receipt exists for ncurses DEBUG: Executing org.macports.main (tmux) DEBUG: Skipping completed org.macports.fetch (tmux) DEBUG: Skipping completed org.macports.checksum (tmux) DEBUG: Skipping completed org.macports.extract (tmux) DEBUG: Skipping completed org.macports.patch (tmux) DEBUG: Skipping completed org.macports.configure (tmux) ---> Building tmux DEBUG: Executing org.macports.build (tmux) DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_sysutils_tmux/work/tmux-1.0" && /usr/bin/ make -j1 all' cc -L/opt/local/lib -o tmux attributes.o buffer-poll.o buffer.o cfg.o client-fn.o client.o clock.o cmd-attach-session.o cmd-bind-key.o cmd- break-pane.o cmd-choose-client.o cmd-choose-session.o cmd-choose- window.o cmd-clear-history.o cmd-clock-mode.o cmd-command-prompt.o cmd- confirm-before.o cmd-copy-buffer.o cmd-copy-mode.o cmd-delete-buffer.o cmd-detach-client.o cmd-display-message.o cmd-display-panes.o cmd-down- pane.o cmd-find-window.o cmd-generic.o cmd-has-session.o cmd-if- shell.o cmd-kill-pane.o cmd-kill-server.o cmd-kill-session.o cmd-kill- window.o cmd-last-window.o cmd-link-window.o cmd-list-buffers.o cmd- list-clients.o cmd-list-commands.o cmd-list-keys.o cmd-list-sessions.o cmd-list-windows.o cmd-list.o cmd-load-buffer.o cmd-lock-server.o cmd- move-window.o cmd-new-session.o cmd-new-window.o cmd-next-layout.o cmd- next-window.o cmd-paste-buffer.o cmd-previous-layout.o cmd-previous- window.o cmd-refresh-client.o cmd-rename-session.o cmd-rename-window.o cmd-resize-pane.o cmd-respawn-window.o cmd-rotate-window.o cmd-save- buffer.o cmd-scroll-mode.o cmd-select-layout.o cmd-select-pane.o cmd- select-prompt.o cmd-select-window.o cmd-send-keys.o cmd-send-prefix.o cmd-server-info.o cmd-set-buffer.o cmd-set-environment.o cmd-set- option.o cmd-set-password.o cmd-set-window-option.o cmd-show-buffer.o cmd-show-environment.o cmd-show-options.o cmd-show-window-options.o cmd-source-file.o cmd-split-window.o cmd-start-server.o cmd-string.o cmd-suspend-client.o cmd-swap-pane.o cmd-swap-window.o cmd-switch- client.o cmd-unbind-key.o cmd-unlink-window.o cmd-up-pane.o cmd.o colour.o environ.o grid-view.o grid.o input-keys.o input.o key- bindings.o key-string.o layout-set.o layout.o log.o mode-key.o names.o options-cmd.o options.o paste.o resize.o screen-redraw.o screen- write.o screen.o server-fn.o server-msg.o server.o session.o status.o tmux.o tty-keys.o tty-term.o tty.o utf8.o window-choose.o window- clock.o window-copy.o window-more.o window-scroll.o window.o xmalloc.o osdep-darwin.o compat/bsd-poll.o compat/strtonum.o compat/vis.o compat/ unvis.o compat/imsg-buffer.o compat/imsg.o -lcurses Undefined symbols: "__vprocmgr_detach_from_console", referenced from: _server_start in server.o ld: symbol(s) not found collect2: ld returned 1 exit status make: *** [tmux] Error 1 Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_sysutils_tmux/work/tmux-1.0" && /usr/bin/ make -j1 all " returned error 2 Command output: cc -L/opt/local/lib -o tmux attributes.o buffer-poll.o buffer.o cfg.o client-fn.o client.o clock.o cmd-attach-session.o cmd- bind-key.o cmd-break-pane.o cmd-choose-client.o cmd-choose-session.o cmd-choose-window.o cmd-clear-history.o cmd-clock-mode.o cmd-command- prompt.o cmd-confirm-before.o cmd-copy-buffer.o cmd-copy-mode.o cmd- delete-buffer.o cmd-detach-client.o cmd-display-message.o cmd-display- panes.o cmd-down-pane.o cmd-find-window.o cmd-generic.o cmd-has- session.o cmd-if-shell.o cmd-kill-pane.o cmd-kill-server.o cmd-kill- session.o cmd-kill-window.o cmd-last-window.o cmd-link-window.o cmd- list-buffers.o cmd-list-clients.o cmd-list-commands.o cmd-list-keys.o cmd-list-sessions.o cmd-list-windows.o cmd-list.o cmd-load-buffer.o cmd-lock-server.o cmd-move-window.o cmd-new-session.o cmd-new-window.o cmd-next-layout.o cmd-next-window.o cmd-paste-buffer.o cmd-previous- layout.o cmd-previous-window.o cmd-refresh-client.o cmd-rename- session.o cmd-rename-window.o cmd-resize-pane.o cmd-respawn-window.o cmd-rotate-window.o cmd-save-buffer.o cmd-scroll-mode.o cmd-select- layout.o cmd-select-pane.o cmd-select-prompt.o cmd-select-window.o cmd- send-keys.o cmd-send-prefix.o cmd-server-info.o cmd-set-buffer.o cmd- set-environment.o cmd-set-option.o cmd-set-password.o cmd-set-window- option.o cmd-show-buffer.o cmd-show-environment.o cmd-show-options.o cmd-show-window-options.o cmd-source-file.o cmd-split-window.o cmd- start-server.o cmd-string.o cmd-suspend-client.o cmd-swap-pane.o cmd- swap-window.o cmd-switch-client.o cmd-unbind-key.o cmd-unlink-window.o cmd-up-pane.o cmd.o colour.o environ.o grid-view.o grid.o input-keys.o input.o key-bindings.o key-string.o layout-set.o layout.o log.o mode- key.o names.o options-cmd.o options.o paste.o resize.o screen-redraw.o screen-write.o screen.o server-fn.o server-msg.o server.o session.o status.o tmux.o tty-keys.o tty-term.o tty.o utf8.o window-choose.o window-clock.o window-copy.o window-more.o window-scroll.o window.o xmalloc.o osdep-darwin.o compat/bsd-poll.o compat/strtonum.o compat/ vis.o compat/unvis.o compat/imsg-buffer.o compat/imsg.o -lcurses Undefined symbols: "__vprocmgr_detach_from_console", referenced from: _server_start in server.o ld: symbol(s) not found collect2: ld returned 1 exit status make: *** [tmux] Error 1 DEBUG: Backtrace: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_sysutils_tmux/work/tmux-1.0" && /usr/bin/ make -j1 all " returned error 2 Command output: cc -L/opt/local/lib -o tmux attributes.o buffer-poll.o buffer.o cfg.o client-fn.o client.o clock.o cmd-attach-session.o cmd- bind-key.o cmd-break-pane.o cmd-choose-client.o cmd-choose-session.o cmd-choose-window.o cmd-clear-history.o cmd-clock-mode.o cmd-command- prompt.o cmd-confirm-before.o cmd-copy-buffer.o cmd-copy-mode.o cmd- delete-buffer.o cmd-detach-client.o cmd-display-message.o cmd-display- panes.o cmd-down-pane.o cmd-find-window.o cmd-generic.o cmd-has- session.o cmd-if-shell.o cmd-kill-pane.o cmd-kill-server.o cmd-kill- session.o cmd-kill-window.o cmd-last-window.o cmd-link-window.o cmd- list-buffers.o cmd-list-clients.o cmd-list-commands.o cmd-list-keys.o cmd-list-sessions.o cmd-list-windows.o cmd-list.o cmd-load-buffer.o cmd-lock-server.o cmd-move-window.o cmd-new-session.o cmd-new-window.o cmd-next-layout.o cmd-next-window.o cmd-paste-buffer.o cmd-previous- layout.o cmd-previous-window.o cmd-refresh-client.o cmd-rename- session.o cmd-rename-window.o cmd-resize-pane.o cmd-respawn-window.o cmd-rotate-window.o cmd-save-buffer.o cmd-scroll-mode.o cmd-select- layout.o cmd-select-pane.o cmd-select-prompt.o cmd-select-window.o cmd- send-keys.o cmd-send-prefix.o cmd-server-info.o cmd-set-buffer.o cmd- set-environment.o cmd-set-option.o cmd-set-password.o cmd-set-window- option.o cmd-show-buffer.o cmd-show-environment.o cmd-show-options.o cmd-show-window-options.o cmd-source-file.o cmd-split-window.o cmd- start-server.o cmd-string.o cmd-suspend-client.o cmd-swap-pane.o cmd- swap-window.o cmd-switch-client.o cmd-unbind-key.o cmd-unlink-window.o cmd-up-pane.o cmd.o colour.o environ.o grid-view.o grid.o input-keys.o input.o key-bindings.o key-string.o layout-set.o layout.o log.o mode- key.o names.o options-cmd.o options.o paste.o resize.o screen-redraw.o screen-write.o screen.o server-fn.o server-msg.o server.o session.o status.o tmux.o tty-keys.o tty-term.o tty.o utf8.o window-choose.o window-clock.o window-copy.o window-more.o window-scroll.o window.o xmalloc.o osdep-darwin.o compat/bsd-poll.o compat/strtonum.o compat/ vis.o compat/unvis.o compat/imsg-buffer.o compat/imsg.o -lcurses Undefined symbols: "__vprocmgr_detach_from_console", referenced from: _server_start in server.o ld: symbol(s) not found collect2: ld returned 1 exit status make: *** [tmux] Error 1 while executing "command_exec build" (procedure "portbuild::build_main" line 9) invoked from within "$procedure $targetname" Warning: the following items did not execute (for tmux): org.macports.destroot org.macports.build DEBUG: Error: Unable to upgrade port: 1 Shall I file a ticket in trac about it? Thanks, -Kastus From ryandesign at macports.org Thu Oct 1 13:16:35 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 1 Oct 2009 15:16:35 -0500 Subject: Php 64 ... Was Re: Apache + php + gd not working at all - PARTIAL SUCCESS In-Reply-To: <9ACF4D54-7AEB-48DB-8C35-D3E8067A18D3@newgeo.com> References: <4AC39366.1090600@emory.edu> <37D92A60-48AA-4E6A-92A3-33C40474735F@macports.org> <4AC49D9D.5000500@emory.edu> <0295D4C7-3911-48C5-9D7F-5A1D54C84B6A@macports.org> <4AC4A448.4020800@emory.edu> <9ACF4D54-7AEB-48DB-8C35-D3E8067A18D3@newgeo.com> Message-ID: <3019FC55-F3E5-4BF4-A70A-9111CE071954@macports.org> On Oct 1, 2009, at 13:36, Scott Haneda wrote: > What do you think about using this patch as opportunity to rebuild > php5 in 64 bit mode on PPC dual G5? > > I'm inclined not to for fear more things may be broken. Though I > really could use 64 bit ints in JSON. > > Do I have to change macports.conf to do so as per the previous > suggestions to the list, or can I just ...upgrade +universal and get > this one at 64 bit? I build php5 x86_64/i386 universal on Snow Leopard and it seems to work. Hopefully that means it should work ppc64/ppc for you too. I don't have a 64-bit PowerPC machine to test on. > Thanks for the rapid patch. I assume it built clean and runs for > you? Were you able to get the random error messages and garbage > string data as test, then have that go away post patch? I must admit I did not really test for it. I felt safe in applying the patch because upstream (and suhosin) had already done so. From ryandesign at macports.org Thu Oct 1 13:20:52 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 1 Oct 2009 15:20:52 -0500 Subject: Apache + php + gd not working at all - PARTIAL SUCCESS In-Reply-To: <94DFD1A4-A2A9-4775-BEA8-081F619740A0@newgeo.com> References: <4AC39366.1090600@emory.edu> <37D92A60-48AA-4E6A-92A3-33C40474735F@macports.org> <4AC49D9D.5000500@emory.edu> <94DFD1A4-A2A9-4775-BEA8-081F619740A0@newgeo.com> Message-ID: On Oct 1, 2009, at 13:29, Scott Haneda wrote: > Your using short tags. Depending on your php.ini settings those may > not be on by default any longer. > > They should be off by default. > > If you need them, turn then on per vhost or per .htaccess with php > admin value. I have not seen a short tag ( versus php ... ?> ) in years. > > "For portable, redistributable code, be sure not to use short tags.? The quoted sentence is indeed the PHP team's recommendation: http://us2.php.net/manual/en/language.basic-syntax.phpmode.php But that doesn't mean everybody follows it. Even Zend Framework (made by the creators of PHP) used and recommended short open tags until a few months ago. Well, I thought that was the case. The documentation says they still use them, but it may be out of date: http://framework.zend.com/manual/en/zend.view.html#zend.view.introduction.shortTags > In order to get GD to work you probably have to enable it. That was > probably mentioned in a message when you installed it. If you > installed with -d (debug) you may have missed it. You can always > issue "port edit php5-whatever" to look at the port instruction > file. Look for the ui messages which are what print notes to stdout > when you install. The only instruction the module ports print is to remove the "extension_dir" line from the php.ini if it is present. Other than that, you don't need to do anything to enable the modules. From ryandesign at macports.org Thu Oct 1 13:28:15 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 1 Oct 2009 15:28:15 -0500 Subject: tmux upgrad problem In-Reply-To: <97408717-D9C4-4D0C-B4CC-48DA86DEE185@tprfct.net> References: <97408717-D9C4-4D0C-B4CC-48DA86DEE185@tprfct.net> Message-ID: <331D2C8F-3AC8-4ABF-9ED8-7A24135267AC@macports.org> On Oct 1, 2009, at 14:06, Kastus Shchuka wrote: > A new version of tmux showed up after port sync: > > tmux 1.0_0 < 1.0_3 > > When trying to upgrade tmux I encouter this error: > Undefined symbols: > "__vprocmgr_detach_from_console", referenced from: > _server_start in server.o > Shall I file a ticket in trac about it? Yes, please. I don't see this problem, but I tried on Snow Leopard, not on Leopard and not on PowerPC, so there may well be unaccounted differences. From talklists at newgeo.com Thu Oct 1 13:42:20 2009 From: talklists at newgeo.com (Scott Haneda) Date: Thu, 1 Oct 2009 13:42:20 -0700 Subject: Php 64 ... Was Re: Apache + php + gd not working at all - PARTIAL SUCCESS In-Reply-To: <3019FC55-F3E5-4BF4-A70A-9111CE071954@macports.org> References: <4AC39366.1090600@emory.edu> <37D92A60-48AA-4E6A-92A3-33C40474735F@macports.org> <4AC49D9D.5000500@emory.edu> <0295D4C7-3911-48C5-9D7F-5A1D54C84B6A@macports.org> <4AC4A448.4020800@emory.edu> <9ACF4D54-7AEB-48DB-8C35-D3E8067A18D3@newgeo.com> <3019FC55-F3E5-4BF4-A70A-9111CE071954@macports.org> Message-ID: <06713E78-B021-4C3F-955D-032DF068ADC2@newgeo.com> On Oct 1, 2009, at 1:16 PM, Ryan Schmidt wrote: > On Oct 1, 2009, at 13:36, Scott Haneda wrote: > >> What do you think about using this patch as opportunity to rebuild >> php5 in 64 bit mode on PPC dual G5? >> >> I'm inclined not to for fear more things may be broken. Though I >> really could use 64 bit ints in JSON. >> >> Do I have to change macports.conf to do so as per the previous >> suggestions to the list, or can I just ...upgrade +universal and >> get this one at 64 bit? > > I build php5 x86_64/i386 universal on Snow Leopard and it seems to > work. Hopefully that means it should work ppc64/ppc for you too. I > don't have a 64-bit PowerPC machine to test on. I am on a live server, I know this is dangerous, but the bug did not surface in dev testing. If I want to go for it and update, can you tell me the commands to do so as 64 bit? I assume to update now I just: sudo port selfupdate port info php5 php5 @5.3.0, Revision 3 That tells me that is the right one correct? So next would be the safe road: sudo port upgrade php5 Or, the 64 bit maybe road: sudo port upgrade php5 +universal Do I have my facts correct? -- Scott * If you contact me off list replace talklists@ with scott@ * From ryandesign at macports.org Thu Oct 1 13:50:30 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 1 Oct 2009 15:50:30 -0500 Subject: Php 64 ... Was Re: Apache + php + gd not working at all - PARTIAL SUCCESS In-Reply-To: <06713E78-B021-4C3F-955D-032DF068ADC2@newgeo.com> References: <4AC39366.1090600@emory.edu> <37D92A60-48AA-4E6A-92A3-33C40474735F@macports.org> <4AC49D9D.5000500@emory.edu> <0295D4C7-3911-48C5-9D7F-5A1D54C84B6A@macports.org> <4AC4A448.4020800@emory.edu> <9ACF4D54-7AEB-48DB-8C35-D3E8067A18D3@newgeo.com> <3019FC55-F3E5-4BF4-A70A-9111CE071954@macports.org> <06713E78-B021-4C3F-955D-032DF068ADC2@newgeo.com> Message-ID: On Oct 1, 2009, at 15:42, Scott Haneda wrote: > On Oct 1, 2009, at 1:16 PM, Ryan Schmidt wrote: > >> On Oct 1, 2009, at 13:36, Scott Haneda wrote: >> >>> What do you think about using this patch as opportunity to rebuild >>> php5 in 64 bit mode on PPC dual G5? >>> >>> I'm inclined not to for fear more things may be broken. Though I >>> really could use 64 bit ints in JSON. >>> >>> Do I have to change macports.conf to do so as per the previous >>> suggestions to the list, or can I just ...upgrade +universal and >>> get this one at 64 bit? >> >> I build php5 x86_64/i386 universal on Snow Leopard and it seems to >> work. Hopefully that means it should work ppc64/ppc for you too. I >> don't have a 64-bit PowerPC machine to test on. > > I am on a live server, I know this is dangerous, but the bug did not > surface in dev testing. > > If I want to go for it and update, can you tell me the commands to > do so as 64 bit? I assume to update now I just: > sudo port selfupdate > port info php5 > php5 @5.3.0, Revision 3 > That tells me that is the right one correct? Yes. > So next would be the safe road: > sudo port upgrade php5 Right, that would build using your build_arch from macports.conf, like it has before. > Or, the 64 bit maybe road: > sudo port upgrade php5 +universal > > Do I have my facts correct? That would attempt to build the universal version. By default, universal_archs is ppc i386 so that's not what you want. To get 32-bit/ 64-bit universal builds, you would set universal_archs to ppc ppc64 in macports.conf first. Then, note that you will need all of php5's dependencies universal before you can build php5 itself universal. To do that, you could: sudo port upgrade --enforce-variants php5 +universal This will rebuild a whole lot of stuff. I don't know if I would feel comfortable doing that on a live server having not tested 64-bit PowerPC builds on a staging server before. If it doesn't work, that might leave a whole lot of ports you'd have to reactivate the old versions of. From talklists at newgeo.com Thu Oct 1 14:11:43 2009 From: talklists at newgeo.com (Scott Haneda) Date: Thu, 1 Oct 2009 14:11:43 -0700 Subject: Php 64 ... Was Re: Apache + php + gd not working at all - PARTIAL SUCCESS In-Reply-To: References: <4AC39366.1090600@emory.edu> <37D92A60-48AA-4E6A-92A3-33C40474735F@macports.org> <4AC49D9D.5000500@emory.edu> <0295D4C7-3911-48C5-9D7F-5A1D54C84B6A@macports.org> <4AC4A448.4020800@emory.edu> <9ACF4D54-7AEB-48DB-8C35-D3E8067A18D3@newgeo.com> <3019FC55-F3E5-4BF4-A70A-9111CE071954@macports.org> <06713E78-B021-4C3F-955D-032DF068ADC2@newgeo.com> Message-ID: <06512A16-6A74-4B5B-A61F-751CC2D83622@newgeo.com> Cool, thanks! I have other issues in the update process in a new thread I would like to work with you guys to make sure it is not my end. I will stick to 32 for now. Thank you again. -- Scott * If you contact me off list replace talklists@ with scott@ * On Oct 1, 2009, at 1:50 PM, Ryan Schmidt wrote: > That would attempt to build the universal version. By default, > universal_archs is ppc i386 so that's not what you want. To get 32- > bit/64-bit universal builds, you would set universal_archs to ppc > ppc64 in macports.conf first. Then, note that you will need all of > php5's dependencies universal before you can build php5 itself > universal. To do that, you could: > > sudo port upgrade --enforce-variants php5 +universal > > This will rebuild a whole lot of stuff. > > I don't know if I would feel comfortable doing that on a live server > having not tested 64-bit PowerPC builds on a staging server before. > If it doesn't work, that might leave a whole lot of ports you'd have > to reactivate the old versions of. From talklists at newgeo.com Thu Oct 1 14:41:05 2009 From: talklists at newgeo.com (Scott Haneda) Date: Thu, 1 Oct 2009 14:41:05 -0700 Subject: .bashrc .profile .bash_profile Message-ID: I need to understand this once and for all, there is varying info on this, the bash man page is verbose and not entirely clear. When bash is invoked as an interactive login shell, or as a non-inter- active shell with the --login option, it first reads and executes com- mands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable. The --noprofile option may be used when the shell is started to inhibit this behavior. This implies, that only one of those files is read. That it stops once it finds one. I have: .bash_profile, .bashrc, and .profile The .profile, macports suggested I make, or maybe made it. export PATH=/opt/local/bin:/opt/local/sbin:$PATH export MANPATH=/opt/local/share/man:$MANPATH What is the suggested way to deal with these files? I have .bashrc with some aliases, history control, ls colors, and apparently some PATH exports for macports. When an interactive shell that is not a login shell is started, bash reads and executes commands from ~/.bashrc, if that file exists. This may be inhibited by using the --norc option. The --rcfile file option will force bash to read and execute commands from file instead of ~/.bashrc. I am pretty sure I need to stop using .bashrc, since that is for interactive non login shells, which I am interpreting as shells that do work that is not the result of me using the shell. So, if I were to alias rm to mv for example, and some app called rm, in reality, it would mv the file. I want to prevent stepping on the assumptions of other apps, correct? I think I even went to extra effort to make this happen as my .bash_profile: if [ -f ~/.bashrc ]; then source ~/.bashrc fi Sounds to me, like the correct course of action is to put my custom shell aliases and settings in ~/.bash_profile, that will get read on start, but then no further reading is done. I then need to source .profile which is the file that MacPorts reads. This brings up a question, if the .bash* files do not cascade, and stop after finding your local one, how is it that MacPorts suggests to use .profile, as that will never get read? Any suggestions on how to be clean about this, I would love to know, this has bothered me for ages. On a side note, I am doing this: export LSCOLORS=dxfxcxdxbxegedabagacad Which has never worked for me on a non darwin OS. Is that the wrong way to do it, are there more appropriate ways to do coloring? I think having this in .bashrc actually hurt me ones, as MacPorts saw either: export CLICOLOR=1 or export CLICOLOR_FORCE=1 and did not like it for some reason, that was here http://archive.netbsd.se/?ml=macports-dev&a=2009-05&t=10790101 but I do not seem to recall whether I solved it or just removed the setting temporarily. I know this is a smidge off topic, but MacPorts does suggest to use a .profile, and I hope you guys can help me figure out the correct usage. Bash man pages imply the first user file is read, then no more reading is done. Thank you -- Scott * If you contact me off list replace talklists@ with scott@ * From allbery at kf8nh.com Thu Oct 1 17:21:07 2009 From: allbery at kf8nh.com (Brandon Allbery) Date: Thu, 1 Oct 2009 20:21:07 -0400 Subject: .bashrc .profile .bash_profile In-Reply-To: References: Message-ID: <6FE8CA9B-FCF8-41ED-8D33-D8CC3A2B54DD@kf8nh.com> On Oct 1, 2009, at 17:41 , Scott Haneda wrote: > I need to understand this once and for all, there is varying info on > this, the bash man page is verbose and not entirely clear. > > When bash is invoked as an interactive login shell, or as a > non-inter- > active shell with the --login option, it first reads and > executes com- > mands from the file /etc/profile, if that file exists. > After reading > that file, it looks for ~/.bash_profile, ~/.bash_login, and > ~/.profile, > in that order, and reads and executes commands from the first > one that > exists and is readable. The --noprofile option may be used > when the > shell is started to inhibit this behavior. > > This implies, that only one of those files is read. That it stops > once it finds one. I have: > .bash_profile, .bashrc, and .profile bash will read .bash_profile and .bashrc. I would put bash-specific session-level information in .bash_profile, portable (to e.g. zsh) session-level information in .profile, and have .bash_profile source .profile. Per-shell information should go in .bashrc. But I've been doing this stuff for a while, and I can imagine people hndling single files better. (I also use the same shell config files on every system I use, which is a rather wide array of operating systems and versions.) Normally it is a good idea not to put environment settings, stty settings, etc. in .bashrc. > I am pretty sure I need to stop using .bashrc, since that is for > interactive non login shells, which I am interpreting as shells that > do work that is not the result of me using the shell. When you open a Terminal window, (by default) you get an interactive login shell. If you type "bash" in that shell, you get an interactive non-login shell. If you run vi and type ":!ls", vi will spawn a noninteractive shell to run "ls". Noninteractive shells are also used by "make", "port", and numerous other commands. > Sounds to me, like the correct course of action is to put my custom > shell aliases and settings Shell aliases should be in .bashrc. > This brings up a question, if the .bash* files do not cascade, and > stop after finding your local one, how is it that MacPorts suggests > to use .profile, as that will never get read? MacPoerts assumes you don't use the shell-specific .bash_profile or .bash_login, or if you do you also "source .profile". I would consider the latter a best practice. > On a side note, I am doing this: > export LSCOLORS=dxfxcxdxbxegedabagacad > Which has never worked for me on a non darwin OS. On many systems it's LS_COLORS, not LSCOLORS, and it has a different format. > Is that the wrong way to do it, are there more appropriate ways to > do coloring? I think having this in .bashrc actually hurt me ones, > as MacPorts saw either: > export CLICOLOR=1 or export CLICOLOR_FORCE=1 CLICOLOR_FORCE will probably cause scripts that use ls to break pretty badly. MacPorts is itself implemented using scripts. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery at kf8nh.com system administrator [openafs,heimdal,too many hats] allbery at ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part URL: From luomo1138 at yahoo.com Thu Oct 1 20:27:12 2009 From: luomo1138 at yahoo.com (Dexter Douglas) Date: Thu, 1 Oct 2009 20:27:12 -0700 (PDT) Subject: realpath failed -- error uninstalling ports Message-ID: <901015.85276.qm@web65606.mail.ac4.yahoo.com> Hello, I get this error message when I try to uninstall inactive ports: Error: port uninstall failed: realpath failed: No such file or directory Does anyone know what this means? Thanks. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From ryandesign at macports.org Thu Oct 1 21:11:19 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 1 Oct 2009 23:11:19 -0500 Subject: realpath failed -- error uninstalling ports In-Reply-To: <901015.85276.qm@web65606.mail.ac4.yahoo.com> References: <901015.85276.qm@web65606.mail.ac4.yahoo.com> Message-ID: <724332E4-9173-4AF6-B28A-70ADFC68FA9A@macports.org> On Oct 1, 2009, at 22:27, Dexter Douglas wrote: > I get this error message when I try to uninstall inactive ports: > > Error: port uninstall failed: realpath failed: No such file or > directory > > Does anyone know what this means? This happens on every port? Has it always been this way or did it recently start? If the latter, what changed? What version of Mac OS X, Xcode, MacPorts? What Mac? From hanche at math.ntnu.no Fri Oct 2 11:49:43 2009 From: hanche at math.ntnu.no (Harald Hanche-Olsen) Date: Fri, 02 Oct 2009 14:49:43 -0400 (EDT) Subject: .bashrc .profile .bash_profile In-Reply-To: <6FE8CA9B-FCF8-41ED-8D33-D8CC3A2B54DD@kf8nh.com> References: <6FE8CA9B-FCF8-41ED-8D33-D8CC3A2B54DD@kf8nh.com> Message-ID: <20091002.144943.249125823.hanche@math.ntnu.no> + Brandon Allbery : > If you run vi and type ":!ls", vi will spawn a noninteractive shell to > run "ls". Noninteractive shells are also used by "make", "port", and > numerous other commands. Note, however, that these invoke /bin/sh and not bash. Even if /bin/sh is bash, it will behave more like the classical Bourne shell for compatility reasons. See the bash man page for the rather hairy details. And thus endeth the minilecture. 8-) - Harald From talklists at newgeo.com Fri Oct 2 13:14:48 2009 From: talklists at newgeo.com (Scott Haneda) Date: Fri, 2 Oct 2009 13:14:48 -0700 Subject: .bashrc .profile .bash_profile In-Reply-To: <6FE8CA9B-FCF8-41ED-8D33-D8CC3A2B54DD@kf8nh.com> References: <6FE8CA9B-FCF8-41ED-8D33-D8CC3A2B54DD@kf8nh.com> Message-ID: <2A566FD9-C6CB-4801-8F4B-1D9E04ED0EB0@newgeo.com> Thank you! comments below... On Oct 1, 2009, at 5:21 PM, Brandon Allbery wrote: > On Oct 1, 2009, at 17:41 , Scott Haneda wrote: >> I need to understand this once and for all, there is varying info >> on this, the bash man page is verbose and not entirely clear. >> >> When bash is invoked as an interactive login shell, or as a >> non-inter- >> active shell with the --login option, it first reads and >> executes com- >> mands from the file /etc/profile, if that file exists. After >> reading >> that file, it looks for ~/.bash_profile, ~/.bash_login, and >> ~/.profile, >> in that order, and reads and executes commands from the first >> one that >> exists and is readable. The --noprofile option may be used >> when the >> shell is started to inhibit this behavior. >> >> This implies, that only one of those files is read. That it stops >> once it finds one. I have: >> .bash_profile, .bashrc, and .profile > > bash will read .bash_profile and .bashrc. > > I would put bash-specific session-level information > in .bash_profile, portable (to e.g. zsh) session-level information > in .profile, and have .bash_profile source .profile. Per-shell > information should go in .bashrc. But I've been doing this stuff > for a while, and I can imagine people hndling single files better. > (I also use the same shell config files on every system I use, which > is a rather wide array of operating systems and versions.) I do the same, move the files from one machine to that of about 10. Can you give an example of what you consider session-level info? > Normally it is a good idea not to put environment settings, stty > settings, etc. in .bashrc. What specifically is an environment setting? This means PATH would be a bad thing to have in .bashrc? What I do is work in my user account, I have aliases, and other helper things as well as the PATH adjustments to MacPorts. Most of this stuff for me is server stuff, and it gets old typing sudo all the time, so I hit up `sudo -s` which drops me into root, even though I do not believe I even have root login on. If I do not have my aliases and such in .bashrc, my `sudo -s` env is pretty stark, and hard to work in. I do not need all my settings to come over when in this `sudo -s` mode, but I certainly would like the macports paths and other things to make it. >> Sounds to me, like the correct course of action is to put my custom >> shell aliases and settings > > Shell aliases should be in .bashrc. Ok, that helps then. so alias l='ls -la' would go in .bashrc just fine? What happens if I were to alias rm to something like rm -i, would apps, installers, uninstallers and the like break? I know they should /bin/rm in their scripts to avoid this, but I also want to make sure I am not going to break things for others. >> This brings up a question, if the .bash* files do not cascade, and >> stop after finding your local one, how is it that MacPorts suggests >> to use .profile, as that will never get read? > > MacPoerts assumes you don't use the shell-specific .bash_profile > or .bash_login, or if you do you also "source .profile". I would > consider the latter a best practice. Ok, source it in .bashrc, or .bash_profile? >> On a side note, I am doing this: >> export LSCOLORS=dxfxcxdxbxegedabagacad >> Which has never worked for me on a non darwin OS. > > On many systems it's LS_COLORS, not LSCOLORS, and it has a different > format. I have never fully understood this one. On Mac OS X, what is the correct way to color your shell listings? >> Is that the wrong way to do it, are there more appropriate ways to >> do coloring? I think having this in .bashrc actually hurt me ones, >> as MacPorts saw either: >> export CLICOLOR=1 or export CLICOLOR_FORCE=1 > > CLICOLOR_FORCE will probably cause scripts that use ls to break > pretty badly. MacPorts is itself implemented using scripts. Ok, I had a feeling I needed to get rid of that, but I believe if I do, I lose my colors, so I need to figure out the correct way to set my colors in OS X. Most google searches just have people telling you to turn it on. The man page on ls is beyond my understanding on this issue. It seems to me like I need to use the CLICOLOR_FORCE, but with that, there are dangers. Brandon, thank you for taking the time on this one, it is appreciated. -- Scott * If you contact me off list replace talklists@ with scott@ * From dweber at macports.org Fri Oct 2 14:50:38 2009 From: dweber at macports.org (Darren Weber) Date: Fri, 2 Oct 2009 14:50:38 -0700 Subject: port upgrade outdated - stops at build failure on doxygen Message-ID: First, a general question about how the outdated ports are sorted - are they sorted alphabetically or is there a dependency heirarchy (or tree) that is searched to identify the order for upgrade? Now, is it possible to have 'port update outdated' continue after a build failure? Below is an example of a long list of outdated ports and the upgrade procedure fails on a port early in the process (doxygen in this case). So the upgrade stops without updating the rest of the outdated ports. For example: [ me at XXX ~ ]$ port outdated The following installed ports are outdated: doxygen 1.5.9_1 < 1.6.1_0 editres 1.0.3_1 < 1.0.4_0 ffmpeg 0.5_3 < 0.5_5 gcc_select 0.1_3 < 0.1_4 gegl 0.1.0_1 < 0.1.0_2 git-core 1.6.4.2_0 < 1.6.4.4_0 glibmm 2.20.1_0 < 2.20.2_0 gnupg 1.4.9_0 < 1.4.10_0 gnupg2 2.0.12_1 < 2.0.13_0 gpg-agent 2.0.11_1 < 2.0.13_0 GraphicsMagick 1.3.6_0 < 1.3.7_0 ImageMagick 6.5.5-7_0 < 6.5.6-1_0 iso-codes 3.10.3_0 < 3.11_0 jasper 1.900.1_4 < 1.900.1_5 libgeotiff 1.2.5_0 < 1.2.5_1 libksba 1.0.5_0 < 1.0.7_0 libquicktime 1.1.3_0 < 1.1.3_1 librsvg 2.26.0_0 < 2.26.0_1 libsdl 1.2.13_6 < 1.2.14_6 libsdl_gfx 2.0.19_0 < 2.0.20_0 libsigcxx2 2.2.3_0 < 2.2.4.2_0 libtheora 1.0_0 < 1.1.1_0 libusb 1.0.2_0 < 1.0.3_0 libxmlxx2 2.26.0_0 < 2.26.1_0 libxslt 1.1.24_2 < 1.1.26_0 llvm 2.5_0 < 2.5_1 luit 1.0.3_1 < 1.0.4_0 maxima 5.18.1_0 < 5.19.2_0 mcpp 2.7.2_1 < 2.7.2_3 mesa 7.4.3_0 < 7.6_0 mod_wsgi 1.1_1 < 2.5_0 mysql5 5.0.85_0 < 5.0.86_0 mysql5-server 5.0.85_0 < 5.0.86_0 neon 0.28.4_0 < 0.28.6_0 netcdf 4.0_0 < 4.0.1_5 ocaml 3.11.1_0 < 3.11.1_2 openmotif 2.3.1-1_2 < 2.3.2_0 orbit2 2.14.17_0 < 2.14.17_1 p5-archive-tar 1.52_0 < 1.54_0 p5-compress-raw-bzip2 2.019_0 < 2.021_0 p5-compress-raw-zlib 2.020_0 < 2.021_0 p5-datetime 0.47_0 < 0.50_0 p5-datetime-locale 0.42_0 < 0.44_0 p5-datetime-timezone 0.86_0 < 0.99_0 p5-digest-sha1 2.11_0 < 2.12_0 p5-extutils-cbuilder 0.2603_0 < 0.260301_0 p5-extutils-parsexs 2.2002_0 < 2.200401_0 p5-html-parser 3.60_0 < 3.62_0 p5-libwww-perl 5.826_0 < 5.832_0 p5-mime-base64 3.07_0 < 3.08_0 p5-module-build 0.34_0 < 0.35_0 p5-params-validate 0.91_0 < 0.92_0 p5-test-manifest 1.22_0 < 1.23_0 p5-uri 1.38_0 < 1.40_0 p5-version 0.76_0 < 0.7702_0 p5-xml-libxml 1.66_0 < 1.69_0 p5-xml-libxslt 1.66_0 < 1.68_0 p5-xml-parser-lite-tree 0.03_0 < 0.11_0 p5-xml-xpathengine 0.11_0 < 0.12_0 php5 5.3.0_2 < 5.3.0_3 php5-apc 3.1.2_3 < 3.1.3p1_0 php5-http 1.6.3_3 < 1.6.5_0 pinentry 0.7.5_0 < 0.7.6_0 poppler 0.11.1_0 < 0.12.0_0 postgresql83 8.3.7_0 < 8.3.8_0 postgresql83-server 8.3.7_0 < 8.3.8_0 postgresql84 8.4.0_0 < 8.4.1_0 py-lint 0.16.0_0 < 0.18.1_0 py-logilab-astng 0.17.4_0 < 0.19.1_0 py-logilab-common 0.42.0_0 < 0.45.0_0 py25-logilab-common 0.42.0_0 < 0.45.0_0 py25-scientific 2.6.1_0 < 2.8_0 py26-cairo 1.8.4_0 < 1.8.8_0 py26-ipython 0.9.1_0 < 0.10_0 py26-mpmath 0.12_0 < 0.13_0 py26-nose 0.10.4_0 < 0.11.1_0 py26-pil 1.1.6_0 < 1.1.6_1 py26-tz 2009j_0 < 2009n_0 python25 2.5.4_6 < 2.5.4_7 R 2.9.1_0 < 2.9.2_0 samba3 3.2.13_0 < 3.2.15_0 schroedinger 1.0.7_0 < 1.0.7_1 subversion 1.6.3_0 < 1.6.5_0 taglib 1.5_0 < 1.6_0 testdisk 6.9_0 < 6.11_0 tightvnc 1.3.9_0 < 1.3.9_2 vim 7.2.222_0 < 7.2.245_1 vim-app 7.2.222_0 < 7.2.245_0 VLC 1.0.0_1 < 1.0.2_0 vtk-devel 5.4.0_5 < 5.4.2_0 wget 1.11.4_3 < 1.12_0 wxWidgets-devel 2.8.10-rc2_0 < 2.9.0_0 x264 20090408_1 < 20090810_2 xauth 1.0.3_1 < 1.0.4_0 xclock 1.0.3_1 < 1.0.4_0 xdm 1.1.8_1 < 1.1.9_0 xinit 1.1.1_4 < 1.1.1_5 xmag 1.0.2_1 < 1.0.3_0 xorg-damageproto 1.1.0_0 < 1.2.0_0 xorg-dmxproto 2.2.2_0 < 2.3_0 xorg-evieproto 1.0.2_0 < 1.1.0_0 xorg-fixesproto 4.0_0 < 4.1_0 xorg-libdmx 1.0.2_1 < 1.0.2_2 xorg-libXcomposite 0.4.0_0 < 0.4.0_1 xorg-libXcursor 1.1.9_0 < 1.1.10_0 xorg-libXdamage 1.1.1_0 < 1.1.1_1 xorg-libXevie 1.0.2_1 < 1.0.2_2 xorg-libXfixes 4.0.3_0 < 4.0.3_1 xorg-libXfontcache 1.0.4_0 < 1.0.4_1 xorg-libXi 1.2.1_0 < 1.3_0 xorg-libXinerama 1.0.3_0 < 1.1_0 xorg-libxkbfile 1.0.5_0 < 1.0.5_1 xorg-libXrandr 1.3.0_0 < 1.3.0_1 xorg-libXres 1.0.3_0 < 1.0.3_1 xorg-libXTrap 1.0.0_2 < 1.0.0_3 xorg-libXtst 1.0.3_0 < 1.0.99.2_0 xorg-libXv 1.0.4_0 < 1.0.4_1 xorg-libXvMC 1.0.4_0 < 1.0.4_1 xorg-libXxf86dga 1.0.2_0 < 1.0.2_1 xorg-libXxf86misc 1.0.1_1 < 1.0.1_2 xorg-libXxf86vm 1.0.2_0 < 1.0.2_1 xorg-recordproto 1.13.2_0 < 1.14_0 xorg-resourceproto 1.0.2_0 < 1.1.0_0 xorg-videoproto 2.2.2_0 < 2.3.0_0 zope 2.8.7_1 < 2.8.7_2 [ me at XXX ~ ]$ [ me at XXX ~ ]$ sudo port upgrade -uR outdated ---> Computing dependencies for doxygen ---> Building doxygen Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_doxygen/work/doxygen-1.6.1" && /usr/bin/make -j8 all " returned error 2 Command output: gmake[2]: Nothing to be done for `all'. gmake[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_doxygen/work/doxygen-1.6.1/src' /opt/local/bin/gmake -f Makefile.doxygen PERL=/opt/local/bin/perl all gmake[2]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_doxygen/work/doxygen-1.6.1/src' /usr/bin/g++-4.0 -L/opt/local/lib -Wl,-search_paths_first -o ../bin/doxygen ../objects/main.o -L../lib -ldoxygen -ldoxycfg -lqtools -lmd5 -liconv Undefined symbols: "_MD5SigToString", referenced from: MemberDef::setAnchor(char const*)in libdoxygen.a(memberdef.o) convertNameToFile(char const*, bool)in libdoxygen.a(util.o) Definition::_docsAlreadyAdded(QCString const&) in libdoxygen.a(definition.o) DirDef::getOutputFileBase() const in libdoxygen.a(dirdef.o) computeMd5Signature(DotNode*, DotNode::GraphType, GraphOutputFormat, bool, bool, bool, QCString&)in libdoxygen.a(dot.o) DotGfxHierarchyTable::writeGraph(QTextStream&, char const*) constin libdoxygen.a(dot.o) MemberGroup::anchor() const in libdoxygen.a(membergroup.o) "_MD5Buffer", referenced from: MemberDef::setAnchor(char const*)in libdoxygen.a(memberdef.o) convertNameToFile(char const*, bool)in libdoxygen.a(util.o) convertNameToFile(char const*, bool)in libdoxygen.a(util.o) Definition::_docsAlreadyAdded(QCString const&) in libdoxygen.a(definition.o) DirDef::getOutputFileBase() const in libdoxygen.a(dirdef.o) computeMd5Signature(DotNode*, DotNode::GraphType, GraphOutputFormat, bool, bool, bool, QCString&)in libdoxygen.a(dot.o) DotGfxHierarchyTable::writeGraph(QTextStream&, char const*) constin libdoxygen.a(dot.o) MemberGroup::anchor() const in libdoxygen.a(membergroup.o) ld: symbol(s) not found collect2: ld returned 1 exit status gmake[2]: *** [../bin/doxygen] Error 1 gmake[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_doxygen/work/doxygen-1.6.1/src' gmake[1]: *** [all] Error 2 gmake[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_doxygen/work/doxygen-1.6.1/src' make: *** [all] Error 2 Error: Unable to upgrade port: 1 [ me at XXX ~ ]$ -------------- next part -------------- An HTML attachment was scrubbed... URL: From luomo1138 at yahoo.com Fri Oct 2 16:31:18 2009 From: luomo1138 at yahoo.com (Dexter Douglas) Date: Fri, 2 Oct 2009 16:31:18 -0700 (PDT) Subject: realpath failed -- error uninstalling ports Message-ID: <657598.29962.qm@web65605.mail.ac4.yahoo.com> Hello, I am sorry.? I left out ALL the important information. I am running Leopard on a PowerBook G4; Xcode 3.1.2; macports 1.8.1. "port uninstall" was working just fine until 1 Oct.? That is when I performed a selfupdate to 1.8.1 and then upgraded all my outdated ports. After the upgrade, I tried to clean up by uninstalling the inactive ports.? That is when I got the error message. I have two most likely unrelated pieces of information. 1) During the upgrading, doxygen failed to compile.? I ended up uninstalling and trying to reinstall.? I was not able to reinstall doxygen.? 2) I suffered from the "MacPorts 1.8.0 deletes ${prefix} if it is a symlink" problem (http://trac.macports.org/ticket/21082). Thanks. --- On Fri, 10/2/09, Ryan Schmidt wrote: > From: Ryan Schmidt > Subject: Re: realpath failed -- error uninstalling ports > To: "Dexter Douglas" > Cc: macports-users at lists.macosforge.org > Date: Friday, October 2, 2009, 12:11 AM > > On Oct 1, 2009, at 22:27, Dexter Douglas wrote: > > > I get this error message when I try to uninstall > inactive ports: > > > > Error: port uninstall failed: realpath failed: No such > file or directory > > > > Does anyone know what this means? > > This happens on every port? Has it always been this way or > did it recently start? If the latter, what changed? > > What version of Mac OS X, Xcode, MacPorts? What Mac? > > > From talklists at newgeo.com Fri Oct 2 19:20:17 2009 From: talklists at newgeo.com (Scott Haneda) Date: Fri, 2 Oct 2009 19:20:17 -0700 Subject: PATH procedures Message-ID: <91EAC9BD-87A6-43EF-B0A4-DD825E0087B6@newgeo.com> Here is my PATH as reported by ENV PATH=/opt/local/bin:/opt/local/sbin:/opt/local/apache2/bin:/Users/me/ bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin Is this pretty standard, to have to add the {prefix}/apache2/bin to your PATH? Take this for example: $which mysql5 /opt/local/bin/mysql5 $which mysqldump5 /opt/local/bin/mysqldump5 That makes things really easy, since mysql's command binaries were all decided to be located in {prefix}/bin, things just work right off the bat. Looking at the portfile for BIND, I can see that the binary for named ends up in {prefix}/sbin/named, also in the default ports PATH. Is Apache the lone soldier here, or should I expect to have to keep appending to my PATH over time? I was also thinking, perhaps the apache2 porfile, in the meantime, should symblink it's command binaries, then there would be no need for that PATH alteration. It appears that is how mysql5 has done it. If I compare the mysql5 portfile, it is 2 lines of tcl in a repeat loop to make it happen. I would be happy to modify the port, or post the suggestion to trac if this is the correct way to go about this. -- Scott * If you contact me off list replace talklists@ with scott@ * From allbery at kf8nh.com Fri Oct 2 20:48:43 2009 From: allbery at kf8nh.com (Brandon Allbery) Date: Fri, 2 Oct 2009 23:48:43 -0400 Subject: PATH procedures In-Reply-To: <91EAC9BD-87A6-43EF-B0A4-DD825E0087B6@newgeo.com> References: <91EAC9BD-87A6-43EF-B0A4-DD825E0087B6@newgeo.com> Message-ID: <3D393C83-1D8F-4A04-880F-97900DF025A7@kf8nh.com> On Oct 2, 2009, at 22:20 , Scott Haneda wrote: > Is this pretty standard, to have to add the {prefix}/apache2/bin to > your PATH? Standard Apache / Apache2 behavior, yes, as distinct from other programs. My understanding is that most of the Apache binaries aren't particularly useful on standard user PATHs (with the possible exception of htpasswd). -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery at kf8nh.com system administrator [openafs,heimdal,too many hats] allbery at ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part URL: From allbery at kf8nh.com Fri Oct 2 21:19:51 2009 From: allbery at kf8nh.com (Brandon Allbery) Date: Sat, 3 Oct 2009 00:19:51 -0400 Subject: .bashrc .profile .bash_profile In-Reply-To: <2A566FD9-C6CB-4801-8F4B-1D9E04ED0EB0@newgeo.com> References: <6FE8CA9B-FCF8-41ED-8D33-D8CC3A2B54DD@kf8nh.com> <2A566FD9-C6CB-4801-8F4B-1D9E04ED0EB0@newgeo.com> Message-ID: On Oct 2, 2009, at 16:14 , Scott Haneda wrote: > What specifically is an environment setting? This means PATH would > be a bad thing to have in .bashrc? What I do is work in my user > account, I have aliases, and other helper things as well as the PATH > adjustments to MacPorts. Anything you set with "export". (Take a look at the output of the "env" command. That's your environment.) They are inherited by subprocesses; the distinction between setting in .profile vs. .bashrc is evident if you add a directory containing non-general-purpose programs (say Apache, or some commercial packages such as Matlab or Cadence) to your path temporarily, as a subshell will lose (or override) the change if you set PATH in .bashrc. Since it's not unusual to have a script which adds the custom package to $PATH and then runs an interactive shell, you'd be undoing the script's work. stty settings are even more pervasive, as they affect the terminal and therefore every program running in it. Rerunning it every time a new shell is created is at best a waste of cycles and at worst can cause subtle breakage because stty outputs an error message when it finds it's not running in a terminal. (scp is where people usually notice this, although there are some vi and emacs commands which can also trigger it.) > Most of this stuff for me is server stuff, and it gets old typing > sudo all the time, so I hit up `sudo -s` which drops me into root, > even though I do not believe I even have root login on. "sudo" isn't root login. If you enable root login, you could use "su", or you could log into OSX as root (not recommended; I'm not even sure it's sane to log in with the GUI, as opposed to suppressing the GUI startup and getting a Darwin login prompt). sudo is generally preferred to enabling/using root directly. > If I do not have my aliases and such in .bashrc, my `sudo -s` env is > pretty stark, and hard to work in. I do not need all my settings to > come over when in this `sudo -s` mode, but I certainly would like > the macports paths and other things to make it. Aliases aren't inherited; they belong in .bashrc. (Shell functions can be inherited, but now we're getting into distinctions you probably don't want to know, much less care, about.) > Ok, that helps then. so alias l='ls -la' would go in .bashrc just > fine? What happens if I were to alias rm to something like rm -i, > would apps, installers, uninstallers and the like break? I know > they should /bin/rm in their scripts to avoid this, but I also want > to make sure I am not going to break things for others. .bashrc is (except in special cases like vi) only read by *interactive* shells, precisely for this reason; scripts won't get your aliases. There is a mechanism you can use ($ENV) to force aliases and such on noninteractive shells, but it's generally a bad idea. >>> This brings up a question, if the .bash* files do not cascade, and >>> stop after finding your local one, how is it that MacPorts >>> suggests to use .profile, as that will never get read? >> >> MacPoerts assumes you don't use the shell-specific .bash_profile >> or .bash_login, or if you do you also "source .profile". I would >> consider the latter a best practice. > > Ok, source it in .bashrc, or .bash_profile? .bash_profile >>> Is that the wrong way to do it, are there more appropriate ways to >>> do coloring? I think having this in .bashrc actually hurt me >>> ones, as MacPorts saw either: >>> export CLICOLOR=1 or export CLICOLOR_FORCE=1 >> >> CLICOLOR_FORCE will probably cause scripts that use ls to break >> pretty badly. MacPorts is itself implemented using scripts. > > Ok, I had a feeling I needed to get rid of that, but I believe if I > do, I lose my colors, so I need to figure out the correct way to set > my colors in OS X. Most google searches just have people telling > you to turn it on. The man page on ls is beyond my understanding on > this issue. CLICOLOR is the correct one to use, as it affects only interactive "ls". CLICOLOR_FORCE will also affect scripts, with similar results to the above discussion --- except that, because you "export" it, it affects more programs. Note that because it's exported, it is still dangerous even if you set it in .bashrc in an attempt to only affect interactive shells. (I wonder if I can find a good description of what's going on here somewhere. It *is* kinda confusing for beginners.) -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery at kf8nh.com system administrator [openafs,heimdal,too many hats] allbery at ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part URL: From allbery at kf8nh.com Fri Oct 2 21:21:21 2009 From: allbery at kf8nh.com (Brandon Allbery) Date: Sat, 3 Oct 2009 00:21:21 -0400 Subject: .bashrc .profile .bash_profile In-Reply-To: <2A566FD9-C6CB-4801-8F4B-1D9E04ED0EB0@newgeo.com> References: <6FE8CA9B-FCF8-41ED-8D33-D8CC3A2B54DD@kf8nh.com> <2A566FD9-C6CB-4801-8F4B-1D9E04ED0EB0@newgeo.com> Message-ID: <5FB1B043-7374-4ED9-B446-F35DF06F6FEB@kf8nh.com> You might want to read the first several chapters of Kernighan and Pike's _The Unix Programming Environment_; the sections about shell programming will clarify quite a bit of what's going on with the environment and various startup files, even though it predates bash. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery at kf8nh.com system administrator [openafs,heimdal,too many hats] allbery at ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part URL: From allbery at kf8nh.com Fri Oct 2 21:23:38 2009 From: allbery at kf8nh.com (Brandon Allbery) Date: Sat, 3 Oct 2009 00:23:38 -0400 Subject: .bashrc .profile .bash_profile In-Reply-To: <20091002.144943.249125823.hanche@math.ntnu.no> References: <6FE8CA9B-FCF8-41ED-8D33-D8CC3A2B54DD@kf8nh.com> <20091002.144943.249125823.hanche@math.ntnu.no> Message-ID: On Oct 2, 2009, at 14:49 , Harald Hanche-Olsen wrote: > + Brandon Allbery : > If you run vi and type ":!ls", vi will spawn a noninteractive shell to >> run "ls". Noninteractive shells are also used by "make", "port", and >> numerous other commands. > > Note, however, that these invoke /bin/sh and not bash. Even if /bin/sh Actually, we've both just lied. vi is a special case; for "!" and ":!" it specifically runs $SHELL, and does so "pseudo-interactively" so it will pick up aliases and local variable declarations from .cshrc / .bashrc / .zshenv etc. as appropriate so you can use them in commands. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery at kf8nh.com system administrator [openafs,heimdal,too many hats] allbery at ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part URL: From ryandesign at macports.org Sat Oct 3 00:47:32 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 3 Oct 2009 02:47:32 -0500 Subject: PATH procedures In-Reply-To: <91EAC9BD-87A6-43EF-B0A4-DD825E0087B6@newgeo.com> References: <91EAC9BD-87A6-43EF-B0A4-DD825E0087B6@newgeo.com> Message-ID: <3AC69C60-5EB0-41F1-BD4C-99631A7AECA5@macports.org> On Oct 2, 2009, at 21:20, Scott Haneda wrote: > Here is my PATH as reported by ENV > PATH=/opt/local/bin:/opt/local/sbin:/opt/local/apache2/bin:/Users/me/ > bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin > > Is this pretty standard, to have to add the {prefix}/apache2/bin to > your PATH? At present, if you want apache2's binaries available without having to type the full path, then yes, you will have to do that to your PATH. > Take this for example: > $which mysql5 > /opt/local/bin/mysql5 > > $which mysqldump5 > /opt/local/bin/mysqldump5 > > That makes things really easy, since mysql's command binaries were > all decided to be located in {prefix}/bin, things just work right > off the bat. Looking at the portfile for BIND, I can see that the > binary for named ends up in {prefix}/sbin/named, also in the default > ports PATH. > > Is Apache the lone soldier here, or should I expect to have to keep > appending to my PATH over time? I was also thinking, perhaps the > apache2 porfile, in the meantime, should symblink it's command > binaries, then there would be no need for that PATH alteration. It > appears that is how mysql5 has done it. > > If I compare the mysql5 portfile, it is 2 lines of tcl in a repeat > loop to make it happen. I would be happy to modify the port, or > post the suggestion to trac if this is the correct way to go about > this. I don't recall specific other ports that install into their own prefixes, other than apache2 and apache20. I think there are a few, but probably not many. I would not be particularly excited about modifying apache2 / apache20 to symlink their binaries into ${prefix}/bin; rather, I would be excited to have it install the files there in the first place. See: http://trac.macports.org/ticket/21315 Note that the current mysql5 layout has also been criticized, and is therefore perhaps not a good model for emulation by other ports. See: http://lists.macosforge.org/pipermail/macports-users/2007-August/004865.html I think there are more recent discussions of that as well but I couldn't immediately locate them. From ryandesign at macports.org Sat Oct 3 00:57:36 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 3 Oct 2009 02:57:36 -0500 Subject: port upgrade outdated - stops at build failure on doxygen In-Reply-To: References: Message-ID: <5F2D66A4-FC0B-4CFE-91D8-4CDB1A0DF73A@macports.org> On Oct 2, 2009, at 16:50, Darren Weber wrote: > First, a general question about how the outdated ports are sorted - > are they sorted alphabetically or is there a dependency heirarchy > (or tree) that is searched to identify the order for upgrade? The displayed list is alphabetically sorted. When you request a port to be upgraded, it will of course upgrade dependencies first, so "sudo port upgrade outdated" will not generally upgrade ports in the order listed. > Now, is it possible to have 'port update outdated' continue after a > build failure? Below is an example of a long list of outdated ports > and the upgrade procedure fails on a port early in the process > (doxygen in this case). So the upgrade stops without updating the > rest of the outdated ports. I don't know why doxygen failed for you; provide more debug output if you need help with it and/or file a ticket. To proceed past errors, use "-p" as in "sudo port -p upgrade outdated". Often this is not a good thing to do because the new version of port B may depend on the new version of port A (or port B's revision may have been specifically bumped so that it would link with the new version of port A) but if A fails and you tell upgrade to proceed to B anyway, B will rebuild against the old version of A, and once you figure out what was wrong with A and upgrade it, B will be left without its needed rebuild. Personally I don't use "sudo port upgrade outdated". Maybe it's just me but I usually have at least one port in the list that I don't want to upgrade, at least not now, because I know it will take a long time. So I just selectively "sudo port upgrade" individual ports. From whodoctor at gmail.com Sat Oct 3 06:49:59 2009 From: whodoctor at gmail.com (Doctor Who) Date: Sat, 3 Oct 2009 09:49:59 -0400 Subject: Issue with fontconfig and Snow Leopard Message-ID: <4b75340e0910030649md472cb1j7aefa4444f947fcb@mail.gmail.com> I'm trying to do an upgrade of my installed ports since upgrading to Snow Leopard and I'm getting the following error with fontconfig: $ sudo port upgrade outdated ---> Computing dependencies for fontconfig ---> Extracting fontconfig Error: You cannot install fontconfig for the architecture(s) x86_64 because /opt/local/lib/libexpat.dylib does not contain the architecture x86_64. Error: Target org.macports.extract returned: incompatible architectures in dependencies Error: Unable to upgrade port: 1 This is MacPorts 1.8.1 What is the preferred method to fix this? Thanks! From Bjoern.Guenzel at gmx.de Sat Oct 3 08:36:35 2009 From: Bjoern.Guenzel at gmx.de (Bjoern Guenzel) Date: Sat, 03 Oct 2009 17:36:35 +0200 Subject: Can't get curl to accept my self-signed root certificate Message-ID: <20091003153635.210720@gmx.net> Hello, I had this working for a short while in the end of July, but then an update to the curl port broke it: when I try to access the url of my git repository, curl answers with curl: (51) SSL peer certificate or SSH remote key was not OK It is working fine on my Linux books, so I assume the configuration of the cacerts is the problem. I have used curl-config --ca to identify the file curl uses to look for the root certificate. It points to /opt/local/share/curl/curl-ca-bundle.crt and I have added the certificate (exported from Firefox as PEM) to that file. Somehow I have alos modified /usr/share/curl - I think that was the location I found before the update broke things. The update also overwrote the ca file I had modified (which was working before). I have no idea what to try next. Sometimes curl also gave an error 60 (What I really want is to access the git repository with git, but git seems to use curl internally, so I try to get curl to load the URL). I would be very happy if somebody has ideas for fixing this. Thanks! Bj?rn -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser From jeremyhu at macports.org Sat Oct 3 09:18:55 2009 From: jeremyhu at macports.org (Jeremy Huddleston) Date: Sat, 3 Oct 2009 09:18:55 -0700 Subject: Issue with fontconfig and Snow Leopard In-Reply-To: <4b75340e0910030649md472cb1j7aefa4444f947fcb@mail.gmail.com> References: <4b75340e0910030649md472cb1j7aefa4444f947fcb@mail.gmail.com> Message-ID: <5C46D770-56F5-4A1A-A296-D48BD1617B44@macports.org> Check out the wiki for details on SL issues. The main thing is that SL defaults to 64bit builds by default. You can either: 1) Set build_arch to i386 in macports.conf and try to salvage your existing install ... or... 2) Nuke, reinstall all your MacPorts On Oct 3, 2009, at 06:49, Doctor Who wrote: > I'm trying to do an upgrade of my installed ports since upgrading to > Snow Leopard and I'm getting the following error with fontconfig: > > $ sudo port upgrade outdated > ---> Computing dependencies for fontconfig > ---> Extracting fontconfig > Error: You cannot install fontconfig for the architecture(s) x86_64 > because /opt/local/lib/libexpat.dylib does not contain the > architecture x86_64. > Error: Target org.macports.extract returned: incompatible > architectures in dependencies > Error: Unable to upgrade port: 1 > > This is MacPorts 1.8.1 > > What is the preferred method to fix this? > > Thanks! > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3333 bytes Desc: not available URL: From pengyu.ut at gmail.com Sat Oct 3 10:06:04 2009 From: pengyu.ut at gmail.com (Peng Yu) Date: Sat, 3 Oct 2009 12:06:04 -0500 Subject: How to install make? Message-ID: <366c6f340910031006g51270c95gebdcca75e39fc4b@mail.gmail.com> Hi, I want to install some packages with macport. I couldn't download the source code and install it. http://mac.softpedia.com/progDownload/GNU-Make-Download-44632.html But can somebody let me know if there is any easier way to install make in order to use MacPorts? Regards, Peng $sudo port install gmake ---> Computing dependencies for gmakeError: Unable to execute port: can't read "build.cmd": Failed to locate 'make' in path: '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at its MacPorts configuration time location, did you move it? From jeremyhu at macports.org Sat Oct 3 10:13:34 2009 From: jeremyhu at macports.org (Jeremy Huddleston) Date: Sat, 3 Oct 2009 10:13:34 -0700 Subject: How to install make? In-Reply-To: <366c6f340910031006g51270c95gebdcca75e39fc4b@mail.gmail.com> References: <366c6f340910031006g51270c95gebdcca75e39fc4b@mail.gmail.com> Message-ID: <7CAC0F8F-0844-4636-8CD2-A20F58C1517D@macports.org> You need to install XCode. http://developer.apple.com On Oct 3, 2009, at 10:06, Peng Yu wrote: > Hi, > > I want to install some packages with macport. I couldn't download the > source code and install it. > http://mac.softpedia.com/progDownload/GNU-Make-Download-44632.html > > But can somebody let me know if there is any easier way to install > make in order to use MacPorts? > > Regards, > Peng > > $sudo port install gmake > ---> Computing dependencies for gmakeError: Unable to execute port: > can't read "build.cmd": Failed to locate 'make' in path: > '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at > its MacPorts configuration time location, did you move it? > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3333 bytes Desc: not available URL: From pengyu.ut at gmail.com Sat Oct 3 14:06:14 2009 From: pengyu.ut at gmail.com (Peng Yu) Date: Sat, 3 Oct 2009 16:06:14 -0500 Subject: How to install make? In-Reply-To: <7CAC0F8F-0844-4636-8CD2-A20F58C1517D@macports.org> References: <366c6f340910031006g51270c95gebdcca75e39fc4b@mail.gmail.com> <7CAC0F8F-0844-4636-8CD2-A20F58C1517D@macports.org> Message-ID: <366c6f340910031406wc48192am29cd6c4f843b4600@mail.gmail.com> I only found Xcode 3.2 Download. "Xcode 3.2 is the developer tool set for Mac OS X 10.6 Snow Leopard. It includes Xcode, Interface Builder, Instruments, Dashcode, and the rest of the developer tools." But OS is Mac OS X 10.5. I download Xcode 3.2, which can not be installed on my Mac machine. Would you please point where I can download X Code my OS? Regards, Peng On Sat, Oct 3, 2009 at 12:13 PM, Jeremy Huddleston wrote: > You need to install XCode. > > http://developer.apple.com > > On Oct 3, 2009, at 10:06, Peng Yu wrote: > >> Hi, >> >> I want to install some packages with macport. I couldn't download the >> source code and install it. >> http://mac.softpedia.com/progDownload/GNU-Make-Download-44632.html >> >> But can somebody let me know if there is any easier way to install >> make in order to use MacPorts? >> >> Regards, >> Peng >> >> $sudo port install gmake >> ---> ?Computing dependencies for gmakeError: Unable to execute port: >> can't read "build.cmd": Failed to locate 'make' in path: >> '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at >> its MacPorts configuration time location, did you move it? >> _______________________________________________ >> macports-users mailing list >> macports-users at lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > From macports at tprfct.net Sat Oct 3 14:51:02 2009 From: macports at tprfct.net (Kastus Shchuka) Date: Sat, 3 Oct 2009 14:51:02 -0700 Subject: tmux upgrad problem In-Reply-To: <331D2C8F-3AC8-4ABF-9ED8-7A24135267AC@macports.org> References: <97408717-D9C4-4D0C-B4CC-48DA86DEE185@tprfct.net> <331D2C8F-3AC8-4ABF-9ED8-7A24135267AC@macports.org> Message-ID: <26E22D2E-364A-4FBB-B77B-8B69CE23DD7B@tprfct.net> On Oct 1, 2009, at 1:28 PM, Ryan Schmidt wrote: > On Oct 1, 2009, at 14:06, Kastus Shchuka wrote: > >> A new version of tmux showed up after port sync: >> >> tmux 1.0_0 < 1.0_3 >> >> When trying to upgrade tmux I encouter this error: > >> Undefined symbols: >> "__vprocmgr_detach_from_console", referenced from: >> _server_start in server.o > >> Shall I file a ticket in trac about it? > > Yes, please. I don't see this problem, but I tried on Snow Leopard, > not on Leopard and not on PowerPC, so there may well be unaccounted > differences. > > ticket # 21804 Thanks! From ryandesign at macports.org Sat Oct 3 16:01:21 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 3 Oct 2009 18:01:21 -0500 Subject: How to install make? In-Reply-To: <366c6f340910031406wc48192am29cd6c4f843b4600@mail.gmail.com> References: <366c6f340910031006g51270c95gebdcca75e39fc4b@mail.gmail.com> <7CAC0F8F-0844-4636-8CD2-A20F58C1517D@macports.org> <366c6f340910031406wc48192am29cd6c4f843b4600@mail.gmail.com> Message-ID: <014C2770-CA21-41FE-888E-E290C628DEF0@macports.org> On Oct 3, 2009, at 16:06, Peng Yu wrote: > I only found Xcode 3.2 Download. > > "Xcode 3.2 is the developer tool set for Mac OS X 10.6 Snow Leopard. > It includes Xcode, Interface Builder, Instruments, Dashcode, and the > rest of the developer tools." > > But OS is Mac OS X 10.5. I download Xcode 3.2, which can not be > installed on my Mac machine. Would you please point where I can > download X Code my OS? The links are here: http://guide.macports.org/chunked/installing.xcode.html From ryandesign at macports.org Sat Oct 3 16:02:32 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 3 Oct 2009 18:02:32 -0500 Subject: Issue with fontconfig and Snow Leopard In-Reply-To: <4b75340e0910030649md472cb1j7aefa4444f947fcb@mail.gmail.com> References: <4b75340e0910030649md472cb1j7aefa4444f947fcb@mail.gmail.com> Message-ID: On Oct 3, 2009, at 08:49, Doctor Who wrote: > I'm trying to do an upgrade of my installed ports since upgrading to > Snow Leopard and I'm getting the following error with fontconfig: > > $ sudo port upgrade outdated > ---> Computing dependencies for fontconfig > ---> Extracting fontconfig > Error: You cannot install fontconfig for the architecture(s) x86_64 > because /opt/local/lib/libexpat.dylib does not contain the > architecture x86_64. > Error: Target org.macports.extract returned: incompatible > architectures in dependencies > Error: Unable to upgrade port: 1 > > This is MacPorts 1.8.1 > > What is the preferred method to fix this? When upgrading from one major version of Mac OS X to another (e.g. from Leopard to Snow Leopard), you need to uninstall and reinstall all ports. See the Migration page: http://trac.macports.org/wiki/Migration From ryandesign at macports.org Sat Oct 3 16:04:00 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 3 Oct 2009 18:04:00 -0500 Subject: Can't get curl to accept my self-signed root certificate In-Reply-To: <20091003153635.210720@gmx.net> References: <20091003153635.210720@gmx.net> Message-ID: <8F3DC1DB-887B-43FE-82E0-651F5B0A2EB9@macports.org> On Oct 3, 2009, at 10:36, Bjoern Guenzel wrote: > I had this working for a short while in the end of July, but then an > update to the curl port broke it: when I try to access the url of my > git repository, curl answers with > > curl: (51) SSL peer certificate or SSH remote key was not OK > > It is working fine on my Linux books, so I assume the configuration > of the cacerts is the problem. > > I have used curl-config --ca to identify the file curl uses to look > for the root certificate. It points to /opt/local/share/curl/curl-ca- > bundle.crt and I have added the certificate (exported from Firefox > as PEM) to that file. > > Somehow I have alos modified /usr/share/curl - I think that was the > location I found before the update broke things. The update also > overwrote the ca file I had modified (which was working before). > > I have no idea what to try next. > > Sometimes curl also gave an error 60 > > (What I really want is to access the git repository with git, but > git seems to use curl internally, so I try to get curl to load the > URL). > > I would be very happy if somebody has ideas for fixing this. I am the maintainer of curl in MacPorts but I have not used the functions you're using so I don't know how to help. You may want to write to the curl mailing list instead. From gonhidi at gmail.com Sun Oct 4 04:56:27 2009 From: gonhidi at gmail.com (=?ISO-8859-1?Q?Gonzalo_HIGUERA_D=CDAZ?=) Date: Sun, 4 Oct 2009 13:56:27 +0200 Subject: [ffmpeg] CPU capabilities: None! In-Reply-To: <25622829.post@talk.nabble.com> References: <25622829.post@talk.nabble.com> Message-ID: <411f59bd0910040456l6255251dx60c55a4ebdfd41de@mail.gmail.com> 2009-09-26, staticfloat wrote: > > Hey, I'm using macports to install ffmpeg, and whether I use ffmpeg-devel or > ffmpeg, the executable I get never has any optimizations built into it! > This causes ffmpeg to run at ridiculously slow speeds! ?Can anyone else shed > any light as to how to fix this?! There is trouble buildling ffmpeg with optimizations on 32-bit Snow Leopard due to GCC 4.2 issues according to ticket #20938: http://trac.macports.org/ticket/20938 -- Gonzalo HIGUERA D?AZ From whodoctor at gmail.com Sun Oct 4 06:49:50 2009 From: whodoctor at gmail.com (Doctor Who) Date: Sun, 4 Oct 2009 09:49:50 -0400 Subject: Issue with mutt-devel after MacPorts update Message-ID: <4b75340e0910040649u64973c9cm7d6128b59e9ac2ed@mail.gmail.com> I had mutt-devel working with no issues on my Snow Leopard install until I did a complete uninstall and reinstall of MacPorts to the latest version. The issue is specifically with getting the "headercache" piece working again. I install mutt-devel with the following variants: sudo port install mutt-devel +headercache +gpgme +imap +ssl +sidebar mutt-devel then appears to install without issue, but when I launch mutt and authenticate, mutt hangs at: Fetching message headers... 0/3106 (0%) and does not progress past this point. If I install mutt without the +headercache variant and launch mutt, I get an error message complaining about the reference to headercache in my .muttrc that can be reconciled, but otherwise I can download and view the mail. Any ideas about how I can get my mutt working again with the headercache option? Not sure why it was working before the MacPorts update but is not working now. Thanks. From pengyu.ut at gmail.com Sun Oct 4 10:53:25 2009 From: pengyu.ut at gmail.com (Peng Yu) Date: Sun, 4 Oct 2009 12:53:25 -0500 Subject: How to fix the problem of "Cannot open display"? Message-ID: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> Hi, I installed X Code and MacPorts. After I installed gnome-terminal using MacPorts, I got the following error when I try to run it. Can somebody let me know how to fix it? Thank you! Regards, Peng $ gnome-terminal $Failed to parse arguments: Cannot open display: From allbery at kf8nh.com Sun Oct 4 10:55:12 2009 From: allbery at kf8nh.com (Brandon Allbery) Date: Sun, 4 Oct 2009 13:55:12 -0400 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> Message-ID: <26F71423-28CF-4204-BE95-5E5F8658AA10@kf8nh.com> On Oct 4, 2009, at 13:53 , Peng Yu wrote: > $ gnome-terminal > $Failed to parse arguments: Cannot open display: Unless you built Gtk+ with native Aqua support (which I think won't yet work with GNOME stuff), you need to install and run Apple's X11. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery at kf8nh.com system administrator [openafs,heimdal,too many hats] allbery at ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part URL: From blb at macports.org Sun Oct 4 12:42:22 2009 From: blb at macports.org (Bryan Blackburn) Date: Sun, 4 Oct 2009 13:42:22 -0600 Subject: Issue with mutt-devel after MacPorts update In-Reply-To: <4b75340e0910040649u64973c9cm7d6128b59e9ac2ed@mail.gmail.com> References: <4b75340e0910040649u64973c9cm7d6128b59e9ac2ed@mail.gmail.com> Message-ID: <20091004194222.GL471@ninagal.withay.com> On Sun, Oct 04, 2009 at 09:49:50AM -0400, Doctor Who said: > I had mutt-devel working with no issues on my Snow Leopard install > until I did a complete uninstall and reinstall of MacPorts to the > latest version. The issue is specifically with getting the > "headercache" piece working again. > > I install mutt-devel with the following variants: > > sudo port install mutt-devel +headercache +gpgme +imap +ssl +sidebar If you use 'port variants mutt-devel' you'll note that you need to select one of the database backends as well: headercache: Enable header caching (requires gdbm, qdbm, or tokyocabinet) The port should probably error out when headercache is selected but no database is... And for what it's worth, 1.5.20 with headercache and tokyocabinet is working fine here 10.6.1. Bryan > > mutt-devel then appears to install without issue, but when I launch > mutt and authenticate, mutt hangs at: > > Fetching message headers... 0/3106 (0%) > > and does not progress past this point. > > If I install mutt without the +headercache variant and launch mutt, I > get an error message complaining about the reference to headercache in > my .muttrc that can be reconciled, but otherwise I can download and > view the mail. > > Any ideas about how I can get my mutt working again with the > headercache option? Not sure why it was working before the MacPorts > update but is not working now. > > Thanks. From whodoctor at gmail.com Sun Oct 4 12:55:11 2009 From: whodoctor at gmail.com (Doctor Who) Date: Sun, 4 Oct 2009 15:55:11 -0400 Subject: Issue with mutt-devel after MacPorts update In-Reply-To: <20091004194222.GL471@ninagal.withay.com> References: <4b75340e0910040649u64973c9cm7d6128b59e9ac2ed@mail.gmail.com> <20091004194222.GL471@ninagal.withay.com> Message-ID: <4b75340e0910041255sf29a5a7uecf0e5a5eab96ddd@mail.gmail.com> On Sun, Oct 4, 2009 at 3:42 PM, Bryan Blackburn wrote: > On Sun, Oct 04, 2009 at 09:49:50AM -0400, Doctor Who said: >> I had mutt-devel working with no issues on my Snow Leopard install >> until I did a complete uninstall and reinstall of MacPorts to the >> latest version. ?The issue is specifically with getting the >> "headercache" piece working again. >> >> I install mutt-devel with the following variants: >> >> sudo port install mutt-devel +headercache +gpgme +imap +ssl +sidebar > > If you use 'port variants mutt-devel' you'll note that you need to select > one of the database backends as well: > > ? headercache: Enable header caching (requires gdbm, qdbm, or tokyocabinet) > > The port should probably error out when headercache is selected but no > database is... > > And for what it's worth, 1.5.20 with headercache and tokyocabinet is working > fine here 10.6.1. > > Bryan > Thanks. I had tried before with gdbm and had the same behavior. Trying now with tokyocabinet seems to have it working again. Weird. From pengyu.ut at gmail.com Sun Oct 4 13:08:38 2009 From: pengyu.ut at gmail.com (Peng Yu) Date: Sun, 4 Oct 2009 15:08:38 -0500 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: <26F71423-28CF-4204-BE95-5E5F8658AA10@kf8nh.com> References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> <26F71423-28CF-4204-BE95-5E5F8658AA10@kf8nh.com> Message-ID: <366c6f340910041308w79d0c80ds4f7a443336a93ee2@mail.gmail.com> On Sun, Oct 4, 2009 at 12:55 PM, Brandon Allbery wrote: > On Oct 4, 2009, at 13:53 , Peng Yu wrote: >> >> $ gnome-terminal >> $Failed to parse arguments: Cannot open display: > > > Unless you built Gtk+ with native Aqua support (which I think won't yet work > with GNOME stuff), you need to install and run Apple's X11. My OS is leopard. Would you please point me where I should download it? And how to install it? Thank you! Regards, Peng From allbery at kf8nh.com Sun Oct 4 13:14:29 2009 From: allbery at kf8nh.com (Brandon Allbery) Date: Sun, 4 Oct 2009 16:14:29 -0400 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: <366c6f340910041308w79d0c80ds4f7a443336a93ee2@mail.gmail.com> References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> <26F71423-28CF-4204-BE95-5E5F8658AA10@kf8nh.com> <366c6f340910041308w79d0c80ds4f7a443336a93ee2@mail.gmail.com> Message-ID: <29FBDB5B-5F23-4F56-A439-1A8F1DEBF38E@kf8nh.com> On Oct 4, 2009, at 16:08 , Peng Yu wrote: > On Sun, Oct 4, 2009 at 12:55 PM, Brandon Allbery > wrote: >> On Oct 4, 2009, at 13:53 , Peng Yu wrote: >>> $ gnome-terminal >>> $Failed to parse arguments: Cannot open display: >> >> >> Unless you built Gtk+ with native Aqua support (which I think won't >> yet work >> with GNOME stuff), you need to install and run Apple's X11. > > My OS is leopard. Would you please point me where I should download > it? And how to install it? Thank you! Official X11 for Leopard is on your install DVD (run System Update afterward). Unofficial, but with updates and bugfixes: http://xquartz.macosforge.net X11 should have been installed by default on Leopard, actually, but without the XQuartz update it won't auto-run; you'll find X11.app in / Applications/Utilities. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery at kf8nh.com system administrator [openafs,heimdal,too many hats] allbery at ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part URL: From pengyu.ut at gmail.com Sun Oct 4 13:54:58 2009 From: pengyu.ut at gmail.com (Peng Yu) Date: Sun, 4 Oct 2009 15:54:58 -0500 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: <29FBDB5B-5F23-4F56-A439-1A8F1DEBF38E@kf8nh.com> References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> <26F71423-28CF-4204-BE95-5E5F8658AA10@kf8nh.com> <366c6f340910041308w79d0c80ds4f7a443336a93ee2@mail.gmail.com> <29FBDB5B-5F23-4F56-A439-1A8F1DEBF38E@kf8nh.com> Message-ID: <366c6f340910041354y4b499a1rab34385329effd1a@mail.gmail.com> On Sun, Oct 4, 2009 at 3:14 PM, Brandon Allbery wrote: > On Oct 4, 2009, at 16:08 , Peng Yu wrote: >> >> On Sun, Oct 4, 2009 at 12:55 PM, Brandon Allbery >> wrote: >>> >>> On Oct 4, 2009, at 13:53 , Peng Yu wrote: >>>> >>>> $ gnome-terminal >>>> $Failed to parse arguments: Cannot open display: >>> >>> >>> Unless you built Gtk+ with native Aqua support (which I think won't yet >>> work >>> with GNOME stuff), you need to install and run Apple's X11. >> >> My OS is leopard. Would you please point me where I should download >> it? And how to install it? Thank you! > > > Official X11 for Leopard is on your install DVD (run System Update > afterward). > Unofficial, but with updates and bugfixes: ?http://xquartz.macosforge.net > > X11 should have been installed by default on Leopard, actually, but without > the XQuartz update it won't auto-run; you'll find X11.app in > /Applications/Utilities. I started X11.app in /Applications/Utilities. But I still got the same error as that in my original post. What's the problem? How to run XQuartz update? Do I need to download X11-2.4.0.dmg and install it? What is the difference between X11-2.4.0.dmg and X11.app in /Applications/Utilities? http://xquartz.macosforge.org/trac/wiki/X112.4.0 Regards, Peng From blb at macports.org Sun Oct 4 13:58:38 2009 From: blb at macports.org (Bryan Blackburn) Date: Sun, 4 Oct 2009 14:58:38 -0600 Subject: Issue with mutt-devel after MacPorts update In-Reply-To: <4b75340e0910041255sf29a5a7uecf0e5a5eab96ddd@mail.gmail.com> References: <4b75340e0910040649u64973c9cm7d6128b59e9ac2ed@mail.gmail.com> <20091004194222.GL471@ninagal.withay.com> <4b75340e0910041255sf29a5a7uecf0e5a5eab96ddd@mail.gmail.com> Message-ID: <20091004205838.GM471@ninagal.withay.com> On Sun, Oct 04, 2009 at 03:55:11PM -0400, Doctor Who said: > On Sun, Oct 4, 2009 at 3:42 PM, Bryan Blackburn wrote: > > On Sun, Oct 04, 2009 at 09:49:50AM -0400, Doctor Who said: > >> I had mutt-devel working with no issues on my Snow Leopard install > >> until I did a complete uninstall and reinstall of MacPorts to the > >> latest version. ?The issue is specifically with getting the > >> "headercache" piece working again. > >> > >> I install mutt-devel with the following variants: > >> > >> sudo port install mutt-devel +headercache +gpgme +imap +ssl +sidebar > > > > If you use 'port variants mutt-devel' you'll note that you need to select > > one of the database backends as well: > > > > ? headercache: Enable header caching (requires gdbm, qdbm, or tokyocabinet) > > > > The port should probably error out when headercache is selected but no > > database is... > > > > And for what it's worth, 1.5.20 with headercache and tokyocabinet is working > > fine here 10.6.1. > > > > Bryan > > > > Thanks. I had tried before with gdbm and had the same behavior. > Trying now with tokyocabinet seems to have it working again. Weird. Hmm, perhaps there's something wrong with headercache+gdbm; looking at the Portfile again, it actually looks like +gdbm should get set if you don't set one of the other databases. Bryan From allbery at kf8nh.com Sun Oct 4 14:32:04 2009 From: allbery at kf8nh.com (Brandon Allbery) Date: Sun, 4 Oct 2009 17:32:04 -0400 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: <366c6f340910041354y4b499a1rab34385329effd1a@mail.gmail.com> References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> <26F71423-28CF-4204-BE95-5E5F8658AA10@kf8nh.com> <366c6f340910041308w79d0c80ds4f7a443336a93ee2@mail.gmail.com> <29FBDB5B-5F23-4F56-A439-1A8F1DEBF38E@kf8nh.com> <366c6f340910041354y4b499a1rab34385329effd1a@mail.gmail.com> Message-ID: On Oct 4, 2009, at 16:54 , Peng Yu wrote: > I started X11.app in /Applications/Utilities. But I still got the same > error as that in my original post. What's the problem? You'll need to run gnome-terminal from the initial xterm, or from X11's Application menu, or after starting X11 do "export DISPLAY=:0" in a Terminal.app, or install the update do launchd will do forwarding automatically. > How to run XQuartz update? Do I need to download X11-2.4.0.dmg and > install it? What is the difference between X11-2.4.0.dmg and X11.app > in /Applications/Utilities? Yes, download and install X11-2.4.0.dmg. (Note that this won't install on Snow Leopard.) The big user-visible change is that X11 2.4.0 hooks into launchd, so launchd presets $DISPLAY for you and X11.app will launch automatically if needed. Otherwise it's mostly bugfixes. If you're going to make significant use of Apple's X11, I suggest subscribing to x11-users at lists.apple.com. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery at kf8nh.com system administrator [openafs,heimdal,too many hats] allbery at ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part URL: From ryandesign at macports.org Sun Oct 4 16:05:44 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 4 Oct 2009 18:05:44 -0500 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> <26F71423-28CF-4204-BE95-5E5F8658AA10@kf8nh.com> <366c6f340910041308w79d0c80ds4f7a443336a93ee2@mail.gmail.com> <29FBDB5B-5F23-4F56-A439-1A8F1DEBF38E@kf8nh.com> <366c6f340910041354y4b499a1rab34385329effd1a@mail.gmail.com> Message-ID: <9DA61651-B94F-4AD0-8B79-CB261657270C@macports.org> On Oct 4, 2009, at 16:32, Brandon Allbery wrote: > On Oct 4, 2009, at 16:54 , Peng Yu wrote: >> I started X11.app in /Applications/Utilities. But I still got the >> same >> error as that in my original post. What's the problem? > > You'll need to run gnome-terminal from the initial xterm, or from > X11's Application menu, or after starting X11 do "export DISPLAY=:0" > in a Terminal.app, or install the update do launchd will do > forwarding automatically. Starting on Leopard, Apple sets the DISPLAY variable for you in a way that X11 should auto-launch when you request an X11 program. So Brandon, you should not manually set DISPLAY, and Peng, I don't understand why X11 did not auto-launch for you. Do you have DISPLAY set to something in for example your .profile? If so, remove that, close the Terminal, open a new one, and try again. Also, note that you can install the xorg-server port and the quartz-wm port in MacPorts, and use /Applications/MacPorts/X11.app instead of Apple's /Applications/Utilities/X11.app. This is a slightly newer version of X11 than the one you'd get from Apple. From brooks at clarksonline.net Sun Oct 4 16:37:09 2009 From: brooks at clarksonline.net (M. Brooks Clark) Date: Sun, 4 Oct 2009 18:37:09 -0500 Subject: php5 and sqlite Message-ID: <6870E81D-85FE-48B7-989D-3078F142176C@clarksonline.net> I have installed php5 along with php5-sqlite. When I try to access a mysql database using PHP, however, I get an exception. The line to open the database is: $db = new PDO("sqlite:/opt/local/var/wview/archive/ weatherAverages.sqlite"); The exception I get is: "could not find driver" Am I missing something in my config files and/or is there something else I need to include in the php code? I'm running MacPorts v1.8.1 on Snow Leopard. Thanks, Brooks From artie.ziff at gmail.com Sun Oct 4 17:26:39 2009 From: artie.ziff at gmail.com (Artie Ziff) Date: Sun, 04 Oct 2009 17:26:39 -0700 Subject: using macports and numpy dependency Message-ID: <4AC93D3F.3050406@gmail.com> Hello, Perhaps someone can clarify dependency details? Does MacPorts "info" indicate that numpy module is configured (in MacPorts) to work only with python24? I already had python26 installed and selected. Is there a way to specify to MacPorts not to install python24, in this situation, and use python 2,6 instead? Is this an example of a situation where it is better to use a different strategy, if I do not want to use python 2.4? ### $ port info py-numpy py-numpy @1.3.0 (python) Description: The core utilities for the scientific library scipy for Python Homepage: http://numpy.scipy.org/ Library Dependencies: python24, fftw-3, py-nose Platforms: darwin License: unknown Maintainers: dh at macports.org, openmaintainer at macports.org ### Thanks! AZ From ryandesign at macports.org Sun Oct 4 17:28:28 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 4 Oct 2009 19:28:28 -0500 Subject: php5 and sqlite In-Reply-To: <6870E81D-85FE-48B7-989D-3078F142176C@clarksonline.net> References: <6870E81D-85FE-48B7-989D-3078F142176C@clarksonline.net> Message-ID: On Oct 4, 2009, at 18:37, M. Brooks Clark wrote: > I have installed php5 along with php5-sqlite. When I try to access a > mysql database using PHP, however, I get an exception. > > The line to open the database is: > > $db = new PDO("sqlite:/opt/local/var/wview/archive/ > weatherAverages.sqlite"); > > The exception I get is: > > "could not find driver" > > > Am I missing something in my config files and/or is there something > else I need to include in the php code? > > I'm running MacPorts v1.8.1 on Snow Leopard. Does sqlite support show up in phpinfo, like this? $ php -r 'phpinfo();' | grep sqlite /opt/local/var/db/php5/sqlite.ini, PDO drivers => mysql, odbc, oci, sqlite, sqlite2 pdo_sqlite PECL Module version => 2.0-dev $Id: sqlite.c,v 1.166.2.13.2.9.2.22 2009/06/25 09:38:04 johannes Exp $ sqlite.assoc_case => 0 => 0 sqlite3 sqlite3.extension_dir => no value => no value If not, check your php.ini for a line beginning with "extension_dir". If you find one, remove it, as it can interfere with loading the extensions. From blb at macports.org Sun Oct 4 17:28:53 2009 From: blb at macports.org (Bryan Blackburn) Date: Sun, 4 Oct 2009 18:28:53 -0600 Subject: using macports and numpy dependency In-Reply-To: <4AC93D3F.3050406@gmail.com> References: <4AC93D3F.3050406@gmail.com> Message-ID: <20091005002853.GN471@ninagal.withay.com> On Sun, Oct 04, 2009 at 05:26:39PM -0700, Artie Ziff said: > Hello, > > Perhaps someone can clarify dependency details? > > Does MacPorts "info" indicate that numpy module is configured (in > MacPorts) to work only with python24? > > I already had python26 installed and selected. > > Is there a way to specify to MacPorts not to install python24, in this > situation, and use python 2,6 instead? You want the py26-numpy port, py-* ports are all 2.4-based, py25-* for 2.5, etc... Bryan > > Is this an example of a situation where it is better to use a different > strategy, if I do not want to use python 2.4? > > ### > > $ port info py-numpy > py-numpy @1.3.0 (python) > > Description: The core utilities for the scientific library > scipy for Python > Homepage: http://numpy.scipy.org/ > > Library Dependencies: python24, fftw-3, py-nose > Platforms: darwin > License: unknown > Maintainers: dh at macports.org, openmaintainer at macports.org > > ### > > Thanks! > AZ From ryandesign at macports.org Sun Oct 4 17:30:05 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 4 Oct 2009 19:30:05 -0500 Subject: using macports and numpy dependency In-Reply-To: <4AC93D3F.3050406@gmail.com> References: <4AC93D3F.3050406@gmail.com> Message-ID: <02D66FAE-7829-4B57-BC0F-8584E0A67B10@macports.org> On Oct 4, 2009, at 19:26, Artie Ziff wrote: > Does MacPorts "info" indicate that numpy module is configured (in > MacPorts) to work only with python24? Yes. > I already had python26 installed and selected. > > Is there a way to specify to MacPorts not to install python24, in this > situation, and use python 2,6 instead? Use the port py26-numpy instead. > Is this an example of a situation where it is better to use a > different > strategy, if I do not want to use python 2.4? Individual Python module ports are for specific versions of Python. The ones without a version number in the port name (py-*) are for Python 2.4. The others (py25-*, py26-*, py31-*) should be self- explanatory. From artie.ziff at gmail.com Sun Oct 4 17:52:05 2009 From: artie.ziff at gmail.com (Artie Ziff) Date: Sun, 04 Oct 2009 17:52:05 -0700 Subject: using macports and numpy dependency In-Reply-To: <02D66FAE-7829-4B57-BC0F-8584E0A67B10@macports.org> References: <4AC93D3F.3050406@gmail.com> <02D66FAE-7829-4B57-BC0F-8584E0A67B10@macports.org> Message-ID: <4AC94335.9070709@gmail.com> Thank you bryan and ryan. I need to spend more time with `port search ` results. I found this, in the interim: sudo port install py26-pip sudo pip-2.6 install numpy Thank you for setting me on the narrow strait. Cheers, AZ From brooks at clarksonline.net Sun Oct 4 18:06:55 2009 From: brooks at clarksonline.net (M. Brooks Clark) Date: Sun, 4 Oct 2009 20:06:55 -0500 Subject: php5 and sqlite In-Reply-To: References: <6870E81D-85FE-48B7-989D-3078F142176C@clarksonline.net> Message-ID: <348C137C-282E-4C67-B462-3F7CAD2ACDE5@clarksonline.net> > > On Oct 4, 2009, at 18:37, M. Brooks Clark wrote: > >> I have installed php5 along with php5-sqlite. When I try to access >> a mysql database using PHP, however, I get an exception. >> >> The line to open the database is: >> >> $db = new PDO("sqlite:/opt/local/var/wview/archive/ >> weatherAverages.sqlite"); >> >> The exception I get is: >> >> "could not find driver" >> >> >> Am I missing something in my config files and/or is there something >> else I need to include in the php code? >> >> I'm running MacPorts v1.8.1 on Snow Leopard. > > > Does sqlite support show up in phpinfo, like this? > > > $ php -r 'phpinfo();' | grep sqlite > /opt/local/var/db/php5/sqlite.ini, > PDO drivers => mysql, odbc, oci, sqlite, sqlite2 > pdo_sqlite > PECL Module version => 2.0-dev $Id: sqlite.c,v 1.166.2.13.2.9.2.22 > 2009/06/25 09:38:04 johannes Exp $ > sqlite.assoc_case => 0 => 0 > sqlite3 > sqlite3.extension_dir => no value => no value > > > If not, check your php.ini for a line beginning with > "extension_dir". If you find one, remove it, as it can interfere > with loading the extensions. > > Thanks. The extension_dir line was not commented out in my php.ini file: extension_dir = "./" Looks like that did it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pengyu.ut at gmail.com Sun Oct 4 18:12:21 2009 From: pengyu.ut at gmail.com (Peng Yu) Date: Sun, 4 Oct 2009 20:12:21 -0500 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: <9DA61651-B94F-4AD0-8B79-CB261657270C@macports.org> References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> <26F71423-28CF-4204-BE95-5E5F8658AA10@kf8nh.com> <366c6f340910041308w79d0c80ds4f7a443336a93ee2@mail.gmail.com> <29FBDB5B-5F23-4F56-A439-1A8F1DEBF38E@kf8nh.com> <366c6f340910041354y4b499a1rab34385329effd1a@mail.gmail.com> <9DA61651-B94F-4AD0-8B79-CB261657270C@macports.org> Message-ID: <366c6f340910041812w60754e1cu3b184d7e35916a36@mail.gmail.com> On Sun, Oct 4, 2009 at 6:05 PM, Ryan Schmidt wrote: > > On Oct 4, 2009, at 16:32, Brandon Allbery wrote: > >> On Oct 4, 2009, at 16:54 , Peng Yu wrote: >>> >>> I started X11.app in /Applications/Utilities. But I still got the same >>> error as that in my original post. What's the problem? >> >> You'll need to run gnome-terminal from the initial xterm, or from X11's >> Application menu, or after starting X11 do "export DISPLAY=:0" in a >> Terminal.app, or install the update do launchd will do forwarding >> automatically. > > Starting on Leopard, Apple sets the DISPLAY variable for you in a way that > X11 should auto-launch when you request an X11 program. So Brandon, you > should not manually set DISPLAY, and Peng, I don't understand why X11 did > not auto-launch for you. Do you have DISPLAY set to something in for example > your .profile? If so, remove that, close the Terminal, open a new one, and > try again. > > Also, note that you can install the xorg-server port and the quartz-wm port > in MacPorts, and use /Applications/MacPorts/X11.app instead of Apple's > /Applications/Utilities/X11.app. This is a slightly newer version of X11 > than the one you'd get from Apple. I deleted 'export DISPLAY=localhost:0' in my ~/.bash_profile. I also installed the xorg-server port and the quartz-wm port, and started /Applications/MacPorts/X11.app. Then I started gnome-terminal. But I got the following error. Would you please let me know how to fix this problem? $ gnome-terminal Xlib: extension "RANDR" missing on display "/tmp/launch-blAgTJ/:0". Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! Failed to get the session bus: Not enough memory Falling back to non-factory mode. Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) ** ERROR:terminal-app.c:1432:terminal_app_init: assertion failed: (app->default_profile_id != NULL) Abort trap From talklists at newgeo.com Sun Oct 4 18:17:47 2009 From: talklists at newgeo.com (Scott Haneda) Date: Sun, 4 Oct 2009 18:17:47 -0700 Subject: .bashrc .profile .bash_profile In-Reply-To: References: <6FE8CA9B-FCF8-41ED-8D33-D8CC3A2B54DD@kf8nh.com> <2A566FD9-C6CB-4801-8F4B-1D9E04ED0EB0@newgeo.com> Message-ID: <6A1CD4B1-DE13-4E41-9E08-A1F392E39183@newgeo.com> Thanks for all this great info, I think I am getting a handle on it much better now. I always had it hobbled together, but do believe I am getting to a point where I understand the repercussions of the files and settings I am creating. More comments inline below... On Oct 2, 2009, at 9:19 PM, Brandon Allbery wrote: > On Oct 2, 2009, at 16:14 , Scott Haneda wrote: >> What specifically is an environment setting? This means PATH would >> be a bad thing to have in .bashrc? What I do is work in my user >> account, I have aliases, and other helper things as well as the >> PATH adjustments to MacPorts. > > Anything you set with "export". (Take a look at the output of the > "env" command. That's your environment.) They are inherited by > subprocesses; the distinction between setting in .profile > vs. .bashrc is evident if you add a directory containing non-general- > purpose programs (say Apache, or some commercial packages such as > Matlab or Cadence) to your path temporarily, as a subshell will lose > (or override) the change if you set PATH in .bashrc. Since it's not > unusual to have a script which adds the custom package to $PATH and > then runs an interactive shell, you'd be undoing the script's work. Understood, thanks. > stty settings are even more pervasive, as they affect the terminal > and therefore every program running in it. Rerunning it every time > a new shell is created is at best a waste of cycles and at worst can > cause subtle breakage because stty outputs an error message when it > finds it's not running in a terminal. (scp is where people usually > notice this, although there are some vi and emacs commands which can > also trigger it.) I started to read up on this the other day. Your mention of cycles seems to be more relevant ages ago, when a new shell could take quite some time to start, as it has to load all the actions it was told to. I suppose, with so much CPU to spare these days, no one much thinks about this. >> Most of this stuff for me is server stuff, and it gets old typing >> sudo all the time, so I hit up `sudo -s` which drops me into root, >> even though I do not believe I even have root login on. > > "sudo" isn't root login. If you enable root login, you could use > "su", or you could log into OSX as root (not recommended; I'm not > even sure it's sane to log in with the GUI, as opposed to > suppressing the GUI startup and getting a Darwin login prompt). > sudo is generally preferred to enabling/using root directly. I am not sure where I picked up `sudo -s` but I have been using it going back to 10.2 or so. Reading up on `man sudo` I learned that `sudo -s` is just running the shell as specified in the SHELL in ENV. $ENV | grep SHELL SHELL=/bin/bash It appears in my shell's case, `sudo -s` is simply going to run `sudo / bin/bash`, which it gets out of ENV. A few things I am still not grasping, is that you state that "sudo is not root". I export my PS1 as this: export PS1="\u@\h \W $" With that, I get \u for username. My default prompt on making a new terminal window: me at macbook ~ $ If I `sudo -s` or longhand it with `sudo /bin/bash` my PS1 setting will look like this: root at macbook ~ $ Can you explain why, if I am not root, the shell thinks that \u is in fact root? What I like about this, is it takes with it most of my ENV, but also treats me more like a root user that is masquerading as my normal user. For example, as `sudo -s`, a few things to take note of: $sudo -s $pwd /Users/me $cd ~ root at macbook ~ $pwd /Users/haneda ( ie: not dropped into roots ~ ) Even though I am listed as user root, my home is not that of root, but my home. Along with that, I get my SSH_AUTH_SOCK, HOME, CLICOLOR_FORCE, PATH, and most all of the other settings I am used to having. I just do not have to deal with prefixing sudo on everything. I try to prefix most of my work with sudo, usually that works fine. The reasons I drop into `sudo -s` is entirely tab completion. Say that I have a path in which the permissions are restrictive enough that my admin user can not get to it. If I try to: sudo cp /some/place/that/I/have/no/permissions/file.txt /opt/local/ some/other/place I will not be able to use tab completion, the second I hits a directory with restrictive permissions, I have to type out the path by hand, which I never can spell correct. If I am in `sudo -s` I ca tab complete any path I desire. Is this bad practice? I should really just `sudo` all my commands and struggle through the really long paths? In my testing of all this, I added in "echo 'this is .profile';" and similar to all the dot files, at line #1, so as I was moving around, I could see what was being sourced, and if I had been sourcing files in the correct way. I learned a lot from this. I usually set up a line like that on all my remote machines, so when I ssh in, I am greeted with something that tells me what machine I am on. Most have the same username, and I try not to add too much data to the PS1 setting, as long paths can do strange visual things for me with line wrap. This has never caused me any issues. However, I tried to use Interarchy, to ssh/sftp into a remote host, something I do all the time, and this time around, I got a login failure. As soon as I removed my echo statements that were printing out which files were being sourced, I was allowed login again. Do you think this is a client issue, with Interarchy, or do I need to perhaps echo those statements out in a different way, in some way that returns data, rather than prints out a string? >> If I do not have my aliases and such in .bashrc, my `sudo -s` env >> is pretty stark, and hard to work in. I do not need all my settings >> to come over when in this `sudo -s` mode, but I certainly would >> like the macports paths and other things to make it. > > Aliases aren't inherited; they belong in .bashrc. (Shell functions > can be inherited, but now we're getting into distinctions you > probably don't want to know, much less care, about.) I get curious, :) you sent another email with some good links and references in them, I will be going thought them. My experience shows they *are* inherited.. alias l='ls -lAG | grep -v DS_Store' alias traceroute='traceroute -I -q 1 -w 2' those are two of many I have set in .bashrc at the moment. In either a normal login, locally, or ssh, where I have copied the .bashrc, I can use `l` as a way to trigger the alias above. If I `sudo -s`, I also get the alias to work. me at macbook ~ $alias | grep trace alias traceroute='traceroute -I -q 1 -w 2' sudo -s **** root at macbook ~ $alias | grep trace alias traceroute='traceroute -I -q 1 -w 2' I just also noticed, with `sudo -s` I also get full use of my .bash_history, so control-r is still useful under that condition as well. >> Ok, that helps then. so alias l='ls -la' would go in .bashrc just >> fine? What happens if I were to alias rm to something like rm -i, >> would apps, installers, uninstallers and the like break? I know >> they should /bin/rm in their scripts to avoid this, but I also want >> to make sure I am not going to break things for others. > > .bashrc is (except in special cases like vi) only read by > *interactive* shells, precisely for this reason; scripts won't get > your aliases. There is a mechanism you can use ($ENV) to force > aliases and such on noninteractive shells, but it's generally a bad > idea. Cool, very good to know. This all came from a few years back, there were several posts, I believe one on macosxhints, on exactly this. This may have been in the tcsh days so a little different. The core idea, was to alias `rm` to `rm -i`, and how doing so would break many other scripts and apps. I walked away thinking, whatever the case may be, that the developer of the app or script should not use `rm` but should fish out the real path toe `rm` and use the full path. If they know the deployment OS, they would not even have to fish it out, but just know where it is, and use /bin/rm, which before they started the work of the script, they could do some small unit tests on it, to make sure it works as they expect it to. >>>> This brings up a question, if the .bash* files do not cascade, >>>> and stop after finding your local one, how is it that MacPorts >>>> suggests to use .profile, as that will never get read? >>> >>> MacPoerts assumes you don't use the shell-specific .bash_profile >>> or .bash_login, or if you do you also "source .profile". I would >>> consider the latter a best practice. >> >> Ok, source it in .bashrc, or .bash_profile? > > .bash_profile Here is what I am doing now: $cat .bash_profile if [ -f ~/.bashrc ]; then source ~/.bashrc fi $cat .bashrc export PS1="\u@\h \W $" ... alias traceroute='traceroute -I -q 1 -w 2' ... more aliases export ..... a few things here and there. # For MacPorts, so I can edit in textmate locally, if remote, I use pico/nano export DISPLAY=:0.0 export EDITOR=/usr/bin/pico if [[ -z $SSH_CLIENT ]]; then export EDITOR=/Users/me/bin/mate else export EDITOR=/usr/bin/pico fi; $cat .profile export PATH=/opt/local/bin:/opt/local/sbin:$PATH export MANPATH=/opt/local/share/man:$MANPATH * Nothing sources .profile, but PATH looks good to me: $echo $PATH /opt/local/bin:/opt/local/sbin:/opt/local/apache2/bin:/Users/me/bin:/ usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin ** Wow, that was a mouthful, hope you were able to follow along, as I barely was :) >>>> Is that the wrong way to do it, are there more appropriate ways >>>> to do coloring? I think having this in .bashrc actually hurt me >>>> ones, as MacPorts saw either: >>>> export CLICOLOR=1 or export CLICOLOR_FORCE=1 >>> >>> CLICOLOR_FORCE will probably cause scripts that use ls to break >>> pretty badly. MacPorts is itself implemented using scripts. >> >> Ok, I had a feeling I needed to get rid of that, but I believe if I >> do, I lose my colors, so I need to figure out the correct way to >> set my colors in OS X. Most google searches just have people >> telling you to turn it on. The man page on ls is beyond my >> understanding on this issue. > > CLICOLOR is the correct one to use, as it affects only interactive > "ls". CLICOLOR_FORCE will also affect scripts, with similar results > to the above discussion --- except that, because you "export" it, it > affects more programs. Note that because it's exported, it is still > dangerous even if you set it in .bashrc in an attempt to only affect > interactive shells. So, can I use it and not export it? It seems in all examples I can find, CLICOLOR_FORCE needs to be exported, but maybe there is a "set" way to do it, 'SET CLICOLOR_FORCE' in which case it would not be exported, but just available to me for my session? > (I wonder if I can find a good description of what's going on here > somewhere. It *is* kinda confusing for beginners.) There is no shortage of data, but mix that with unix, linux, bash, tcsh, and all the rest, sprinkle in some general misunderstanding of how this all works, and it seems better to get answers from people who can answer "why", and not those who just say "paste this in the terminal"... Thank you again for all this, I will do my best to grok it all, and get it written up somewhere that others may benefit from it. -- Scott * If you contact me off list replace talklists@ with scott@ * From rfritz333 at gmail.com Sun Oct 4 18:33:34 2009 From: rfritz333 at gmail.com (Randolph Fritz) Date: Mon, 5 Oct 2009 01:33:34 +0000 (UTC) Subject: OpenSceneGraph debug libraries? Message-ID: Is there any way I can get MacPorts to build debug versions of the OSG libraries? Or does it already do so and me not knowing? -- Randolph Fritz design machine group, architecture department, university of washington rfritz at u.washington.edu -or- rfritz333 at gmail.com From ryandesign at macports.org Sun Oct 4 20:05:44 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 4 Oct 2009 22:05:44 -0500 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: <366c6f340910041812w60754e1cu3b184d7e35916a36@mail.gmail.com> References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> <26F71423-28CF-4204-BE95-5E5F8658AA10@kf8nh.com> <366c6f340910041308w79d0c80ds4f7a443336a93ee2@mail.gmail.com> <29FBDB5B-5F23-4F56-A439-1A8F1DEBF38E@kf8nh.com> <366c6f340910041354y4b499a1rab34385329effd1a@mail.gmail.com> <9DA61651-B94F-4AD0-8B79-CB261657270C@macports.org> <366c6f340910041812w60754e1cu3b184d7e35916a36@mail.gmail.com> Message-ID: <7329EB1B-F846-4993-8D94-8BA35C061BD0@macports.org> On Oct 4, 2009, at 20:12, Peng Yu wrote: > I deleted 'export DISPLAY=localhost:0' in my ~/.bash_profile. I also > installed the xorg-server port and the quartz-wm port, and started > /Applications/MacPorts/X11.app. Then I started gnome-terminal. But I > got the following error. Would you please let me know how to fix this > problem? > > $ gnome-terminal > Xlib: extension "RANDR" missing on display "/tmp/launch-blAgTJ/:0". FYI, you can ignore the RANDR message. > Dynamic session lookup supported but failed: launchd did not provide a > socket path, verify that org.freedesktop.dbus-session.plist is loaded! Sounds like org.freedesktop.dbus-session.plist is not loaded. You should load it. It is provided by the dbus port, which should have printed instructions for you upon installation advising you how to load it. I believe the line it would have printed is: launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus- session.plist So run that command (not as sudo). From pengyu.ut at gmail.com Sun Oct 4 20:36:36 2009 From: pengyu.ut at gmail.com (Peng Yu) Date: Sun, 4 Oct 2009 22:36:36 -0500 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: <7329EB1B-F846-4993-8D94-8BA35C061BD0@macports.org> References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> <26F71423-28CF-4204-BE95-5E5F8658AA10@kf8nh.com> <366c6f340910041308w79d0c80ds4f7a443336a93ee2@mail.gmail.com> <29FBDB5B-5F23-4F56-A439-1A8F1DEBF38E@kf8nh.com> <366c6f340910041354y4b499a1rab34385329effd1a@mail.gmail.com> <9DA61651-B94F-4AD0-8B79-CB261657270C@macports.org> <366c6f340910041812w60754e1cu3b184d7e35916a36@mail.gmail.com> <7329EB1B-F846-4993-8D94-8BA35C061BD0@macports.org> Message-ID: <366c6f340910042036l6f0c0329y80bb43b9742d5f77@mail.gmail.com> On Sun, Oct 4, 2009 at 10:05 PM, Ryan Schmidt wrote: > On Oct 4, 2009, at 20:12, Peng Yu wrote: > >> I deleted 'export DISPLAY=localhost:0' in my ~/.bash_profile. I also >> installed the xorg-server port and the quartz-wm port, and started >> /Applications/MacPorts/X11.app. Then I started gnome-terminal. But I >> got the following error. Would you please let me know how to fix this >> problem? >> >> $ gnome-terminal >> Xlib: ?extension "RANDR" missing on display "/tmp/launch-blAgTJ/:0". > > FYI, you can ignore the RANDR message. > > >> Dynamic session lookup supported but failed: launchd did not provide a >> socket path, verify that org.freedesktop.dbus-session.plist is loaded! > > Sounds like org.freedesktop.dbus-session.plist is not loaded. You should > load it. It is provided by the dbus port, which should have printed > instructions for you upon installation advising you how to load it. I > believe the line it would have printed is: > > > launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist > > > So run that command (not as sudo). Here is what I got after running the command that you mentioned. What's the problem? $sudo port install dbus Password: ---> Computing dependencies for dbus ---> Cleaning dbus $ launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist launchctl: CFURLWriteDataAndPropertiesToResource(/Library/LaunchAgents/org.freedesktop.dbus-session.plist) failed: -10 $ls /Library/LaunchAgents/org.freedesktop.dbus-session.plist /Library/LaunchAgents/org.freedesktop.dbus-session.plist From lists at pbw.id.au Sun Oct 4 23:16:40 2009 From: lists at pbw.id.au (Peter B. West) Date: Mon, 5 Oct 2009 16:16:40 +1000 Subject: /usr/local In-Reply-To: <271C7E31-AB87-46B9-8497-8D847FF796A7@macports.org> References: <271C7E31-AB87-46B9-8497-8D847FF796A7@macports.org> Message-ID: On 30/09/2009, at 3:21 PM, Ryan Schmidt wrote: > On Sep 29, 2009, at 23:59, Peter B. West wrote: > >> Following some recent messages about problems with software in /usr/ >> local. I had a look. I had quite a bit of stuff in there. >> >> hg >> mysql >> tcl/tk >> gfortran >> gcc in libexec >> wireshark > > Note it is only software that is installed in prefix /usr/local > (e.g. /usr/local/bin, /usr/local/lib, etc.) that is a problem. > Software installed in a prefix somewhere under /usr/local (e.g. /usr/ > local/mysql/bin, /usr/local/mysql/lib) is no problem at all. > Thanks for that clarification. > >> I removed the mysql, and installed mysql5-devel and mysql5-server- >> devel from MacPorts. >> >> I removed wireshark from Applications, and cleaned up as best I >> could in /use/local. Now I notice that someone else is reporting >> wireshark problems. I haven't tried to install yet. > > pango 1.26.0 was causing widespread problems. I reverted pango to > 1.24.5 and await resolution from the developers of pango. > Wireshark now installed OK. > >> The tcl/tk and gfortran came with the R installation. I removed R, >> and tried to install again with a manual location override. >> Unfortunately, although R itself goes in appropriate places, the >> tcl/tk and fortran extensions go into /usr/local, and can't be >> persuaded other wise. > > I didn't quite understand: you're installing the R port in MacPorts, > or some other standalone R package? You should be installing it > using MacPorts. "sudo port install R". If that is what you're doing, > then please explain a bit more, maybe show which files go where. > I had installed the stand-alone R package, which put supporting software in /usr/local/. > >> Trying to install R, I ran into a problem with cairo, which I >> recall seeing discussed recently, but can't remember the details. > > The one you filed as #21710? > Yes R now installed OK, after re-installing all of my ports, as in the migration guide. > >> MacFUSE is also in /usr/local, and I don't know what it was >> associated with, so I left it there. > > FYI MacFUSE is also available in MacPorts. "sudo port install > macfuse" -- though it is an older version. I'm not clear on why it > has not been updated to the latest version. There is an open ticket. > > >> I installed 1.8.1 using selfupdate. Is there some simple procedure >> I should be applying, that will let everything build? > > Other than following the Migration procedure if you upgrade to a new > major version of Mac OS X, you should just be able to install ports. > If they don't work, please file tickets so they can be fixed. > Peter From milosh at macports.org Mon Oct 5 03:33:53 2009 From: milosh at macports.org (Emmanuel Hainry) Date: Mon, 5 Oct 2009 12:33:53 +0200 Subject: Issue with mutt-devel after MacPorts update In-Reply-To: <20091004205838.GM471@ninagal.withay.com> References: <4b75340e0910040649u64973c9cm7d6128b59e9ac2ed@mail.gmail.com> <20091004194222.GL471@ninagal.withay.com> <4b75340e0910041255sf29a5a7uecf0e5a5eab96ddd@mail.gmail.com> <20091004205838.GM471@ninagal.withay.com> Message-ID: <20091005103353.GB19814@weetamoe.loria.fr> Citando Bryan Blackburn : > > On Sun, Oct 04, 2009 at 03:55:11PM -0400, Doctor Who said: > > On Sun, Oct 4, 2009 at 3:42 PM, Bryan Blackburn > > wrote: > > > On Sun, Oct 04, 2009 at 09:49:50AM -0400, Doctor Who said: > > >> I had mutt-devel working with no issues on my Snow Leopard > > >> install until I did a complete uninstall and reinstall of > > >> MacPorts to the latest version. ?The issue is specifically with > > >> getting the "headercache" piece working again. > > >> > > >> I install mutt-devel with the following variants: > > >> > > >> sudo port install mutt-devel +headercache +gpgme +imap +ssl > > >> +sidebar > > > > > > If you use 'port variants mutt-devel' you'll note that you need to > > > select one of the database backends as well: > > > > > > ? headercache: Enable header caching (requires gdbm, qdbm, or > > > tokyocabinet) > > > > > > The port should probably error out when headercache is selected > > > but no database is... > > > > > > And for what it's worth, 1.5.20 with headercache and tokyocabinet > > > is working fine here 10.6.1. > > > > > > > Thanks. I had tried before with gdbm and had the same behavior. > > Trying now with tokyocabinet seems to have it working again. Weird. > > Hmm, perhaps there's something wrong with headercache+gdbm; looking at > the Portfile again, it actually looks like +gdbm should get set if you > don't set one of the other databases. > If the headercache has been generated with tokyocabinet, it is quite normal it fails to be read with gdbm. When changing thi format, you should try to delete the header_cache file generated with the previous variant and relaunch. Emmanuel -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From lists at pbw.id.au Mon Oct 5 05:30:05 2009 From: lists at pbw.id.au (Peter B. West) Date: Mon, 5 Oct 2009 22:30:05 +1000 Subject: .bashrc .profile .bash_profile In-Reply-To: References: Message-ID: <22A970F0-343F-4F6F-BAF5-2204C1D34281@pbw.id.au> Many years ago (when bash2 was being introduced) I tried to work out a set of startup files that would work in all the environments I might use. I didn't get there, but found some workable compromises, which I have used as a basis since. The main difference, for me, was between interactive and non- interactive shells, so I tried to keep these apart. Get rid of .bash_profile and .bash_login. Better still, make .bash_profile a link to .profile. .profile has some leading comments that try to describe the conditions applying (still, I think) in the various circumstances in which the shell gets started. .interactive has the interactive stuff. .bashrc tends to get sourced always, one way or another. pathFuncs has some very useful path manipulation stuff. dirFuncs provides some extended aliases for pushd and popd. These files have been following me around for a while, so there if probably a lot of cruft in there. Peter -------------- next part -------------- A non-text attachment was scrubbed... Name: .profile Type: application/octet-stream Size: 3089 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: .bashrc Type: application/octet-stream Size: 3593 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: .interactive Type: application/octet-stream Size: 1168 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: pathFuncs Type: application/octet-stream Size: 4966 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: dirFuncs Type: application/octet-stream Size: 907 bytes Desc: not available URL: From face at CentosPrime.COM Mon Oct 5 05:37:06 2009 From: face at CentosPrime.COM (Chris Janton) Date: Mon, 05 Oct 2009 05:37:06 -0700 Subject: php5 and sqlite In-Reply-To: References: <6870E81D-85FE-48B7-989D-3078F142176C@clarksonline.net> Message-ID: On 2009-10-04 , at 17:28 , Ryan Schmidt wrote: > $ php -r 'phpinfo();' | grep sqlite As an aside the command php -i does pretty much the same thing as php -r 'phpinfo();' 8) From ryandesign at macports.org Mon Oct 5 05:38:40 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 5 Oct 2009 07:38:40 -0500 Subject: php5 and sqlite In-Reply-To: References: <6870E81D-85FE-48B7-989D-3078F142176C@clarksonline.net> Message-ID: On Oct 5, 2009, at 07:37, Chris Janton wrote: > On 2009-10-04 , at 17:28 , Ryan Schmidt wrote: > >> $ php -r 'phpinfo();' | grep sqlite > > As an aside the command > > php -i > > does pretty much the same thing as php -r 'phpinfo();' Thanks, that's much easier. Now if I can only remember to use that! From face at CentosPrime.COM Mon Oct 5 06:02:48 2009 From: face at CentosPrime.COM (Chris Janton) Date: Mon, 05 Oct 2009 06:02:48 -0700 Subject: .bashrc .profile .bash_profile In-Reply-To: <6A1CD4B1-DE13-4E41-9E08-A1F392E39183@newgeo.com> References: <6FE8CA9B-FCF8-41ED-8D33-D8CC3A2B54DD@kf8nh.com> <2A566FD9-C6CB-4801-8F4B-1D9E04ED0EB0@newgeo.com> <6A1CD4B1-DE13-4E41-9E08-A1F392E39183@newgeo.com> Message-ID: <04094F64-8952-4A87-A49C-D220A1FC88DA@centosprime.com> On 2009-10-04 , at 18:17 , Scott Haneda wrote: > I usually set up a line like that on all my remote machines, so when > I ssh in, I am greeted with something that tells me what machine I > am on. Most have the same username, and I try not to add too much > data to the PS1 setting, as long paths can do strange visual things > for me with line wrap. > > This has never caused me any issues. However, I tried to use > Interarchy, to ssh/sftp into a remote host, something I do all the > time, and this time around, I got a login failure. As soon as I > removed my echo statements that were printing out which files were > being sourced, I was allowed login again. > > Do you think this is a client issue, with Interarchy, or do I need > to perhaps echo those statements out in a different way, in some way > that returns data, rather than prints out a string? "chatter" from .profile and friends is not a good thing. As you can see some applications fail (sometimes in the most confusing way) when there is unexpected output on stdout (or stderr for that matter). Keep your profiles quiet and your applications will be happy. Things really don't change - this has been a problem/feature since the 1980s 8) From raimue at macports.org Mon Oct 5 11:39:44 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Mon, 05 Oct 2009 20:39:44 +0200 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: <366c6f340910042036l6f0c0329y80bb43b9742d5f77@mail.gmail.com> References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> <26F71423-28CF-4204-BE95-5E5F8658AA10@kf8nh.com> <366c6f340910041308w79d0c80ds4f7a443336a93ee2@mail.gmail.com> <29FBDB5B-5F23-4F56-A439-1A8F1DEBF38E@kf8nh.com> <366c6f340910041354y4b499a1rab34385329effd1a@mail.gmail.com> <9DA61651-B94F-4AD0-8B79-CB261657270C@macports.org> <366c6f340910041812w60754e1cu3b184d7e35916a36@mail.gmail.com> <7329EB1B-F846-4993-8D94-8BA35C061BD0@macports.org> <366c6f340910042036l6f0c0329y80bb43b9742d5f77@mail.gmail.com> Message-ID: <4ACA3D70.3040401@macports.org> Peng Yu wrote: > On Sun, Oct 4, 2009 at 10:05 PM, Ryan Schmidt wrote: >> launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist >> >> So run that command (not as sudo). > > Here is what I got after running the command that you mentioned. > What's the problem? > > $sudo port install dbus > Password: > ---> Computing dependencies for dbus > ---> Cleaning dbus > $ launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist > launchctl: CFURLWriteDataAndPropertiesToResource(/Library/LaunchAgents/org.freedesktop.dbus-session.plist) > failed: -10 > $ls /Library/LaunchAgents/org.freedesktop.dbus-session.plist > /Library/LaunchAgents/org.freedesktop.dbus-session.plist The -w option requires write access to that file what you usually do not have as a normal user. It is used to remove the Disabled key from the file. Alternatively you can force the load like this: $ launchctl load -F /Library/LaunchAgents/org.freedesktop.dbus-session.plist Rainer From pengyu.ut at gmail.com Mon Oct 5 12:07:11 2009 From: pengyu.ut at gmail.com (Peng Yu) Date: Mon, 5 Oct 2009 14:07:11 -0500 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: <4ACA3D70.3040401@macports.org> References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> <366c6f340910041308w79d0c80ds4f7a443336a93ee2@mail.gmail.com> <29FBDB5B-5F23-4F56-A439-1A8F1DEBF38E@kf8nh.com> <366c6f340910041354y4b499a1rab34385329effd1a@mail.gmail.com> <9DA61651-B94F-4AD0-8B79-CB261657270C@macports.org> <366c6f340910041812w60754e1cu3b184d7e35916a36@mail.gmail.com> <7329EB1B-F846-4993-8D94-8BA35C061BD0@macports.org> <366c6f340910042036l6f0c0329y80bb43b9742d5f77@mail.gmail.com> <4ACA3D70.3040401@macports.org> Message-ID: <366c6f340910051207s6e24b5adpe129abcfb88f1fa5@mail.gmail.com> On Mon, Oct 5, 2009 at 1:39 PM, Rainer M?ller wrote: > Peng Yu wrote: >> On Sun, Oct 4, 2009 at 10:05 PM, Ryan Schmidt wrote: >>> launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist >>> >>> So run that command (not as sudo). >> >> Here is what I got after running the command that you mentioned. >> What's the problem? >> >> $sudo port install dbus >> Password: >> ---> ?Computing dependencies for dbus >> ---> ?Cleaning dbus >> $ launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist >> launchctl: CFURLWriteDataAndPropertiesToResource(/Library/LaunchAgents/org.freedesktop.dbus-session.plist) >> failed: -10 >> $ls /Library/LaunchAgents/org.freedesktop.dbus-session.plist >> /Library/LaunchAgents/org.freedesktop.dbus-session.plist > > The -w option requires write access to that file what you usually do not > have as a normal user. It is used to remove the Disabled key from the file. > > Alternatively you can force the load like this: > $ launchctl load -F /Library/LaunchAgents/org.freedesktop.dbus-session.plist Here is what I get and I still get errors when I run gnome-terminal. $ launchctl load -F /Library/LaunchAgents/org.freedesktop.dbus-session.plist org.freedesktop.dbus-session: Already loaded $ gnome-terminal Xlib: extension "RANDR" missing on display "/tmp/launch-blAgTJ/:0". ** ERROR:terminal-app.c:1433:terminal_app_init: assertion failed: (app->system_font_desc != NULL) Abort trap From dweber at macports.org Mon Oct 5 12:59:05 2009 From: dweber at macports.org (Darren Weber) Date: Mon, 5 Oct 2009 12:59:05 -0700 Subject: vtk-devel updated to 5.4.2 Message-ID: The port for vtk-devel has been updated to ver 5.4.2 (it may take a few hours to propagate this svn update into the rsync distribution). This update builds and installs using 'sudo port install vtk-devel +huge'. (This updated version was only tested on Leopard.) The port now uses PostgreSQL 8.4 instead of 8.3 (the 8.3 variant is still available for those who require that - get back to me with any problems doing an upgrade or new install that requires the pgsql83 variant). Take care, Darren PS, The Portfile can be viewed here: http://trac.macports.org/browser/trunk/dports/graphics/vtk-devel/Portfile -------------- next part -------------- An HTML attachment was scrubbed... URL: From rfritz333 at gmail.com Mon Oct 5 13:21:33 2009 From: rfritz333 at gmail.com (Randolph Fritz) Date: Mon, 5 Oct 2009 20:21:33 +0000 (UTC) Subject: Metamail? Message-ID: Do any of the ports contain metamail? I want it for use with slrn. -- Randolph Fritz design machine group, architecture department, university of washington rfritz at u.washington.edu -or- rfritz333 at gmail.com From mbrut at stanford.edu Mon Oct 5 15:23:47 2009 From: mbrut at stanford.edu (Marie Noella Brut) Date: Mon, 5 Oct 2009 15:23:47 -0700 (PDT) Subject: error while installing molden Message-ID: <129168331.762341254781427191.JavaMail.root@zm08.stanford.edu> I am trying to install molden, but after a few minutes, I get the following message: ---> Verifying checksum(s) for molden Error: Checksum (md5) mismatch for molden4.8.tar.gz Error: Checksum (sha1) mismatch for molden4.8.tar.gz Error: Target org.macports.checksum returned: Unable to verify file checksums Error: Status 1 encountered during processing. I have found a similar error in your archives and tried : port sync port install molden But I still have the same error. What can I do? Many thanks, Marie From talklists at newgeo.com Mon Oct 5 15:52:41 2009 From: talklists at newgeo.com (Scott Haneda) Date: Mon, 5 Oct 2009 15:52:41 -0700 Subject: error while installing molden In-Reply-To: <129168331.762341254781427191.JavaMail.root@zm08.stanford.edu> References: <129168331.762341254781427191.JavaMail.root@zm08.stanford.edu> Message-ID: <3A9B855B-EC3A-4BEB-B85B-5479260B9602@newgeo.com> It sounds to me like the port file was made targeting molden4.8.tar.gz Perhaps the developer made a small change to 4.8 but did not increment the version. Since the distro changed, you are getting a mismatch on the hash of the download. It's also possible there is an error in the reference to the file. I usually see files named as filename-versionnum.minor.ext. In this case the dash or maybe a dot are not there. So it could also be the file is simply not there, but the server returns something that macports is downloading, also getting a hash mismatch. Try running with the -d flag to your install. That will give you a lot more data to be able to see what is going on. You can also enter "port edit molden" and find the download source and version. Try to download the version manually and check the hash in the terminal. If I get a chance I'll see if I can look into it myself. -- Scott Iphone says hello. On Oct 5, 2009, at 3:23 PM, Marie Noella Brut wrote: > I am trying to install molden, but after a few minutes, I get the > following message: > > ---> Verifying checksum(s) for molden > Error: Checksum (md5) mismatch for molden4.8.tar.gz > Error: Checksum (sha1) mismatch for molden4.8.tar.gz > Error: Target org.macports.checksum returned: Unable to verify file > checksums > Error: Status 1 encountered during processing. > > I have found a similar error in your archives and tried : > > port sync > port install molden > > But I still have the same error. > > What can I do? > > Many thanks, From raimue at macports.org Mon Oct 5 16:30:14 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Tue, 06 Oct 2009 01:30:14 +0200 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: <366c6f340910051207s6e24b5adpe129abcfb88f1fa5@mail.gmail.com> References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> <366c6f340910041308w79d0c80ds4f7a443336a93ee2@mail.gmail.com> <29FBDB5B-5F23-4F56-A439-1A8F1DEBF38E@kf8nh.com> <366c6f340910041354y4b499a1rab34385329effd1a@mail.gmail.com> <9DA61651-B94F-4AD0-8B79-CB261657270C@macports.org> <366c6f340910041812w60754e1cu3b184d7e35916a36@mail.gmail.com> <7329EB1B-F846-4993-8D94-8BA35C061BD0@macports.org> <366c6f340910042036l6f0c0329y80bb43b9742d5f77@mail.gmail.com> <4ACA3D70.3040401@macports.org> <366c6f340910051207s6e24b5adpe129abcfb88f1fa5@mail.gmail.com> Message-ID: <4ACA8186.5010202@macports.org> On 2009-10-05 21:07 , Peng Yu wrote: > Here is what I get and I still get errors when I run gnome-terminal. > > $ launchctl load -F /Library/LaunchAgents/org.freedesktop.dbus-session.plist > org.freedesktop.dbus-session: Already loaded > $ gnome-terminal > Xlib: extension "RANDR" missing on display "/tmp/launch-blAgTJ/:0". > ** > ERROR:terminal-app.c:1433:terminal_app_init: assertion failed: > (app->system_font_desc != NULL) > Abort trap Found an upstream bug report of this problem: Rainer From raimue at macports.org Mon Oct 5 16:38:53 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Tue, 06 Oct 2009 01:38:53 +0200 Subject: OpenSceneGraph debug libraries? In-Reply-To: References: Message-ID: <4ACA838D.8060703@macports.org> On 2009-10-05 03:33 , Randolph Fritz wrote: > Is there any way I can get MacPorts to build debug versions of the OSG > libraries? Or does it already do so and me not knowing? No, MacPorts does use -O2 in CFLAGS by default. Rainer From rfritz333 at gmail.com Mon Oct 5 16:43:12 2009 From: rfritz333 at gmail.com (Randolph Fritz) Date: Mon, 5 Oct 2009 23:43:12 +0000 (UTC) Subject: OpenSceneGraph debug libraries? References: <4ACA838D.8060703@macports.org> Message-ID: On 2009-10-05, Rainer M?ller wrote: > On 2009-10-05 03:33 , Randolph Fritz wrote: >> Is there any way I can get MacPorts to build debug versions of the OSG >> libraries? Or does it already do so and me not knowing? > > No, MacPorts does use -O2 in CFLAGS by default. > OK, thanks. -- Randolph Fritz design machine group, architecture department, university of washington rfritz at u.washington.edu -or- rfritz333 at gmail.com From ryandesign at macports.org Mon Oct 5 17:11:44 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 5 Oct 2009 19:11:44 -0500 Subject: Metamail? In-Reply-To: References: Message-ID: <311E2CC1-4110-4F84-9C46-EAC22A07181E@macports.org> On Oct 5, 2009, at 15:21, Randolph Fritz wrote: > Do any of the ports contain metamail? I want it for use with slrn. I don't see one, so feel free to submit one, or file a port request ticket. From ryandesign at macports.org Mon Oct 5 17:19:46 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 5 Oct 2009 19:19:46 -0500 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: <4ACA3D70.3040401@macports.org> References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> <26F71423-28CF-4204-BE95-5E5F8658AA10@kf8nh.com> <366c6f340910041308w79d0c80ds4f7a443336a93ee2@mail.gmail.com> <29FBDB5B-5F23-4F56-A439-1A8F1DEBF38E@kf8nh.com> <366c6f340910041354y4b499a1rab34385329effd1a@mail.gmail.com> <9DA61651-B94F-4AD0-8B79-CB261657270C@macports.org> <366c6f340910041812w60754e1cu3b184d7e35916a36@mail.gmail.com> <7329EB1B-F846-4993-8D94-8BA35C061BD0@macports.org> <366c6f340910042036l6f0c0329y80bb43b9742d5f77@mail.gmail.com> <4ACA3D70.3040401@macports.org> Message-ID: <0317A280-C30D-4201-8542-3CF97D32B062@macports.org> On Oct 5, 2009, at 13:39, Rainer M?ller wrote: > Peng Yu wrote: >> On Sun, Oct 4, 2009 at 10:05 PM, Ryan Schmidt > > wrote: >>> launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus- >>> session.plist >>> >>> So run that command (not as sudo). >> >> Here is what I got after running the command that you mentioned. >> What's the problem? >> >> $sudo port install dbus >> Password: >> ---> Computing dependencies for dbus >> ---> Cleaning dbus >> $ launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus- >> session.plist >> launchctl: CFURLWriteDataAndPropertiesToResource(/Library/ >> LaunchAgents/org.freedesktop.dbus-session.plist) >> failed: -10 >> $ls /Library/LaunchAgents/org.freedesktop.dbus-session.plist >> /Library/LaunchAgents/org.freedesktop.dbus-session.plist > > The -w option requires write access to that file what you usually do > not > have as a normal user. It is used to remove the Disabled key from > the file. So the instructions the port prints out are wrong? Is there a way to correct them? It sounds like you're saying you need "sudo" to have access to write the changes to the plist, but I remember from prior discussions that this would cause the launchagent to be running as root, when in fact we want the launchagent running as the current user. > Alternatively you can force the load like this: > $ launchctl load -F /Library/LaunchAgents/org.freedesktop.dbus- > session.plist From ryandesign at macports.org Mon Oct 5 17:24:01 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 5 Oct 2009 19:24:01 -0500 Subject: error while installing molden In-Reply-To: <129168331.762341254781427191.JavaMail.root@zm08.stanford.edu> References: <129168331.762341254781427191.JavaMail.root@zm08.stanford.edu> Message-ID: <9E3A0B5C-A809-4C65-A480-B3AD2B4AC082@macports.org> On Oct 5, 2009, at 17:23, Marie Noella Brut wrote: > I am trying to install molden, but after a few minutes, I get the > following message: > > ---> Verifying checksum(s) for molden > Error: Checksum (md5) mismatch for molden4.8.tar.gz > Error: Checksum (sha1) mismatch for molden4.8.tar.gz > Error: Target org.macports.checksum returned: Unable to verify file > checksums > Error: Status 1 encountered during processing. > > I have found a similar error in your archives and tried : > > port sync > port install molden > > But I still have the same error. > > What can I do? I have updated the molden port to the latest version. Please wait 30 minutes, then "sudo port sync" and "sudo port install molden". The developers of molden are in the habit of changing their software without changing the version number. This occurred 13 times (that we noticed) during molden 4.6 and is continuing with 4.8 now. These "stealth updates" inevitably results in a checksum mismatch. At least this lets us know the port needs to be updated, and whenever it occurs, you can report it here or in a ticket and we can update it. "port livecheck molden" will also tell you whether the distfile has been updated. From rfritz333 at gmail.com Mon Oct 5 17:46:00 2009 From: rfritz333 at gmail.com (Randolph Fritz) Date: Tue, 6 Oct 2009 00:46:00 +0000 (UTC) Subject: Metamail? References: <311E2CC1-4110-4F84-9C46-EAC22A07181E@macports.org> Message-ID: On 2009-10-06, Ryan Schmidt wrote: > On Oct 5, 2009, at 15:21, Randolph Fritz wrote: > >> Do any of the ports contain metamail? I want it for use with slrn. > > I don't see one, so feel free to submit one, or file a port request > ticket. > > Thanks! -- Randolph Fritz design machine group, architecture department, university of washington rfritz at u.washington.edu -or- rfritz333 at gmail.com From jmr at macports.org Mon Oct 5 19:26:02 2009 From: jmr at macports.org (Joshua Root) Date: Tue, 06 Oct 2009 13:26:02 +1100 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: <0317A280-C30D-4201-8542-3CF97D32B062@macports.org> References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> <26F71423-28CF-4204-BE95-5E5F8658AA10@kf8nh.com> <366c6f340910041308w79d0c80ds4f7a443336a93ee2@mail.gmail.com> <29FBDB5B-5F23-4F56-A439-1A8F1DEBF38E@kf8nh.com> <366c6f340910041354y4b499a1rab34385329effd1a@mail.gmail.com> <9DA61651-B94F-4AD0-8B79-CB261657270C@macports.org> <366c6f340910041812w60754e1cu3b184d7e35916a36@mail.gmail.com> <7329EB1B-F846-4993-8D94-8BA35C061BD0@macports.org> <366c6f340910042036l6f0c0329y80bb43b9742d5f77@mail.gmail.com> <4ACA3D70.3040401@macports.org> <0317A280-C30D-4201-8542-3CF97D32B062@macports.org> Message-ID: <4ACAAABA.3070102@macports.org> On 2009-10-6 11:19, Ryan Schmidt wrote: > > On Oct 5, 2009, at 13:39, Rainer M?ller wrote: > >> Peng Yu wrote: >>> $ launchctl load -w >>> /Library/LaunchAgents/org.freedesktop.dbus-session.plist >>> launchctl: >>> CFURLWriteDataAndPropertiesToResource(/Library/LaunchAgents/org.freedesktop.dbus-session.plist) >>> >>> failed: -10 >>> $ls /Library/LaunchAgents/org.freedesktop.dbus-session.plist >>> /Library/LaunchAgents/org.freedesktop.dbus-session.plist >> >> The -w option requires write access to that file what you usually do not >> have as a normal user. It is used to remove the Disabled key from the >> file. > > So the instructions the port prints out are wrong? Is there a way to > correct them? It sounds like you're saying you need "sudo" to have > access to write the changes to the plist, but I remember from prior > discussions that this would cause the launchagent to be running as root, > when in fact we want the launchagent running as the current user. The bottom line is that the startupitem code needs some love. At present it really can't handle anything beyond launchdaemons that will be started by root. - Josh From luomo1138 at yahoo.com Mon Oct 5 20:10:27 2009 From: luomo1138 at yahoo.com (Dexter Douglas) Date: Mon, 5 Oct 2009 20:10:27 -0700 (PDT) Subject: realpath failed -- error uninstalling ports In-Reply-To: Message-ID: <422566.87010.qm@web65614.mail.ac4.yahoo.com> Hello, I was able to reinstall doxygen. Thanks. --- On Sat, 10/3/09, Chris Scharver wrote: > From: Chris Scharver > Subject: Re: realpath failed -- error uninstalling ports > To: "Dexter Douglas" > Cc: "Ryan Schmidt" , "macports-users at lists.macosforge.org" > Date: Saturday, October 3, 2009, 7:23 AM > > On Oct 2, 2009, at 7:31 PM, Dexter Douglas > wrote: > > > 1) During the upgrading, doxygen failed to > compile.? I ended up uninstalling and trying to > reinstall.? I was not able to reinstall doxygen. > > Your build error results from a known incompatibility when > the libwww port is installed. You will need to deactivate > libwww, build and install doxygen, then activate libwww. See > this ticket for more information: > > http://trac.macports.org/ticket/18748 > > Chris > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From raimue at macports.org Tue Oct 6 01:15:59 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Tue, 06 Oct 2009 10:15:59 +0200 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: <4ACAAABA.3070102@macports.org> References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> <26F71423-28CF-4204-BE95-5E5F8658AA10@kf8nh.com> <366c6f340910041308w79d0c80ds4f7a443336a93ee2@mail.gmail.com> <29FBDB5B-5F23-4F56-A439-1A8F1DEBF38E@kf8nh.com> <366c6f340910041354y4b499a1rab34385329effd1a@mail.gmail.com> <9DA61651-B94F-4AD0-8B79-CB261657270C@macports.org> <366c6f340910041812w60754e1cu3b184d7e35916a36@mail.gmail.com> <7329EB1B-F846-4993-8D94-8BA35C061BD0@macports.org> <366c6f340910042036l6f0c0329y80bb43b9742d5f77@mail.gmail.com> <4ACA3D70.3040401@macports.org> <0317A280-C30D-4201-8542-3CF97D32B062@macports.org> <4ACAAABA.3070102@macports.org> Message-ID: <4ACAFCBF.9080007@macports.org> On 2009-10-06 04:26 , Joshua Root wrote: > On 2009-10-6 11:19, Ryan Schmidt wrote: >> So the instructions the port prints out are wrong? Is there a way to >> correct them? It sounds like you're saying you need "sudo" to have >> access to write the changes to the plist, but I remember from prior >> discussions that this would cause the launchagent to be running as root, >> when in fact we want the launchagent running as the current user. You are right, LaunchAgents/org.freedesktop.dbus-session.plist is meant to be run by the current user, not root. And yes, the instructions look kind of wrong. launchctl load -w without sudo does not work because it requires write access to the file. But if -w is not used, the Disabled key will not be removed and it cannot be loaded automatically at system startup time... > The bottom line is that the startupitem code needs some love. At present > it really can't handle anything beyond launchdaemons that will be > started by root. dbus does not use the startupitem.* code for org.freedesktop.dbus-sesstion.plist as it installs multiple plist files which startupitem.* cannot handle. Rainer From pengyu.ut at gmail.com Tue Oct 6 07:42:52 2009 From: pengyu.ut at gmail.com (Peng Yu) Date: Tue, 6 Oct 2009 09:42:52 -0500 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: <4ACAFCBF.9080007@macports.org> References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> <9DA61651-B94F-4AD0-8B79-CB261657270C@macports.org> <366c6f340910041812w60754e1cu3b184d7e35916a36@mail.gmail.com> <7329EB1B-F846-4993-8D94-8BA35C061BD0@macports.org> <366c6f340910042036l6f0c0329y80bb43b9742d5f77@mail.gmail.com> <4ACA3D70.3040401@macports.org> <0317A280-C30D-4201-8542-3CF97D32B062@macports.org> <4ACAAABA.3070102@macports.org> <4ACAFCBF.9080007@macports.org> Message-ID: <366c6f340910060742m22b287d7xbfc5177720a5651b@mail.gmail.com> On Tue, Oct 6, 2009 at 3:15 AM, Rainer M?ller wrote: > On 2009-10-06 04:26 , Joshua Root wrote: >> On 2009-10-6 11:19, Ryan Schmidt wrote: >>> So the instructions the port prints out are wrong? Is there a way to >>> correct them? It sounds like you're saying you need "sudo" to have >>> access to write the changes to the plist, but I remember from prior >>> discussions that this would cause the launchagent to be running as root, >>> when in fact we want the launchagent running as the current user. > > You are right, LaunchAgents/org.freedesktop.dbus-session.plist is meant > to be run by the current user, not root. > > And yes, the instructions look kind of wrong. launchctl load -w without > sudo does not work because it requires write access to the file. But if > -w is not used, the Disabled key will not be removed and it cannot be > loaded automatically at system startup time... > >> The bottom line is that the startupitem code needs some love. At present >> it really can't handle anything beyond launchdaemons that will be >> started by root. > > dbus does not use the startupitem.* code for > org.freedesktop.dbus-sesstion.plist as it installs multiple plist files > which startupitem.* cannot handle. I don't understand what would be the solution to my problem. Could somebody let me know the detailed steps what I should do? Regards, Peng From mvfranz at gmail.com Tue Oct 6 17:55:11 2009 From: mvfranz at gmail.com (Michael Franz) Date: Tue, 6 Oct 2009 20:55:11 -0400 Subject: Ticket #21500 - IcedTea 1.11 Message-ID: Hi, I think I have figured out the installation script for IcedTea. The only issue I have and would like input on is how to handle the different compiler for Snow Leopard. The Snow Leopard default 4.2 compiler will not compile the OpenJDK (thus IcedTea). The alternate gcc 4.0 will work fine. Do I need to have a variant for each platform or is it enough to force gcc 4.0 in the portfile? As a note, the current tip of the openjdk will build with 4.2 on snow leopard, but there are some bugs in 4.2 that cause the jdk to crash. Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Tue Oct 6 18:16:11 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 6 Oct 2009 20:16:11 -0500 Subject: Ticket #21500 - IcedTea 1.11 In-Reply-To: References: Message-ID: <9227BA4F-AC99-40EB-8058-89E3A7D83B6D@macports.org> On Oct 6, 2009, at 19:55, Michael Franz wrote: > I think I have figured out the installation script for IcedTea. The > only issue I have and would like input on is how to handle the > different compiler for Snow Leopard. The Snow Leopard default 4.2 > compiler will not compile the OpenJDK (thus IcedTea). The alternate > gcc 4.0 will work fine. Do I need to have a variant for each > platform or is it enough to force gcc 4.0 in the portfile? gcc-4.0 is the default on Tiger and Leopard, and is available on Snow Leopard, so you could simply add this line to the portfile: configure.compiler gcc-4.0 You should probably preface that with a comment explaining why: # IcedTea 1.11 doesn't compile with gcc-4.2 configure.compiler gcc-4.0 (or make the comment specific to OpenJDK and mention its version, maybe; I'm not totally clear on the relationship between IcedTea and OpenJDK) > As a note, the current tip of the openjdk will build with 4.2 on > snow leopard, but there are some bugs in 4.2 that cause the jdk to > crash. Sounds like they're making progress, anyway. :) From allbery at kf8nh.com Tue Oct 6 18:22:19 2009 From: allbery at kf8nh.com (Brandon Allbery) Date: Tue, 6 Oct 2009 21:22:19 -0400 Subject: .bashrc .profile .bash_profile In-Reply-To: <6A1CD4B1-DE13-4E41-9E08-A1F392E39183@newgeo.com> References: <6FE8CA9B-FCF8-41ED-8D33-D8CC3A2B54DD@kf8nh.com> <2A566FD9-C6CB-4801-8F4B-1D9E04ED0EB0@newgeo.com> <6A1CD4B1-DE13-4E41-9E08-A1F392E39183@newgeo.com> Message-ID: On Oct 4, 2009, at 21:17 , Scott Haneda wrote: >>> If I do not have my aliases and such in .bashrc, my `sudo -s` env >>> is pretty stark, and hard to work in. I do not need all my >>> settings to come over when in this `sudo -s` mode, but I certainly >>> would like the macports paths and other things to make it. >> >> Aliases aren't inherited; they belong in .bashrc. (Shell functions >> can be inherited, but now we're getting into distinctions you >> probably don't want to know, much less care, about.) > > I get curious, :) you sent another email with some good links and > references in them, I will be going thought them. My experience > shows they *are* inherited.. Not necessarily unless you arranged for .bashrc to not load in those cases (it will be loaded by default). > The core idea, was to alias `rm` to `rm -i`, and how doing so would > break many other scripts and apps. I walked away thinking, whatever > the case may be, that the developer of the app or script should not > use `rm` but should fish out the real path toe `rm` and use the full > path. Actually, any serious script should reset the PATH to a known set of directories (and also reset IFS, CDPATH, and a number of other "interesting" environment variables). > So, can I use it and not export it? It seems in all examples I can > find, CLICOLOR_FORCE needs to be exported, but maybe there is a > "set" way to do it, 'SET CLICOLOR_FORCE' in which case it would not > be exported, but just available to me for my session? Is there some reason you insist on CLICOLOR_FORCE instead of CLICOLOR? This *will* hurt you. There's a way to set it without exporting it, yes --- but if it's not exported, ls won't see it. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery at kf8nh.com system administrator [openafs,heimdal,too many hats] allbery at ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part URL: From talklists at newgeo.com Tue Oct 6 21:17:25 2009 From: talklists at newgeo.com (Scott Haneda) Date: Tue, 6 Oct 2009 21:17:25 -0700 Subject: .bashrc .profile .bash_profile In-Reply-To: References: <6FE8CA9B-FCF8-41ED-8D33-D8CC3A2B54DD@kf8nh.com> <2A566FD9-C6CB-4801-8F4B-1D9E04ED0EB0@newgeo.com> <6A1CD4B1-DE13-4E41-9E08-A1F392E39183@newgeo.com> Message-ID: <524F7AC9-D665-4A29-97AD-D1DB56F53372@newgeo.com> On Oct 6, 2009, at 6:22 PM, Brandon Allbery wrote: >> So, can I use it and not export it? It seems in all examples I can >> find, CLICOLOR_FORCE needs to be exported, but maybe there is a >> "set" way to do it, 'SET CLICOLOR_FORCE' in which case it would not >> be exported, but just available to me for my session? > > Is there some reason you insist on CLICOLOR_FORCE instead of > CLICOLOR? This *will* hurt you. > > There's a way to set it without exporting it, yes --- but if it's > not exported, ls won't see it. Just could never get it to work... # Color output export CLICOLOR=1 #export CLICOLOR_FORCE=1 export LSCOLORS=dxfxcxdxbxegedabagacad If I type ls -la I get coloring, if I use an alias based on the same thing, I get no coloring. Ah ha, I was aliasing ls -la | grep - v .DS_Store, which kills the color. Suggestions on how to mask out those files, and still maintain my colors? -- Scott * If you contact me off list replace talklists@ with scott@ * From derek at chocolate-fish.com Tue Oct 6 21:41:42 2009 From: derek at chocolate-fish.com (Derek Harland) Date: Wed, 7 Oct 2009 17:41:42 +1300 Subject: .bashrc .profile .bash_profile In-Reply-To: <524F7AC9-D665-4A29-97AD-D1DB56F53372@newgeo.com> References: <6FE8CA9B-FCF8-41ED-8D33-D8CC3A2B54DD@kf8nh.com> <2A566FD9-C6CB-4801-8F4B-1D9E04ED0EB0@newgeo.com> <6A1CD4B1-DE13-4E41-9E08-A1F392E39183@newgeo.com> <524F7AC9-D665-4A29-97AD-D1DB56F53372@newgeo.com> Message-ID: Hi Scott If stdout is not a terminal then "ls" disables color information by default. So if you want to pipe it to anything like grep then you *must* have CLICOLOR_FORCE in the environment. But as Brandon points out, that can bite you in general ... perhaps you want to define an alias with a different name to ls that does want you want. For example, here's what my bashrc defines function ll () { command env CLICOLOR_FORCE=X ls -lAFG "$@" | less - R; } Perhaps you want something like function myls () { command env CLICOLOR_FORCE=X ls -la "$@" | grep - v .DS_Store; } derek On 7/10/2009, at 5:17 PM, Scott Haneda wrote: > On Oct 6, 2009, at 6:22 PM, Brandon Allbery wrote: > >>> So, can I use it and not export it? It seems in all examples I >>> can find, CLICOLOR_FORCE needs to be exported, but maybe there is >>> a "set" way to do it, 'SET CLICOLOR_FORCE' in which case it would >>> not be exported, but just available to me for my session? >> >> Is there some reason you insist on CLICOLOR_FORCE instead of >> CLICOLOR? This *will* hurt you. >> >> There's a way to set it without exporting it, yes --- but if it's >> not exported, ls won't see it. > > > Just could never get it to work... > # Color output > export CLICOLOR=1 > #export CLICOLOR_FORCE=1 > export LSCOLORS=dxfxcxdxbxegedabagacad > > If I type ls -la I get coloring, if I use an alias based on the same > thing, I get no coloring. Ah ha, I was aliasing ls -la | grep - > v .DS_Store, which kills the color. > > Suggestions on how to mask out those files, and still maintain my > colors? > -- > Scott * If you contact me off list replace talklists@ with scott@ * > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From dlidstrom at gmail.com Wed Oct 7 04:21:13 2009 From: dlidstrom at gmail.com (=?ISO-8859-1?Q?Daniel_Lidstr=F6m?=) Date: Wed, 7 Oct 2009 13:21:13 +0200 Subject: Problem installing UnitTest++ Message-ID: <30879999-AADC-4C6F-A47D-ED50332983DB@gmail.com> Hi, I stumbled upon a problem when trying to install UnitTest++: daniel-lidstroms-imac-g5:/Users/daniel/programming/othello> sudo port install unittest-cpp ---> Computing dependencies for unittest-cpp ---> Fetching unittest-cpp ---> Verifying checksum(s) for unittest-cpp ---> Extracting unittest-cpp ---> Configuring unittest-cpp ---> Building unittest-cpp Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_devel_unittest-cpp/work/UnitTest++" && / usr/bin/make -j1 all " returned error 2 Command output: src/MemoryOutStream.cpp src/DeferredTestReporter.cpp src/DeferredTestResult.cpp src/XmlTestReporter.cpp src/CurrentTest.cpp src/Posix/SignalTranslator.cpp src/Posix/TimeHelpers.cpp Creating libUnitTest++.a library... src/tests/Main.cpp src/tests/TestAssertHandler.cpp src/tests/TestChecks.cpp src/tests/TestUnitTest++.cpp src/tests/TestTest.cpp src/tests/TestTestResults.cpp src/tests/TestTestRunner.cpp src/tests/TestCheckMacros.cpp src/tests/TestTestList.cpp src/tests/TestTestMacros.cpp src/tests/TestTimeConstraint.cpp src/tests/TestTimeConstraintMacro.cpp src/tests/TestMemoryOutStream.cpp src/tests/TestDeferredTestReporter.cpp src/tests/TestXmlTestReporter.cpp src/tests/TestCurrentTest.cpp Linking TestUnitTest++... Running unit tests... :107: error: Failure in test: Expected 2 but was 0 FAILURE: 1 out of 174 tests failed (1 failures). Test time: 0.11 seconds. make: *** [TestUnitTest++] Error 1 Error: Status 1 encountered during processing. daniel-lidstroms-imac-g5:/Users/daniel/programming/othello> find /opt - name libUnitTest++.a /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_devel_unittest-cpp/work/UnitTest++/ libUnitTest++.a Can I just copy libUnitTest++.a into /op/local/lib in the meantime? System Version: Mac OS X 10.5.8 (9L31a) Model Name: iMac G5 Regards, Daniel Lidstr?m Stockholm, Sweden -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeff.pitman at gmail.com Wed Oct 7 05:23:23 2009 From: jeff.pitman at gmail.com (Jeff Pitman) Date: Wed, 7 Oct 2009 20:23:23 +0800 Subject: Bus error for dbus-daemon --nofork --session Message-ID: <6b9c17630910070523x7e5d6fd4l51f4ab315b37d8c7@mail.gmail.com> Hi! After a major upgrade, gimp broke for me. All my ports should be up-to-date. I've traced down to several upgrade problems and have been working through them one-by-one. This one has me stumped. For some reason, "dbus-daemon --nofork --session" is broken. sudo or as user, doesn't matter. It returns Bus error everytime... $ dbus-daemon --nofork --session Bus error I've messed with session.conf, so that it skips session-local.conf and session.d, but it had no effect. I'm including what I see what I get when run through gdb and dtruss below. Maybe those that worked on the launchd patch for dbus could help? I have reinstalled dbus / dbus-glib, but it's just the same behavior. I appreciate anyone's help on this. take care, jeff ======== (system) ======== $ xcodebuild -version Xcode 3.1.3 Component versions: DevToolsCore-1192.0; DevToolsSupport-1186.0 BuildVersion: 9M2736 $ uname -a Darwin xinix.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386 i386 $ port version Version: 1.8.1 ======== (gdb) ======== (gdb) run --nofork --session Starting program: /opt/local/bin/dbus-daemon --nofork --session Reading symbols for shared libraries +++. done Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x00000000 0x00030b9a in _dbus_server_new_for_launchd () ======== (dtruss) ======== SYSCALL(args) = return open("/dev/urandom\0", 0x0, 0xBFFFF748) = 3 0 read(0x3, "-\352_\221\253\215'\235\\\vl\354\0", 0xC) = 12 0 close(0x3) = 0 0 mmap(0x0, 0x1000000, 0x3, 0x1002, 0x2000000, 0x100000000) = 0x200000 0 munmap(0x200000, 0x600000) = 0 0 munmap(0x1000000, 0x200000) = 0 0 open("/opt/local/etc/dbus-1/session.conf\0", 0x0, 0xBFFFF698) = 3 0 fstat(0x3, 0xBFFFF680, 0xBFFFF698) = 0 0 read(0x3, "\n\n From mvfranz at gmail.com Wed Oct 7 05:25:11 2009 From: mvfranz at gmail.com (Michael Franz) Date: Wed, 7 Oct 2009 08:25:11 -0400 Subject: Ticket #21500 - IcedTea 1.11 In-Reply-To: <9227BA4F-AC99-40EB-8058-89E3A7D83B6D@macports.org> References: <9227BA4F-AC99-40EB-8058-89E3A7D83B6D@macports.org> Message-ID: On Tue, Oct 6, 2009 at 9:16 PM, Ryan Schmidt wrote: > > On Oct 6, 2009, at 19:55, Michael Franz wrote: > > I think I have figured out the installation script for IcedTea. The only >> issue I have and would like input on is how to handle the different compiler >> for Snow Leopard. The Snow Leopard default 4.2 compiler will not compile >> the OpenJDK (thus IcedTea). The alternate gcc 4.0 will work fine. Do I >> need to have a variant for each platform or is it enough to force gcc 4.0 in >> the portfile? >> > > gcc-4.0 is the default on Tiger and Leopard, and is available on Snow > Leopard, so you could simply add this line to the portfile: > > configure.compiler gcc-4.0 > > You should probably preface that with a comment explaining why: > > # IcedTea 1.11 doesn't compile with gcc-4.2 > configure.compiler gcc-4.0 > > I have found that adding that does not work. I also had to add build.args CC=gcc-4.0 CXX=g++-4.0 otherwise it still using gcc 4.2. Is this normal? IcedTea provides an additional step to the OpenJDK build process that allows older JDKs to be used to build OpenJDK (the goal is to not require non-open source/free tools to build OpenJDK). It also provides replacement code for the binary plugins that were initially release with the OpenJDK (I think they have all been replaced in OpenJDK). This additional step allows the use of Apple's JDK 5 to build OpenJDK 7 without requiring JDK 6 - which was not available when I started this process. This should work on PowerPC once Zero and Shark are integrated into the BSD port thus bringing JDK 7 to PowerPC macs. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeff.pitman at gmail.com Wed Oct 7 05:31:19 2009 From: jeff.pitman at gmail.com (Jeff Pitman) Date: Wed, 7 Oct 2009 20:31:19 +0800 Subject: mp4v2, libmp4v2, and pango Message-ID: <6b9c17630910070531v4295f422r8c7a7a81a5315ee0@mail.gmail.com> Hi again, Back real quick with another problem with a recent selfupdate / upgrade outdated. Macports at 1.8.1 and I have the following 2 problems doing "upgrade outdated": 1. mp4v2 seems to replace libmp4v2, but faac and mpeg4ip still depend on libmp4v2. So, when I execute "sudo port -u uninstall", it gives the following error: $ sudo port -u uninstall ---> Unable to uninstall libmp4v2 1.5.0.1_0, the following ports depend on it: ---> faac ---> mpeg4ip ---> faac Error: port uninstall failed: Please uninstall the ports that depend on libmp4v2 first. Seems like these tickets are tracking this issue: http://trac.macports.org/ticket/19141 http://trac.macports.org/ticket/19142 2. An older version of pango thinks it's newer than the real newer version of pango. $ sudo port upgrade outdated ---> Computing dependencies for pango ---> Fetching pango ---> Verifying checksum(s) for pango ---> Extracting pango ---> Applying patches to pango ---> Configuring pango ---> Building pango ---> Staging pango into destroot ---> Deactivating pango @1.26.0_0+macosx ---> Computing dependencies for pango ---> Installing pango @1.24.5_0+macosx ---> Activating pango @1.24.5_0+macosx ---> Cleaning pango $ sudo port activate pango ---> The following versions of pango are currently installed: ---> pango @1.24.5_0+macosx (active) ---> pango @1.26.0_0+macosx Error: port activate failed: Registry error: Please specify the full version as recorded in the port registry. I see this ticket describes a big problem with 1.26: https://trac.macports.org/ticket/21624 However, my gimp has been rendered completely unusable with the latest upgrades. :( Any tips appreciated! take care, jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Wed Oct 7 05:36:11 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 7 Oct 2009 07:36:11 -0500 Subject: Ticket #21500 - IcedTea 1.11 In-Reply-To: References: <9227BA4F-AC99-40EB-8058-89E3A7D83B6D@macports.org> Message-ID: <147000C4-4DBE-4400-8BD3-4E7BCFF7CF03@macports.org> On Oct 7, 2009, at 07:25, Michael Franz wrote: > On Tue, Oct 6, 2009 at 9:16 PM, Ryan Schmidt wrote: > >> gcc-4.0 is the default on Tiger and Leopard, and is available on >> Snow Leopard, so you could simply add this line to the portfile: >> >> configure.compiler gcc-4.0 >> >> You should probably preface that with a comment explaining why: >> >> # IcedTea 1.11 doesn't compile with gcc-4.2 >> configure.compiler gcc-4.0 > > I have found that adding that does not work. I also had to add > build.args CC=gcc-4.0 CXX=g++-4.0 > otherwise it still using gcc 4.2. Is this normal? MacPorts passes these variables to the configure script, which is supposed to record those values and use them later. If IcedTea's configure script does not do this, then yes, you will have to pass them again, e.g. in the build.args or build.env. The proper way would be: build.args CC=${configure.cc} CXX=${configure.cxx} -- after setting configure.compiler as above. > IcedTea provides an additional step to the OpenJDK build process > that allows older JDKs to be used to build OpenJDK (the goal is to > not require non-open source/free tools to build OpenJDK). It also > provides replacement code for the binary plugins that were initially > release with the OpenJDK (I think they have all been replaced in > OpenJDK). > > This additional step allows the use of Apple's JDK 5 to build > OpenJDK 7 without requiring JDK 6 - which was not available when I > started this process. This should work on PowerPC once Zero and > Shark are integrated into the BSD port thus bringing JDK 7 to > PowerPC macs. From ryandesign at macports.org Wed Oct 7 05:48:50 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 7 Oct 2009 07:48:50 -0500 Subject: mp4v2, libmp4v2, and pango In-Reply-To: <6b9c17630910070531v4295f422r8c7a7a81a5315ee0@mail.gmail.com> References: <6b9c17630910070531v4295f422r8c7a7a81a5315ee0@mail.gmail.com> Message-ID: On Oct 7, 2009, at 07:31, Jeff Pitman wrote: > 1. mp4v2 seems to replace libmp4v2, Yes. > but faac and mpeg4ip still depend on libmp4v2. They don't appear to, at present: $ port deps faac Full Name: faac @1.28+universal Build Dependencies: autoconf, automake, libtool Library Dependencies: mp4v2 $ port deps mpeg4ip Full Name: mpeg4ip @1.5.0.1 mpeg4ip has no Build Dependencies, Runtime Dependencies, Fetch Dependencies, Library Dependencies, Extract Dependencies $ They probably did at one point -- specifically at a point when you installed these ports, so those now-deleted dependencies are still recorded in your registry. > So, when I execute "sudo port -u uninstall", it gives the following > error: > > $ sudo port -u uninstall > ---> Unable to uninstall libmp4v2 1.5.0.1_0, the following ports > depend on it: > ---> faac > ---> mpeg4ip > ---> faac > Error: port uninstall failed: Please uninstall the ports that depend > on libmp4v2 first. It should be fine to force the uninstallation in this case. sudo port -f uninstall libmp4v2 @1.5.0.1_0 > Seems like these tickets are tracking this issue: > http://trac.macports.org/ticket/19141 > http://trac.macports.org/ticket/19142 They seem to be tracking issues relating to the transition from libmp4v2 to mp4v2 but not specifically the issue of old dependencies remaining in your registry, which is a known deficiency of registry 1.0 which is described here: http://trac.macports.org/ticket/13054 > 2. An older version of pango thinks it's newer than the real newer > version of pango. > > $ sudo port upgrade outdated > ---> Computing dependencies for pango > ---> Fetching pango > ---> Verifying checksum(s) for pango > ---> Extracting pango > ---> Applying patches to pango > ---> Configuring pango > ---> Building pango > ---> Staging pango into destroot > ---> Deactivating pango @1.26.0_0+macosx > ---> Computing dependencies for pango > ---> Installing pango @1.24.5_0+macosx > ---> Activating pango @1.24.5_0+macosx > ---> Cleaning pango > $ sudo port activate pango > ---> The following versions of pango are currently installed: > ---> pango @1.24.5_0+macosx (active) > ---> pango @1.26.0_0+macosx > Error: port activate failed: Registry error: Please specify the full > version as recorded in the port registry. > > I see this ticket describes a big problem with 1.26: > https://trac.macports.org/ticket/21624 Yes, and as you see, I therefore downgraded pango from 1.26.0 back to 1.24.5 in order to fix this problem: http://trac.macports.org/ticket/21624#comment:7 Hopefully the pango developers will be able to figure out what caused this problem, and to fix it, and a future version of pango will again work well for us. > However, my gimp has been rendered completely unusable with the > latest upgrades. :( I'm sorry to hear that. I saw your other email about dbus bus errors but I'm afraid I have no insight on them. If you are having yet additional issues, please describe them. From ryandesign at macports.org Wed Oct 7 06:00:04 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 7 Oct 2009 08:00:04 -0500 Subject: Problem installing UnitTest++ In-Reply-To: <30879999-AADC-4C6F-A47D-ED50332983DB@gmail.com> References: <30879999-AADC-4C6F-A47D-ED50332983DB@gmail.com> Message-ID: On Oct 7, 2009, at 06:21, Daniel Lidstr?m wrote: > I stumbled upon a problem when trying to install UnitTest++: > > daniel-lidstroms-imac-g5:/Users/daniel/programming/othello> sudo > port install unittest-cpp > ---> Computing dependencies for unittest-cpp > ---> Fetching unittest-cpp > ---> Verifying checksum(s) for unittest-cpp > ---> Extracting unittest-cpp > ---> Configuring unittest-cpp > ---> Building unittest-cpp > Error: Target org.macports.build returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_unittest > -cpp/work/UnitTest++" && /usr/bin/make -j1 all " returned error 2 > Command output: src/MemoryOutStream.cpp > src/DeferredTestReporter.cpp > src/DeferredTestResult.cpp > src/XmlTestReporter.cpp > src/CurrentTest.cpp > src/Posix/SignalTranslator.cpp > src/Posix/TimeHelpers.cpp > Creating libUnitTest++.a library... > src/tests/Main.cpp > src/tests/TestAssertHandler.cpp > src/tests/TestChecks.cpp > src/tests/TestUnitTest++.cpp > src/tests/TestTest.cpp > src/tests/TestTestResults.cpp > src/tests/TestTestRunner.cpp > src/tests/TestCheckMacros.cpp > src/tests/TestTestList.cpp > src/tests/TestTestMacros.cpp > src/tests/TestTimeConstraint.cpp > src/tests/TestTimeConstraintMacro.cpp > src/tests/TestMemoryOutStream.cpp > src/tests/TestDeferredTestReporter.cpp > src/tests/TestXmlTestReporter.cpp > src/tests/TestCurrentTest.cpp > Linking TestUnitTest++... > Running unit tests... > :107: error: Failure in test: Expected 2 but was 0 > FAILURE: 1 out of 174 tests failed (1 failures). > Test time: 0.11 seconds. > make: *** [TestUnitTest++] Error 1 > > Error: Status 1 encountered during processing. > daniel-lidstroms-imac-g5:/Users/daniel/programming/othello> find / > opt -name libUnitTest++.a > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_unittest > -cpp/work/UnitTest++/libUnitTest++.a > > Can I just copy libUnitTest++.a into /op/local/lib in the meantime? That might not be a good idea. Installing software by hand into the MacPorts prefix will cause a conflict if you later try again to install unittest-cpp (or try to install a port that depends on it) because the file will already exist but MacPorts won't know where it came from. And presumably the tests verify the software functions correctly, so a failing test may indicate the software will not work correctly. You should file an issue in our issue tracker to report this problem, and/or speak with the developers of this software. I see one other report of this problem, for Debian, here: http://osdir.com/ml/debian-bugs-rc/2009-04/msg02036.html Unfortunately I don't see any discussion or solution presented. The port installs fine for me on Leopard and Snow Leopard, both on a MacBook Pro. From mikiemike600 at gmail.com Wed Oct 7 08:05:52 2009 From: mikiemike600 at gmail.com (mikie mike) Date: Wed, 7 Oct 2009 17:05:52 +0200 Subject: gimp snow leopard problem Message-ID: <182a1ea60910070805x73f70b16he2c23840dc245bee@mail.gmail.com> There is a problem with gimp installation on Snow Leopard described here: http://trac.macports.org/ticket/21011 I actually don't need gimp for now but I need ufraw package, which tries to install gimp as dependency or something. Is there any chance to workaround the problem with gimp or install ufraw without installing gimp? Thanks, Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: From aeronova at teramail.com Wed Oct 7 10:40:08 2009 From: aeronova at teramail.com (Kyunghoon Lee) Date: Wed, 07 Oct 2009 13:40:08 -0400 Subject: How to clean a failed package to build? Message-ID: <4ACCD278.4070103@teramail.com> Hello all, I was trying to build pang with a quartz option and it failed because of the option. I wanted to rebuild pango w/o the quartz option, but port kept using the same variants option. I tried to clean, but it seems "port clean" works only for successfully installed packages. I'd appreciate it if someone help me clean the unsuccessful install process so that I can build pango as if I'm building it for the first time. Thank you in adv. From talklists at newgeo.com Wed Oct 7 12:38:53 2009 From: talklists at newgeo.com (Scott Haneda) Date: Wed, 7 Oct 2009 12:38:53 -0700 Subject: .bashrc .profile .bash_profile In-Reply-To: References: <6FE8CA9B-FCF8-41ED-8D33-D8CC3A2B54DD@kf8nh.com> <2A566FD9-C6CB-4801-8F4B-1D9E04ED0EB0@newgeo.com> <6A1CD4B1-DE13-4E41-9E08-A1F392E39183@newgeo.com> <524F7AC9-D665-4A29-97AD-D1DB56F53372@newgeo.com> Message-ID: <6569F916-7ABE-4597-ADB0-C71E1EB99BF4@newgeo.com> Very cool. I had a few functions, but this is a handy one. I did not know I could just set the CLIFORCE_COLOR for the one session. I also like how I believe you pass in the $@, so I can send in arguments to my ls alias, which I was not able to do in the past. Was your use of CLICOLOR_FORCE=X meant literally, or should I use boolean? I have used boolean in the past, and the man page for ls does not state what 'X" does, though it does work. Thank you to all who have contributed to this thread. What started as wonting to know the best way to deal with the .profile that MacPorts wants to set, has taught me a lot. -- Scott * If you contact me off list replace talklists@ with scott@ * On Oct 6, 2009, at 9:41 PM, Derek Harland wrote: > Hi Scott > > If stdout is not a terminal then "ls" disables color information by > default. So if you want to pipe it to anything like grep then you > *must* have CLICOLOR_FORCE in the environment. > > But as Brandon points out, that can bite you in general ... perhaps > you want to define an alias with a different name to ls that does > want you want. > > For example, here's what my bashrc defines > > function ll () { command env CLICOLOR_FORCE=X ls -lAFG "$@" | less - > R; } > > Perhaps you want something like > > function myls () { command env CLICOLOR_FORCE=X ls -la "$@" | grep - > v .DS_Store; } From ryandesign at macports.org Wed Oct 7 13:22:10 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 7 Oct 2009 15:22:10 -0500 Subject: .bashrc .profile .bash_profile In-Reply-To: <6569F916-7ABE-4597-ADB0-C71E1EB99BF4@newgeo.com> References: <6FE8CA9B-FCF8-41ED-8D33-D8CC3A2B54DD@kf8nh.com> <2A566FD9-C6CB-4801-8F4B-1D9E04ED0EB0@newgeo.com> <6A1CD4B1-DE13-4E41-9E08-A1F392E39183@newgeo.com> <524F7AC9-D665-4A29-97AD-D1DB56F53372@newgeo.com> <6569F916-7ABE-4597-ADB0-C71E1EB99BF4@newgeo.com> Message-ID: <6C15ED0C-7786-4A6A-AB0C-CBB6A89AD760@macports.org> On Oct 7, 2009, at 14:38, Scott Haneda wrote: > Was your use of CLICOLOR_FORCE=X meant literally, or should I use > boolean? I have used boolean in the past, and the man page for ls > does not state what 'X" does, though it does work. Perhaps it doesn't look at what value CLICOLOR_FORCE is set to, only that it is set at all. From ryandesign at macports.org Wed Oct 7 13:38:43 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 7 Oct 2009 15:38:43 -0500 Subject: How to clean a failed package to build? In-Reply-To: <4ACCD278.4070103@teramail.com> References: <4ACCD278.4070103@teramail.com> Message-ID: On Oct 7, 2009, at 12:40, Kyunghoon Lee wrote: > I was trying to build pang with a quartz option and it failed > because of the option. I wanted to rebuild pango w/o the quartz > option, but port kept using the same variants option. I tried to > clean, but it seems "port clean" works only for successfully > installed packages. I'd appreciate it if someone help me clean the > unsuccessful install process so that I can build pango as if I'm > building it for the first time. Thank you in adv. What problem did you experience cleaning pango? "sudo port clean pango" cleans the pango work directory and should be all you need. Cleaning an already-installed port probably isn't useful most of the time, since MacPorts cleans a port automatically after it installs it. From aeronova at teramail.com Wed Oct 7 13:48:57 2009 From: aeronova at teramail.com (Kyunghoon Lee) Date: Wed, 07 Oct 2009 16:48:57 -0400 Subject: How to clean a failed package to build? In-Reply-To: References: <4ACCD278.4070103@teramail.com> Message-ID: <4ACCFEB9.3080109@teramail.com> Ryan Schmidt wrote: > > On Oct 7, 2009, at 12:40, Kyunghoon Lee wrote: > >> I was trying to build pang with a quartz option and it failed because >> of the option. I wanted to rebuild pango w/o the quartz option, but >> port kept using the same variants option. I tried to clean, but it >> seems "port clean" works only for successfully installed packages. >> I'd appreciate it if someone help me clean the unsuccessful install >> process so that I can build pango as if I'm building it for the first >> time. Thank you in adv. > > What problem did you experience cleaning pango? "sudo port clean > pango" cleans the pango work directory and should be all you need. > Cleaning an already-installed port probably isn't useful most of the > time, since MacPorts cleans a port automatically after it installs it. After I failed to build pango, I tried again and get the following message: Error: Requrested variants "+macosx" do not match original selection "+macosx+quartz". Please use the same variants again, perform 'port clean pango' or specify the force option (-f). Is it safe to use the '-f' option in this case to build pango w/o the quartz option? From rppass at rppass.com Wed Oct 7 13:54:47 2009 From: rppass at rppass.com (Ralph Pass) Date: Wed, 07 Oct 2009 16:54:47 -0400 Subject: .bashrc .profile .bash_profile In-Reply-To: <6569F916-7ABE-4597-ADB0-C71E1EB99BF4@newgeo.com> References: <6FE8CA9B-FCF8-41ED-8D33-D8CC3A2B54DD@kf8nh.com> <2A566FD9-C6CB-4801-8F4B-1D9E04ED0EB0@newgeo.com> <6A1CD4B1-DE13-4E41-9E08-A1F392E39183@newgeo.com> <524F7AC9-D665-4A29-97AD-D1DB56F53372@newgeo.com> <6569F916-7ABE-4597-ADB0-C71E1EB99BF4@newgeo.com> Message-ID: <4ACD0017.1040500@rppass.com> What I learned was that the spaces are important!. Thanks to all who contributed. Ralph Pass Scott Haneda wrote: > Very cool. I had a few functions, but this is a handy one. I did not > know I could just set the CLIFORCE_COLOR for the one session. I also > like how I believe you pass in the $@, so I can send in arguments to > my ls alias, which I was not able to do in the past. > > Was your use of CLICOLOR_FORCE=X meant literally, or should I use > boolean? I have used boolean in the past, and the man page for ls > does not state what 'X" does, though it does work. > > Thank you to all who have contributed to this thread. What started as > wonting to know the best way to deal with the .profile that MacPorts > wants to set, has taught me a lot. From ryandesign at macports.org Wed Oct 7 15:46:00 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 7 Oct 2009 17:46:00 -0500 Subject: How to clean a failed package to build? In-Reply-To: <4ACCFEB9.3080109@teramail.com> References: <4ACCD278.4070103@teramail.com> <4ACCFEB9.3080109@teramail.com> Message-ID: <76975DC0-7BC5-4560-B32B-D0063275FC54@macports.org> On Oct 7, 2009, at 15:48, Kyunghoon Lee wrote: > Ryan Schmidt wrote: >> > >> On Oct 7, 2009, at 12:40, Kyunghoon Lee wrote: >> >>> I was trying to build pang with a quartz option and it failed >>> because of the option. I wanted to rebuild pango w/o the quartz >>> option, but port kept using the same variants option. I tried to >>> clean, but it seems "port clean" works only for successfully >>> installed packages. [snip] >> >> What problem did you experience cleaning pango? [snip] > > After I failed to build pango, I tried again and get the following > message: > Error: Requrested variants "+macosx" do not match original selection > "+macosx+quartz". > Please use the same variants again, perform 'port clean pango' or > specify the force option (-f). > > Is it safe to use the '-f' option in this case to build pango w/o > the quartz option? No, not really. What happens when you "sudo port clean pango" and then try "sudo port install pango" again? From aeronova at teramail.com Wed Oct 7 22:19:49 2009 From: aeronova at teramail.com (Kyunghoon Lee) Date: Thu, 08 Oct 2009 01:19:49 -0400 Subject: How to clean a failed package to build? In-Reply-To: <76975DC0-7BC5-4560-B32B-D0063275FC54@macports.org> References: <4ACCD278.4070103@teramail.com> <4ACCFEB9.3080109@teramail.com> <76975DC0-7BC5-4560-B32B-D0063275FC54@macports.org> Message-ID: <4ACD7675.3070602@teramail.com> Ryan Schmidt wrote: > > On Oct 7, 2009, at 15:48, Kyunghoon Lee wrote: > >> Ryan Schmidt wrote: >>> >> >>> On Oct 7, 2009, at 12:40, Kyunghoon Lee wrote: >>> >>>> I was trying to build pang with a quartz option and it failed >>>> because of the option. I wanted to rebuild pango w/o the quartz >>>> option, but port kept using the same variants option. I tried to >>>> clean, but it seems "port clean" works only for successfully >>>> installed packages. [snip] >>> >>> What problem did you experience cleaning pango? [snip] >> >> After I failed to build pango, I tried again and get the following >> message: >> Error: Requrested variants "+macosx" do not match original selection >> "+macosx+quartz". >> Please use the same variants again, perform 'port clean pango' or >> specify the force option (-f). >> >> Is it safe to use the '-f' option in this case to build pango w/o the >> quartz option? > > No, not really. What happens when you "sudo port clean pango" and then > try "sudo port install pango" again? > Here's what I got: $ sudo port clean pango Password: ---> Cleaning pango $ sudo port install pango ---> Computing dependencies for pango ---> Fetching pango ---> Verifying checksum(s) for pango ---> Extracting pango Error: To install pango without the quartz variant, cairo must be installed without the quartz variant. Error: Target org.macports.extract returned: incompatible cairo installation Error: Status 1 encountered during processing. So I guess I need to uninstall & install cario again w/o quartz, then try to install pango w/o quartz, right? BTW, this might be a silly question, but what is quartz? From ryandesign at macports.org Wed Oct 7 22:29:48 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 8 Oct 2009 00:29:48 -0500 Subject: How to clean a failed package to build? In-Reply-To: <4ACD7675.3070602@teramail.com> References: <4ACCD278.4070103@teramail.com> <4ACCFEB9.3080109@teramail.com> <76975DC0-7BC5-4560-B32B-D0063275FC54@macports.org> <4ACD7675.3070602@teramail.com> Message-ID: <1F651D75-D089-40DD-8E9D-3ABA4DD4522B@macports.org> On Oct 8, 2009, at 00:19, Kyunghoon Lee wrote: > $ sudo port install pango > ---> Computing dependencies for pango > ---> Fetching pango > ---> Verifying checksum(s) for pango > ---> Extracting pango > Error: To install pango without the quartz variant, cairo must be > installed without the quartz variant. > Error: Target org.macports.extract returned: incompatible cairo > installation > Error: Status 1 encountered during processing. > > So I guess I need to uninstall & install cario again w/o quartz, > then try to install pango w/o quartz, right? Yes. If you install one port with the quartz variant, really you should install all ports with it, and vice versa. pango has specific checks for this, but even for those that don't, this holds true. > BTW, this might be a silly question, but what is quartz? It's this: http://en.wikipedia.org/wiki/Quartz_(graphics_layer) In MacPorts, the quartz variant is often the way you indicate you want native Mac OS X drawing routines to be used instead of the default X11 drawing routines. However, these are less-well tested and so might not work. From jeff.pitman at gmail.com Thu Oct 8 07:42:29 2009 From: jeff.pitman at gmail.com (Jeff Pitman) Date: Thu, 8 Oct 2009 22:42:29 +0800 Subject: Gimp Message-ID: <6b9c17630910080742w3d4d16abhd0a0e82b3dfdef2a@mail.gmail.com> Hi all, I finally got Gimp to work again. This is what I did: 1. port uninstall --follow-dependents gtk2 2. port uninstall --follow-dependents gimp2 3. port uninstall --follow-dependents gimp-app 4. port clean cairo 5. port clean pango 6. port clean gtk2 7. port clean gimp2 8. port install gtk2 +quartz +no_x11 9. port install gimp2 +quartz +no_x11 10. port install gimp-app +quartz +no_x11 Something along those lines. Anyhow, apparently no_x11 skips the dbus-daemon stuff, so I can just leave a broken dbus there. thanks, jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: From wesbland at gmail.com Thu Oct 8 09:12:54 2009 From: wesbland at gmail.com (Wesley Bland) Date: Thu, 8 Oct 2009 12:12:54 -0400 Subject: Problem with Snow Leopard and gnuplot Message-ID: I'm having a problem installing gnuplot on my Snow Leopard box from macports. I've already done a port upgrade outdated to make sure everything is up to date and I've installed p5-libintl-perl, but I'm still getting this error: > $ sudo port install gnuplot ---> Computing dependencies for gnuplot ---> Configuring p5-locale-gettext 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_perl_p5-locale-gettext/work/gettext-1.05" > && /opt/local/bin/perl Makefile.PL INSTALLDIRS=vendor " returned error 2 Command output: checking for gettext... no checking for gettext in -I/opt/local/include -L/opt/local/lib > -lintl...gettext function not found. Please install libintl at Makefile.PL > line 18. no > Error: The following dependencies failed to build: gd2 autoconf help2man > p5-locale-gettext m4 automake libtool xpm xorg-libX11 xorg-bigreqsproto > xorg-inputproto xorg-kbproto xorg-libXau xorg-xproto xorg-libXdmcp > xorg-util-macros xorg-xcmiscproto xorg-xextproto xorg-xf86bigfontproto > xorg-xtrans pdflib Error: Status 1 encountered during processing. I've Googled around for related problems, but I haven't seen anything that seems to be helpful to me. This is a program I really need to do my work. Does anyone know why I'd be getting this error? Thanks, Wesley -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Thu Oct 8 09:49:13 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 8 Oct 2009 11:49:13 -0500 Subject: Problem with Snow Leopard and gnuplot In-Reply-To: References: Message-ID: On Oct 8, 2009, at 11:12, Wesley Bland wrote: > I'm having a problem installing gnuplot on my Snow Leopard box from > macports. I've already done a port upgrade outdated to make sure > everything is up to date and I've installed p5-libintl-perl, but I'm > still getting this error: > >> $ sudo port install gnuplot >> ---> Computing dependencies for gnuplot >> ---> Configuring p5-locale-gettext >> 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_perl_p5 >> -locale-gettext/work/gettext-1.05" && /opt/local/bin/perl >> Makefile.PL INSTALLDIRS=vendor " returned error 2 >> Command output: checking for gettext... no >> checking for gettext in -I/opt/local/include -L/opt/local/lib - >> lintl...gettext function not found. Please install libintl at Makefile.PL >> line 18. >> no >> >> Error: The following dependencies failed to build: gd2 autoconf >> help2man p5-locale-gettext m4 automake libtool xpm xorg-libX11 xorg- >> bigreqsproto xorg-inputproto xorg-kbproto xorg-libXau xorg-xproto >> xorg-libXdmcp xorg-util-macros xorg-xcmiscproto xorg-xextproto xorg- >> xf86bigfontproto xorg-xtrans pdflib >> Error: Status 1 encountered during processing. > > I've Googled around for related problems, but I haven't seen > anything that seems to be helpful to me. This is a program I really > need to do my work. Does anyone know why I'd be getting this error? There is this: http://trac.macports.org/ticket/19381 But it only relates to building p5-locale-gettext for a different architecture than the default one. Did you request a different architecture by setting build_conf in macports.conf, or are you just trying to build the default way, which should work? I assume you upgraded to Snow Leopard from Leopard? If so, did you follow the migration procedure and uninstall and reinstall all ports? http://trac.macports.org/wiki/Migration From dweber at macports.org Thu Oct 8 11:37:47 2009 From: dweber at macports.org (Darren Weber) Date: Thu, 8 Oct 2009 11:37:47 -0700 Subject: location of hdf5 header files Message-ID: In cursory exploration of /opt/local/include/, it appears that many, if not all, of the hdf5 header files are located at the root of /opt/local/include/. Is that a mistake? Should the hdf5 include files get stored into something like /opt/local/include/hdf5/? Take care, Darren -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Thu Oct 8 12:16:08 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 8 Oct 2009 14:16:08 -0500 Subject: location of hdf5 header files In-Reply-To: References: Message-ID: On Oct 8, 2009, at 13:37, Darren Weber wrote: > In cursory exploration of /opt/local/include/, it appears that many, > if not all, of the hdf5 header files are located at the root of /opt/ > local/include/. Is that a mistake? Should the hdf5 include files > get stored into something like /opt/local/include/hdf5/? Using "port contents hdf5 | grep \\.h$" I would agree that all this port's headers are in ${prefix}/include. Is that a problem? Would it be better to have them in a subdirectory? The port doesn't seem to do anything to change the header location at present, so it just installs them where the developer of that software thought they should go. Is there a problem you're trying to solve by moving the headers? From dweber at macports.org Thu Oct 8 12:46:43 2009 From: dweber at macports.org (Darren Weber) Date: Thu, 8 Oct 2009 12:46:43 -0700 Subject: location of hdf5 header files In-Reply-To: References: Message-ID: On Thu, Oct 8, 2009 at 12:16 PM, Ryan Schmidt wrote: > On Oct 8, 2009, at 13:37, Darren Weber wrote: > > In cursory exploration of /opt/local/include/, it appears that many, if >> not all, of the hdf5 header files are located at the root of >> /opt/local/include/. Is that a mistake? Should the hdf5 include files get >> stored into something like /opt/local/include/hdf5/? >> > > Using "port contents hdf5 | grep \\.h$" I would agree that all this port's > headers are in ${prefix}/include. Is that a problem? Would it be better to > have them in a subdirectory? The port doesn't seem to do anything to change > the header location at present, so it just installs them where the developer > of that software thought they should go. Is there a problem you're trying to > solve by moving the headers? > > Ah, it's not a current problem that prevents or interference with other ports within MacPorts, ASFAIK. Firstly, it's a convenience. When using ctags or any IDE system to analyze a set of header files (for programming autocompletion), it is convenient to have the headers in a package specific path within the general ${prefix}/include path. This is especially true for large packages, like wx*, vtk*, InsightToolkit*, etc. Secondly, it's a safety-net. At the very least, it is significant and important that any headers located in the generic ${prefix}/include have some kind of unique naming convention, like a prefix in their file name, to avoid any conflicts with other software packages. The hdf5 package appears to have the file prefix of "H5" to distinguish it from other packages. However, a two-char prefix is not exactly a reliable unique identifier, especially on a file system that is not case sensitive. To avoid potential conflicts with other software packages, it may be preferable to locate the headers within ${prefix}/include/hdf5/. An additional layer may be added by using ${prefix}/include/hdf5-${ver} where ver=1.6 (as of the current writing, we have hdf5 @ 1.6.9). The version specific path should allow multiple versions of the library to co-exist in the ports tree (in this regard, we have seen some issues with versions of the hdf5 port in relation to the netcdf port). Take care, Darren -------------- next part -------------- An HTML attachment was scrubbed... URL: From kuepper.jochen at googlemail.com Thu Oct 8 12:53:44 2009 From: kuepper.jochen at googlemail.com (=?iso-8859-1?Q?Jochen_K=FCpper?=) Date: Thu, 8 Oct 2009 21:53:44 +0200 Subject: location of hdf5 header files In-Reply-To: References: Message-ID: On 08.10.2009, at 21:46, Darren Weber wrote: > On Thu, Oct 8, 2009 at 12:16 PM, Ryan Schmidt > wrote: > On Oct 8, 2009, at 13:37, Darren Weber wrote: > > In cursory exploration of /opt/local/include/, it appears that many, > if not all, of the hdf5 header files are located at the root of /opt/ > local/include/. Is that a mistake? Should the hdf5 include files > get stored into something like /opt/local/include/hdf5/? > > Using "port contents hdf5 | grep \\.h$" I would agree that all this > port's headers are in ${prefix}/include. Is that a problem? Would it > be better to have them in a subdirectory? The port doesn't seem to > do anything to change the header location at present, so it just > installs them where the developer of that software thought they > should go. Is there a problem you're trying to solve by moving the > headers? > > > > Ah, it's not a current problem that prevents or interference with > other ports within MacPorts, ASFAIK. > > Firstly, it's a convenience. When using ctags or any IDE system to > analyze a set of header files (for programming autocompletion), it > is convenient to have the headers in a package specific path within > the general ${prefix}/include path. This is especially true for > large packages, like wx*, vtk*, InsightToolkit*, etc. > > Secondly, it's a safety-net. At the very least, it is significant > and important that any headers located in the generic ${prefix}/ > include have some kind of unique naming convention, like a prefix in > their file name, to avoid any conflicts with other software > packages. The hdf5 package appears to have the file prefix of "H5" > to distinguish it from other packages. However, a two-char prefix > is not exactly a reliable unique identifier, especially on a file > system that is not case sensitive. To avoid potential conflicts > with other software packages, it may be preferable to locate the > headers within ${prefix}/include/hdf5/. An additional layer may be > added by using ${prefix}/include/hdf5-${ver} where ver=1.6 (as of > the current writing, we have hdf5 @ 1.6.9). The version specific > path should allow multiple versions of the library to co-exist in > the ports tree (in this regard, we have seen some issues with > versions of the hdf5 port in relation to the netcdf port). But you then have to teach your compiler where to find the headers individually for all these packets... Software written for hdf5 generally assumes that #include works and no #include is necessary... I think it's fine as it is, until there is a actual name clash. Then it should be fixed upstream and all software has to be adopted to the new naming scheme... (Just my 2ct;-) Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de Libert?, ?galit?, Fraternit? GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll From ryandesign at macports.org Thu Oct 8 13:15:31 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 8 Oct 2009 15:15:31 -0500 Subject: location of hdf5 header files In-Reply-To: References: Message-ID: <1313959D-FCF7-420A-A092-26B896DE457F@macports.org> On Oct 8, 2009, at 14:46, Darren Weber wrote: > Firstly, it's a convenience. When using ctags or any IDE system to > analyze a set of header files (for programming autocompletion), it > is convenient to have the headers in a package specific path within > the general ${prefix}/include path. This is especially true for > large packages, like wx*, vtk*, InsightToolkit*, etc. > > Secondly, it's a safety-net. At the very least, it is significant > and important that any headers located in the generic ${prefix}/ > include have some kind of unique naming convention, like a prefix in > their file name, to avoid any conflicts with other software > packages. The hdf5 package appears to have the file prefix of "H5" > to distinguish it from other packages. However, a two-char prefix > is not exactly a reliable unique identifier, especially on a file > system that is not case sensitive. To avoid potential conflicts > with other software packages, it may be preferable to locate the > headers within ${prefix}/include/hdf5/. An additional layer may be > added by using ${prefix}/include/hdf5-${ver} where ver=1.6 (as of > the current writing, we have hdf5 @ 1.6.9). The version specific > path should allow multiple versions of the library to co-exist in > the ports tree (in this regard, we have seen some issues with > versions of the hdf5 port in relation to the netcdf port). For most ports, there's no need to install into directories whose names contain the version number, since there's no way to install multiple versions of a port and have them all active at the same time anyway. hdf could be an exception there, since we do have three hdf ports (hdf4, hdf5, hdf5-18). In large part, the install location is up to the developer of the software. Developers can choose where they want their headers and other files to go. We can second-guess the developer, but we should carefully consider whether we know better than they do, and what problems such changes might cause. Any software that uses hdf would have to know where its headers are -- or use a pkg-config file or *- config program to find out, neither of which hdf appears to provide -- so unless we install hdf in the usual place, we would also have to patch every other port in MacPorts that uses hdf. This may not be that many (I count 20 ports that depend on hdf4, hdf5 or hdf5-18) but it is something to consider. From domiman at gmail.com Thu Oct 8 13:15:35 2009 From: domiman at gmail.com (Dominik Reichardt) Date: Thu, 8 Oct 2009 22:15:35 +0200 Subject: More KDE4 madness Message-ID: <6C47BD97-91EE-4D1D-A831-F2F9F90866E7@gmail.com> I'm still trying to build Krusader on Snow Leopard. yesterday and today some port updates landed that *should* make it possible. Problems I have run into so far when I just tried to have Krusader built with "sudo port install krusader +universal": - qt4-mac does not build without +cocoa set, some errors occured but at least they hinted at cocoa problems, I think. - after building qt4-mac on its own with +cocoa +universal, kdelibs4 would not build, even with the new portfile that had just landed (4.3.2_1), but this was again with trying to build with "... install krusader +universal". When I cleaned kdelibs4 and just tried to build it without +universal it suddenly found gsed in its dependancies. So either this gets ignored when building kdelibs4 is "just" a dependancy of Krusader or it gets ignored when +universal is set or ... sudo port install kdelibs4 ---> Computing dependencies for gsed ---> Fetching gsed ---> Verifying checksum(s) for gsed ---> Extracting gsed ---> Configuring gsed ---> Building gsed ---> Staging gsed into destroot ---> Installing gsed @4.2.1_0 ---> Activating gsed @4.2.1_0 ---> Cleaning gsed ---> Computing dependencies for kdelibs4 ---> Fetching kdelibs4 ---> Verifying checksum(s) for kdelibs4 ---> Extracting kdelibs4 ---> Applying patches to kdelibs4 ---> Configuring kdelibs4 ---> Building kdelibs4 ---> Staging kdelibs4 into destroot ---> Installing kdelibs4 @4.3.2_1 ---> Activating kdelibs4 @4.3.2_1 (unfortunately I have not saved the error message for qt4-mac, but I reported it in the ticket #20362, even though that is closed, but I thought that would be better than just opening a new one, but I'll gladly stand corrected, I'm still not sure on how things are done here :)) Thanks Dom From dweber at macports.org Thu Oct 8 14:26:13 2009 From: dweber at macports.org (Darren Weber) Date: Thu, 8 Oct 2009 14:26:13 -0700 Subject: location of hdf5 header files In-Reply-To: References: Message-ID: On Thu, Oct 8, 2009 at 12:53 PM, Jochen K?pper < kuepper.jochen at googlemail.com> wrote: > On 08.10.2009, at 21:46, Darren Weber wrote: > > On Thu, Oct 8, 2009 at 12:16 PM, Ryan Schmidt >> wrote: >> On Oct 8, 2009, at 13:37, Darren Weber wrote: >> >> In cursory exploration of /opt/local/include/, it appears that many, if >> not all, of the hdf5 header files are located at the root of >> /opt/local/include/. Is that a mistake? Should the hdf5 include files get >> stored into something like /opt/local/include/hdf5/? >> >> Using "port contents hdf5 | grep \\.h$" I would agree that all this port's >> headers are in ${prefix}/include. Is that a problem? Would it be better to >> have them in a subdirectory? The port doesn't seem to do anything to change >> the header location at present, so it just installs them where the developer >> of that software thought they should go. Is there a problem you're trying to >> solve by moving the headers? >> >> >> >> Ah, it's not a current problem that prevents or interference with other >> ports within MacPorts, ASFAIK. >> >> Firstly, it's a convenience. When using ctags or any IDE system to >> analyze a set of header files (for programming autocompletion), it is >> convenient to have the headers in a package specific path within the general >> ${prefix}/include path. This is especially true for large packages, like >> wx*, vtk*, InsightToolkit*, etc. >> >> Secondly, it's a safety-net. At the very least, it is significant and >> important that any headers located in the generic ${prefix}/include have >> some kind of unique naming convention, like a prefix in their file name, to >> avoid any conflicts with other software packages. The hdf5 package appears >> to have the file prefix of "H5" to distinguish it from other packages. >> However, a two-char prefix is not exactly a reliable unique identifier, >> especially on a file system that is not case sensitive. To avoid potential >> conflicts with other software packages, it may be preferable to locate the >> headers within ${prefix}/include/hdf5/. An additional layer may be added by >> using ${prefix}/include/hdf5-${ver} where ver=1.6 (as of the current >> writing, we have hdf5 @ 1.6.9). The version specific path should allow >> multiple versions of the library to co-exist in the ports tree (in this >> regard, we have seen some issues with versions of the hdf5 port in relation >> to the netcdf port). >> > > But you then have to teach your compiler where to find the headers > individually for all these packets... Software written for hdf5 generally > assumes that > #include > works and no > #include > is necessary... > > I think it's fine as it is, until there is a actual name clash. > Then it should be fixed upstream and all software has to be adopted to the > new naming scheme... > > Yes, it's best practice to avoid #includes like this: #include Rather, the common and perhaps preferred method to avoid such #include code styles is to use an include path as an argument to the compiler. This is the way to provide code that can build on various systems and it's the purpose of autoconf and similar tools to figure out where to find the libraries if they are not specified using some form of include path option (gcc has the -I and -L options). For example, assume a source file contains: #include "H5ArrayType.h" This file may be compiled on any distribution (where the package maintainers determine where stuff goes), using the convention of specific include path options for autoconf-like tools or the compiler suite. If the hdf5 libs are located in /opt/local/, that is the path to provide, eg: gcc -I/opt/local ... Software developers do "suggest" the default locations for the include and lib files in the default settings for autoconf and like tools (perhaps they provide a install shell script with defaults). The defaults are often consistent with a general consensus on where things go, like /usr/local and such. Note that MacPorts already discards the general consensus for using /usr/* paths, for good reason too. It is just a consensus, not a rule of law. The beauty of path specifications for autoconf and compilers is that the source code can be developed independently of the installation location for the headers/libs and, furthermore, package distribution systems can use ANY path configuration (e.g., AFAIK fink uses /sw/*). Getting back to the main point here, in the case of hdf5, there are multiple ports related to this software package: [ me at XXX ~ ]$ port search hdf h4h5tools @2.0 (science) HDF4 to HDF5 conversion tools. hdf4 @4.2r4 (science) file format for storing scientific data and utilities hdf5 @1.6.9 (science) HDF5 general purpose library and file format for storing scientific data hdf5-18 @1.8.3 (science) HDF5 general purpose library and file format for storing scientific data hdfeos @2.15v1.00 (science) HDF-EOS library built on HDF4 py25-tables @2.1.2 (python, python, science) Python package for HDF5 file access. py26-tables @2.1.2 (python, python, science) Python package for HDF5 file access. Now, if a program in another package distribution depends on a hdf* library, unless the MacPorts system uses specific include/lib paths, how do we know whether it is building against hdf4, hdf5, or hdf5-18? (Of course, we can use otool, that's not the point here; the point is, how do we specify the dependency exactly?) Do all these package versions have different header file prefixes so they can coexist in ${prefix}/include/? (If so, and they are some kind of custom hack within MacPorts, then that is likely to break source code that assumes a standard file name convention for the hdf4 or hdf5 libraries.) Furthermore, if you design a new port for MacPorts that does depend on ONE of these libraries, how can you be clear about specifying that dependency (obviously, you can specify port:hdf...), but what about specifics in the Portfile for any include or lib paths in the configure phase? My preference: A. When coding a new port that depends on hdf5 @ 1.6.x, specify a port dependency on port:hdf5-16 and specify to the configure phase that the include path is ${prefix}/include/hdf5-1.6 B. When coding a new port that depends on hdf5 @ 1.8.x, specify a port dependency on port:hdf5-18 and specify to the configure phase that the include path is ${prefix}/include/hdf5-1.8 C. There may be a port called simply hdf5 (or hdf4), with no version specific suffix in the name. Any dependency on that port would be port:hdf5 and the configure include path would be ${prefix}/include/hdf5 (and that path might actually be a symlink to the "latest" version specific include path). Take care, Darren P.S., It's odd that the hdf5 port is @ 1.6.x, whereas the hdf5-18 port is a later version. In general, the consensus in MacPorts appears to be that ports with a generic name, like hdf5, contain the latest version available. Any prior releases assume a version specific port name. Suggestion: the port name "hdf5" always contains the latest (stable) release; the port name "hdf5-devel" contains the latest development version (not necessarily stable); any prior version specific releases are named "hdf5-${major}${minor}", like hdf5-16. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dweber at macports.org Thu Oct 8 16:11:46 2009 From: dweber at macports.org (Darren Weber) Date: Thu, 8 Oct 2009 16:11:46 -0700 Subject: cvs2svn dependencies Message-ID: With reference to this page: http://cvs2svn.tigris.org/cvs2svn.html There are various run-time dependencies indicated under the title of "Requirements". Are any of these included as dependencies in the MacPorts cvs2svn port? (I don't see any.) Also, is it possible to have a symlink or hardlink: /opt/local/bin/cvs2svn -> /opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin/cvs2svn Take care, Darren -------------- next part -------------- An HTML attachment was scrubbed... URL: From dluke at geeklair.net Thu Oct 8 16:23:36 2009 From: dluke at geeklair.net (Daniel J. Luke) Date: Thu, 8 Oct 2009 19:23:36 -0400 Subject: cvs2svn dependencies In-Reply-To: References: Message-ID: On Oct 8, 2009, at 7:11 PM, Darren Weber wrote: > With reference to this page: > http://cvs2svn.tigris.org/cvs2svn.html > > There are various run-time dependencies indicated under the title of > "Requirements". Are any of these included as dependencies in the > MacPorts cvs2svn port? (I don't see any.) That page lists 1- python (which is a port dependency) 2- db library and python bindings (python26 port builds with db46 and gdbm already) 3- gnu sort (comes with mac os x) optionally can use rcs or cvs if you pass in appropriate options (and you can pass the path to those binaries). both cvs and rcs are included with Mac OS X (or you could install a macports version if you wanted and point cvs2svn to them). did you notice something broken? > Also, is it possible to have a symlink or hardlink: > > /opt/local/bin/cvs2svn -> /opt/local/Library/Frameworks/ > Python.framework/Versions/2.6/bin/cvs2svn cvs2svn used to install to ${prefix}/bin but the python26 portgroup sets prefix to ${frameworks_dir}/Python.framework/Versions/2.6 presumably this is so that one could install a cvs2svn against python26 and one against another version of python... Linking cvs2bzr, cvs2git, and cvs2svn to ${prefix}/bin would be one possible solution ... -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ From pth at ispnet.ca Thu Oct 8 16:24:38 2009 From: pth at ispnet.ca (Peter Hindrichs) Date: Thu, 8 Oct 2009 19:24:38 -0400 Subject: Install Error Message-ID: I am looking to further my understanding and knowledge of the command line and "Ports" so when I tried to install the port "CosmicDebris" I got this message. I have tried to figure it out, but am having no luck, could someone please help me to understand what is actually being said here. Could this have something to do with the fact that the program is not Snow Leopard compatible or is there another reason ? Freedom:~ peterhin$ sudo port install CosmicDebris Password: ---> Computing dependencies for CosmicDebris ---> Fetching CosmicDebris ---> Attempting to fetch CosmicDebrisSource.zip from http://distfiles.macports.org/CosmicDebris/2.0 ---> Verifying checksum(s) for CosmicDebris ---> Extracting CosmicDebris ---> Configuring CosmicDebris ---> Building CosmicDebris Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_CosmicDebris /work/CosmicDebrisSource" && /usr/bin/xcodebuild -project "Cosmic Debris.xcodeproj" -target "Cosmic Debris" -configuration Deployment " returned error 1 Command output: === BUILD NATIVE TARGET Cosmic Debris OF PROJECT Cosmic Debris WITH CONFIGURATION Deployment === Check dependencies error: There is no SDK with the name or path '/Developer/SDKs/ MacOSX10.4u.sdk' [BEROR]error: There is no SDK with the name or path '/Developer/SDKs/ MacOSX10.4u.sdk' ** BUILD FAILED ** Error: Status 1 encountered during processing. Freedom:~ peterhin$ Many Thanks Peter From blb at macports.org Thu Oct 8 16:34:11 2009 From: blb at macports.org (Bryan Blackburn) Date: Thu, 8 Oct 2009 17:34:11 -0600 Subject: Install Error In-Reply-To: References: Message-ID: <20091008233411.GA65456@ninagal.withay.com> On Thu, Oct 08, 2009 at 07:24:38PM -0400, Peter Hindrichs said: > I am looking to further my understanding and knowledge of the command > line and "Ports" so when I tried to install the port "CosmicDebris" > I got this message. > > I have tried to figure it out, but am having no luck, could someone > please help me to understand what is actually being said here. Could > this have something to do with the fact that the program is not Snow > Leopard compatible or is there another reason ? That's entirely possible since it's wanting to build against the 10.4 SDK which isn't installed by default with Xcode on 10.6 (if I recall correctly). I also note that the current port version is 2.0 while there is an update available, which notes "Version 2.1: Works with Mac OS X 10.5"...someone needs to give the port an update at least. Bryan [...] > " returned error 1 > Command output: > === BUILD NATIVE TARGET Cosmic Debris OF PROJECT Cosmic Debris WITH > CONFIGURATION Deployment === > Check dependencies > error: There is no SDK with the name or path '/Developer/SDKs/ > MacOSX10.4u.sdk' > [BEROR]error: There is no SDK with the name or path '/Developer/SDKs/ > MacOSX10.4u.sdk' > ** BUILD FAILED ** > > > Error: Status 1 encountered during processing. > Freedom:~ peterhin$ > > > Many Thanks > > Peter From LenoreHorner at sbcglobal.net Thu Oct 8 16:37:14 2009 From: LenoreHorner at sbcglobal.net (Lenore Horner) Date: Thu, 8 Oct 2009 18:37:14 -0500 Subject: Install Error In-Reply-To: References: Message-ID: On Oct 8, 2009, at 18:24 , Peter Hindrichs wrote: > I am looking to further my understanding and knowledge of the > command line and "Ports" so when I tried to install the port > "CosmicDebris" I got this message. > > I have tried to figure it out, but am having no luck, could someone > please help me to understand what is actually being said here. Could > this have something to do with the fact that the program is not Snow > Leopard compatible or is there another reason ? > > > > Freedom:~ peterhin$ sudo port install CosmicDebris > Password: > ---> Computing dependencies for CosmicDebris > ---> Fetching CosmicDebris > ---> Attempting to fetch CosmicDebrisSource.zip from http://distfiles.macports.org/CosmicDebris/2.0 > ---> Verifying checksum(s) for CosmicDebris > ---> Extracting CosmicDebris > ---> Configuring CosmicDebris > ---> Building CosmicDebris > Error: Target org.macports.build returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_aqua_CosmicDebris/work/ > CosmicDebrisSource" && /usr/bin/xcodebuild -project "Cosmic > Debris.xcodeproj" -target "Cosmic Debris" -configuration Deployment > " returned error 1 > Command output: > === BUILD NATIVE TARGET Cosmic Debris OF PROJECT Cosmic Debris WITH > CONFIGURATION Deployment === > Check dependencies > error: There is no SDK with the name or path '/Developer/SDKs/ > MacOSX10.4u.sdk' > [BEROR]error: There is no SDK with the name or path '/Developer/SDKs/ > MacOSX10.4u.sdk' > ** BUILD FAILED ** > > > Error: Status 1 encountered during processing. > Freedom:~ peterhin$ > > > Many Thanks > > Peter > I have 10.5 installed on my Mac. I have both /Developer/SDKs/ MacOSX10.4u.sdk and /Developer/SDKs/MacOSX10.5.sdk. I have vague memories that somewhere in installing developer tools I had a choice about installing sdks. Completely naively, I would have expected Snow Leopard developer tools to install 10.4, 10.5, and 10.6 sdks but maybe that doesn't work. If you go back to your installation disk do you have sdk installation options? Lenore -------------- next part -------------- An HTML attachment was scrubbed... URL: From pth at ispnet.ca Thu Oct 8 16:52:03 2009 From: pth at ispnet.ca (Peter Hindrichs) Date: Thu, 8 Oct 2009 19:52:03 -0400 Subject: Install Error In-Reply-To: References: Message-ID: <4F6FBB22-530B-4CA6-B9E4-3E004E7C186C@ispnet.ca> On 2009-10-08, at 19:37 , Lenore Horner wrote: > > On Oct 8, 2009, at 18:24 , Peter Hindrichs wrote: > >> I am looking to further my understanding and knowledge of the >> command line and "Ports" so when I tried to install the port >> "CosmicDebris" I got this message. >> >> I have tried to figure it out, but am having no luck, could someone >> please help me to understand what is actually being said here. >> Could this have something to do with the fact that the program is >> not Snow Leopard compatible or is there another reason ? >> >> >> >> Freedom:~ peterhin$ sudo port install CosmicDebris >> Password: >> ---> Computing dependencies for CosmicDebris >> ---> Fetching CosmicDebris >> ---> Attempting to fetch CosmicDebrisSource.zip from http://distfiles.macports.org/CosmicDebris/2.0 >> ---> Verifying checksum(s) for CosmicDebris >> ---> Extracting CosmicDebris >> ---> Configuring CosmicDebris >> ---> Building CosmicDebris >> Error: Target org.macports.build returned: shell command " cd "/opt/ >> local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_CosmicDebris >> /work/CosmicDebrisSource" && /usr/bin/xcodebuild -project "Cosmic >> Debris.xcodeproj" -target "Cosmic Debris" -configuration >> Deployment " returned error 1 >> Command output: >> === BUILD NATIVE TARGET Cosmic Debris OF PROJECT Cosmic Debris WITH >> CONFIGURATION Deployment === >> Check dependencies >> error: There is no SDK with the name or path '/Developer/SDKs/ >> MacOSX10.4u.sdk' >> [BEROR]error: There is no SDK with the name or path '/Developer/ >> SDKs/MacOSX10.4u.sdk' >> ** BUILD FAILED ** >> >> >> Error: Status 1 encountered during processing. >> Freedom:~ peterhin$ >> >> >> Many Thanks >> >> Peter >> > I have 10.5 installed on my Mac. I have both /Developer/SDKs/ > MacOSX10.4u.sdk and /Developer/SDKs/MacOSX10.5.sdk. I have vague > memories that somewhere in installing developer tools I had a choice > about installing sdks. Completely naively, I would have expected > Snow Leopard developer tools to install 10.4, 10.5, and 10.6 sdks > but maybe that doesn't work. If you go back to your installation > disk do you have sdk installation options? > > Lenore I checked the Install disk and I could not find any reference to sdk under optional installs. Peter -------------- next part -------------- An HTML attachment was scrubbed... URL: From dweber at macports.org Thu Oct 8 18:09:20 2009 From: dweber at macports.org (Darren Weber) Date: Thu, 8 Oct 2009 18:09:20 -0700 Subject: cvs2svn dependencies In-Reply-To: References: Message-ID: On Thu, Oct 8, 2009 at 4:23 PM, Daniel J. Luke wrote: > On Oct 8, 2009, at 7:11 PM, Darren Weber wrote: > >> With reference to this page: >> http://cvs2svn.tigris.org/cvs2svn.html >> >> There are various run-time dependencies indicated under the title of >> "Requirements". Are any of these included as dependencies in the MacPorts >> cvs2svn port? (I don't see any.) >> > > That page lists > > 1- python (which is a port dependency) > 2- db library and python bindings (python26 port builds with db46 and gdbm > already) > 3- gnu sort (comes with mac os x) > > optionally can use rcs or cvs if you pass in appropriate options (and you > can pass the path to those binaries). both cvs and rcs are included with Mac > OS X (or you could install a macports version if you wanted and point > cvs2svn to them). > > did you notice something broken? > No, I just couldn't find 'cvs2svn' in the default bin path. Then looking over the web page indicated earlier it appeared that some dependencies were not specified, but you clarified all that above. I guess it wouldn't hurt to specify build or lib dependencies on 'gdbm' and 'coreutils' (but coreutils can install with a 'g' prefix such as /opt/local/bin/gsort and it's unlikely that cvs2svn will look for that). > > Also, is it possible to have a symlink or hardlink: >> >> /opt/local/bin/cvs2svn -> >> /opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin/cvs2svn >> > > cvs2svn used to install to ${prefix}/bin but the python26 portgroup sets > prefix to ${frameworks_dir}/Python.framework/Versions/2.6 > > presumably this is so that one could install a cvs2svn against python26 and > one against another version of python... > > Linking cvs2bzr, cvs2git, and cvs2svn to ${prefix}/bin would be one > possible solution ... > Oh, I see. (Maybe they should be using $pyPrefix to avoid a clash with the general MacPorts $prefix?) I now have a bash alias as a personal work-around: alias cvs2svn='/opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin/cvs2svn' Thanks! Darren -------------- next part -------------- An HTML attachment was scrubbed... URL: From luomo1138 at yahoo.com Thu Oct 8 18:11:43 2009 From: luomo1138 at yahoo.com (Dexter Douglas) Date: Thu, 8 Oct 2009 18:11:43 -0700 (PDT) Subject: realpath failed -- error uninstalling ports In-Reply-To: <657598.29962.qm@web65605.mail.ac4.yahoo.com> Message-ID: <535661.45764.qm@web65608.mail.ac4.yahoo.com> Hello, I still have this problem on my PowerBook G4, but I do not have this problem on my Intel-based MacBook Pro (Snow Leopard). Does anyone know what realpath is? I am not sure how to track this problem down. Thanks. --- On Fri, 10/2/09, Dexter Douglas wrote: > From: Dexter Douglas > Subject: Re: realpath failed -- error uninstalling ports > To: "Ryan Schmidt" > Cc: macports-users at lists.macosforge.org > Date: Friday, October 2, 2009, 7:31 PM > Hello, > > I am sorry.? I left out ALL the important information. > > I am running Leopard on a PowerBook G4; Xcode 3.1.2; > macports 1.8.1. > > "port uninstall" was working just fine until 1 Oct.? That > is when I performed a selfupdate to 1.8.1 and then upgraded > all my outdated ports. > > After the upgrade, I tried to clean up by uninstalling the > inactive ports.? That is when I got the error message. > > I have two most likely unrelated pieces of information. > 1) During the upgrading, doxygen failed to compile.? I > ended up uninstalling and trying to reinstall.? I was not > able to reinstall doxygen.? 2) I suffered from the > "MacPorts 1.8.0 deletes ${prefix} if it is a symlink" > problem (http://trac.macports.org/ticket/21082). > > Thanks. > > > > --- On Fri, 10/2/09, Ryan Schmidt > wrote: > > > From: Ryan Schmidt > > Subject: Re: realpath failed -- error uninstalling > ports > > To: "Dexter Douglas" > > Cc: macports-users at lists.macosforge.org > > Date: Friday, October 2, 2009, 12:11 AM > > > > On Oct 1, 2009, at 22:27, Dexter Douglas wrote: > > > > > I get this error message when I try to uninstall > > inactive ports: > > > > > > Error: port uninstall failed: realpath failed: No > such > > file or directory > > > > > > Does anyone know what this means? > > > > This happens on every port? Has it always been this > way or > > did it recently start? If the latter, what changed? > > > > What version of Mac OS X, Xcode, MacPorts? What Mac? > > > > > > > > > > ? ? ? > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > From ryandesign at macports.org Thu Oct 8 19:00:15 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 8 Oct 2009 21:00:15 -0500 Subject: Install Error In-Reply-To: <4F6FBB22-530B-4CA6-B9E4-3E004E7C186C@ispnet.ca> References: <4F6FBB22-530B-4CA6-B9E4-3E004E7C186C@ispnet.ca> Message-ID: <61137A66-9327-4ECE-B085-E7919AE43A7F@macports.org> On Oct 8, 2009, at 18:52, Peter Hindrichs wrote: > On 2009-10-08, at 19:37 , Lenore Horner wrote: > >> I have 10.5 installed on my Mac. I have both /Developer/SDKs/ >> MacOSX10.4u.sdk and /Developer/SDKs/MacOSX10.5.sdk. I have vague >> memories that somewhere in installing developer tools I had a >> choice about installing sdks. Completely naively, I would have >> expected Snow Leopard developer tools to install 10.4, 10.5, and >> 10.6 sdks but maybe that doesn't work. If you go back to your >> installation disk do you have sdk installation options? >> > > I checked the Install disk and I could not find any reference to sdk > under optional installs. The 10.4u SDK is an optional not-installed-by-default option, in the Xcode 3.2 installer. I specifically remember seeing it and selecting it. From ryandesign at macports.org Thu Oct 8 19:28:29 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 8 Oct 2009 21:28:29 -0500 Subject: cvs2svn dependencies In-Reply-To: References: Message-ID: On Oct 8, 2009, at 18:23, Daniel J. Luke wrote: > On Oct 8, 2009, at 7:11 PM, Darren Weber wrote: > >> With reference to this page: >> http://cvs2svn.tigris.org/cvs2svn.html >> >> There are various run-time dependencies indicated under the title >> of "Requirements". Are any of these included as dependencies in >> the MacPorts cvs2svn port? (I don't see any.) > > That page lists > > 1- python (which is a port dependency) > 2- db library and python bindings (python26 port builds with db46 > and gdbm already) > 3- gnu sort (comes with mac os x) > > optionally can use rcs or cvs if you pass in appropriate options > (and you can pass the path to those binaries). both cvs and rcs are > included with Mac OS X (or you could install a macports version if > you wanted and point cvs2svn to them). > > did you notice something broken? > >> Also, is it possible to have a symlink or hardlink: >> >> /opt/local/bin/cvs2svn -> /opt/local/Library/Frameworks/ >> Python.framework/Versions/2.6/bin/cvs2svn > > cvs2svn used to install to ${prefix}/bin but the python26 portgroup > sets prefix to ${frameworks_dir}/Python.framework/Versions/2.6 > > presumably this is so that one could install a cvs2svn against > python26 and one against another version of python... > > Linking cvs2bzr, cvs2git, and cvs2svn to ${prefix}/bin would be one > possible solution ... It sounds like a good solution to me. Probably this difference between the python25 and python26 portgroups was just not considered when updating the port to use python26 in r56139. From pth at ispnet.ca Thu Oct 8 19:50:51 2009 From: pth at ispnet.ca (Peter Hindrichs) Date: Thu, 8 Oct 2009 22:50:51 -0400 Subject: Install Error In-Reply-To: <61137A66-9327-4ECE-B085-E7919AE43A7F@macports.org> References: <4F6FBB22-530B-4CA6-B9E4-3E004E7C186C@ispnet.ca> <61137A66-9327-4ECE-B085-E7919AE43A7F@macports.org> Message-ID: On 2009-10-08, at 22:00 , Ryan Schmidt wrote: > On Oct 8, 2009, at 18:52, Peter Hindrichs wrote: > >> On 2009-10-08, at 19:37 , Lenore Horner wrote: >> >>> I have 10.5 installed on my Mac. I have both /Developer/SDKs/ >>> MacOSX10.4u.sdk and /Developer/SDKs/MacOSX10.5.sdk. I have vague >>> memories that somewhere in installing developer tools I had a >>> choice about installing sdks. Completely naively, I would have >>> expected Snow Leopard developer tools to install 10.4, 10.5, and >>> 10.6 sdks but maybe that doesn't work. If you go back to your >>> installation disk do you have sdk installation options? >>> >> >> I checked the Install disk and I could not find any reference to >> sdk under optional installs. > > The 10.4u SDK is an optional not-installed-by-default option, in the > Xcode 3.2 installer. I specifically remember seeing it and selecting > it. > > OK I found 10.4u SDK and installed it. This is what I get now when I try to do the install: Freedom:~ peterhin$ sudo port install CosmicDebris Password: ---> Computing dependencies for CosmicDebris ---> Building CosmicDebris Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_CosmicDebris /work/CosmicDebrisSource" && /usr/bin/xcodebuild -project "Cosmic Debris.xcodeproj" -target "Cosmic Debris" -configuration Deployment " returned error 1 Command output: === BUILD NATIVE TARGET Cosmic Debris OF PROJECT Cosmic Debris WITH CONFIGURATION Deployment === Check dependencies GCC 4.2 is not compatible with the Mac OS X 10.4 SDK (file main.m) GCC 4.2 is not compatible with the Mac OS X 10.4 SDK (file main.m) ** BUILD FAILED ** Error: Status 1 encountered during processing. Freedom:~ peterhin$ Do the last few lines indicate that I need to get an earlier version of Gcc ? Peter From ryandesign at macports.org Thu Oct 8 19:52:25 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 8 Oct 2009 21:52:25 -0500 Subject: Install Error In-Reply-To: References: <4F6FBB22-530B-4CA6-B9E4-3E004E7C186C@ispnet.ca> <61137A66-9327-4ECE-B085-E7919AE43A7F@macports.org> Message-ID: On Oct 8, 2009, at 21:50, Peter Hindrichs wrote: > OK I found 10.4u SDK and installed it. This is what I get now when I > try to do the install: > > Freedom:~ peterhin$ sudo port install CosmicDebris > Password: > ---> Computing dependencies for CosmicDebris > ---> Building CosmicDebris > Error: Target org.macports.build returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_CosmicDebris > /work/CosmicDebrisSource" && /usr/bin/xcodebuild -project "Cosmic > Debris.xcodeproj" -target "Cosmic Debris" -configuration Deployment > " returned error 1 > Command output: > === BUILD NATIVE TARGET Cosmic Debris OF PROJECT Cosmic Debris WITH > CONFIGURATION Deployment === > Check dependencies > GCC 4.2 is not compatible with the Mac OS X 10.4 SDK (file main.m) > GCC 4.2 is not compatible with the Mac OS X 10.4 SDK (file main.m) > ** BUILD FAILED ** > > > Error: Status 1 encountered during processing. > Freedom:~ peterhin$ > > Do the last few lines indicate that I need to get an earlier version > of Gcc ? You already have gcc-4.0 installed, in addition to the gcc-4.2 which is now the default. The message indicates this software has not been tested on Snow Leopard, clearly. You could try adding the line "configure.compiler gcc-4.0" to the portfile, but no guarantee there won't be other problems. If you find out how to make it work, please let us know so we can update the portfile. From pth at ispnet.ca Thu Oct 8 20:01:31 2009 From: pth at ispnet.ca (Peter Hindrichs) Date: Thu, 8 Oct 2009 23:01:31 -0400 Subject: Install Error In-Reply-To: References: <4F6FBB22-530B-4CA6-B9E4-3E004E7C186C@ispnet.ca> <61137A66-9327-4ECE-B085-E7919AE43A7F@macports.org> Message-ID: <0D3FC285-0322-4BEC-AF04-0ADEC25FFB00@ispnet.ca> On 2009-10-08, at 22:52 , Ryan Schmidt wrote: > > On Oct 8, 2009, at 21:50, Peter Hindrichs wrote: > >> OK I found 10.4u SDK and installed it. This is what I get now when >> I try to do the install: >> >> Freedom:~ peterhin$ sudo port install CosmicDebris >> Password: >> ---> Computing dependencies for CosmicDebris >> ---> Building CosmicDebris >> Error: Target org.macports.build returned: shell command " cd "/opt/ >> local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_CosmicDebris >> /work/CosmicDebrisSource" && /usr/bin/xcodebuild -project "Cosmic >> Debris.xcodeproj" -target "Cosmic Debris" -configuration >> Deployment " returned error 1 >> Command output: >> === BUILD NATIVE TARGET Cosmic Debris OF PROJECT Cosmic Debris WITH >> CONFIGURATION Deployment === >> Check dependencies >> GCC 4.2 is not compatible with the Mac OS X 10.4 SDK (file main.m) >> GCC 4.2 is not compatible with the Mac OS X 10.4 SDK (file main.m) >> ** BUILD FAILED ** >> >> >> Error: Status 1 encountered during processing. >> Freedom:~ peterhin$ >> >> Do the last few lines indicate that I need to get an earlier >> version of Gcc ? > > You already have gcc-4.0 installed, in addition to the gcc-4.2 which > is now the default. The message indicates this software has not been > tested on Snow Leopard, clearly. You could try adding the line > "configure.compiler gcc-4.0" to the portfile, but no guarantee there > won't be other problems. If you find out how to make it work, please > let us know so we can update the portfile. > > > Thanks for the info. This is starting to get way over my head, but I shall keep at it a little longer. I did find this note in the Xcode Release notes: Note: GCC 4.2 cannot be used with the Mac OS X 10.4u SDK. If you want to build targets using the 10.4u SDK on Xcode 3.2, you must set the Compiler Version to GCC 4.0 Not sure how to set the compiler version Peter -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Thu Oct 8 20:02:28 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 8 Oct 2009 22:02:28 -0500 Subject: Install Error In-Reply-To: <0D3FC285-0322-4BEC-AF04-0ADEC25FFB00@ispnet.ca> References: <4F6FBB22-530B-4CA6-B9E4-3E004E7C186C@ispnet.ca> <61137A66-9327-4ECE-B085-E7919AE43A7F@macports.org> <0D3FC285-0322-4BEC-AF04-0ADEC25FFB00@ispnet.ca> Message-ID: <3D32CB25-6EDC-4CDD-97CD-BB23839AFB20@macports.org> On Oct 8, 2009, at 22:01, Peter Hindrichs wrote: > I did find this note in the Xcode Release notes: > Note: GCC 4.2 cannot be used with the Mac OS X 10.4u SDK. If you > want to build targets using the 10.4u SDK on Xcode 3.2, you must set > the Compiler Version to GCC 4.0 > Not sure how to set the compiler version By adding the line "configure.compiler gcc-4.0" to the portfile. From francisco.licea at gmail.com Thu Oct 8 20:17:44 2009 From: francisco.licea at gmail.com (Frank Licea) Date: Thu, 8 Oct 2009 21:17:44 -0600 Subject: How do I apply a patch for a failed macport install? Message-ID: <8eb39ac50910082017h60e46e79n2100807db7e88c@mail.gmail.com> Hello, The macport for sbcl failed when I tried to install it. I found the SnowLeopard issues wiki and it supplies some patches that can be applied to make-config.sh and Portfile. http://trac.macports.org/ticket/20904 I know how to apply a patch to make-config.org but I don't know how to apply to to Portfile. Where is this file located for sbcl? I also wonder how to "restart" the install not from the fetch phase but from the build phase once I have patched the necessary files. Will installing the ports in this manner somehow screw up my macports install? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dluke at geeklair.net Thu Oct 8 20:29:32 2009 From: dluke at geeklair.net (Daniel J. Luke) Date: Thu, 8 Oct 2009 23:29:32 -0400 Subject: cvs2svn dependencies In-Reply-To: References: Message-ID: On Oct 8, 2009, at 10:28 PM, Ryan Schmidt wrote: >> Linking cvs2bzr, cvs2git, and cvs2svn to ${prefix}/bin would be one >> possible solution ... > > It sounds like a good solution to me. Probably this difference > between the python25 and python26 portgroups was just not considered > when updating the port to use python26 in r56139. symlinks added in r59060 -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ From ryandesign at macports.org Thu Oct 8 20:29:47 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 8 Oct 2009 22:29:47 -0500 Subject: How do I apply a patch for a failed macport install? In-Reply-To: <8eb39ac50910082017h60e46e79n2100807db7e88c@mail.gmail.com> References: <8eb39ac50910082017h60e46e79n2100807db7e88c@mail.gmail.com> Message-ID: On Oct 8, 2009, at 22:17, Frank Licea wrote: > The macport for sbcl failed when I tried to install it. I found the > SnowLeopard issues wiki and it supplies some patches that can be > applied to make-config.sh and Portfile. > > http://trac.macports.org/ticket/20904 > > I know how to apply a patch to make-config.org but I don't know how > to apply to to Portfile. Where is this file located for sbcl? The command "port file sbcl" tells you where sbcl's portfile is located. > I also wonder how to "restart" the install not from the fetch phase > but from the build phase once I have patched the necessary files. If you modify the portfile, MacPorts will notice and clean the work area and start again. The distfile will not need to be fetched again because it was already fetched and is not stored in the work area but in the distfiles area. > Will installing the ports in this manner somehow screw up my > macports install? No, it's fine. Note that assuming your ports directory is synced using rsync, as it is by default, any changes you make to its contents will be wiped out when you next "sudo port sync". From domiman at gmail.com Thu Oct 8 22:20:33 2009 From: domiman at gmail.com (Dominik Reichardt) Date: Fri, 9 Oct 2009 07:20:33 +0200 Subject: More KDE4 madness In-Reply-To: <6C47BD97-91EE-4D1D-A831-F2F9F90866E7@gmail.com> References: <6C47BD97-91EE-4D1D-A831-F2F9F90866E7@gmail.com> Message-ID: <334D58DE-8BEB-4D21-B31A-2FAEC66CC7A5@gmail.com> Am 08.10.2009 um 22:15 schrieb Dominik Reichardt: > I'm still trying to build Krusader on Snow Leopard. > yesterday and today some port updates landed that *should* make it > possible. It all compiled now but kdeinit crashes on every start. The error report states something about USING_FORK_WITHOUT_EXEC_IS_NOT_SUPPORTED_BY_FILE_MANAGER Does this work for anyone else at the moment? Thanks Dom -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmr at macports.org Thu Oct 8 23:33:15 2009 From: jmr at macports.org (Joshua Root) Date: Fri, 09 Oct 2009 17:33:15 +1100 Subject: realpath failed -- error uninstalling ports In-Reply-To: <535661.45764.qm@web65608.mail.ac4.yahoo.com> References: <535661.45764.qm@web65608.mail.ac4.yahoo.com> Message-ID: <4ACED92B.6040504@macports.org> On 2009-10-9 12:11, Dexter Douglas wrote: > Hello, > > I still have this problem on my PowerBook G4, but I do not have this problem on my Intel-based MacBook Pro (Snow Leopard). > > Does anyone know what realpath is? I am not sure how to track this problem down. Basically we need to know which file doesn't exist. Adding something like: ui_debug "getting realpath for $theFile" to portuninstall.tcl just above line 199 would produce this information. - Josh From jmr at macports.org Fri Oct 9 00:14:21 2009 From: jmr at macports.org (Joshua Root) Date: Fri, 09 Oct 2009 18:14:21 +1100 Subject: Install Error In-Reply-To: References: Message-ID: <4ACEE2CD.6040908@macports.org> On 2009-10-9 10:24, Peter Hindrichs wrote: > I am looking to further my understanding and knowledge of the command > line and "Ports" so when I tried to install the port "CosmicDebris" I > got this message. > > I have tried to figure it out, but am having no luck, could someone > please help me to understand what is actually being said here. Could > this have something to do with the fact that the program is not Snow > Leopard compatible or is there another reason ? The port is in much better shape now that it has been updated to version 2.1 and is using the xcode portgroup. It still uses NSMailDelivery which is not available when building 64-bit, so I've restricted the port to building 32-bit until upstream fixes this. - Josh From pth at ispnet.ca Fri Oct 9 04:02:23 2009 From: pth at ispnet.ca (Peter Hindrichs) Date: Fri, 9 Oct 2009 07:02:23 -0400 Subject: Install Error In-Reply-To: <3D32CB25-6EDC-4CDD-97CD-BB23839AFB20@macports.org> References: <4F6FBB22-530B-4CA6-B9E4-3E004E7C186C@ispnet.ca> <61137A66-9327-4ECE-B085-E7919AE43A7F@macports.org> <0D3FC285-0322-4BEC-AF04-0ADEC25FFB00@ispnet.ca> <3D32CB25-6EDC-4CDD-97CD-BB23839AFB20@macports.org> Message-ID: <6544F8F6-5197-4427-9FE0-EB7AB94AC830@ispnet.ca> On 2009-10-08, at 23:02 , Ryan Schmidt wrote: > > On Oct 8, 2009, at 22:01, Peter Hindrichs wrote: > >> I did find this note in the Xcode Release notes: >> Note: GCC 4.2 cannot be used with the Mac OS X 10.4u SDK. If you >> want to build targets using the 10.4u SDK on Xcode 3.2, you must >> set the Compiler Version to GCC 4.0 >> Not sure how to set the compiler version > > By adding the line "configure.compiler gcc-4.0" to the portfile. > > I have read through section 4 of the MacPorts Guide, and am at a loss as to how I access the portfile for "CosmicDebris" assuming that this is what is meant by the portfile. Thanks Peter From pth at ispnet.ca Fri Oct 9 06:22:03 2009 From: pth at ispnet.ca (Peter Hindrichs) Date: Fri, 9 Oct 2009 09:22:03 -0400 Subject: Install Error In-Reply-To: <3D32CB25-6EDC-4CDD-97CD-BB23839AFB20@macports.org> References: <4F6FBB22-530B-4CA6-B9E4-3E004E7C186C@ispnet.ca> <61137A66-9327-4ECE-B085-E7919AE43A7F@macports.org> <0D3FC285-0322-4BEC-AF04-0ADEC25FFB00@ispnet.ca> <3D32CB25-6EDC-4CDD-97CD-BB23839AFB20@macports.org> Message-ID: <8DCB846D-001B-4DE7-9A6F-CC334ABF02D4@ispnet.ca> On 2009-10-08, at 23:02 , Ryan Schmidt wrote: > > On Oct 8, 2009, at 22:01, Peter Hindrichs wrote: > >> I did find this note in the Xcode Release notes: >> Note: GCC 4.2 cannot be used with the Mac OS X 10.4u SDK. If you >> want to build targets using the 10.4u SDK on Xcode 3.2, you must >> set the Compiler Version to GCC 4.0 >> Not sure how to set the compiler version > > By adding the line "configure.compiler gcc-4.0" to the portfile. > > Upon further reading and some experimenting I have found via Spotlight the portfile for CosmicDebris, and opened it with TextEdit. I tried to add the line suggested, however it won't let me save it. I haven't got write privileges. I must be able to do this on the command line with sudo but I am at a loss. Any help would be appreciated. Peter From pth at ispnet.ca Fri Oct 9 06:44:18 2009 From: pth at ispnet.ca (Peter Hindrichs) Date: Fri, 9 Oct 2009 09:44:18 -0400 Subject: Install Error In-Reply-To: <3D32CB25-6EDC-4CDD-97CD-BB23839AFB20@macports.org> References: <4F6FBB22-530B-4CA6-B9E4-3E004E7C186C@ispnet.ca> <61137A66-9327-4ECE-B085-E7919AE43A7F@macports.org> <0D3FC285-0322-4BEC-AF04-0ADEC25FFB00@ispnet.ca> <3D32CB25-6EDC-4CDD-97CD-BB23839AFB20@macports.org> Message-ID: On 2009-10-08, at 23:02 , Ryan Schmidt wrote: > > On Oct 8, 2009, at 22:01, Peter Hindrichs wrote: > >> I did find this note in the Xcode Release notes: >> Note: GCC 4.2 cannot be used with the Mac OS X 10.4u SDK. If you >> want to build targets using the 10.4u SDK on Xcode 3.2, you must >> set the Compiler Version to GCC 4.0 >> Not sure how to set the compiler version > > By adding the line "configure.compiler gcc-4.0" to the portfile. > > First I must apologize for the excessive e-mails prior to doing further research on my part. I have been able to get the "CosmicDebris" portfile open with "TextWrangler" and insert the "configure.compiler gcc-4.0" and save the file. The result is the same when I try to install "CosmicDebris". If I read correctly what Joshua Root wrote, then I am out of luck till a 64-bit update is built. I still have the question how would I get to the portfile via the command line, this is still puzzling. Thank you though, for your patience regarding what must be very basic and obvious to all of you. I am learning more each day and that is my goal here, to be more conversant with using the command line. Peter From dave at difference.com.au Fri Oct 9 08:49:26 2009 From: dave at difference.com.au (David Cake) Date: Fri, 9 Oct 2009 23:49:26 +0800 Subject: apr-util not building because it can't find db Message-ID: Everytime I issue port upgrade outdated, it tries to build apr-util, and fails with configure: error: Berkeley DB not found. db46 is installed, but the apr-util build just doesn't seem to believe it is there. Any advice? Regards David From listsub at systame.com Fri Oct 9 10:32:25 2009 From: listsub at systame.com (Randall Perry) Date: Fri, 09 Oct 2009 13:32:25 -0400 Subject: Error building python26 on ppc, Tiger Message-ID: Here's my setup Xserve 2Ghz DP G5 OSXS 10.4.11 Macports 1.8.1 gcc 4.0 (also tried 3.3 & got same error) Here's the error /usr/bin/gcc-4.0 -o hacklocaledir.so -fPIC -bundle hacklocaledir.c hacklocaledir.c: In function '__open': hacklocaledir.c:44: error: 'RTLD_NEXT' undeclared (first use in this function) hacklocaledir.c:44: error: (Each undeclared identifier is reported only once hacklocaledir.c:44: error: for each function it appears in.) hacklocaledir.c: At top level: hacklocaledir.c:113: warning: alias definitions not supported in Mach-O; ignored make: *** [hacklocaledir.so] Error 1 Error: The following dependencies failed to build: tk xorg-libXScrnSaver xorg-libXext xorg-libX11 autoconf help2man m4 automake libtool xorg-bigreqsproto xorg-inputproto xorg-kbproto xorg-libXau xorg-libXdmcp xorg-util-macros xorg-xcmiscproto xorg-xextproto xorg-xf86bigfontproto xorg-xtrans xorg-scrnsaverproto Error: Status 1 encountered during processing. Looks like it might night be python that's the issue, but one or more of the dependencies? -- Randall Perry From abe.gillespie.lists at gmail.com Fri Oct 9 11:19:34 2009 From: abe.gillespie.lists at gmail.com (Abram Gillespie) Date: Fri, 9 Oct 2009 14:19:34 -0400 Subject: Install error of postgres84 + leopard Message-ID: <283a65ca0910091119v6a5c7b4do3827aff2d17d924f@mail.gmail.com> I'm getting this: configure: error: library 'ossp-uuid' or 'uuid' is required for OSSP-UUID I found something to try within the comments of this post: http://www.robbyonrails.com/articles/2008/01/22/installing-ruby-on-rails-and-postgresql-on-os-x-third-edition (look for njakobsen) But after doing so I was still getting the same thing. Any ideas? Thanks. -Abe From abe.gillespie.lists at gmail.com Fri Oct 9 12:07:00 2009 From: abe.gillespie.lists at gmail.com (Abram Gillespie) Date: Fri, 9 Oct 2009 15:07:00 -0400 Subject: Install error of postgres84 + leopard In-Reply-To: <283a65ca0910091119v6a5c7b4do3827aff2d17d924f@mail.gmail.com> References: <283a65ca0910091119v6a5c7b4do3827aff2d17d924f@mail.gmail.com> Message-ID: <283a65ca0910091207u6de21ce0gd62b86c502f47c22@mail.gmail.com> OK, so doing an uninstall and reinstall fixed the issue, though I suspect the steps I did from the previously-mentioned post may have helped. -Abe On Fri, Oct 9, 2009 at 2:19 PM, Abram Gillespie wrote: > I'm getting this: > > configure: error: library 'ossp-uuid' or 'uuid' is required for OSSP-UUID > > I found something to try within the comments of this post: > http://www.robbyonrails.com/articles/2008/01/22/installing-ruby-on-rails-and-postgresql-on-os-x-third-edition > (look for njakobsen) > > But after doing so I was still getting the same thing. > > Any ideas? > > Thanks. > -Abe > From abe.gillespie.lists at gmail.com Fri Oct 9 12:10:01 2009 From: abe.gillespie.lists at gmail.com (Abram Gillespie) Date: Fri, 9 Oct 2009 15:10:01 -0400 Subject: PostGIS / libproj Issues Message-ID: <283a65ca0910091210o751fcf7flb7cfebab133ee766@mail.gmail.com> I'm getting an error when installing PostGIS. Note that "ls /opt/local/lib/*proj*" gives me this: /opt/local/lib/libproj.0.5.5.dylib /opt/local/lib/libproj.dylib /opt/local/lib/libproj.0.dylib /opt/local/lib/libproj.la /opt/local/lib/libproj.a The error is: configure: error: could not find libproj - you may need to specify the directory of a PROJ.4 installation using --with-projdir Thanks. -Abe OS X Leopard / 10.6.1 From allbery at kf8nh.com Fri Oct 9 14:00:50 2009 From: allbery at kf8nh.com (Brandon Allbery) Date: Fri, 9 Oct 2009 17:00:50 -0400 Subject: Install Error In-Reply-To: References: <4F6FBB22-530B-4CA6-B9E4-3E004E7C186C@ispnet.ca> <61137A66-9327-4ECE-B085-E7919AE43A7F@macports.org> <0D3FC285-0322-4BEC-AF04-0ADEC25FFB00@ispnet.ca> <3D32CB25-6EDC-4CDD-97CD-BB23839AFB20@macports.org> Message-ID: On Oct 9, 2009, at 09:44 , Peter Hindrichs wrote: > I still have the question how would I get to the portfile via the > command line, this is still puzzling. mress:23478 Z$ port file CosmicDebris /opt/local/var/macports/sources/rsync.macports.org/release/ports/aqua/ CosmicDebris/Portfile (which was mentioned earlier in this thread) Also, TextWrangler should be able to tell you the full path; for a GUI editor it's fairly CLI friendly. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery at kf8nh.com system administrator [openafs,heimdal,too many hats] allbery at ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part URL: From dluke at geeklair.net Fri Oct 9 14:03:02 2009 From: dluke at geeklair.net (Daniel J. Luke) Date: Fri, 9 Oct 2009 17:03:02 -0400 Subject: apr-util not building because it can't find db In-Reply-To: References: Message-ID: <14DC9D71-258C-478A-86FC-D1D5CDFB6992@geeklair.net> On Oct 9, 2009, at 11:49 AM, David Cake wrote: > Everytime I issue port upgrade outdated, it tries to build apr- > util, and fails with > configure: error: Berkeley DB not found. > db46 is installed, but the apr-util build just doesn't seem to > believe it is there. > Any advice? are you sure your db46 port is happy/healthy? You could try uninstalling/cleaning/reinstalling it, then cleaning apr- util and see if it works then? Otherwise posting the port -dv upgrade apr-util output (or opening a bug with it attached) would be the next step in helping to troubleshoot it. -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ From domiman at gmail.com Fri Oct 9 15:16:29 2009 From: domiman at gmail.com (Dominik Reichardt) Date: Sat, 10 Oct 2009 00:16:29 +0200 Subject: manually building Dosbox CVS in 32-bit Message-ID: <602049A9-527F-4637-9D75-96EE86EF69FC@gmail.com> Hi all, I'm wondering how to build Dosbox CVS in 32-bit. If I edit the port file of dosbox by adding if {$build_arch == "x86_64"} { configure.build_arch i386 } elseif {$build_arch == "ppc64"} { configure.build_arch ppc } if {[variant_isset universal] && [string match *64* $universal_archs]} { pre-fetch { return -code error "$name $version cannot be built for 64-bit architectures" } } and commenting out #platform darwin { # configure.args-append --build=${build_arch}-apple-darwin${os.major} #} stopping the port install process in configuring and then overwriting the 0.73 release source with the CVS and then starting port install dosbox again, I am able to build a 32-bit Dosbox CVS that is stable and doesn't crash when switching to dynamic core (like the 64-bit version properly built by MacPorts does). So that is working by tricking MacPort but I'm wondering how to do that manually. I've tried with configuring dosbox with ./configure -build=i386-apple-darwin10.0.0 --target=i386-apple- darwin10 --prefix=/opt/local --disable-sdltest --disable-alsatest but that didn't work and has the same compile errors that the MacPorts port had before the last patch. So I'm obviously missing something that MacPorts does right when I use the above trick to build Dosbox in 32-bit. What is it? Can anyone help me? Dominik P.S.: Dosbox CVS still needs the midi_coreaudio.h patch that MacPorts does and in src/hardware/serialport/libserial.cpp you need to exchange #include with #include (line 260) - just as an help to anyone trying their hand on the cvs as well. I've reported both issues to the Dosbox developers. From ryandesign at macports.org Fri Oct 9 15:30:59 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 9 Oct 2009 17:30:59 -0500 Subject: Error building python26 on ppc, Tiger In-Reply-To: References: Message-ID: <9AB0970C-68DD-4672-B09E-74B36A31DF18@macports.org> On Oct 9, 2009, at 12:32, Randall Perry wrote: > hacklocaledir.c:44: error: 'RTLD_NEXT' undeclared (first use in this > function) Google searching this error I see: http://www.macgeek.co.za/2009/05/11/compliation-of-package-x-failed-rtld_next-undeclared/ Do you have /usr/local/include/dlfcn.h? Stuff in /usr/local interferes with MacPorts and I recommend you remove anything you have there. From ryandesign at macports.org Fri Oct 9 15:31:43 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 9 Oct 2009 17:31:43 -0500 Subject: PostGIS / libproj Issues In-Reply-To: <283a65ca0910091210o751fcf7flb7cfebab133ee766@mail.gmail.com> References: <283a65ca0910091210o751fcf7flb7cfebab133ee766@mail.gmail.com> Message-ID: On Oct 9, 2009, at 14:10, Abram Gillespie wrote: > I'm getting an error when installing PostGIS. Note that "ls > /opt/local/lib/*proj*" gives me this: > > /opt/local/lib/libproj.0.5.5.dylib /opt/local/lib/libproj.dylib > /opt/local/lib/libproj.0.dylib /opt/local/lib/libproj.la > /opt/local/lib/libproj.a > > The error is: > configure: error: could not find libproj - you may need to specify the > directory of a PROJ.4 installation using --with-projdir > > Thanks. > -Abe > OS X Leopard / 10.6.1 Please file a ticket in the issue tracker and provide more information including the full debug output of your attempted installation. From ryandesign at macports.org Fri Oct 9 15:34:31 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 9 Oct 2009 17:34:31 -0500 Subject: manually building Dosbox CVS in 32-bit In-Reply-To: <602049A9-527F-4637-9D75-96EE86EF69FC@gmail.com> References: <602049A9-527F-4637-9D75-96EE86EF69FC@gmail.com> Message-ID: On Oct 9, 2009, at 17:16, Dominik Reichardt wrote: > I'm wondering how to build Dosbox CVS in 32-bit. If I edit the port > file of dosbox by adding > > if {$build_arch == "x86_64"} { > configure.build_arch i386 > } elseif {$build_arch == "ppc64"} { > configure.build_arch ppc > } > if {[variant_isset universal] && [string match *64* > $universal_archs]} { > pre-fetch { > return -code error "$name $version cannot be built for 64-bit > architectures" > } > } > > > and commenting out > > #platform darwin { > # configure.args-append --build=${build_arch}-apple-darwin$ > {os.major} > #} > > stopping the port install process in configuring and then > overwriting the 0.73 release source with the CVS and then starting > port install dosbox again, I am able to build a 32-bit Dosbox CVS > that is stable and doesn't crash when switching to dynamic core > (like the 64-bit version properly built by MacPorts does). > > So that is working by tricking MacPort but I'm wondering how to do > that manually. > > I've tried with configuring dosbox with > ./configure -build=i386-apple-darwin10.0.0 --target=i386-apple- > darwin10 --prefix=/opt/local --disable-sdltest --disable-alsatest > but that didn't work and has the same compile errors that the > MacPorts port had before the last patch. So I'm obviously missing > something that MacPorts does right when I use the above trick to > build Dosbox in 32-bit. > What is it? Can anyone help me? You're probably missing the "-arch i386" flags MacPorts adds to various environment variables. Use "sudo port -d configure dosbox" and examine the line beginning with "DEBUG: Environment:" to see all the environment variables MacPorts sets for you. > P.S.: Dosbox CVS still needs the midi_coreaudio.h patch that > MacPorts does and in src/hardware/serialport/libserial.cpp you need > to exchange #include with #include (line 260) > - just as an help to anyone trying their hand on the cvs as well. > I've reported both issues to the Dosbox developers. From rppass at rppass.com Fri Oct 9 17:47:12 2009 From: rppass at rppass.com (Ralph Pass) Date: Fri, 09 Oct 2009 20:47:12 -0400 Subject: MacPorts 1.8.1 has been released In-Reply-To: <20090929212502.GL471@ninagal.withay.com> References: <4AC14BA8.8090807@macports.org> <4AC26FF3.5080803@rppass.com> <4AC2727A.1070604@rppass.com> <20090929212502.GL471@ninagal.withay.com> Message-ID: <4ACFD990.80708@rppass.com> I have now done a sudo port selfupdate on two more Macs running Snow Leopard: One a Macbook Pro that is about 30 months old and an iMac that was purchased a month ago. Both times it worked and the sudo port update outdated did as well. The only problem machine was a Macbook Pro purchased four months ago. I guess the only solution is to remove Macports and reinstall. Ralph Pass Bryan Blackburn wrote: > On Tue, Sep 29, 2009 at 04:47:54PM -0400, Ralph Pass said: > >> More information: >> >> doing a lipo -info /Libary/Tcl/macports1.0/Macports.dylib shows that >> on the system that works, the architecture is x86_64 and on the one >> that does not work, the architecture is i386. Both cases the gcc is >> gcc-4.2. Further the dates on the Macports.dylib file is the time of >> the sudo port selfupdate. >> >> >> So why did the selfupdate use architecture i386 (and I know that Snow >> Leopard now defaults to x87_64 rather than i386)? >> > > That's definitely the question, as it shouldn't be doing that. It shouldn't > be what you have for build_arch in macports.conf as I tried that, and > MacPorts.dylib was still x86_64 after a selfupdate. > > What is the result from the following commands? > > $ ls -l /usr/bin/gcc* > $ port installed "gcc*" > > Also, did you run selfupdate from the shell, or where you in port's > interactive mode? > > Bryan > > > >> >> Ralph Pass >> >> Ralph Pass wrote: >> >>> Like several other people I have had trouble with updating to 1.8.1 >>> on Snow Leopard. >>> >>> On my Mac Pro (about 19 months old), I updated to Snow Leopard and >>> then 1.8.0 and things worked. I then did a sudo port selfupdate >>> and it worked. A sudo port upgrade outdated also worked. >>> On a new (3 month old) Macbook Pro, I updated to Snow Leopard and >>> then 1.8.0 and things worked. However, it failed when I did a sudo >>> port selfupdate: >>> >>> >>> >>> >>> sudo port selfupdate >>> dlopen(/Library/Tcl/macports1.0/MacPorts.dylib, 10): no suitable >>> image found. Did find: >>> /Library/Tcl/macports1.0/MacPorts.dylib: mach-o, but wrong >>> architecture >>> while executing >>> "load /Library/Tcl/macports1.0/MacPorts.dylib" >>> ("package ifneeded macports 1.0" script) >>> invoked from within >>> "package require macports" >>> (file "/opt/local/bin/port" line 39) >>> >>> >>> Note that for >>> uname -a gives: >>> Darwin mars.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31 >>> 22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386 i386 >>> >>> sw_vers gives: >>> ProductName: Mac OS X >>> ProductVersion: 10.6.1 >>> BuildVersion: 10B504 >>> >>> So I am bit perplexed and looking for guidance. >>> >>> Thanks, >>> Ralph Pass >>> > [...] > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > From jmr at macports.org Fri Oct 9 21:07:25 2009 From: jmr at macports.org (Joshua Root) Date: Sat, 10 Oct 2009 15:07:25 +1100 Subject: MacPorts 1.8.1 has been released In-Reply-To: <4ACFD990.80708@rppass.com> References: <4AC14BA8.8090807@macports.org> <4AC26FF3.5080803@rppass.com> <4AC2727A.1070604@rppass.com> <20090929212502.GL471@ninagal.withay.com> <4ACFD990.80708@rppass.com> Message-ID: <4AD0087D.1000608@macports.org> On 2009-10-10 11:47, Ralph Pass wrote: > I have now done a sudo port selfupdate on two more Macs running Snow > Leopard: One a Macbook Pro that is about 30 months old and an iMac that > was purchased a month ago. Both times it worked and the sudo port > update outdated did as well. > > The only problem machine was a Macbook Pro purchased four months ago. > > I guess the only solution is to remove Macports and reinstall. Or install 1.8.1 from the dmg. - Josh From jmr at macports.org Fri Oct 9 21:10:24 2009 From: jmr at macports.org (Joshua Root) Date: Sat, 10 Oct 2009 15:10:24 +1100 Subject: Install Error In-Reply-To: References: <4F6FBB22-530B-4CA6-B9E4-3E004E7C186C@ispnet.ca> <61137A66-9327-4ECE-B085-E7919AE43A7F@macports.org> <0D3FC285-0322-4BEC-AF04-0ADEC25FFB00@ispnet.ca> <3D32CB25-6EDC-4CDD-97CD-BB23839AFB20@macports.org> Message-ID: <4AD00930.4080800@macports.org> On 2009-10-10 00:44, Peter Hindrichs wrote: > If I read correctly what Joshua Root wrote, then I am out of luck till a > 64-bit update is built. Sorry, I guess I didn't make myself very clear. The port builds and works fine now AFAICT, it just builds for i386 where everything would normally be built for x86_64. - Josh From pth at ispnet.ca Fri Oct 9 21:13:59 2009 From: pth at ispnet.ca (Peter Hindrichs) Date: Sat, 10 Oct 2009 00:13:59 -0400 Subject: Install Error In-Reply-To: References: <4F6FBB22-530B-4CA6-B9E4-3E004E7C186C@ispnet.ca> <61137A66-9327-4ECE-B085-E7919AE43A7F@macports.org> <0D3FC285-0322-4BEC-AF04-0ADEC25FFB00@ispnet.ca> <3D32CB25-6EDC-4CDD-97CD-BB23839AFB20@macports.org> Message-ID: <98904AFB-3257-4B7E-8EC6-B0459B12385F@ispnet.ca> On 2009-10-09, at 17:00 , Brandon Allbery wrote: > On Oct 9, 2009, at 09:44 , Peter Hindrichs wrote: >> I still have the question how would I get to the portfile via the >> command line, this is still puzzling. > > > mress:23478 Z$ port file CosmicDebris > /opt/local/var/macports/sources/rsync.macports.org/release/ports/ > aqua/CosmicDebris/Portfile > > (which was mentioned earlier in this thread) > > Also, TextWrangler should be able to tell you the full path; for a > GUI editor it's fairly CLI friendly. > > -- > brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allbery at kf8nh.com > system administrator [openafs,heimdal,too many hats] allbery at ece.cmu.edu > electrical and computer engineering, carnegie mellon university > KF8NH > > > > OK Thanks for that, I must have missed the earlier mention. Peter From im.not.using.any.numbers at gmail.com Fri Oct 9 21:54:05 2009 From: im.not.using.any.numbers at gmail.com (Ludwig) Date: Fri, 09 Oct 2009 21:54:05 -0700 Subject: Installing old version of a port Message-ID: <4AD0136D.9070802@gmail.com> I'm trying to figure out how to install an outdated version of a port and having not much luck. Is there a simple way of installing, for instance, rdiff-backup-devel @1.1.5? I've found the portfile for it but I'm not sure what to do with it. Thanks From wodenhelm at gmail.com Fri Oct 9 23:54:59 2009 From: wodenhelm at gmail.com (Wodenhelm) Date: Sat, 10 Oct 2009 02:54:59 -0400 Subject: I screwed up my .xinitrc Message-ID: <4AD02FC3.6050303@gmail.com> (Apple iMac G4, 800 MHz PPC, 512 MB of RAM, Mac OS X 10.4.11, Darwin 8.x) In a stroke of genius, I screwed up my ._xinitrc_ I'm trying to run KDE by means of "_startx_," using _echo 'source /sw/bin/init.sh export KDEWM=kwin /sw/bin/startkde >/tmp/kde.log 2>&1' > ~/.xinitrc _And this is what I get: waelhealla:~ Sky$ startx 2009-10-10 02:45:41.458 XDarwin[692] Incompatible applications: app=org.xfree86.XDarwin, targetApp=com.apple.Safari 2009-10-10 02:45:49.014 XDarwin[692] XDarwin 1.4a1 XFree86 Version 4.7.0 / X Window System (protocol Version 11, revision 0) Release Date: 12 August 2007 If the server is older than 6-12 months, or if your hardware is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Operating System: Darwin Apple Computer, Inc. Could not find keymapping file USA.keymapping. Reading keymap from the system. _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root Loading GLX bundle glxCGL.bundle (using Apple's OpenGL) Display mode: Rootless Quartz -- Xplugin implementation PseudoramiX screen 0 added: 1024x747 @ (0,21). PseudoramiX screen 0 placed at X11 coordinate (0,0). [DRI] screen 0 installation complete Screen 0 added: 1024x747 @ (0,21) Screen 0 placed at X11 coordinate (0,0). Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! waiting for X server to shut down Quitting XDarwin... waelhealla:~ Sky$ Any knowing folks able to help me set it straight, who can spell it out for me? Many thanks to those who help. -Bill W. From ryandesign at macports.org Sat Oct 10 00:21:10 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 10 Oct 2009 02:21:10 -0500 Subject: Installing old version of a port In-Reply-To: <4AD0136D.9070802@gmail.com> References: <4AD0136D.9070802@gmail.com> Message-ID: <888DE02A-349F-48DD-B9A5-760C8D62A2F5@macports.org> On Oct 9, 2009, at 23:54, Ludwig wrote: > I'm trying to figure out how to install an outdated version of a port > and having not much luck. Is there a simple way of installing, for > instance, rdiff-backup-devel @1.1.5? I've found the portfile for it > but > I'm not sure what to do with it. Read this: http://trac.macports.org/wiki/howto/InstallingOlderPort From ryandesign at macports.org Sat Oct 10 03:08:57 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 10 Oct 2009 05:08:57 -0500 Subject: realpath failed -- error uninstalling ports In-Reply-To: <657598.29962.qm@web65605.mail.ac4.yahoo.com> References: <657598.29962.qm@web65605.mail.ac4.yahoo.com> Message-ID: <23343022-5972-4B04-B972-75E0319C1F72@macports.org> On Oct 2, 2009, at 18:31, Dexter Douglas wrote: > I am running Leopard on a PowerBook G4; Xcode 3.1.2; macports 1.8.1. > > "port uninstall" was working just fine until 1 Oct. That is when I > performed a selfupdate to 1.8.1 and then upgraded all my outdated > ports. > > After the upgrade, I tried to clean up by uninstalling the inactive > ports. That is when I got the error message. > > I have two most likely unrelated pieces of information. > 1) During the upgrading, doxygen failed to compile. I ended up > uninstalling and trying to reinstall. I was not able to reinstall > doxygen. 2) I suffered from the "MacPorts 1.8.0 deletes ${prefix} > if it is a symlink" problem (http://trac.macports.org/ticket/21082). The realpath command was added to MacPorts in 1.8.1 specifically to fix the symlink problem described in 21082. What is your MacPorts install prefix? Is part of your prefix still a symlink? If so, which part, and where does it point to? Is there anything else unusual about your prefix -- is there a space or any other special character in it (or, if it's a symlink, the place it points to)? Is it on a different disk than your startup disk? Anything else you can think of that would make your MacPorts different from ours? And if you can rebuild your MacPorts with the change Joshua suggested and let us know what it says, that could help as well. From jmr at macports.org Sat Oct 10 03:49:45 2009 From: jmr at macports.org (Joshua Root) Date: Sat, 10 Oct 2009 21:49:45 +1100 Subject: realpath failed -- error uninstalling ports In-Reply-To: <23343022-5972-4B04-B972-75E0319C1F72@macports.org> References: <657598.29962.qm@web65605.mail.ac4.yahoo.com> <23343022-5972-4B04-B972-75E0319C1F72@macports.org> Message-ID: <4AD066C9.8050407@macports.org> On 2009-10-10 21:08, Ryan Schmidt wrote: > And if you can rebuild your MacPorts with the change Joshua suggested > and let us know what it says, that could help as well. No need to rebuild even, you can just edit ${prefix}/share/macports/Tcl/registry1.0/portuninstall.tcl in place. - Josh From pth at ispnet.ca Sat Oct 10 06:47:16 2009 From: pth at ispnet.ca (Peter Hindrichs) Date: Sat, 10 Oct 2009 09:47:16 -0400 Subject: Install Error In-Reply-To: <4AD00930.4080800@macports.org> References: <4F6FBB22-530B-4CA6-B9E4-3E004E7C186C@ispnet.ca> <61137A66-9327-4ECE-B085-E7919AE43A7F@macports.org> <0D3FC285-0322-4BEC-AF04-0ADEC25FFB00@ispnet.ca> <3D32CB25-6EDC-4CDD-97CD-BB23839AFB20@macports.org> <4AD00930.4080800@macports.org> Message-ID: On 2009-10-10, at 24:10 , Joshua Root wrote: > On 2009-10-10 00:44, Peter Hindrichs wrote: >> If I read correctly what Joshua Root wrote, then I am out of luck >> till a >> 64-bit update is built. > > Sorry, I guess I didn't make myself very clear. The port builds and > works fine now AFAICT, it just builds for i386 where everything would > normally be built for x86_64. > > - Josh Yes, Thank you I have it working fine now. Thanks for all the help everyone. Peter From domiman at gmail.com Sat Oct 10 07:58:46 2009 From: domiman at gmail.com (Dominik Reichardt) Date: Sat, 10 Oct 2009 16:58:46 +0200 Subject: How to fix the problem of "Cannot open display"? In-Reply-To: <366c6f340910060742m22b287d7xbfc5177720a5651b@mail.gmail.com> References: <366c6f340910041053h683f11d8s9dd1ffa690ffb7ef@mail.gmail.com> <9DA61651-B94F-4AD0-8B79-CB261657270C@macports.org> <366c6f340910041812w60754e1cu3b184d7e35916a36@mail.gmail.com> <7329EB1B-F846-4993-8D94-8BA35C061BD0@macports.org> <366c6f340910042036l6f0c0329y80bb43b9742d5f77@mail.gmail.com> <4ACA3D70.3040401@macports.org> <0317A280-C30D-4201-8542-3CF97D32B062@macports.org> <4ACAAABA.3070102@macports.org> <4ACAFCBF.9080007@macports.org> <366c6f340910060742m22b287d7xbfc5177720a5651b@mail.gmail.com> Message-ID: <02284396-6FDA-44F2-BA5E-06C2A553E818@gmail.com> Am 06.10.2009 um 16:42 schrieb Peng Yu: >>>> So the instructions the port prints out are wrong? Is there a way >>>> to >>>> correct them? It sounds like you're saying you need "sudo" to have >>>> access to write the changes to the plist, but I remember from prior >>>> discussions that this would cause the launchagent to be running >>>> as root, >>>> when in fact we want the launchagent running as the current user. >> >> You are right, LaunchAgents/org.freedesktop.dbus-session.plist is >> meant >> to be run by the current user, not root. >> >> And yes, the instructions look kind of wrong. launchctl load -w >> without >> sudo does not work because it requires write access to the file. >> But if >> -w is not used, the Disabled key will not be removed and it cannot be >> loaded automatically at system startup time... >> >>> The bottom line is that the startupitem code needs some love. At >>> present >>> it really can't handle anything beyond launchdaemons that will be >>> started by root. >> >> dbus does not use the startupitem.* code for >> org.freedesktop.dbus-sesstion.plist as it installs multiple plist >> files >> which startupitem.* cannot handle. > > I don't understand what would be the solution to my problem. Could > somebody let me know the detailed steps what I should do? I would like to know that, too. It seems to me that dbus is not running correctly on SL and therefore KDE stuff is not running since kdeinit fails... Dom From listsub at systame.com Sat Oct 10 14:07:24 2009 From: listsub at systame.com (Randall Perry) Date: Sat, 10 Oct 2009 17:07:24 -0400 Subject: Error building python26 on ppc, Tiger Message-ID: Ryan Schmidt wrote: > > On Oct 9, 2009, at 12:32, Randall Perry wrote: > >> hacklocaledir.c:44: error: 'RTLD_NEXT' undeclared (first use in this >> function) > > Google searching this error I see: > > http://www.macgeek.co.za/2009/05/11/compliation-of-package-x-failed-rtld_next-un declared/ > > Do you have /usr/local/include/dlfcn.h? Stuff in /usr/local interferes with MacPorts and I recommend you remove anything you have there. > > Thanks, that did it. -- Randall Perry From d.l.tDeContes at free.fr Sat Oct 10 18:49:00 2009 From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=) Date: Sun, 11 Oct 2009 03:49:00 +0200 Subject: readline Message-ID: hi :-) + port -u upgrade outdated MacPorts running without privileges. You may be unable to complete certain actions (eg install). ---> Computing dependencies for readline MacPorts running without privileges. You may be unable to complete certain actions (eg install). MacPorts running without privileges. You may be unable to complete certain actions (eg install). MacPorts running without privileges. You may be unable to complete certain actions (eg install). MacPorts running without privileges. You may be unable to complete certain actions (eg install). ---> Applying patches to readline Error: Target org.macports.patch returned: shell command " cd "/Users/ thomas/Documents/prgm/bin/autoinstall/macports/var/macports/build/ _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sourc es_rsync.macports.org_release_ports_devel_readline/work/readline-6.0" && /usr/bin/patch -p0 < '/Users/thomas/Documents/prgm/bin/autoinstall/ macports/var/macports/sources/rsync.macports.org/release/ports/devel/ readline/files/patch-shobj-conf.diff'" returned error 1 Command output: patching file support/shobj-conf Hunk #1 FAILED at 152. Hunk #2 FAILED at 176. 2 out of 2 hunks FAILED -- saving rejects to file support/shobj-conf.rej Error: Unable to upgrade port: 1 what's the problem ? -- T?l?assistance / T?l?maintenance http://www.portparallele.com/ThomasDECONTES/ From luomo1138 at yahoo.com Sat Oct 10 19:10:49 2009 From: luomo1138 at yahoo.com (Dexter Douglas) Date: Sat, 10 Oct 2009 19:10:49 -0700 (PDT) Subject: realpath failed -- error uninstalling ports In-Reply-To: <4AD066C9.8050407@macports.org> Message-ID: <192785.21727.qm@web65614.mail.ac4.yahoo.com> Hello, I added the debugging statement that you suggested. Here is the output. $ sudo port -f uninstall inactive Password: ---> Uninstalling coreutils @7.4_0 getting realpath for /opt/local/var/macports/software/coreutils/7.4_0/opt/local/bin/g[ Error: port uninstall failed: realpath failed: No such file or directory $port installed shows coreutils @7.4_0 coreutils @7.5_0 coreutils @7.6_0 (active) However, I looked in /opt/local/var/macports/software/coreutils. I only see 7.5_0 and 7.6_0 directories. I have found similar problems with some other ports. For example, $port installed name:zlib zlib @1.2.3_2 zlib @1.2.3_3 (active) but /opt/local/var/macports/software/zlib only contains 1.2.3_3. How do I clean these up? Thanks. --- On Sat, 10/10/09, Joshua Root wrote: > From: Joshua Root > Subject: Re: realpath failed -- error uninstalling ports > To: "Ryan Schmidt" > Cc: "Dexter Douglas" , macports-users at lists.macosforge.org > Date: Saturday, October 10, 2009, 6:49 AM > On 2009-10-10 21:08, Ryan Schmidt > wrote: > > And if you can rebuild your MacPorts with the change > Joshua suggested > > and let us know what it says, that could help as > well. > > No need to rebuild even, you can just edit > ${prefix}/share/macports/Tcl/registry1.0/portuninstall.tcl > in place. > > - Josh > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From abe.gillespie.lists at gmail.com Sun Oct 11 00:14:19 2009 From: abe.gillespie.lists at gmail.com (Abram Gillespie) Date: Sun, 11 Oct 2009 03:14:19 -0400 Subject: PostGIS / libproj Issues In-Reply-To: References: <283a65ca0910091210o751fcf7flb7cfebab133ee766@mail.gmail.com> Message-ID: <283a65ca0910110014n6450f7b0u1e1876156d35e547@mail.gmail.com> Sure will. But how do I get the full debug output? Thanks. -Abe On Fri, Oct 9, 2009 at 6:31 PM, Ryan Schmidt wrote: > > On Oct 9, 2009, at 14:10, Abram Gillespie wrote: > >> I'm getting an error when installing PostGIS. ?Note that "ls >> /opt/local/lib/*proj*" gives me this: >> >> /opt/local/lib/libproj.0.5.5.dylib ? ? ?/opt/local/lib/libproj.dylib >> /opt/local/lib/libproj.0.dylib ? ? ? ? ?/opt/local/lib/libproj.la >> /opt/local/lib/libproj.a >> >> The error is: >> configure: error: could not find libproj - you may need to specify the >> directory of a PROJ.4 installation using --with-projdir >> >> Thanks. >> -Abe >> OS X Leopard / 10.6.1 > > Please file a ticket in the issue tracker and provide more information > including the full debug output of your attempted installation. > > > > From jmr at macports.org Sun Oct 11 01:32:54 2009 From: jmr at macports.org (Joshua Root) Date: Sun, 11 Oct 2009 19:32:54 +1100 Subject: realpath failed -- error uninstalling ports In-Reply-To: <192785.21727.qm@web65614.mail.ac4.yahoo.com> References: <192785.21727.qm@web65614.mail.ac4.yahoo.com> Message-ID: <4AD19836.7040400@macports.org> On 2009-10-11 13:10, Dexter Douglas wrote: > Hello, > > I added the debugging statement that you suggested. Here is the output. > > $ sudo port -f uninstall inactive > Password: > ---> Uninstalling coreutils @7.4_0 > getting realpath for /opt/local/var/macports/software/coreutils/7.4_0/opt/local/bin/g[ > Error: port uninstall failed: realpath failed: No such file or directory > > $port installed shows > coreutils @7.4_0 > coreutils @7.5_0 > coreutils @7.6_0 (active) > > However, I looked in /opt/local/var/macports/software/coreutils. I only see 7.5_0 and 7.6_0 directories. > > I have found similar problems with some other ports. For example, > > $port installed name:zlib > zlib @1.2.3_2 > zlib @1.2.3_3 (active) > > but /opt/local/var/macports/software/zlib only contains 1.2.3_3. > > How do I clean these up? OK, looks like your previous uninstall attempts must have died partway through because of the bug. You can clean up by removing the receipt directory corresponding to the missing software/ subdir, e.g. rm -rf /opt/local/var/macports/receipts/coreutils/7.4_0 - Josh From ryandesign at macports.org Sun Oct 11 03:59:13 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 11 Oct 2009 05:59:13 -0500 Subject: readline In-Reply-To: References: Message-ID: On Oct 10, 2009, at 20:49, Thomas De Contes wrote: > + port -u upgrade outdated > MacPorts running without privileges. You may be unable to complete > certain actions (eg install). > ---> Computing dependencies for readline > MacPorts running without privileges. You may be unable to complete > certain actions (eg install). > MacPorts running without privileges. You may be unable to complete > certain actions (eg install). > MacPorts running without privileges. You may be unable to complete > certain actions (eg install). > MacPorts running without privileges. You may be unable to complete > certain actions (eg install). > ---> Applying patches to readline > Error: Target org.macports.patch returned: shell command " cd "/ > Users/thomas/Documents/prgm/bin/autoinstall/macports/var/macports/ > build/ > _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sources_rsync.macports.org_release_ports_devel_readline > /work/readline-6.0" && /usr/bin/patch -p0 < '/Users/thomas/Documents/ > prgm/bin/autoinstall/macports/var/macports/sources/ > rsync.macports.org/release/ports/devel/readline/files/patch-shobj- > conf.diff'" returned error 1 > Command output: patching file support/shobj-conf > Hunk #1 FAILED at 152. > Hunk #2 FAILED at 176. > 2 out of 2 hunks FAILED -- saving rejects to file support/shobj- > conf.rej > > Error: Unable to upgrade port: 1 Since the first thing shown for readline is "Applying patches" instead of "Fetching" or "Extracting", this suggests you had previously started installing readline and cancelled it just after it finished the patch phase but before it recorded that it had finished the patch phase. So now it's trying to apply the patches a second time, and failing, because they are already applied. In those situations you usually see the message "Reversed (or previously applied) patch detected! Assume -R? [n]". But the readline port not only applies patchfiles to the source files, it also has a post-patch step which does a reinplace on shobj-conf. Therefore the way the file looks now is not exactly the way it would look after only applying the patches, therefore the patch program doesn't know what to do. The solution should be to clean the port, selfupdate to make sure you have the latest MacPorts and port definitions, and try again. This is probably the first step you should try any time any port fails. sudo port clean readline sudo port selfupdate sudo port upgrade readline From ryandesign at macports.org Sun Oct 11 04:07:20 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 11 Oct 2009 06:07:20 -0500 Subject: PostGIS / libproj Issues In-Reply-To: <283a65ca0910110014n6450f7b0u1e1876156d35e547@mail.gmail.com> References: <283a65ca0910091210o751fcf7flb7cfebab133ee766@mail.gmail.com> <283a65ca0910110014n6450f7b0u1e1876156d35e547@mail.gmail.com> Message-ID: On Oct 11, 2009, at 02:14, Abram Gillespie wrote: > On Fri, Oct 9, 2009 at 6:31 PM, Ryan Schmidt wrote: >> > >> On Oct 9, 2009, at 14:10, Abram Gillespie wrote: >> >>> I'm getting an error when installing PostGIS. [snip] >> >> Please file a ticket in the issue tracker and provide more >> information >> including the full debug output of your attempted installation. > > Sure will. But how do I get the full debug output? sudo port clean postgis sudo port -d install postgis build.jobs=1 2>&1 | tee ~/Desktop/ postgis.txt The debug output will be displayed onscreen and saved in the file postgis.txt on your desktop, from which you can attach it to your Trac ticket if it fails again. From luomo1138 at yahoo.com Sun Oct 11 05:20:58 2009 From: luomo1138 at yahoo.com (Dexter Douglas) Date: Sun, 11 Oct 2009 05:20:58 -0700 (PDT) Subject: realpath failed -- error uninstalling ports In-Reply-To: <4AD19836.7040400@macports.org> Message-ID: <451688.52607.qm@web65607.mail.ac4.yahoo.com> Hello, That fixed it. Thank you very much! --- On Sun, 10/11/09, Joshua Root wrote: > From: Joshua Root > Subject: Re: realpath failed -- error uninstalling ports > To: "Dexter Douglas" > Cc: "Ryan Schmidt" , macports-users at lists.macosforge.org > Date: Sunday, October 11, 2009, 4:32 AM > On 2009-10-11 13:10, Dexter Douglas > wrote: > > Hello, > > > > I added the debugging statement that you > suggested.? Here is the output. > > > > $ sudo port -f uninstall inactive > > Password: > > --->? Uninstalling coreutils @7.4_0 > > getting realpath for > /opt/local/var/macports/software/coreutils/7.4_0/opt/local/bin/g[ > > Error: port uninstall failed: realpath failed: No such > file or directory > > > > $port installed shows > >???coreutils @7.4_0 > >???coreutils @7.5_0 > >???coreutils @7.6_0 (active) > > > > However, I looked in > /opt/local/var/macports/software/coreutils.? I only see > 7.5_0 and 7.6_0 directories. > > > > I have found similar problems with some other > ports.? For example, > > > > $port installed name:zlib > >???zlib @1.2.3_2 > >???zlib @1.2.3_3 (active) > > > > but /opt/local/var/macports/software/zlib only > contains 1.2.3_3. > > > > How do I clean these up? > > OK, looks like your previous uninstall attempts must have > died partway > through because of the bug. You can clean up by removing > the receipt > directory corresponding to the missing software/ subdir, > e.g. > > rm -rf /opt/local/var/macports/receipts/coreutils/7.4_0 > > - Josh > From d.l.tDeContes at free.fr Sun Oct 11 07:43:27 2009 From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=) Date: Sun, 11 Oct 2009 16:43:27 +0200 Subject: readline In-Reply-To: References: Message-ID: Le 11 oct. 09 ? 12:59, Ryan Schmidt a ?crit : > On Oct 10, 2009, at 20:49, Thomas De Contes wrote: > >> + port -u upgrade outdated >> MacPorts running without privileges. You may be unable to complete >> certain actions (eg install). >> ---> Computing dependencies for readline >> MacPorts running without privileges. You may be unable to complete >> certain actions (eg install). >> MacPorts running without privileges. You may be unable to complete >> certain actions (eg install). >> MacPorts running without privileges. You may be unable to complete >> certain actions (eg install). >> MacPorts running without privileges. You may be unable to complete >> certain actions (eg install). >> ---> Applying patches to readline >> Error: Target org.macports.patch returned: shell command " cd "/ >> Users/thomas/Documents/prgm/bin/autoinstall/macports/var/macports/ >> build/ >> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_so >> urces_rsync.macports.org_release_ports_devel_readline/work/ >> readline-6.0" && /usr/bin/patch -p0 < '/Users/thomas/Documents/ >> prgm/bin/autoinstall/macports/var/macports/sources/ >> rsync.macports.org/release/ports/devel/readline/files/patch-shobj- >> conf.diff'" returned error 1 >> Command output: patching file support/shobj-conf >> Hunk #1 FAILED at 152. >> Hunk #2 FAILED at 176. >> 2 out of 2 hunks FAILED -- saving rejects to file support/shobj- >> conf.rej >> >> Error: Unable to upgrade port: 1 > > Since the first thing shown for readline is "Applying patches" > instead of "Fetching" or "Extracting", this suggests you had > previously started installing readline and cancelled it just after > it finished the patch phase but before it recorded that it had > finished the patch phase. So now it's trying to apply the patches a > second time, and failing, because they are already applied. no, it made an error, and i just run it again > The solution should be to clean the port, selfupdate to make sure > you have the latest MacPorts and port definitions, and try again. > This is probably the first step you should try any time any port > fails. > > sudo port clean readline > sudo port selfupdate > sudo port upgrade readline i did port clean readline and then : + port selfupdate ... + port -u upgrade outdated MacPorts running without privileges. You may be unable to complete certain actions (eg install). ---> Computing dependencies for readline MacPorts running without privileges. You may be unable to complete certain actions (eg install). ---> Fetching readline MacPorts running without privileges. You may be unable to complete certain actions (eg install). ---> Verifying checksum(s) for readline MacPorts running without privileges. You may be unable to complete certain actions (eg install). ---> Extracting readline MacPorts running without privileges. You may be unable to complete certain actions (eg install). ---> Applying patches to readline Error: Target org.macports.patch returned: could not set group for file "/Users/thomas/Documents/prgm/bin/autoinstall/macports/var/ macports/build/ _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sourc es_rsync.macports.org_release_ports_devel_readline/work/readline-6.0/ support/shobj-conf": not owner Error: Unable to upgrade port: 1 -- T?l?assistance / T?l?maintenance http://www.portparallele.com/ThomasDECONTES/ From ryandesign at macports.org Sun Oct 11 13:23:10 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 11 Oct 2009 15:23:10 -0500 Subject: readline In-Reply-To: References: Message-ID: <06BA46CE-8BF3-49DB-A717-75D870FF632F@macports.org> On Oct 11, 2009, at 09:43, Thomas De Contes wrote: > Le 11 oct. 09 ? 12:59, Ryan Schmidt a ?crit : > >> On Oct 10, 2009, at 20:49, Thomas De Contes wrote: >> >>> + port -u upgrade outdated >>> MacPorts running without privileges. You may be unable to complete >>> certain actions (eg install). >>> ---> Computing dependencies for readline >>> MacPorts running without privileges. You may be unable to complete >>> certain actions (eg install). >>> MacPorts running without privileges. You may be unable to complete >>> certain actions (eg install). >>> MacPorts running without privileges. You may be unable to complete >>> certain actions (eg install). >>> MacPorts running without privileges. You may be unable to complete >>> certain actions (eg install). >>> ---> Applying patches to readline >>> Error: Target org.macports.patch returned: shell command " cd "/ >>> Users/thomas/Documents/prgm/bin/autoinstall/macports/var/macports/ >>> build/ >>> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sources_rsync.macports.org_release_ports_devel_readline >>> /work/readline-6.0" && /usr/bin/patch -p0 < '/Users/thomas/ >>> Documents/prgm/bin/autoinstall/macports/var/macports/sources/ >>> rsync.macports.org/release/ports/devel/readline/files/patch-shobj- >>> conf.diff'" returned error 1 >>> Command output: patching file support/shobj-conf >>> Hunk #1 FAILED at 152. >>> Hunk #2 FAILED at 176. >>> 2 out of 2 hunks FAILED -- saving rejects to file support/shobj- >>> conf.rej >>> >>> Error: Unable to upgrade port: 1 >> >> Since the first thing shown for readline is "Applying patches" >> instead of "Fetching" or "Extracting", this suggests you had >> previously started installing readline and cancelled it just after >> it finished the patch phase but before it recorded that it had >> finished the patch phase. So now it's trying to apply the patches a >> second time, and failing, because they are already applied. > > no, it made an error, and i just run it again Ah, ok. Still, the error you reported was caused by running it a second time without cleaning. >> The solution should be to clean the port, selfupdate to make sure >> you have the latest MacPorts and port definitions, and try again. >> This is probably the first step you should try any time any port >> fails. >> >> sudo port clean readline >> sudo port selfupdate >> sudo port upgrade readline > > > i did > port clean readline > and then : > > + port selfupdate > ... > + port -u upgrade outdated > MacPorts running without privileges. You may be unable to complete > certain actions (eg install). > ---> Computing dependencies for readline > MacPorts running without privileges. You may be unable to complete > certain actions (eg install). > ---> Fetching readline > MacPorts running without privileges. You may be unable to complete > certain actions (eg install). > ---> Verifying checksum(s) for readline > MacPorts running without privileges. You may be unable to complete > certain actions (eg install). > ---> Extracting readline > MacPorts running without privileges. You may be unable to complete > certain actions (eg install). > ---> Applying patches to readline > Error: Target org.macports.patch returned: could not set group for > file "/Users/thomas/Documents/prgm/bin/autoinstall/macports/var/ > macports/build/ > _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sources_rsync.macports.org_release_ports_devel_readline > /work/readline-6.0/support/shobj-conf": not owner > Error: Unable to upgrade port: 1 Ok, that's the first and real error, and is: http://trac.macports.org/ticket/20896 As shown in the ticket, I identified the change that caused that problem. Joshua, what do you think we should do about this? We could apply the patch I supplied, which would revert one of your prior changes. Or we could try to figure out a way to allow your change while still avoiding this issue. From dave at difference.com.au Sun Oct 11 08:07:37 2009 From: dave at difference.com.au (David Cake) Date: Sun, 11 Oct 2009 23:07:37 +0800 Subject: apr-util not building because it can't find db In-Reply-To: <74EFB5DB-CCCF-42BD-962D-C50C12BE8579@us.ntt.net> References: <74EFB5DB-CCCF-42BD-962D-C50C12BE8579@us.ntt.net> Message-ID: At 5:00 PM -0400 9/10/09, Daniel J. Luke wrote: >On Oct 9, 2009, at 11:49 AM, David Cake wrote: >> Everytime I issue port upgrade outdated, it tries to build >>apr-util, and fails with >>configure: error: Berkeley DB not found. >> db46 is installed, but the apr-util build just doesn't seem >>to believe it is there. >> Any advice? > >are you sure your db46 port is happy/healthy? No reason to think it isn't. port install db46 reported that it succeeded. >You could try uninstalling/cleaning/reinstalling it, then cleaning >apr-util and see if it works then? > >Otherwise posting the port -dv upgrade apr-util output (or opening a >bug with it attached) would be the next step in helping to >troubleshoot it. sudo port -dv upgrade apr-util output Password: DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/apr-util DEBUG: epoch: in tree: 0 installed: 0 DEBUG: apr-util 1.3.9_0 exists in the ports tree DEBUG: apr-util 1.3.8_0 is the latest installed DEBUG: apr-util 1.3.8_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/apr-util DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Requested variant darwin is not provided by port apr-util. DEBUG: Requested variant i386 is not provided by port apr-util. DEBUG: Requested variant macosx is not provided by port apr-util. DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/apr DEBUG: epoch: in tree: 0 installed: 0 DEBUG: apr 1.3.8_0 exists in the ports tree DEBUG: apr 1.3.8_0 is the latest installed DEBUG: apr 1.3.8_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/apr DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Requested variant darwin is not provided by port apr. DEBUG: Requested variant i386 is not provided by port apr. DEBUG: Requested variant macosx is not provided by port apr. DEBUG: No need to upgrade! apr 1.3.8_0 >= apr 1.3.8_0 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/expat DEBUG: epoch: in tree: 0 installed: 0 DEBUG: expat 2.0.1_0 exists in the ports tree DEBUG: expat 2.0.1_0 is the latest installed DEBUG: expat 2.0.1_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/expat DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Requested variant darwin is not provided by port expat. DEBUG: Requested variant i386 is not provided by port expat. DEBUG: Requested variant macosx is not provided by port expat. DEBUG: No need to upgrade! expat 2.0.1_0 >= expat 2.0.1_0 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv DEBUG: epoch: in tree: 0 installed: 0 DEBUG: libiconv 1.13_0 exists in the ports tree DEBUG: libiconv 1.13_0 is the latest installed DEBUG: libiconv 1.13_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant darwin is not provided by port libiconv. DEBUG: Requested variant i386 is not provided by port libiconv. DEBUG: Requested variant macosx is not provided by port libiconv. DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gperf DEBUG: epoch: in tree: 0 installed: 0 DEBUG: gperf 3.0.4_0 exists in the ports tree DEBUG: gperf 3.0.4_0 is the latest installed DEBUG: gperf 3.0.4_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gperf DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant darwin is not provided by port gperf. DEBUG: Requested variant i386 is not provided by port gperf. DEBUG: Requested variant macosx is not provided by port gperf. DEBUG: No need to upgrade! gperf 3.0.4_0 >= gperf 3.0.4_0 DEBUG: No need to upgrade! libiconv 1.13_0 >= libiconv 1.13_0 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/databases/db46 DEBUG: epoch: in tree: 0 installed: 0 DEBUG: db46 4.6.21_5 exists in the ports tree DEBUG: db46 4.6.21_5 is the latest installed DEBUG: db46 4.6.21_5 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/databases/db46 DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant darwin is not provided by port db46. DEBUG: Requested variant i386 is not provided by port db46. DEBUG: Requested variant macosx is not provided by port db46. DEBUG: No need to upgrade! db46 4.6.21_5 >= db46 4.6.21_5 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/databases/sqlite3 DEBUG: epoch: in tree: 0 installed: 0 DEBUG: sqlite3 3.6.18_0 exists in the ports tree DEBUG: sqlite3 3.6.18_0 is the latest installed DEBUG: sqlite3 3.6.18_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/databases/sqlite3 DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Requested variant darwin is not provided by port sqlite3. DEBUG: Requested variant i386 is not provided by port sqlite3. DEBUG: Requested variant macosx is not provided by port sqlite3. DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/readline DEBUG: epoch: in tree: 0 installed: 0 DEBUG: readline 6.0.000_2 exists in the ports tree DEBUG: readline 6.0.000_2 +darwin is the latest installed DEBUG: readline 6.0.000_2 +darwin is active DEBUG: Merging existing variants darwin into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/readline DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant i386 is not provided by port readline. DEBUG: Requested variant macosx is not provided by port readline. DEBUG: Executing variant darwin provides darwin DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncurses DEBUG: epoch: in tree: 0 installed: 0 DEBUG: ncurses 5.7_0 exists in the ports tree DEBUG: ncurses 5.7_0 is the latest installed DEBUG: ncurses 5.7_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncurses DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant darwin is not provided by port ncurses. DEBUG: Requested variant i386 is not provided by port ncurses. DEBUG: Requested variant macosx is not provided by port ncurses. DEBUG: Executing variant darwin_10 provides darwin_10 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncursesw DEBUG: epoch: in tree: 0 installed: 0 DEBUG: ncursesw 5.7_0 exists in the ports tree DEBUG: ncursesw 5.7_0 is the latest installed DEBUG: ncursesw 5.7_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncursesw DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant darwin is not provided by port ncursesw. DEBUG: Requested variant i386 is not provided by port ncursesw. DEBUG: Requested variant macosx is not provided by port ncursesw. DEBUG: Executing variant darwin_10 provides darwin_10 Warning: Skipping upgrade since ncursesw 5.7_0 >= ncursesw 5.7_0, even though installed variants "" do not match "+darwin_10". Use 'upgrade --enforce-variants' to switch to the requested variants. Warning: Skipping upgrade since ncurses 5.7_0 >= ncurses 5.7_0, even though installed variants "" do not match "+darwin_10". Use 'upgrade --enforce-variants' to switch to the requested variants. DEBUG: No need to upgrade! readline 6.0.000_2 >= readline 6.0.000_2 DEBUG: No need to upgrade! sqlite3 3.6.18_0 >= sqlite3 3.6.18_0 ---> Computing dependencies for apr-util DEBUG: Searching for dependency: apr DEBUG: Found Dependency: receipt exists for apr DEBUG: Searching for dependency: expat DEBUG: Found Dependency: receipt exists for expat DEBUG: Searching for dependency: libiconv DEBUG: Found Dependency: receipt exists for libiconv DEBUG: Searching for dependency: db46 DEBUG: Found Dependency: receipt exists for db46 DEBUG: Searching for dependency: sqlite3 DEBUG: Found Dependency: receipt exists for sqlite3 DEBUG: Executing org.macports.main (apr-util) DEBUG: Skipping completed org.macports.fetch (apr-util) DEBUG: Skipping completed org.macports.checksum (apr-util) DEBUG: setting option extract.cmd to /usr/bin/bzip2 DEBUG: Skipping completed org.macports.extract (apr-util) DEBUG: Skipping completed org.macports.patch (apr-util) ---> Configuring apr-util DEBUG: Using compiler 'Mac OS X gcc 4.2' DEBUG: Executing proc-pre-org.macports.configure-configure-0 DEBUG: Executing org.macports.configure (apr-util) DEBUG: Environment: CFLAGS='-O2 -arch x86_64' CPPFLAGS='-I/opt/local/include' CXXFLAGS='-O2 -arch x86_64' MACOSX_DEPLOYMENT_TARGET='10.6' CXX='/usr/bin/g++-4.2' F90FLAGS='-O2 -m64' LDFLAGS='-L/opt/local/lib' OBJC='/usr/bin/gcc-4.2' FCFLAGS='-O2 -m64' INSTALL='/usr/bin/install -c' OBJCFLAGS='-O2 -arch x86_64' FFLAGS='-O2 -m64' CC='/usr/bin/gcc-4.2' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_apr-util/work/apr-util-1.3.9" && ./configure --prefix=/opt/local --with-apr=/opt/local/bin/apr-1-config --with-expat=/opt/local --with-iconv=/opt/local --with-berkeley-db=/opt/local/include:/opt/local/lib/db46 --without-mysql --without-pgsql --with-sqlite3=/opt/local' checking build system type... i386-apple-darwin10.0.0 checking host system type... i386-apple-darwin10.0.0 checking target system type... i386-apple-darwin10.0.0 checking for a BSD-compatible install... /usr/bin/install -c checking for working mkdir -p... yes APR-util Version: 1.3.9 checking for chosen layout... apr-util checking for gcc... /usr/bin/gcc-4.2 checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/bin/gcc-4.2 accepts -g... yes checking for /usr/bin/gcc-4.2 option to accept ISO C89... none needed Applying apr-util hints file rules for i386-apple-darwin10.0.0 checking for APR... yes setting CPP to "/usr/bin/gcc-4.2 -E" adding "-DDARWIN" to CPPFLAGS adding "-DSIGPROCMASK_SETS_THREAD_MASK" to CPPFLAGS adding "-no-cpp-precomp" to CPPFLAGS checking how to run the C preprocessor... /usr/bin/gcc-4.2 -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for ldap support... checking for Berkeley DB 4.7 in /opt/local/include and /opt/local/lib/db46... checking db47/db.h usability... no checking db47/db.h presence... no checking for db47/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb-4.7... no checking db47/db.h usability... no checking db47/db.h presence... no checking for db47/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb4-4.7... no checking db47/db.h usability... no checking db47/db.h presence... no checking for db47/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb47... no checking db47/db.h usability... no checking db47/db.h presence... no checking for db47/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb4... no checking db47/db.h usability... no checking db47/db.h presence... no checking for db47/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb... no checking for Berkeley DB 4.6 in /opt/local/include and /opt/local/lib/db46... checking db46/db.h usability... yes checking db46/db.h presence... yes checking for db46/db.h... yes checking for -ldb-4.6... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb-4.6... no checking db46/db.h usability... yes checking db46/db.h presence... yes checking for db46/db.h... yes checking for -ldb4-4.6... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb4-4.6... no checking db46/db.h usability... yes checking db46/db.h presence... yes checking for db46/db.h... yes checking for -ldb46... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb46... no checking db46/db.h usability... yes checking db46/db.h presence... yes checking for db46/db.h... yes checking for -ldb4... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb4... no checking db46/db.h usability... yes checking db46/db.h presence... yes checking for db46/db.h... yes checking for -ldb... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb... no checking for Berkeley DB 4.5 in /opt/local/include and /opt/local/lib/db46... checking db45/db.h usability... no checking db45/db.h presence... no checking for db45/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb-4.5... no checking db45/db.h usability... no checking db45/db.h presence... no checking for db45/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb4-4.5... no checking db45/db.h usability... no checking db45/db.h presence... no checking for db45/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb45... no checking db45/db.h usability... no checking db45/db.h presence... no checking for db45/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb4... no checking db45/db.h usability... no checking db45/db.h presence... no checking for db45/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb... no checking for Berkeley DB 4.4 in /opt/local/include and /opt/local/lib/db46... checking db44/db.h usability... no checking db44/db.h presence... no checking for db44/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb-4.4... no checking db44/db.h usability... no checking db44/db.h presence... no checking for db44/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb4-4.4... no checking db44/db.h usability... no checking db44/db.h presence... no checking for db44/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb44... no checking db44/db.h usability... no checking db44/db.h presence... no checking for db44/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb4... no checking db44/db.h usability... no checking db44/db.h presence... no checking for db44/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb... no checking for Berkeley DB 4.3 in /opt/local/include and /opt/local/lib/db46... checking db43/db.h usability... no checking db43/db.h presence... no checking for db43/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb-4.3... no checking db43/db.h usability... no checking db43/db.h presence... no checking for db43/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb4-4.3... no checking db43/db.h usability... no checking db43/db.h presence... no checking for db43/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb43... no checking db43/db.h usability... no checking db43/db.h presence... no checking for db43/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb4... no checking db43/db.h usability... no checking db43/db.h presence... no checking for db43/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb... no checking for Berkeley DB 4.2 in /opt/local/include and /opt/local/lib/db46... checking db42/db.h usability... no checking db42/db.h presence... no checking for db42/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb-4.2... no checking db42/db.h usability... no checking db42/db.h presence... no checking for db42/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb42... no checking db42/db.h usability... no checking db42/db.h presence... no checking for db42/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb4... no checking db42/db.h usability... no checking db42/db.h presence... no checking for db42/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb... no checking for Berkeley DB 4.1 in /opt/local/include and /opt/local/lib/db46... checking db41/db.h usability... no checking db41/db.h presence... no checking for db41/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb-4.1... no checking db41/db.h usability... no checking db41/db.h presence... no checking for db41/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb41... no checking db41/db.h usability... no checking db41/db.h presence... no checking for db41/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb4... no checking db41/db.h usability... no checking db41/db.h presence... no checking for db41/db.h... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb... no checking for Berkeley DB 4.0 in /opt/local/include and /opt/local/lib/db46... checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb-4.0... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb4... no checking db4/db.h usability... no checking db4/db.h presence... no checking for db4/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb... no checking for Berkeley DB 3 in /opt/local/include and /opt/local/lib/db46... checking db3/db.h usability... no checking db3/db.h presence... no checking for db3/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb3... no checking db3/db.h usability... no checking db3/db.h presence... no checking for db3/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for -ldb... no checking for Berkeley DB 2 in /opt/local/include and /opt/local/lib/db46... checking db2/db.h usability... no checking db2/db.h presence... no checking for db2/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for db_open in -ldb2... no checking db2/db.h usability... no checking db2/db.h presence... no checking for db2/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for db_open in -ldb... no checking for Berkeley DB 1.0.0 in /opt/local/include and /opt/local/lib/db46... checking db1/db.h usability... no checking db1/db.h presence... no checking for db1/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for dbopen in -ldb1... no checking for Berkeley DB 1 in /opt/local/include and /opt/local/lib/db46... checking db_185.h usability... no checking db_185.h presence... no checking for db_185.h... no checking for Berkeley DB... not found configure: error: Berkeley DB not found. 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_devel_apr-util/work/apr-util-1.3.9" && ./configure --prefix=/opt/local --with-apr=/opt/local/bin/apr-1-config --with-expat=/opt/local --with-iconv=/opt/local --with-berkeley-db=/opt/local/include:/opt/local/lib/db46 --without-mysql --without-pgsql --with-sqlite3=/opt/local " returned error 1 Command output: checking for -ldb... no checking for Berkeley DB 2 in /opt/local/include and /opt/local/lib/db46... checking db2/db.h usability... no checking db2/db.h presence... no checking for db2/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for db_open in -ldb2... no checking db2/db.h usability... no checking db2/db.h presence... no checking for db2/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for db_open in -ldb... no checking for Berkeley DB 1.0.0 in /opt/local/include and /opt/local/lib/db46... checking db1/db.h usability... no checking db1/db.h presence... no checking for db1/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for dbopen in -ldb1... no checking for Berkeley DB 1 in /opt/local/include and /opt/local/lib/db46... checking db_185.h usability... no checking db_185.h presence... no checking for db_185.h... no checking for Berkeley DB... not found configure: error: Berkeley DB not found. DEBUG: Backtrace: configure failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_apr-util/work/apr-util-1.3.9" && ./configure --prefix=/opt/local --with-apr=/opt/local/bin/apr-1-config --with-expat=/opt/local --with-iconv=/opt/local --with-berkeley-db=/opt/local/include:/opt/local/lib/db46 --without-mysql --without-pgsql --with-sqlite3=/opt/local " returned error 1 Command output: checking for -ldb... no checking for Berkeley DB 2 in /opt/local/include and /opt/local/lib/db46... checking db2/db.h usability... no checking db2/db.h presence... no checking for db2/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for db_open in -ldb2... no checking db2/db.h usability... no checking db2/db.h presence... no checking for db2/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for db_open in -ldb... no checking for Berkeley DB 1.0.0 in /opt/local/include and /opt/local/lib/db46... checking db1/db.h usability... no checking db1/db.h presence... no checking for db1/db.h... no checking db.h usability... yes checking db.h presence... yes checking for db.h... yes checking for dbopen in -ldb1... no checking for Berkeley DB 1 in /opt/local/include and /opt/local/lib/db46... checking db_185.h usability... no checking db_185.h presence... no checking for db_185.h... no checking for Berkeley DB... not found configure: error: Berkeley DB not found. while executing "$procedure $targetname" Warning: the following items did not execute (for apr-util): org.macports.destroot org.macports.configure org.macports.build DEBUG: couldn't read file "/opt/local/share/macports/Tcl/darwintrace1.0/pkgIndex.tcl": no such file or directory while executing "source [file join $dir pkgIndex.tcl]" Error: Unable to upgrade port: 1 From dluke at geeklair.net Sun Oct 11 17:10:05 2009 From: dluke at geeklair.net (Daniel J. Luke) Date: Sun, 11 Oct 2009 20:10:05 -0400 Subject: apr-util not building because it can't find db In-Reply-To: References: <74EFB5DB-CCCF-42BD-962D-C50C12BE8579@us.ntt.net> Message-ID: <359DB881-2104-48B2-B57E-7F03623AE7E7@geeklair.net> On Oct 11, 2009, at 11:07 AM, David Cake wrote: > At 5:00 PM -0400 9/10/09, Daniel J. Luke wrote: >> On Oct 9, 2009, at 11:49 AM, David Cake wrote: >>> Everytime I issue port upgrade outdated, it tries to build apr- >>> util, and fails with >>> configure: error: Berkeley DB not found. >>> db46 is installed, but the apr-util build just doesn't seem to >>> believe it is there. >>> Any advice? >> >> are you sure your db46 port is happy/healthy? > > No reason to think it isn't. port install db46 reported that it > succeeded. except for the fact that apr-util can't seem to find it ;-) >> You could try uninstalling/cleaning/reinstalling it, then cleaning >> apr-util and see if it works then? did you try this? >> Otherwise posting the port -dv upgrade apr-util output (or opening >> a bug with it attached) would be the next step in helping to >> troubleshoot it. > > checking for Berkeley DB 4.6 in /opt/local/include and /opt/local/ > lib/db46... > checking db46/db.h usability... yes > checking db46/db.h presence... yes > checking for db46/db.h... yes > checking for -ldb-4.6... no so, here's the problem, do you have /opt/local/lib/db46/ libdb-4.6.dylib ? If you do have that file, is it the right architecture? (try `file / opt/local/lib/db46/libdb-4.6.dylib`) apr-util's configure script is finding the db46 header file, but not the library. -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ From ryandesign at macports.org Sun Oct 11 18:47:43 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 11 Oct 2009 20:47:43 -0500 Subject: apr-util not building because it can't find db In-Reply-To: <359DB881-2104-48B2-B57E-7F03623AE7E7@geeklair.net> References: <74EFB5DB-CCCF-42BD-962D-C50C12BE8579@us.ntt.net> <359DB881-2104-48B2-B57E-7F03623AE7E7@geeklair.net> Message-ID: <58EE75B8-9777-41B3-AEA9-D926D3B54A32@macports.org> On Oct 11, 2009, at 19:10, Daniel J. Luke wrote: > so, here's the problem, do you have /opt/local/lib/db46/ > libdb-4.6.dylib ? > > If you do have that file, is it the right architecture? (try `file / > opt/local/lib/db46/libdb-4.6.dylib`) I don't recall what OS David is using, but it seems on Snow Leopard "file" no longer tells you the architectures in a file. "lipo -info" still does, though. $ file /opt/local/lib/db46/libdb-4.6.dylib /opt/local/lib/db46/libdb-4.6.dylib: Mach-O fat file with 2 architectures $ lipo -info /opt/local/lib/db46/libdb-4.6.dylib Architectures in the fat file: /opt/local/lib/db46/libdb-4.6.dylib are: i386 x86_64 $ From blb at macports.org Sun Oct 11 19:32:52 2009 From: blb at macports.org (Bryan Blackburn) Date: Sun, 11 Oct 2009 20:32:52 -0600 Subject: apr-util not building because it can't find db In-Reply-To: <58EE75B8-9777-41B3-AEA9-D926D3B54A32@macports.org> References: <74EFB5DB-CCCF-42BD-962D-C50C12BE8579@us.ntt.net> <359DB881-2104-48B2-B57E-7F03623AE7E7@geeklair.net> <58EE75B8-9777-41B3-AEA9-D926D3B54A32@macports.org> Message-ID: <20091012023252.GJ65456@ninagal.withay.com> On Sun, Oct 11, 2009 at 08:47:43PM -0500, Ryan Schmidt said: > On Oct 11, 2009, at 19:10, Daniel J. Luke wrote: > > >so, here's the problem, do you have /opt/local/lib/db46/ > >libdb-4.6.dylib ? > > > >If you do have that file, is it the right architecture? (try `file > >/opt/local/lib/db46/libdb-4.6.dylib`) > > I don't recall what OS David is using, but it seems on Snow Leopard > "file" no longer tells you the architectures in a file. "lipo -info" > still does, though. 'which file' are you using? $ file /bin/ls /bin/ls: Mach-O universal binary with 2 architectures /bin/ls (for architecture x86_64): Mach-O 64-bit executable x86_64 /bin/ls (for architecture i386): Mach-O executable i386 Bryan > > > $ file /opt/local/lib/db46/libdb-4.6.dylib > /opt/local/lib/db46/libdb-4.6.dylib: Mach-O fat file with 2 > architectures > $ lipo -info /opt/local/lib/db46/libdb-4.6.dylib > Architectures in the fat file: /opt/local/lib/db46/libdb-4.6.dylib > are: i386 x86_64 From ryandesign at macports.org Sun Oct 11 20:10:23 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 11 Oct 2009 22:10:23 -0500 Subject: apr-util not building because it can't find db In-Reply-To: <20091012023252.GJ65456@ninagal.withay.com> References: <74EFB5DB-CCCF-42BD-962D-C50C12BE8579@us.ntt.net> <359DB881-2104-48B2-B57E-7F03623AE7E7@geeklair.net> <58EE75B8-9777-41B3-AEA9-D926D3B54A32@macports.org> <20091012023252.GJ65456@ninagal.withay.com> Message-ID: <39501212-833A-4511-A452-6C68A0BFFE04@macports.org> On Oct 11, 2009, at 21:32, Bryan Blackburn wrote: > On Sun, Oct 11, 2009 at 08:47:43PM -0500, Ryan Schmidt said: > >> On Oct 11, 2009, at 19:10, Daniel J. Luke wrote: >> >>> so, here's the problem, do you have /opt/local/lib/db46/ >>> libdb-4.6.dylib ? >>> >>> If you do have that file, is it the right architecture? (try `file >>> /opt/local/lib/db46/libdb-4.6.dylib`) >> >> I don't recall what OS David is using, but it seems on Snow Leopard >> "file" no longer tells you the architectures in a file. "lipo -info" >> still does, though. > > 'which file' are you using? > > $ file /bin/ls > /bin/ls: Mach-O universal binary with 2 architectures > /bin/ls (for architecture x86_64): Mach-O 64-bit executable x86_64 > /bin/ls (for architecture i386): Mach-O executable i386 Ah, I have the "file" port installed. (Not by choice; as a dependency of the sox port.) From dave at difference.com.au Sun Oct 11 20:55:30 2009 From: dave at difference.com.au (David Cake) Date: Mon, 12 Oct 2009 11:55:30 +0800 Subject: apr-util not building because it can't find db In-Reply-To: <39501212-833A-4511-A452-6C68A0BFFE04@macports.org> References: <74EFB5DB-CCCF-42BD-962D-C50C12BE8579@us.ntt.net> <359DB881-2104-48B2-B57E-7F03623AE7E7@geeklair.net> <58EE75B8-9777-41B3-AEA9-D926D3B54A32@macports.org> <20091012023252.GJ65456@ninagal.withay.com> <39501212-833A-4511-A452-6C68A0BFFE04@macports.org> Message-ID: Well, there is the problem lipo -info /opt/local/lib/db46/libdb-4.6.dyli b Non-fat file: /opt/local/lib/db46/libdb-4.6.dylib is architecture: i386 But why? I installed it on Snow Leopard, so why didn't it build it for both architectures? And how do I make it do so? And how do I change my whole installation so this is the default (as I am having similar problems with other installs)? Cheers David From ryandesign at macports.org Sun Oct 11 22:36:16 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 12 Oct 2009 00:36:16 -0500 Subject: apr-util not building because it can't find db In-Reply-To: References: <74EFB5DB-CCCF-42BD-962D-C50C12BE8579@us.ntt.net> <359DB881-2104-48B2-B57E-7F03623AE7E7@geeklair.net> <58EE75B8-9777-41B3-AEA9-D926D3B54A32@macports.org> <20091012023252.GJ65456@ninagal.withay.com> <39501212-833A-4511-A452-6C68A0BFFE04@macports.org> Message-ID: <8E3B5CCF-9407-4ECE-A086-C763E9C4DA80@macports.org> On Oct 11, 2009, at 22:55, David Cake wrote: > Well, there is the problem > lipo -info /opt/local/lib/db46/libdb-4.6.dylib > Non-fat file: /opt/local/lib/db46/libdb-4.6.dylib is architecture: > i386 > But why? I installed it on Snow Leopard, so why didn't it build it > for both architectures? If you installed it on Snow Leopard, it should have built for x86_64 only. If you want both x86_64 and i386, you need to build with the +universal variant. > And how do I make it do so? And how do I change my whole > installation so this is the default (as I am having similar problems > with other installs)? x86_64 is the default on Snow Leopard. Check your macports.conf to verify that you haven't changed build_arch to i386. From dave at difference.com.au Mon Oct 12 00:01:17 2009 From: dave at difference.com.au (David Cake) Date: Mon, 12 Oct 2009 15:01:17 +0800 Subject: apr-util not building because it can't find db In-Reply-To: <8E3B5CCF-9407-4ECE-A086-C763E9C4DA80@macports.org> References: <74EFB5DB-CCCF-42BD-962D-C50C12BE8579@us.ntt.net> <359DB881-2104-48B2-B57E-7F03623AE7E7@geeklair.net> <58EE75B8-9777-41B3-AEA9-D926D3B54A32@macports.org> <20091012023252.GJ65456@ninagal.withay.com> <39501212-833A-4511-A452-6C68A0BFFE04@macports.org> <8E3B5CCF-9407-4ECE-A086-C763E9C4DA80@macports.org> Message-ID: At 12:36 AM -0500 12/10/09, Ryan Schmidt wrote: >On Oct 11, 2009, at 22:55, David Cake wrote: > >> Well, there is the problem >>lipo -info /opt/local/lib/db46/libdb-4.6.dylib >>Non-fat file: /opt/local/lib/db46/libdb-4.6.dylib is architecture: i386 >> But why? I installed it on Snow Leopard, so why didn't it >>build it for both architectures? > >If you installed it on Snow Leopard, it should have built for x86_64 >only. If you want both x86_64 and i386, you need to build with the >+universal variant. Hmmm.... curious. > >>And how do I make it do so? And how do I change my whole >>installation so this is the default (as I am having similar >>problems with other installs)? > >x86_64 is the default on Snow Leopard. Check your macports.conf to >verify that you haven't changed build_arch to i386. Nope, no build_arch specified (which wasn't a surprise, I don't recall ever altering macports.conf, I didn't even know where it was). I am assuming it is related to Snow Leopard upgrade issues - nuking and starting again. Regards David From fbartolom at gmail.com Mon Oct 12 06:13:39 2009 From: fbartolom at gmail.com (Fabrizio Bartolomucci) Date: Mon, 12 Oct 2009 15:13:39 +0200 Subject: Path problems Message-ID: <4AD32B83.1070804@gmail.com> Following a web suggestion, I edited file macports.conf in /opt/local/etc/macports to add /Developer/usr/bin in the sbin path, but I came to the following error. What else must I make? sudo ./port upgrade outdated ---> Computing dependencies for zlib ---> Building zlib Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_archivers_zlib/work/zlib-1.2.3" && /Developer/usr/bin/make -j2 all " returned error 2 Command output: /usr/bin/gcc-4.2 -O2 -arch x86_64 -DNO_snprintf -DHAS_sprintf_void -DNO_ERRNO_H -c -o example.o example.c make: /usr/bin/gcc-4.2: Command not found From raimue at macports.org Mon Oct 12 06:28:03 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Mon, 12 Oct 2009 15:28:03 +0200 Subject: Path problems In-Reply-To: <4AD32B83.1070804@gmail.com> References: <4AD32B83.1070804@gmail.com> Message-ID: <4AD32EE3.2080203@macports.org> Fabrizio Bartolomucci wrote: > Following a web suggestion, I edited file macports.conf in > /opt/local/etc/macports to add /Developer/usr/bin in the sbin path, but > I came to the following error. > What else must I make? This is absolutely unnecessary. > sudo ./port upgrade outdated > ---> Computing dependencies for zlib > ---> Building zlib > Error: Target org.macports.build returned: shell command " cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_archivers_zlib/work/zlib-1.2.3" > && /Developer/usr/bin/make -j2 all " returned error 2 > Command output: /usr/bin/gcc-4.2 -O2 -arch x86_64 -DNO_snprintf > -DHAS_sprintf_void -DNO_ERRNO_H -c -o example.o example.c > make: /usr/bin/gcc-4.2: Command not found Seems like you do not have Xcode installed which is a requirement for MacPorts. Please see Rainer From ryandesign at macports.org Mon Oct 12 06:59:33 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 12 Oct 2009 08:59:33 -0500 Subject: Path problems In-Reply-To: <4AD32EE3.2080203@macports.org> References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> Message-ID: On Oct 12, 2009, at 08:28, Rainer M?ller wrote: > Fabrizio Bartolomucci wrote: >> Following a web suggestion, I edited file macports.conf in >> /opt/local/etc/macports to add /Developer/usr/bin in the sbin path, >> but >> I came to the following error. >> What else must I make? > > This is absolutely unnecessary. > >> sudo ./port upgrade outdated >> ---> Computing dependencies for zlib >> ---> Building zlib >> Error: Target org.macports.build returned: shell command " cd >> "/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_archivers_zlib >> /work/zlib-1.2.3" >> && /Developer/usr/bin/make -j2 all " returned error 2 >> Command output: /usr/bin/gcc-4.2 -O2 -arch x86_64 -DNO_snprintf >> -DHAS_sprintf_void -DNO_ERRNO_H -c -o example.o example.c >> make: /usr/bin/gcc-4.2: Command not found > > Seems like you do not have Xcode installed which is a requirement for > MacPorts. Please see Or if you do have Xcode installed, then perhaps you unchecked the Unix Development checkbox in the Xcode installer package. If so, reinstall Xcode, and do not deselect that checkbox, because it installs /usr/bin/ gcc-4.2 and other components required by MacPorts. From dluke at geeklair.net Mon Oct 12 07:00:48 2009 From: dluke at geeklair.net (Daniel J. Luke) Date: Mon, 12 Oct 2009 10:00:48 -0400 Subject: apr-util not building because it can't find db In-Reply-To: <58EE75B8-9777-41B3-AEA9-D926D3B54A32@macports.org> References: <74EFB5DB-CCCF-42BD-962D-C50C12BE8579@us.ntt.net> <359DB881-2104-48B2-B57E-7F03623AE7E7@geeklair.net> <58EE75B8-9777-41B3-AEA9-D926D3B54A32@macports.org> Message-ID: On Oct 11, 2009, at 9:47 PM, Ryan Schmidt wrote: > I don't recall what OS David is using, but it seems on Snow Leopard > "file" no longer tells you the architectures in a file. "lipo -info" > still does, though. it still does if it's a single-arch: % file /opt/local/lib/db46/libdb-4.6.dylib /opt/local/lib/db46/libdb-4.6.dylib: Mach-O 64-bit dynamically linked shared library x86_64 (just not if it's 'fat'). -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ From peter at softwolves.pp.se Mon Oct 12 07:04:20 2009 From: peter at softwolves.pp.se (Peter Krefting) Date: Mon, 12 Oct 2009 15:04:20 +0100 (CET) Subject: MacPorts privoxy and autostart on Snow Leopard Message-ID: Hi! I switched my Privoxy installation over to use the MacPorts version because I had problems autostarting the "official" Mac version after upgrading to Leopard and Snow Leopard (I hacked around the autostart on Leopard, but it stopped working again). After installing the version from MacPorts, it doesn't seem to autostart either, though. I am probably missing something vital here, and would appreciate if someone could point me to how to set it up to autostart (starting on boot as a special "privoxy" user). Thank you in advance, -- \\// Peter - http://www.softwolves.pp.se/ From ryandesign at macports.org Mon Oct 12 07:21:51 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 12 Oct 2009 09:21:51 -0500 Subject: MacPorts privoxy and autostart on Snow Leopard In-Reply-To: References: Message-ID: <02181DBE-8EDD-49EB-A997-F9D7484AA0E4@macports.org> On Oct 12, 2009, at 09:04, Peter Krefting wrote: > I switched my Privoxy installation over to use the MacPorts version > because I had problems autostarting the "official" Mac version after > upgrading to Leopard and Snow Leopard (I hacked around the autostart > on Leopard, but it stopped working again). > > After installing the version from MacPorts, it doesn't seem to > autostart either, though. I am probably missing something vital > here, and would appreciate if someone could point me to how to set > it up to autostart (starting on boot as a special "privoxy" user). What have you tried so far? Have you loaded the launchd plist? If so, what command did you use to do that? From ryandesign at macports.org Mon Oct 12 08:05:32 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 12 Oct 2009 10:05:32 -0500 Subject: Path problems In-Reply-To: <4AD344EB.8040902@gmail.com> References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> Message-ID: On Oct 12, 2009, at 10:02, Fabrizio Bartolomucci wrote: > Ryan Schmidt ha scritto: >> > >> On Oct 12, 2009, at 08:28, Rainer M?ller wrote: >> >>> Seems like you do not have Xcode installed which is a requirement >>> for >>> MacPorts. Please see >> >> Or if you do have Xcode installed, then perhaps you unchecked the >> Unix Development checkbox in the Xcode installer package. If so, >> reinstall Xcode, and do not deselect that checkbox, because it >> installs /usr/bin/gcc-4.2 and other components required by MacPorts. > > Actually I did nothing but installing Snow Leopard to discover > MacPorts did not like it so much... MacPorts works great with Snow Leopard. Maybe you didn't upgrade your Xcode to version 3.2? You need to do that. The Xcode 3.2 installer package is on the Snow Leopard DVD. P.S: Don't forget to use Reply All so your reply goes to the list too, not just to me. From Damien at Clauzel.nom.fr Mon Oct 12 08:10:50 2009 From: Damien at Clauzel.nom.fr (Damien Clauzel) Date: Mon, 12 Oct 2009 17:10:50 +0200 Subject: MacPorts privoxy and autostart on Snow Leopard In-Reply-To: References: Message-ID: <2B29EFF2-0120-4AAE-9B69-057E69E89057@Clauzel.nom.fr> Le 12 oct. 2009 ? 16:04, Peter Krefting a ?crit : > I switched my Privoxy installation over to use the MacPorts version > because I had problems autostarting the "official" Mac version after > upgrading to Leopard and Snow Leopard (I hacked around the autostart > on Leopard, but it stopped working again). I am using this plist for launchd. It lives in /Library/LaunchDaemons/fr.nom.Clauzel.privoxy.plist and starts automatically privoxy on startup. ___ Label fr.nom.Clauzel.privoxy OnDemand ProgramArguments /opt/local/sbin/privoxy --no-daemon /opt/local/etc/privoxy/config RunAtLoad UserName privoxy GroupName privoxy ServiceDescription dClauzel privoxy serveur ___ I know that some people use daemondo, but I have never see the point of using this tool for managing processes; launched does everything that is needed. Cheers, Damien From fbartolom at gmail.com Mon Oct 12 08:41:07 2009 From: fbartolom at gmail.com (Fabrizio Bartolomucci) Date: Mon, 12 Oct 2009 17:41:07 +0200 Subject: Path problems In-Reply-To: References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> Message-ID: <4AD34E13.7040809@gmail.com> Ryan Schmidt ha scritto: > > On Oct 12, 2009, at 10:02, Fabrizio Bartolomucci wrote: > >> Ryan Schmidt ha scritto: >>> >> >>> On Oct 12, 2009, at 08:28, Rainer M?ller wrote: >>> >>>> Seems like you do not have Xcode installed which is a requirement for >>>> MacPorts. Please see >>> >>> Or if you do have Xcode installed, then perhaps you unchecked the >>> Unix Development checkbox in the Xcode installer package. If so, >>> reinstall Xcode, and do not deselect that checkbox, because it >>> installs /usr/bin/gcc-4.2 and other components required by MacPorts. >> > >> Actually I did nothing but installing Snow Leopard to discover >> MacPorts did not like it so much... > > MacPorts works great with Snow Leopard. Maybe you didn't upgrade your > Xcode to version 3.2? You need to do that. The Xcode 3.2 installer > package is on the Snow Leopard DVD. > Actually I am installing it form Apple: version is 321_10m2003, I shall see what happens. From fbartolom at gmail.com Mon Oct 12 08:44:23 2009 From: fbartolom at gmail.com (Fabrizio Bartolomucci) Date: Mon, 12 Oct 2009 17:44:23 +0200 Subject: Path problems In-Reply-To: References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> Message-ID: <4AD34ED7.1020105@gmail.com> Ryan Schmidt ha scritto: > >> Actually I did nothing but installing Snow Leopard to discover >> MacPorts did not like it so much... > > MacPorts works great with Snow Leopard. Maybe you didn't upgrade your > Xcode to version 3.2? You need to do that. The Xcode 3.2 installer > package is on the Snow Leopard DVD. In fact it now goes forward. I shall report if it gets stuck somewhere else. Thanks, Fabrizio From payam.minoofar at meissner.com Mon Oct 12 09:08:03 2009 From: payam.minoofar at meissner.com (Payam Minoofar) Date: Mon, 12 Oct 2009 09:08:03 -0700 Subject: libfontconfig Message-ID: <4804DEAE-5F85-4F81-8DB8-F7B3CA909FBD@meissner.com> Hi, I get this error when I try to upgrade wine-devel. I can't figure which package provides libfontconfig using "list" and "search". Thanks in advance. Payam [payam-imac:~] payam% sudo port upgrade wine-devel ---> Computing dependencies for wine-devel ---> Extracting wine-devel Error: You cannot install wine-devel for the architecture(s) i386 Error: because /opt/local/lib/libfontconfig.dylib only contains the architecture(s) x86_64. Error: Try reinstalling the port that provides /opt/local/lib/ libfontconfig.dylib with the +universal variant. Error: Target org.macports.extract returned: incompatible architectures in dependencies Error: Unable to upgrade port: 1 From fbartolom at gmail.com Mon Oct 12 09:09:43 2009 From: fbartolom at gmail.com (Fabrizio Bartolomucci) Date: Mon, 12 Oct 2009 18:09:43 +0200 Subject: Path problems In-Reply-To: References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> Message-ID: <4AD354C7.3080700@gmail.com> Ryan Schmidt ha scritto: > > > MacPorts works great with Snow Leopard. Maybe you didn't upgrade your > Xcode to version 3.2? You need to do that. The Xcode 3.2 installer > package is on the Snow Leopard DVD. > > In fact now error has passed to: checking abstract socket namespace... no checking for XML_ParserCreate_MM in -lexpat... no configure: error: Could not find expat.h, check config.log for failed attempts Error: Unable to upgrade port: 1 From ryandesign at macports.org Mon Oct 12 09:31:05 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 12 Oct 2009 11:31:05 -0500 Subject: libfontconfig In-Reply-To: <4804DEAE-5F85-4F81-8DB8-F7B3CA909FBD@meissner.com> References: <4804DEAE-5F85-4F81-8DB8-F7B3CA909FBD@meissner.com> Message-ID: <44ECA864-AF5B-46A9-99A2-D538EC4CF0A2@macports.org> On Oct 12, 2009, at 11:08, Payam Minoofar wrote: > I get this error when I try to upgrade wine-devel. I can't figure > which package provides libfontconfig using "list" and "search". > > Thanks in advance. > > Payam > > [payam-imac:~] payam% sudo port upgrade wine-devel > ---> Computing dependencies for wine-devel > ---> Extracting wine-devel > Error: You cannot install wine-devel for the architecture(s) i386 > Error: because /opt/local/lib/libfontconfig.dylib only contains the > architecture(s) x86_64. > Error: Try reinstalling the port that provides /opt/local/lib/ > libfontconfig.dylib with the +universal variant. > Error: Target org.macports.extract returned: incompatible > architectures in dependencies > Error: Unable to upgrade port: 1 "port provides /opt/local/lib/libfontconfig.dylib" should tell you that this file is provided by the "fontconfig" port. From ryandesign at macports.org Mon Oct 12 09:33:34 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 12 Oct 2009 11:33:34 -0500 Subject: Path problems In-Reply-To: <4AD354C7.3080700@gmail.com> References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> <4AD354C7.3080700@gmail.com> Message-ID: <15536E86-F445-47CB-BBC4-3156A2811029@macports.org> On Oct 12, 2009, at 11:09, Fabrizio Bartolomucci wrote: > checking abstract socket namespace... no > checking for XML_ParserCreate_MM in -lexpat... no > configure: error: Could not find expat.h, check config.log for > failed attempts > > Error: Unable to upgrade port: 1 Did you upgrade from Leopard, and if so did you previously have MacPorts installed in Leopard, and if so did you follow the migration procedure and reinstall all ports now that you're on Snow Leopard? See: http://trac.macports.org/wiki/Migration If that's not it, then please "sudo port clean PORT" where PORT is the name of whatever port failed, and then "sudo port -d install PORT" where PORT is whatever port you were trying to install, then send us the complete debug output so that we can try to figure out what went wrong. From payam.minoofar at meissner.com Mon Oct 12 11:02:38 2009 From: payam.minoofar at meissner.com (Payam Minoofar) Date: Mon, 12 Oct 2009 11:02:38 -0700 Subject: libsm compile problem Message-ID: Hi, In the process of upgrading wine-devel, I keep encountering architecture mismatch errors. I cannot get port to upgrade dependencies to universal builds with sudo port upgrade --enforce-variants wine-devel or with sudo port install wine-devel +universal In the process of manually upgrading all the ports that need to be compiled as universal, I encountered this problem with libsm. I hope the solution is simple. Payam [payam-imac:~] payam% sudo port install xorg-libsm +universal ---> Computing dependencies for xorg-libsm ---> Fetching xorg-libsm ---> Verifying checksum(s) for xorg-libsm ---> Extracting xorg-libsm ---> Configuring xorg-libsm ---> Building xorg-libsm Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg -libsm/work/libSM-1.1.1" && /usr/bin/make -j2 all " returned error 2 Command output: _SmcOpenConnection in sm_client.o _SmcOpenConnection in sm_client.o _SmcOpenConnection in sm_client.o _SmcOpenConnection in sm_client.o _SmcSetProperties in sm_client.o _SmcSetProperties in sm_client.o _SmcSetProperties in sm_client.o _SmsShutdownCancelled in sm_manager.o _SmsShutdownCancelled in sm_manager.o _SmsSaveComplete in sm_manager.o _SmsSaveComplete in sm_manager.o _SmsDie in sm_manager.o _SmsDie in sm_manager.o _SmsInteract in sm_manager.o _SmsInteract in sm_manager.o _SmsSaveYourselfPhase2 in sm_manager.o _SmsSaveYourselfPhase2 in sm_manager.o _SmsSaveYourself in sm_manager.o _SmsSaveYourself in sm_manager.o _SmsRegisterClientReply in sm_manager.o _SmsRegisterClientReply in sm_manager.o _SmsReturnProperties in sm_manager.o _SmsReturnProperties in sm_manager.o _SmsReturnProperties in sm_manager.o ld: symbol(s) not found collect2: ld returned 1 exit status lipo: can't open input file: /var/tmp//ccbXaEji.out (No such file or directory) make[2]: *** [libSM.la] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Error: Status 1 encountered during processing. From nospaming at aedon.eu Mon Oct 12 11:15:24 2009 From: nospaming at aedon.eu (Peter J. Nachtigall) Date: Mon, 12 Oct 2009 20:15:24 +0200 Subject: testdisk. huh where is it? In-Reply-To: <4AD34ED7.1020105@gmail.com> References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> <4AD34ED7.1020105@gmail.com> Message-ID: <4AD3723C.1030609@aedon.eu> hi all sudo port install testdisk ---> Computing dependencies for testdisk ---> Fetching testdisk ---> Verifying checksum(s) for testdisk ---> Extracting testdisk ---> Configuring testdisk ---> Building testdisk ---> Staging testdisk into destroot ---> Installing testdisk @6.11_0 ---> Activating testdisk @6.11_0 ---> Cleaning testdisk /opt/local/var/macports/sources/rsync.macports.org/release/ports/sysutils/testdisk user:/> testdisk -bash: testdisk: command not found /opt/local/var/macports/sources/rsync.macports.org/release/ports/sysutils/testdisk user:/> which testdisk /opt/local/var/macports/sources/rsync.macports.org/release/ports/sysutils/testdisk What is wrong? Cheers -- Peter J. Nachtigall aedon DESIGNS http://www.hochzeitsbuch.info/ From ryandesign at macports.org Mon Oct 12 17:39:49 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 12 Oct 2009 19:39:49 -0500 Subject: testdisk. huh where is it? In-Reply-To: <4AD3723C.1030609@aedon.eu> References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> <4AD34ED7.1020105@gmail.com> <4AD3723C.1030609@aedon.eu> Message-ID: On Oct 12, 2009, at 13:15, Peter J. Nachtigall wrote: > sudo port install testdisk > ---> Computing dependencies for testdisk > ---> Fetching testdisk > ---> Verifying checksum(s) for testdisk > ---> Extracting testdisk > ---> Configuring testdisk > ---> Building testdisk > ---> Staging testdisk into destroot > ---> Installing testdisk @6.11_0 > ---> Activating testdisk @6.11_0 > ---> Cleaning testdisk > /opt/local/var/macports/sources/rsync.macports.org/release/ports/ > sysutils/testdisk > user:/> testdisk > -bash: testdisk: command not found > /opt/local/var/macports/sources/rsync.macports.org/release/ports/ > sysutils/testdisk > user:/> which testdisk > /opt/local/var/macports/sources/rsync.macports.org/release/ports/ > sysutils/testdisk > > What is wrong? "port contents testdisk" should tell you exactly what it put on your hard drive and where. In this case, you should find that the testdisk program is in the directory /opt/local/sbin. /opt/local/sbin should be in your PATH, just like /opt/local/bin is, so I'm not sure why you didn't find it. What is your PATH set to? You may want to adjust it. From ryandesign at macports.org Mon Oct 12 17:48:43 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 12 Oct 2009 19:48:43 -0500 Subject: libsm compile problem In-Reply-To: References: Message-ID: <49B024DD-2638-42BB-A382-5C2BE0B7AC28@macports.org> On Oct 12, 2009, at 13:02, Payam Minoofar wrote: > In the process of upgrading wine-devel, I keep encountering > architecture mismatch errors. You should encounter these errors on initial installation, but not on upgrade -- unless perhaps you upgraded from Leopard to Snow Leopard and have not uninstalled and reinstalled all ports as per the Migration instructions? http://trac.macports.org/wiki/Migration > I cannot get port to upgrade > dependencies to universal builds with > sudo port upgrade --enforce-variants wine-devel > or with > sudo port install wine-devel +universal Did you try sudo port upgrade --enforce-variants wine-devel +universal ? The point of --enforce-variants is to enforce the variants you specify on the command line (or in variants.conf) but you didn't specify any variants on the command line. > In the process of manually upgrading all the ports that need to be > compiled as universal, I encountered this problem with libsm. I hope > the solution is simple. [snip] > ---> Building xorg-libsm > Error: Target org.macports.build returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg > -libsm/work/libSM-1.1.1" && /usr/bin/make -j2 all " returned error 2 > Command output: _SmcOpenConnection in sm_client.o [snip] > _SmsReturnProperties in sm_manager.o > ld: symbol(s) not found This is probably again an architecture mismatch. You're not seeing the first error because MacPorts only shows the last 30 lines of error, but if you reinstall with the -d switch (sudo port -d install whatever) and examine the output more closely you should find a line about architectures being missing from some library (some dependency of xorg-libsm) and you must reinstall that port universal. Before you can install wine-devel on Snow Leopard, I'm afraid ALL library and runtime dependencies of wine-devel will need to be built universal (or for i386 only, but that's probably not a good idea). From t.stein at syseleven.de Tue Oct 13 02:13:27 2009 From: t.stein at syseleven.de (Thomas Stein) Date: Tue, 13 Oct 2009 11:13:27 +0200 Subject: kmail (could not start process for imap) Message-ID: <4AD444B7.9060509@syseleven.de> Hello. I have a few questions regarding kmail-4.3.2. I installed kmail successfull via macports. When i first started kmail i was able to configure my imap account and check for messages and recieved them and so one. Everything was fine. But now i get the error message "Could not start process for imap" after kmail has been started. Someone has an idea whats causing this? By the way, what is the correct way to start an macports X11 application? Do i have to run launchctl every time? best regards and thanks t. From ryandesign at macports.org Tue Oct 13 04:10:37 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 13 Oct 2009 06:10:37 -0500 Subject: kmail (could not start process for imap) In-Reply-To: <4AD444B7.9060509@syseleven.de> References: <4AD444B7.9060509@syseleven.de> Message-ID: <37EB20FB-F9A8-4DCB-B26B-82C45C332365@macports.org> On Oct 13, 2009, at 04:13, Thomas Stein wrote: > I have a few questions regarding kmail-4.3.2. I installed kmail > successfull via macports. When i first started kmail i was able to > configure my imap account and check for messages and recieved them > and so one. Everything was fine. But now i get the error message > "Could not start process for imap" after kmail has been started. > Someone has an idea whats causing this? > > By the way, what is the correct way to start an macports X11 > application? Do i have to run launchctl every time? I don't know kmail, but to start an X11 app, you just type its name in the terminal, as you would with any command line program. Mac OS X 10.5 and later will automatically start X11 for you if it is not already running (assuming you have not overwritten Apple's value for the DISPLAY environment variable). Usually you would only use launchctl to either start a server process now and cause it to start automatically at every system startup, or to do the reverse and stop a server process and cause it to no longer start automatically at system startup. As far as I can tell, kmail is an email client, so I'm not sure why that would require a server process. Even if it did, you would only need to start it once and it would from then on always be running. What command are you running with launchctl? From t.stein at syseleven.de Tue Oct 13 04:29:39 2009 From: t.stein at syseleven.de (Thomas Stein) Date: Tue, 13 Oct 2009 13:29:39 +0200 Subject: kmail (could not start process for imap) In-Reply-To: <37EB20FB-F9A8-4DCB-B26B-82C45C332365@macports.org> References: <4AD444B7.9060509@syseleven.de> <37EB20FB-F9A8-4DCB-B26B-82C45C332365@macports.org> Message-ID: <4AD464A3.40909@syseleven.de> Ryan Schmidt schrieb: > Usually you would only use launchctl to either start a server process > now and cause it to start automatically at every system startup, or to > do the reverse and stop a server process and cause it to no longer > start automatically at system startup. As far as I can tell, kmail is > an email client, so I'm not sure why that would require a server > process. Even if it did, you would only need to start it once and it > would from then on always be running. What command are you running > with launchctl? I have to start an dbus session, that's what the documentation says. launchctl load /Library/LaunchAgents/org.freedesktop.dbus-session.plist After that i can start kmail which starts but has problems with the imap process. Any idea on that issue. Thanks and regards t. From s.l.cotter at warwick.ac.uk Tue Oct 13 04:40:17 2009 From: s.l.cotter at warwick.ac.uk (Simon Cotter) Date: Tue, 13 Oct 2009 12:40:17 +0100 Subject: Checksum mismatch while installing gperf Message-ID: <965F2ACC-85AA-4F5A-9544-D9DB86EF3FC8@warwick.ac.uk> I am trying to install scipy and other python packages on my machine (snow leopard, intel core duo), but I am repeatedly coming up against the following error while trying to build one of the dependencies, gperf: ---> Computing dependencies for gperf ---> Verifying checksum(s) for gperf Error: Checksum (md5) mismatch for gperf-3.0.4.tar.gz Error: Checksum (sha1) mismatch for gperf-3.0.4.tar.gz Error: Checksum (rmd160) mismatch for gperf-3.0.4.tar.gz Error: Target org.macports.checksum returned: Unable to verify file checksums Error: Status 1 encountered during processing. I have tried to clean it and install again a few times but to no avail. I'm not sure if the file is corrupt or if there has been a stealth upgrade, or if I am being stupid, but any help is appreciated. Many thanks, Simon Cotter From ryandesign at macports.org Tue Oct 13 04:46:38 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 13 Oct 2009 06:46:38 -0500 Subject: Checksum mismatch while installing gperf In-Reply-To: <965F2ACC-85AA-4F5A-9544-D9DB86EF3FC8@warwick.ac.uk> References: <965F2ACC-85AA-4F5A-9544-D9DB86EF3FC8@warwick.ac.uk> Message-ID: <235283C4-D3DF-4775-96F2-9A9E183B0FE6@macports.org> Simon, On Oct 13, 2009, at 06:40, Simon Cotter wrote: > I am trying to install scipy and other python packages on my machine > (snow leopard, intel core duo), but I am repeatedly coming up > against the following error while trying to build one of the > dependencies, gperf: > > ---> Computing dependencies for gperf > ---> Verifying checksum(s) for gperf > Error: Checksum (md5) mismatch for gperf-3.0.4.tar.gz > Error: Checksum (sha1) mismatch for gperf-3.0.4.tar.gz > Error: Checksum (rmd160) mismatch for gperf-3.0.4.tar.gz > Error: Target org.macports.checksum returned: Unable to verify file > checksums > Error: Status 1 encountered during processing. > > I have tried to clean it and install again a few times but to no > avail. I'm not sure if the file is corrupt or if there has been a > stealth upgrade, or if I am being stupid, but any help is appreciated. Please clean out the mismatched distfile and try again: sudo port clean --all gperf sudo port install gperf If it again doesn't work, it should print a line saying what server it downloaded the file from. Show us this output so we can investigate that server. Also, you can investigate the distfile it downloaded. It's located in / opt/local/var/macports/distfiles/gperf/. It's supposed to be a gzipped tarball. Is it? Or is it perhaps an HTML page, or some other kind of file? What's in it? From lars.sonchocky-helldorf at hamburg.de Tue Oct 13 07:06:08 2009 From: lars.sonchocky-helldorf at hamburg.de (Lars Sonchocky-Helldorf) Date: Tue, 13 Oct 2009 16:06:08 +0200 Subject: X11 problems References: <442965B8-B05C-4043-8381-7DCF44F592F5@assense.com> Message-ID: After doing a sudo port -v upgrade outdated and a subsequent sudo port -v uninstall inactive I now get the following messages over and over in my system.log: Oct 13 15:50:55 local-admins-macbook-pro com.apple.launchd[200] (org.x.startx): Throttling respawn: Will start in 8 seconds Oct 13 15:50:55 local-admins-macbook-pro org.x.privileged_startx [64739]: font_cache: Done Oct 13 15:51:03 local-admins-macbook-pro org.x.startx[13522]: font_cache: Scanning user font directories to generate X11 font caches Oct 13 15:51:03 local-admins-macbook-pro org.x.startx[13522]: font_cache: Updating FC cache Oct 13 15:51:03 local-admins-macbook-pro org.x.privileged_startx [64739]: font_cache: Scanning system font directories to generate X11 font caches Oct 13 15:51:03 local-admins-macbook-pro defaults[13552]: \nThe domain/default pair of (org.x.X11, dpi) does not exist Oct 13 15:51:03 local-admins-macbook-pro org.x.startx[13522]: xauth: creating new authority file /Users/lars/.serverauth.13522 Oct 13 15:51:03 local-admins-macbook-pro org.x.startx[13522]: Xquartz: Unable to find application for org.x.X11 Oct 13 15:51:03 local-admins-macbook-pro org.x.privileged_startx [64739]: font_cache: Updating FC cache Oct 13 15:51:05 local-admins-macbook-pro org.x.startx[13522]: font_cache: Done Oct 13 15:51:05 local-admins-macbook-pro org.x.startx[13522]: giving up. Oct 13 15:51:05 local-admins-macbook-pro org.x.startx[13522]: /usr/ X11/bin/xinit: Connection refused (errno 61): unable to connect to X server Oct 13 15:51:05 local-admins-macbook-pro org.x.startx[13522]: /usr/ X11/bin/xinit: Oct 13 15:51:05 local-admins-macbook-pro org.x.startx[13522]: No such process (errno 3): Server error. Oct 13 15:51:05 local-admins-macbook-pro com.apple.launchd[200] (org.x.startx): Throttling respawn: Will start in 8 seconds I then tried: sudo port uninstall xorg-server sudo port uninstall xinit port clean --all xorg-server port clean --all xinit sudo port -v install xorg-server but this didn't help the cause. My X11.app is in /Applications/MacPorts/X11.app (which I can start by double clicking - but the log messages still keep coming then) and there was an older version lingering around in /Applications/ Utilities which I deleted manually. What can I do now? thanks, Lars From and.damore at macports.org Tue Oct 13 09:01:43 2009 From: and.damore at macports.org (Andrea D'Amore) Date: Tue, 13 Oct 2009 18:01:43 +0200 Subject: I screwed up my .xinitrc In-Reply-To: <4AD02FC3.6050303@gmail.com> References: <4AD02FC3.6050303@gmail.com> Message-ID: On 10/ott/09, at 08:54, Wodenhelm wrote: > I'm trying to run KDE by means of "_startx_," using _echo 'source / > sw/bin/init.sh > > export KDEWM=kwin > > /sw/bin/startkde >/tmp/kde.log 2>&1' > ~/.xinitrc > > _And this is what I get: Not sure what you were trying to do but you've dumped output form fink's kde start script into ~/.xinitrc, now you can delete that file and try to just use the startkde from macports package. -- Andrea From deliverable at gmail.com Tue Oct 13 09:36:40 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Tue, 13 Oct 2009 12:36:40 -0400 Subject: Snow Leopard ate my ports Message-ID: <7c737f300910130936m7f9a0e3s2e2e632c02f89592@mail.gmail.com> So I upgraded to SL, just to get port command to spit abuse about images all being wrong now. By contrast to 32 bit => 64 bit upgrade, my old port setup doesn't work anymore so I can't follow the procedure for re-installing ports by creating a list of those previously installed with the "list installed" command. How do I extract the exact list of ports to re-install from my now-useless old setup? Cheers, Alexy From jmr at macports.org Tue Oct 13 09:38:39 2009 From: jmr at macports.org (Joshua Root) Date: Wed, 14 Oct 2009 03:38:39 +1100 Subject: Snow Leopard ate my ports In-Reply-To: <7c737f300910130936m7f9a0e3s2e2e632c02f89592@mail.gmail.com> References: <7c737f300910130936m7f9a0e3s2e2e632c02f89592@mail.gmail.com> Message-ID: <4AD4AD0F.6060703@macports.org> On 2009-10-14 03:36, Alexy Khrabrov wrote: > So I upgraded to SL, just to get port command to spit abuse about > images all being wrong now. By contrast to 32 bit => 64 bit upgrade, > my old port setup doesn't work anymore so I can't follow the procedure > for re-installing ports by creating a list of those previously > installed with the "list installed" command. 'port list' isn't what you want anyway; just follow the instructions at - Josh From deliverable at gmail.com Tue Oct 13 10:03:11 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Tue, 13 Oct 2009 13:03:11 -0400 Subject: Snow Leopard ate my ports In-Reply-To: <4AD4AD0F.6060703@macports.org> References: <7c737f300910130936m7f9a0e3s2e2e632c02f89592@mail.gmail.com> <4AD4AD0F.6060703@macports.org> Message-ID: <7c737f300910131003i1efb4a54n1269092c02ddc569@mail.gmail.com> Well, I moved /opt/local to /opt/local-old prior to running the Snow Leopard installer of the new MacPorts. Now 'port installed' says that no ports are installed. Am I supposed to run the installer on top of the existing /opt/local? In general, I'd like a simple way to examine a former /opt/local and list the ports which were there when it was "the" /opt/local... Cheers, Alexy On Tue, Oct 13, 2009 at 12:38 PM, Joshua Root wrote: > On 2009-10-14 03:36, Alexy Khrabrov wrote: > 'port list' isn't what you want anyway; just follow the instructions at > From jmr at macports.org Tue Oct 13 10:39:29 2009 From: jmr at macports.org (Joshua Root) Date: Wed, 14 Oct 2009 04:39:29 +1100 Subject: Snow Leopard ate my ports In-Reply-To: <7c737f300910131003i1efb4a54n1269092c02ddc569@mail.gmail.com> References: <7c737f300910130936m7f9a0e3s2e2e632c02f89592@mail.gmail.com> <4AD4AD0F.6060703@macports.org> <7c737f300910131003i1efb4a54n1269092c02ddc569@mail.gmail.com> Message-ID: <4AD4BB51.1090601@macports.org> On 2009-10-14 04:03, Alexy Khrabrov wrote: > Well, I moved /opt/local to /opt/local-old prior to running the Snow > Leopard installer of the new MacPorts. Now 'port installed' says that > no ports are installed. Am I supposed to run the installer on top of > the existing /opt/local? It's obviously not going to know about anything you moved somewhere else, so yeah... > In general, I'd like a simple way to examine a former /opt/local and > list the ports which were there when it was "the" /opt/local... ls -d /opt/local-old/var/macports/receipts/*/* - Josh From davidh at ipac.caltech.edu Tue Oct 13 11:45:30 2009 From: davidh at ipac.caltech.edu (David Henderson) Date: Tue, 13 Oct 2009 11:45:30 -0700 Subject: privoxy install v 3.0.12 needs default.action.master copied to default.action (Re: macports-users Digest, Vol 38, Issue 12) In-Reply-To: References: Message-ID: Hello Peter, I too was puzzled. The daemon would immediately exit. I ran it from the command line and found that the configuration wasn't quite complete. Hint: to run it from the terminal window: 1. cd /opt/local/etc/privoxy 2. make the files in that directory readable and executable 3. simply run it from the shell: privoxy --no-daemon What I found was that the macports build script does not do a step the privoxy installer does, backup the "default.action" and copy default.action.master over default.action. So, I downloaded the 3.0.12 source for privoxy, untar'd it, and copied the default.action.master file into /opt/local/etc/privoxy/ default.action I found this out when Snow Leopard became the hot topic, and I neglected to write a ticket on this. Some action needs to be taken to get it to start up without this manual configuration twiddling. I'm at a loss what the correct build script action should be. At a minimum it should copy default.action.master to /opt/local/etc/privoxy and give the user a clue that it needs renaming to default.action Any other ideas on how to resolve this from others more experienced with macports? David On Oct 13, 2009, at 7:00 AM, macports-users- request at lists.macosforge.org wrote: > > Message: 2 > Date: Mon, 12 Oct 2009 15:04:20 +0100 (CET) > From: Peter Krefting > To: macports-users at lists.macosforge.org > Subject: MacPorts privoxy and autostart on Snow Leopard > Message-ID: > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > Hi! > > I switched my Privoxy installation over to use the MacPorts version > because I > had problems autostarting the "official" Mac version after upgrading > to Leopard > and Snow Leopard (I hacked around the autostart on Leopard, but it > stopped > working again). > > After installing the version from MacPorts, it doesn't seem to > autostart > either, though. I am probably missing something vital here, and would > appreciate if someone could point me to how to set it up to > autostart (starting > on boot as a special "privoxy" user). > > Thank you in advance, > -- > \\// Peter - http://www.softwolves.pp.se/ > > > ------------------------------ > > Message: 3 > Date: Mon, 12 Oct 2009 09:21:51 -0500 > From: Ryan Schmidt > To: Peter Krefting > Cc: macports-users at lists.macosforge.org > Subject: Re: MacPorts privoxy and autostart on Snow Leopard > Message-ID: <02181DBE-8EDD-49EB-A997-F9D7484AA0E4 at macports.org> > Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes > > > On Oct 12, 2009, at 09:04, Peter Krefting wrote: > >> I switched my Privoxy installation over to use the MacPorts version >> because I had problems autostarting the "official" Mac version after >> upgrading to Leopard and Snow Leopard (I hacked around the autostart >> on Leopard, but it stopped working again). >> >> After installing the version from MacPorts, it doesn't seem to >> autostart either, though. I am probably missing something vital >> here, and would appreciate if someone could point me to how to set >> it up to autostart (starting on boot as a special "privoxy" user). > > What have you tried so far? Have you loaded the launchd plist? If so, > what command did you use to do that? > > > > ------------------------------ > > Message: 4 > Date: Mon, 12 Oct 2009 10:05:32 -0500 > From: Ryan Schmidt > To: Fabrizio Bartolomucci > Cc: MacPorts Users > Subject: Re: Path problems > Message-ID: > Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes > > > On Oct 12, 2009, at 10:02, Fabrizio Bartolomucci wrote: > >> Ryan Schmidt ha scritto: >>> >> >>> On Oct 12, 2009, at 08:28, Rainer M?ller wrote: >>> >>>> Seems like you do not have Xcode installed which is a requirement >>>> for >>>> MacPorts. Please see >>> >>> Or if you do have Xcode installed, then perhaps you unchecked the >>> Unix Development checkbox in the Xcode installer package. If so, >>> reinstall Xcode, and do not deselect that checkbox, because it >>> installs /usr/bin/gcc-4.2 and other components required by MacPorts. >> > >> Actually I did nothing but installing Snow Leopard to discover >> MacPorts did not like it so much... > > MacPorts works great with Snow Leopard. Maybe you didn't upgrade your > Xcode to version 3.2? You need to do that. The Xcode 3.2 installer > package is on the Snow Leopard DVD. > > > P.S: Don't forget to use Reply All so your reply goes to the list too, > not just to me. > > > > ------------------------------ > > Message: 5 > Date: Mon, 12 Oct 2009 17:10:50 +0200 > From: Damien Clauzel > To: MacPorts Users > Subject: Re: MacPorts privoxy and autostart on Snow Leopard > Message-ID: <2B29EFF2-0120-4AAE-9B69-057E69E89057 at Clauzel.nom.fr> > Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes > > Le 12 oct. 2009 ? 16:04, Peter Krefting a ?crit : > >> I switched my Privoxy installation over to use the MacPorts version >> because I had problems autostarting the "official" Mac version after >> upgrading to Leopard and Snow Leopard (I hacked around the autostart >> on Leopard, but it stopped working again). > > I am using this plist for launchd. > > It lives in /Library/LaunchDaemons/fr.nom.Clauzel.privoxy.plist and > starts automatically privoxy on startup. > > ___ > > "> > > > > Label > fr.nom.Clauzel.privoxy > > OnDemand > > > ProgramArguments > > /opt/local/sbin/privoxy > --no-daemon > /opt/local/etc/privoxy/config > > > RunAtLoad > > > UserName > privoxy > GroupName > privoxy > > ServiceDescription > dClauzel privoxy serveur > > > ___ > > I know that some people use daemondo, but I have never see the point > of using this tool for managing processes; launched does everything > that is needed. > > Cheers, > Damien -------------- next part -------------- An HTML attachment was scrubbed... URL: From deliverable at gmail.com Tue Oct 13 12:00:18 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Tue, 13 Oct 2009 15:00:18 -0400 Subject: Snow Leopard ate my ports In-Reply-To: <4AD4BB51.1090601@macports.org> References: <7c737f300910130936m7f9a0e3s2e2e632c02f89592@mail.gmail.com> <4AD4AD0F.6060703@macports.org> <7c737f300910131003i1efb4a54n1269092c02ddc569@mail.gmail.com> <4AD4BB51.1090601@macports.org> Message-ID: <7c737f300910131200y28757d6bx92959dab147b07f3@mail.gmail.com> Josh -- On Tue, Oct 13, 2009 at 1:39 PM, Joshua Root wrote: > ls -d /opt/local-old/var/macports/receipts/*/* Thanks! Still the migration doc is pretty bare bones -- it says to save a simple list of ports, hand-pick the ones you still need, and skip the dependencies, and remember to reinstall with the right variants! But of course I'm going to forget to add +weird_godzilla_hack for an obscure dependency I need, and it's all going to be wrong. Is there a more semi-automatic way to -- record all ports with all variants needed to reinstall them -- in correct order of dependencies -- and feed it to a new, empty port install? Cheers, Alexy From dluke at geeklair.net Tue Oct 13 12:22:48 2009 From: dluke at geeklair.net (Daniel J. Luke) Date: Tue, 13 Oct 2009 15:22:48 -0400 Subject: Snow Leopard ate my ports In-Reply-To: <7c737f300910131200y28757d6bx92959dab147b07f3@mail.gmail.com> References: <7c737f300910130936m7f9a0e3s2e2e632c02f89592@mail.gmail.com> <4AD4AD0F.6060703@macports.org> <7c737f300910131003i1efb4a54n1269092c02ddc569@mail.gmail.com> <4AD4BB51.1090601@macports.org> <7c737f300910131200y28757d6bx92959dab147b07f3@mail.gmail.com> Message-ID: <61FC0C9E-050E-48C3-AE05-DDEC190C5AA1@geeklair.net> On Oct 13, 2009, at 3:00 PM, Alexy Khrabrov wrote: > -- record all ports with all variants needed to reinstall them port installed lists the ports with their variants. > -- in correct order of dependencies I don't think that you can do this with a simple port foo command. > -- and feed it to a new, empty port install? you could probably use the port installed output to generate a list of commands for port, it shouldn't matter too much if it's not in dependency order since port will install dependencies when they are needed and if they're listed later it'll just say "already installed" for that port. -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ From deliverable at gmail.com Tue Oct 13 12:26:56 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Tue, 13 Oct 2009 15:26:56 -0400 Subject: Snow Leopard ate my ports In-Reply-To: <7c737f300910131200y28757d6bx92959dab147b07f3@mail.gmail.com> References: <7c737f300910130936m7f9a0e3s2e2e632c02f89592@mail.gmail.com> <4AD4AD0F.6060703@macports.org> <7c737f300910131003i1efb4a54n1269092c02ddc569@mail.gmail.com> <4AD4BB51.1090601@macports.org> <7c737f300910131200y28757d6bx92959dab147b07f3@mail.gmail.com> Message-ID: <7c737f300910131226s67e2e267wd52329efd1baf0e@mail.gmail.com> OK, for the Snow Leopard on top of Leopard case, I went back and did the following: -- put back my old /opt/local -- ran the new 1.8.1 installer, which dropped the new port command and friends on top if it Now port installed shows stuff, and they seemed to work as before. In fact they did work, at least those I used, under SL, it's just the port command itself was broken by the upgrade, and now fixed by install-over. My question is, do I really need to reinstall all ports, or this SL on top of L is OK? Last time, I migrated from 32-bit Leopard to 64-bit one (moving to a new MBP), and then I felt I had to do it, although 32-bit stuff still worked -- but there was a presumable advantage of getting thing recompiled under 64-bit gcc and stuff. But are there any caveats why one should recompile a 64-bit Leopard-fathered ports setup after SL upgrade? Cheers, Alexy From dweber at macports.org Tue Oct 13 12:41:49 2009 From: dweber at macports.org (Darren Weber) Date: Tue, 13 Oct 2009 12:41:49 -0700 Subject: suggestion for 'port outdated' to print a dependency tree Message-ID: Is it possible to get a txt-based listing of the dependency tree from 'port outdated'? Regards, Darren -------------- next part -------------- An HTML attachment was scrubbed... URL: From perry at macports.org Tue Oct 13 12:47:39 2009 From: perry at macports.org (Perry Lee) Date: Tue, 13 Oct 2009 12:47:39 -0700 Subject: suggestion for 'port outdated' to print a dependency tree In-Reply-To: References: Message-ID: <4AD4D95B.5000105@macports.org> Darren Weber wrote: > Is it possible to get a txt-based listing of the dependency tree from > 'port outdated'? Not from `port outdated`, but you may want to look at port-rdeps - http://svn.macports.org/repository/macports/contrib/port-rdeps/port-rdeps From face at CentosPrime.COM Tue Oct 13 13:19:15 2009 From: face at CentosPrime.COM (Chris Janton) Date: Tue, 13 Oct 2009 13:19:15 -0700 Subject: php5 - apache configuration file moved, no notice during upgrade Message-ID: <522CCD57-B8D3-4DC7-A171-8B1D189739AE@centosprime.com> ---> Activating php5 @5.3.0_3+apache2+darwin_10+macosx+pear You may need to update your php.ini for any changes that have been made in this version of php. Compare /opt/local/etc/php5/php.ini with /opt/local/etc/php5/php.ini-development (if this is a development server) or /opt/local/etc/php5/php.ini-production (if this is a production server). If this is your first install, you need to activate PHP in your web server. To enable PHP in Apache, run cd /opt/local/apache2/modules /opt/local/apache2/bin/apxs -a -e -n "php5" libphp5.so send a SIGHUP to apache daemondo process and get this error in the logs. httpd: Syntax error on line 486 of /opt/local/apache2/conf/httpd.conf: Could not open configuration file /opt/local/apache2/conf/extras-conf/ mod_php.conf: No such file or directory Look at changes on MacPorts Trac Changeset 58844 "move conf file from extras-conf to extra to match the rest of apache2's extra conf files (#21217)" I need to "fix" my httpd.conf file after this update. There should be a warning somewhere, since it is unlikely that I am going to go to the Trac database and look to see what all changed in a "minor" update to PHP 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From ghe at slsware.com Tue Oct 13 14:49:26 2009 From: ghe at slsware.com (ghe) Date: Tue, 13 Oct 2009 15:49:26 -0600 Subject: SDL_* Message-ID: <4568B609-304E-4FE3-AB68-0A7F4581981C@slsware.com> Anybody get a successful install of anything depending on the SDL libraries? I tried (on Snow Leopard) for frozenbubble2, and get errors when it gets to SDL. It looks very much like the SDL_*.h files don't define the same structs that libsdl* try to access. Missing fields in SDL_PixelFormat, SDL_surface, I think, and maybe others... -- Glenn English ghe at slsware.com From phasetwo at mac.com Tue Oct 13 15:11:14 2009 From: phasetwo at mac.com (Steve Hellyer) Date: Tue, 13 Oct 2009 18:11:14 -0400 Subject: Output buffer too small in latest lame 3.98.2 Message-ID: Wondering if there is a way in Macports to request particular version of a port when installing? I am running Snow Leopard 10.6.1 and have Mac Ports 1.8.1 and it is working fine. I installed ports ffmpeg +lame. Both compiled and installed without error. Turns out there is a problem with latest Lame package 3.98.2 with ffmpeg as produces buffer errors... FFmpeg version 0.5, Copyright (c) 2000-2009 Fabrice Bellard, et al. configuration: --prefix=/opt/local --disable-vhook --enable-gpl -- enable-postproc --enable-swscale --enable-avfilter --enable-avfilter- lavf --enable-libmp3lame --enable-libvorbis --enable-libtheora -- enable-libdirac --enable-libschroedinger --enable-libfaac --enable- libfaad --enable-libxvid --enable-libx264 --mandir=/opt/local/share/ man --enable-shared --enable-pthreads --cc=/usr/bin/gcc-4.2 -- arch=x86_64 libavutil 49.15. 0 / 49.15. 0 libavcodec 52.20. 0 / 52.20. 0 libavformat 52.31. 0 / 52.31. 0 libavdevice 52. 1. 0 / 52. 1. 0 libavfilter 1. 4. 0 / 1. 4. 0 libswscale 1. 7. 1 / 1. 7. 1 libpostproc 51. 2. 0 / 51. 2. 0 built on Oct 13 2009 15:53:36, gcc: 4.2.1 (Apple Inc. build 5646) Input #0, au, from '/Users/shellyer/Desktop/ voice_message_2009-10-13_9-19-34.au': Duration: N/A, bitrate: N/A Stream #0.0: Audio: pcm_mulaw, 8000 Hz, mono, s16, 64 kb/s Output #0, mp3, to '/Users/shellyer/Desktop/ voice_message_2009-10-13_9-19-34.mp3': Stream #0.0: Audio: libmp3lame, 8000 Hz, mono, s16, 64 kb/s Stream mapping: Stream #0.0 -> #0.0 Press [q] to stop encoding [libmp3lame @ 0x101812800]lame: output buffer too small (buffer index: 8064, free bytes: 1728) Audio encoding failed Some investigation suggest that going back to 3.97 version lame removes this problem. http://drupal.org/node/376012 So wondering if it possible to ask for an older version. I have uninstalled ffmpeg and lame and tried to install lame 3.97 using sudo port install lame at 3.97 but I am still getting the 3.98.2 version from MacPorts using above method. Appreciate the advice. Steve From mnick at macports.org Tue Oct 13 16:02:36 2009 From: mnick at macports.org (Maximilian Nickel) Date: Wed, 14 Oct 2009 01:02:36 +0200 Subject: Output buffer too small in latest lame 3.98.2 In-Reply-To: References: Message-ID: <7bad5d350910131602g573afa8fge1740b15472ad657@mail.gmail.com> On Wed, Oct 14, 2009 at 12:11 AM, Steve Hellyer wrote: > So wondering if it possible to ask for an older version. ?I have uninstalled > ffmpeg and lame and tried to install lame 3.97 using > > sudo port install lame at 3.97 > > but I am still getting the 3.98.2 version from MacPorts using above method. Please see http://trac.macports.org/wiki/howto/InstallingOlderPort for instructions how to install an older version of a port From bpabbott at mac.com Tue Oct 13 16:34:42 2009 From: bpabbott at mac.com (Ben Abbott) Date: Tue, 13 Oct 2009 19:34:42 -0400 Subject: selfupdate via http? In-Reply-To: References: Message-ID: I was under the impression that I could selfupdate via http by changing my sources.conf as seen below. > $ cat /opt/local/etc/macports/sources.conf > # MacPorts system wide sources configuration file > # $Id: sources.conf 42662 2008-11-28 23:18:50Z raimue at macports.org $ > > # To setup a local ports repository, insert a "file://" entry > following > # the example below that points to your local ports directory: > # Example: file:///Users/landonf/misc/MacPorts/ports > > # The default MacPorts repository should always be tagged [default] > # for proper functionality of various resources (port groups, mirror > # sites, etc). If you switch it from the rsync:// URL, be sure to > keep > # it tagged [default]. > > # To prevent a source from synchronizing when `port sync` is used, > # append [nosync] at the end as shown in this example: > # Example: file:///Users/landonf/misc/MacPorts/ports [nosync] > > # NOTE: The port command parses source URLs in order and installs the > # first occurrance when a port appears in multiple > repositories. > # So keep "file://" URLs above other URL types. > > > # To get the ports tree from the master MacPorts server in > California, USA use: > # rsync://rsync.macports.org/release/ports/ > # To get it from the mirror in Trondheim, Norway use: > # rsync://trd.no.rsync.macports.org/release/ports/ > # A current list of mirrors is available at http://trac.macports.org/wiki/Mirrors > > # rsync://rsync.macports.org/release/ports/ [default] > http://www.macports.org/files/ports.tar.gz [default] While the change to http (from rsync) allows me to update the port descriptions, updating the base fails. > DEBUG: MacPorts sources location: /opt/local/var/macports/sources/ > rsync.macports.org/release/base > ---> Updating MacPorts base sources using rsync > rsync: failed to connect to superman.com: Operation timed out (60) > rsync error: error in socket IO (code 10) at /SourceCache/rsync/ > rsync-35.2/rsync/clientserver.c(105) [receiver=2.6.9] > DEBUG: Error synchronizing MacPorts sources: shell command "/usr/bin/ > rsync -rtzv --delete-after rsync://rsync.macports.org/release/base//opt/local/var/macports/sources/rsync.macports.org/release/base > " returned error 10 > Command output: rsync: failed to connect to superman.com: Operation > timed out (60) > rsync error: error in socket IO (code 10) at /SourceCache/rsync/ > rsync-35.2/rsync/clientserver.c(105) [receiver=2.6.9] > > while executing > "macports::selfupdate [array get global_options]" > Error: /opt/local/bin/port: port selfupdate failed: Error > synchronizing MacPorts sources: shell command "/usr/bin/rsync -rtzv --delete-afterrsync://rsync.macports.org/release/base/ > /opt/local/var/macports/sources/rsync.macports.org/release/base" > returned error 10 > Command output: rsync: failed to connect to superman.com: Operation > timed out (60) > rsync error: error in socket IO (code 10) at /SourceCache/rsync/ > rsync-35.2/rsync/clientserver.c(105) [receiver=2.6.9] > As my corporate firewall has the ports for both rsync an cvs closed, is there a way for me to keep my macports up to date? TiA, Ben From perrefe at gmail.com Tue Oct 13 16:36:17 2009 From: perrefe at gmail.com (Pablo Ramirez) Date: Tue, 13 Oct 2009 20:36:17 -0300 Subject: Port builds perl5.8 even if already installed in the system Message-ID: <83416c000910131636x534b1982ve67e865fba385993@mail.gmail.com> Hi, I'm not sure if this behaviour is correct or exists a way to avoid it. I've a OSX Snow Leopard installed and it includes a perl version 5.10.0, so when tried to install wine using "sudo port install wine", the first package for build was perl 5.8.9. Why port doesn't use the system's perl ? This can be avoided with some argument for "install" ? This is normal and strict ? Many thanks and sorry for my english. Regards Pablo Ram?rez -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Tue Oct 13 16:47:45 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 13 Oct 2009 18:47:45 -0500 Subject: selfupdate via http? In-Reply-To: References: Message-ID: On Oct 13, 2009, at 18:34, Ben Abbott wrote: > I was under the impression that I could selfupdate via http by > changing my sources.conf as seen below. >> # To get the ports tree from the master MacPorts server in >> California, USA use: >> # rsync://rsync.macports.org/release/ports/ >> # To get it from the mirror in Trondheim, Norway use: >> # rsync://trd.no.rsync.macports.org/release/ports/ >> # A current list of mirrors is available at http://trac.macports.org/wiki/Mirrors >> >> # rsync://rsync.macports.org/release/ports/ [default] >> http://www.macports.org/files/ports.tar.gz [default] No, this only affects ports. Hence the word "ports" in the URL. > While the change to http (from rsync) allows me to update the port > descriptions, updating the base fails. >> rsync error: error in socket IO (code 10) at /SourceCache/rsync/ >> rsync-35.2/rsync/clientserver.c(105) [receiver=2.6.9] > > As my corporate firewall has the ports for both rsync an cvs closed, > is there a way for me to keep my macports up to date? You can download the MacPorts 1.8.1 source via http from the downloads area and compile it yourself. Or you can download the 1.8.1 disk image and install that; it will not adversely affect your installed ports or settings. From ryandesign at macports.org Tue Oct 13 16:49:28 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 13 Oct 2009 18:49:28 -0500 Subject: Port builds perl5.8 even if already installed in the system In-Reply-To: <83416c000910131636x534b1982ve67e865fba385993@mail.gmail.com> References: <83416c000910131636x534b1982ve67e865fba385993@mail.gmail.com> Message-ID: On Oct 13, 2009, at 18:36, Pablo Ramirez wrote: > I'm not sure if this behaviour is correct or exists a way to avoid it. The behavior is correct. There is no way to avoid it. > I've a OSX Snow Leopard installed and it includes a perl version > 5.10.0, so when tried to install wine using "sudo port install > wine", the first package for build was perl 5.8.9. > > Why port doesn't use the system's perl ? For the reasons explained in the FAQ: http://trac.macports.org/wiki/FAQ#syslibs > This can be avoided with some argument for "install" ? No. > This is normal and strict ? This is normal. From ryandesign at macports.org Tue Oct 13 16:53:53 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 13 Oct 2009 18:53:53 -0500 Subject: Snow Leopard ate my ports In-Reply-To: <7c737f300910131226s67e2e267wd52329efd1baf0e@mail.gmail.com> References: <7c737f300910130936m7f9a0e3s2e2e632c02f89592@mail.gmail.com> <4AD4AD0F.6060703@macports.org> <7c737f300910131003i1efb4a54n1269092c02ddc569@mail.gmail.com> <4AD4BB51.1090601@macports.org> <7c737f300910131200y28757d6bx92959dab147b07f3@mail.gmail.com> <7c737f300910131226s67e2e267wd52329efd1baf0e@mail.gmail.com> Message-ID: On Oct 13, 2009, at 14:26, Alexy Khrabrov wrote: > OK, for the Snow Leopard on top of Leopard case, I went back and did > the following: > > -- put back my old /opt/local > -- ran the new 1.8.1 installer, which dropped the new port command and > friends on top if it > > Now port installed shows stuff, and they seemed to work as before. In > fact they did work, at least those I used, under SL, it's just the > port command itself was broken by the upgrade, and now fixed by > install-over. My question is, do I really need to reinstall all > ports, or this SL on top of L is OK? It is not ok. You really do need to uninstall all ports and reinstall them, exactly as stated in the Migration page. > Last time, I migrated from > 32-bit Leopard to 64-bit one (moving to a new MBP), and then I felt I > had to do it, although 32-bit stuff still worked -- but there was a > presumable advantage of getting thing recompiled under 64-bit gcc and > stuff. But are there any caveats why one should recompile a 64-bit > Leopard-fathered ports setup after SL upgrade? Whenever you make a major OS or architecture change (PowerPC to Intel, 32-bit to 64-bit, one OS version to another) you must uninstall all ports and reinstall them. MacPorts will not detect these changes, and will assume all ports currently installed were installed with the current arch and OS version, which is obviously not correct if you go and change them. So please uninstall and reinstall all ports now. From bpabbott at mac.com Tue Oct 13 17:11:38 2009 From: bpabbott at mac.com (Ben Abbott) Date: Tue, 13 Oct 2009 20:11:38 -0400 Subject: selfupdate via http? In-Reply-To: References: Message-ID: <89AD4486-6F27-4E02-9970-91763F3F8214@mac.com> On Oct 13, 2009, at 7:47 PM, Ryan Schmidt wrote: > On Oct 13, 2009, at 18:34, Ben Abbott wrote: > >> I was under the impression that I could selfupdate via http by >> changing my sources.conf as seen below. > >>> # To get the ports tree from the master MacPorts server in >>> California, USA use: >>> # rsync://rsync.macports.org/release/ports/ >>> # To get it from the mirror in Trondheim, Norway use: >>> # rsync://trd.no.rsync.macports.org/release/ports/ >>> # A current list of mirrors is available at http://trac.macports.org/wiki/Mirrors >>> >>> # rsync://rsync.macports.org/release/ports/ [default] >>> http://www.macports.org/files/ports.tar.gz [default] > > No, this only affects ports. Hence the word "ports" in the URL. > >> While the change to http (from rsync) allows me to update the port >> descriptions, updating the base fails. > >>> rsync error: error in socket IO (code 10) at /SourceCache/rsync/ >>> rsync-35.2/rsync/clientserver.c(105) [receiver=2.6.9] >> >> As my corporate firewall has the ports for both rsync an cvs >> closed, is there a way for me to keep my macports up to date? > > You can download the MacPorts 1.8.1 source via http from the > downloads area and compile it yourself. Or you can download the > 1.8.1 disk image and install that; it will not adversely affect your > installed ports or settings. Ryan, assuming I decide to download new version, where should the sources be placed and how to I initiate the compilation ... if it is more complicated than placing the tar-ball in the appropriate location and issuing "sudo port selfupdate" or a similar simple command, just say the word and I'll go with the diskimage. Thanks Ben From LenoreHorner at sbcglobal.net Tue Oct 13 17:15:55 2009 From: LenoreHorner at sbcglobal.net (Lenore Horner) Date: Tue, 13 Oct 2009 19:15:55 -0500 Subject: Snow Leopard ate my ports In-Reply-To: References: <7c737f300910130936m7f9a0e3s2e2e632c02f89592@mail.gmail.com> <4AD4AD0F.6060703@macports.org> <7c737f300910131003i1efb4a54n1269092c02ddc569@mail.gmail.com> <4AD4BB51.1090601@macports.org> <7c737f300910131200y28757d6bx92959dab147b07f3@mail.gmail.com> <7c737f300910131226s67e2e267wd52329efd1baf0e@mail.gmail.com> Message-ID: <8F66A5C1-FD1B-4A2A-A498-D5308A6E770E@sbcglobal.net> > Whenever you make a major OS or architecture change (PowerPC to > Intel, 32-bit to 64-bit, one OS version to another) you must > uninstall all ports and reinstall them. MacPorts will not detect > these changes, and will assume all ports currently installed were > installed with the current arch and OS version, which is obviously > not correct if you go and change them. So please uninstall and > reinstall all ports now. Really naive question: The goal seems to be to have MacPorts use no OS libraries, however we seem to live in an awkward in-between state where MacPorts uses enough OS libraries to break with (at least) major OS upgrades but still requires a lot of stuff to be duplicated. Is it impossible for MacPorts to be entirely independent or is the restriction people time to fix/write stuff? If it's theoretically impossible, it seems like trying to use as few as possible puts us in a worst of both worlds of having to reinstall MacPorts and having to take the time and disk space to duplicate many OS things. (Compile time is an issue for me. So is disk space since I need to keep my disk usage under 40GB so I have enough swap space.) Lenore From ventimig at msu.edu Tue Oct 13 17:47:57 2009 From: ventimig at msu.edu (David A. Ventimiglia) Date: Tue, 13 Oct 2009 20:47:57 -0400 Subject: "No such file or directory" using Macports on Tiger Message-ID: <1255481277.9147.5.camel@dventimi-laptop> Hello, I tried installing plplot following these instructions, http://plplot.darwinports.com/ with the command: sudo port install plplot and got the error pasted in below. What does it mean, and how do I resolve it? I find I often (always?) get errors like this when using MacPorts. Perhaps my MacPorts is broken. Is there a way to fix it? Maybe reinstall it? Thanks. Best, David ---- BEGIN PASTE ----- Error: Target org.macports.configure returned: autoreconf failure: shell command " cd "/opt/local/var/macports/build/_opt_lo\ cal_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-libX11/work/libX11-1.3" && autoreconf --install -fvi " re\ turned error 1 Command output: sh: line 1: cd: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_por\ ts_x11_xorg-libX11/work/libX11-1.3: No such file or directory Error: Problem while installing xorg-libX11 Error: Unable to execute port: upgrade pango failed From kw at codebykevin.com Tue Oct 13 20:03:08 2009 From: kw at codebykevin.com (Kevin Walzer) Date: Tue, 13 Oct 2009 23:03:08 -0400 Subject: PortAuthority 3.0 released Message-ID: <4AD53F6C.3040704@codebykevin.com> Code by Kevin has released PortAuthority 3.0, a GUI for the MacPorts Unix software management system for Mac OS X. PortAuthority provides a graphical user interface for the MacPorts software management system for Mac OS X. MacPorts is a powerful command-line tool for installing and updating a variety of Unix-based applications for the Mac. Its power, though, comes at the cost of some complexity; in the past the only way to utilize MacPorts was to type in various commands into the Mac's Terminal application, which can be intimidating for those users without a Unix background. PortAuthority aims to bring the power of MacPorts to the traditional Mac user by providing a user-friendly graphical interface to MacPorts. Using a familiar combination of windows, icons, and menus, PortAuthority users can search, install, update, and remove MacPorts programs and the MacPorts infrastructure itself. Among the features and improvements in this release: * Now a 64-bit application built on the Cocoa frameworks. * Updated user interface includes more modern button styles. * Context-sensitive popup menu in table display. * Now checks for MacPorts installation on startup and notifies user if MacPorts not found. * Better experience for first-time users; fewer popup dialogs, smoother startup. * Faster, more intuitive help viewer. PortAuthority is shareware; a license costs $24.95 and a 30-day demo is available. Mac OS X 10.5 is the minimum supported OS. PortAuthority is a universal binary. For more information about PortAuthority, including download links, see http://www.codebykevin.com/portauthority.html. -- Kevin Walzer Code by Kevin http://www.codebykevin.com From jmr at macports.org Wed Oct 14 00:41:42 2009 From: jmr at macports.org (Joshua Root) Date: Wed, 14 Oct 2009 18:41:42 +1100 Subject: Snow Leopard ate my ports In-Reply-To: <7c737f300910131226s67e2e267wd52329efd1baf0e@mail.gmail.com> References: <7c737f300910130936m7f9a0e3s2e2e632c02f89592@mail.gmail.com> <4AD4AD0F.6060703@macports.org> <7c737f300910131003i1efb4a54n1269092c02ddc569@mail.gmail.com> <4AD4BB51.1090601@macports.org> <7c737f300910131200y28757d6bx92959dab147b07f3@mail.gmail.com> <7c737f300910131226s67e2e267wd52329efd1baf0e@mail.gmail.com> Message-ID: <4AD580B6.5050107@macports.org> On 2009-10-14 06:26, Alexy Khrabrov wrote: > My question is, do I really need to reinstall all > ports, or this SL on top of L is OK? Last time, I migrated from > 32-bit Leopard to 64-bit one (moving to a new MBP), and then I felt I > had to do it, although 32-bit stuff still worked -- but there was a > presumable advantage of getting thing recompiled under 64-bit gcc and > stuff. But are there any caveats why one should recompile a 64-bit > Leopard-fathered ports setup after SL upgrade? As Ryan said, the only method we endorse is that described on the Migration wiki page. You would have run into problems if you tried to keep the 32-bit ports next time you tried to install or upgrade anything, as gcc would produce 64-bit binaries which would not be able to link to the existing 32-bit ones. You could try to work around this by setting build_arch to i386, but not all ports correctly respect this. Additionally, there are platform variants which would be set incorrectly in your existing ports. In the case where your ports are already 64-bit, it is possible (but by no means guaranteed) that things will work OK after you run sudo port upgrade --enforce-variants installed in order to replace the old darwin_9 variants with darwin_10. But if anything goes wrong, all we will suggest is following the Migration instructions. - Josh From ryandesign at macports.org Wed Oct 14 02:07:40 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 14 Oct 2009 04:07:40 -0500 Subject: selfupdate via http? In-Reply-To: <89AD4486-6F27-4E02-9970-91763F3F8214@mac.com> References: <89AD4486-6F27-4E02-9970-91763F3F8214@mac.com> Message-ID: <4874A662-8100-4980-A650-BDF78A992F47@macports.org> On Oct 13, 2009, at 19:11, Ben Abbott wrote: > On Oct 13, 2009, at 7:47 PM, Ryan Schmidt wrote: > >> You can download the MacPorts 1.8.1 source via http from the >> downloads area and compile it yourself. Or you can download the >> 1.8.1 disk image and install that; it will not adversely affect >> your installed ports or settings. > > Ryan, assuming I decide to download new version, where should the > sources be placed and how to I initiate the compilation ... if it is > more complicated than placing the tar-ball in the appropriate > location and issuing "sudo port selfupdate" or a similar simple > command, just say the word and I'll go with the diskimage. Unless you have a specific need to compile from source, just use the correct disk image and install from that. I should have probably listed that option first. From ryandesign at macports.org Wed Oct 14 02:11:53 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 14 Oct 2009 04:11:53 -0500 Subject: "No such file or directory" using Macports on Tiger In-Reply-To: <1255481277.9147.5.camel@dventimi-laptop> References: <1255481277.9147.5.camel@dventimi-laptop> Message-ID: <9F6EC4A0-FF4A-4C31-8D7A-E77D633EFD61@macports.org> Hi David, On Oct 13, 2009, at 19:47, David A. Ventimiglia wrote: > I tried installing plplot following these instructions, > http://plplot.d*****p****.com/ Please do not refer to that web site for any information about MacPorts. It is not authoritative, is inaccurate, and is not owned by us. For more information about this situation please see: http://trac.macports.org/wiki/DarwinPorts Please refer to http://www.macports.org/ for all official information about MacPorts. > with the command: > > sudo port install plplot > > and got the error pasted in below. What does it mean, and how do I > resolve it? I find I often (always?) get errors like this when using > MacPorts. Perhaps my MacPorts is broken. Is there a way to fix it? > Maybe reinstall it? Thanks. > > Best, > David > > ---- BEGIN PASTE ----- > > Error: Target org.macports.configure returned: autoreconf failure: > shell command " cd "/opt/local/var/macports/build/_opt_lo\ > cal_var_macports_sources_rsync.macports.org_release_ports_x11_xorg- > libX11/work/libX11-1.3" && autoreconf --install -fvi " re\ > turned error 1 > Command output: sh: line 1: cd: /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_por\ > ts_x11_xorg-libX11/work/libX11-1.3: No such file or directory > > Error: Problem while installing xorg-libX11 > Error: Unable to execute port: upgrade pango failed I'm not sure how you got in this situation. How did you initially install MacPorts? On what machine, with what version of Mac OS X, Xcode and MacPorts? Are you still on those versions or have you upgraded (to what)? Have you run "sudo port selfupdate" to make sure you have the latest MacPorts and port definitions? If you still experience the issue, can you please clean the affected port ("sudo port clean xorg-libX11") and then try again with the debug switch ("sudo port -d install xorg-libX11") and send us all the output so we can try to figure out what's going wrong? From ryandesign at macports.org Wed Oct 14 02:33:04 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 14 Oct 2009 04:33:04 -0500 Subject: Snow Leopard ate my ports In-Reply-To: <8F66A5C1-FD1B-4A2A-A498-D5308A6E770E@sbcglobal.net> References: <7c737f300910130936m7f9a0e3s2e2e632c02f89592@mail.gmail.com> <4AD4AD0F.6060703@macports.org> <7c737f300910131003i1efb4a54n1269092c02ddc569@mail.gmail.com> <4AD4BB51.1090601@macports.org> <7c737f300910131200y28757d6bx92959dab147b07f3@mail.gmail.com> <7c737f300910131226s67e2e267wd52329efd1baf0e@mail.gmail.com> <8F66A5C1-FD1B-4A2A-A498-D5308A6E770E@sbcglobal.net> Message-ID: <8F4FC0ED-1BA0-49E3-95D7-CDBF5DB47683@macports.org> On Oct 13, 2009, at 19:15, Lenore Horner wrote: >> Whenever you make a major OS or architecture change (PowerPC to >> Intel, 32-bit to 64-bit, one OS version to another) you must >> uninstall all ports and reinstall them. MacPorts will not detect >> these changes, and will assume all ports currently installed were >> installed with the current arch and OS version, which is obviously >> not correct if you go and change them. So please uninstall and >> reinstall all ports now. > > Really naive question: The goal seems to be to have MacPorts use no > OS libraries, however we seem to live in an awkward in-between state > where MacPorts uses enough OS libraries to break with (at least) > major OS upgrades but still requires a lot of stuff to be > duplicated. Is it impossible for MacPorts to be entirely > independent or is the restriction people time to fix/write stuff? > If it's theoretically impossible, it seems like trying to use as few > as possible puts us in a worst of both worlds of having to reinstall > MacPorts and having to take the time and disk space to duplicate > many OS things. > > (Compile time is an issue for me. So is disk space since I need to > keep my disk usage under 40GB so I have enough swap space.) It is not a goal for a set of ports installed on one Mac / Mac OS X version to be usable on another Mac / Mac OS X version. It *is* a goal for MacPorts to be able to notice when you have moved from one Mac / Mac OS X version to another, and to offer to rebuild your ports for you. But that's probably far down the road. As far as I'm concerned, compile time is not a major source of concern for us in general because computers are getting faster and faster, and disk usage is not a consideration because disks are getting bigger and bigger. The FAQ explains why we like using our own libraries. It gives consistency across OS releases and lets us update things on our schedule instead of having it dictated to us by Apple. Take X11 for example. It was an exception to the rule before; we used to use Apple's X11. But in Tiger Apple's X11 was based on XFree86 and on Leopard it was based on X.org. They're different, and we encountered a lot of bugs -- first, bugs on Leopard from software that wasn't expecting X.org. Later, once Leopard had been out for awhile, bugs on Tiger from software that had been updated to work with X.org. Now that we have an X.org-based X11 in MacPorts and always use it, no more problems. Software builds the same on all OSes. Ports are allowed to declare "platform" variants to do things on different OS versions, e.g. a "platform darwin 9" section to take effect only on Darwin 9 (a.k.a. Mac OS X 10.5 Leopard). MacPorts does not know whether these differences will result in the files on the hard drive being different. Perhaps for some port, the "platform darwin 9" section enables a feature only applicable to Leopard. If you move this installation over to Snow Leopard, you're now running a program with a feature enabled on an OS that feature doesn't work on. Aside from what can be done in a portfile, the software itself might detect things about the OS and build itself differently as a result. For example, CoreText was introduced in Leopard. If software is built on Tiger, it might detect CoreText is not available and thus not use it, whereas if you were to build it on Leopard, it would use it. Or, a more modern example, Snow Leopard introduces OpenCL, and something similar could happen there. In these examples, you would merely be missing useful functionality on the newer OS, but it goes both ways: APIs that used to exist get deprecated and removed. It happens all the time that ports that used to work on one OS don't work on the next. Snow Leopard has the additional distinction of being the first Mac OS X version to build things 64-bit by default, instead of 32-bit as before. This isn't a matter of using or not using some system libraries. MacPorts adopts this default as well (because it is error prone not to do so) so anything you had installed from Leopard will be 32-bit but now that you're on Snow Leopard anything you build will be 64-bit. Try to build 64-bit software against 32-bit dependencies and you won't get very far. You must rebuild everything first. From ryandesign at macports.org Wed Oct 14 02:38:28 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 14 Oct 2009 04:38:28 -0500 Subject: SDL_* In-Reply-To: <4568B609-304E-4FE3-AB68-0A7F4581981C@slsware.com> References: <4568B609-304E-4FE3-AB68-0A7F4581981C@slsware.com> Message-ID: <0C193464-3E79-4768-B4A3-A6D424994BC1@macports.org> On Oct 13, 2009, at 16:49, ghe wrote: > Anybody get a successful install of anything depending on the SDL > libraries? > > I tried (on Snow Leopard) for frozenbubble2, and get errors when it > gets to SDL. It looks very much like the SDL_*.h files don't define > the same structs that libsdl* try to access. Missing fields in > SDL_PixelFormat, SDL_surface, I think, and maybe others... There is http://trac.macports.org/ticket/21863 so this may be a known issue. However, I was able to compile frozenbubble2 on Snow Leopard with no problem. And if that ticket does not describe the errors you see, please describe them in greater detail. During activation I did encounter a minor problem for which I filed this ticket: http://trac.macports.org/ticket/22057 From LenoreHorner at sbcglobal.net Wed Oct 14 05:03:45 2009 From: LenoreHorner at sbcglobal.net (Lenore Horner) Date: Wed, 14 Oct 2009 07:03:45 -0500 Subject: Snow Leopard ate my ports In-Reply-To: <8F4FC0ED-1BA0-49E3-95D7-CDBF5DB47683@macports.org> References: <7c737f300910130936m7f9a0e3s2e2e632c02f89592@mail.gmail.com> <4AD4AD0F.6060703@macports.org> <7c737f300910131003i1efb4a54n1269092c02ddc569@mail.gmail.com> <4AD4BB51.1090601@macports.org> <7c737f300910131200y28757d6bx92959dab147b07f3@mail.gmail.com> <7c737f300910131226s67e2e267wd52329efd1baf0e@mail.gmail.com> <8F66A5C1-FD1B-4A2A-A498-D5308A6E770E@sbcglobal.net> <8F4FC0ED-1BA0-49E3-95D7-CDBF5DB47683@macports.org> Message-ID: On Oct 14, 2009, at 04:33 , Ryan Schmidt wrote: > > On Oct 13, 2009, at 19:15, Lenore Horner wrote: > >>> Whenever you make a major OS or architecture change (PowerPC to >>> Intel, 32-bit to 64-bit, one OS version to another) you must >>> uninstall all ports and reinstall them. MacPorts will not detect >>> these changes, and will assume all ports currently installed were >>> installed with the current arch and OS version, which is obviously >>> not correct if you go and change them. So please uninstall and >>> reinstall all ports now. >> >> Really naive question: The goal seems to be to have MacPorts use >> no OS libraries, however we seem to live in an awkward in-between >> state where MacPorts uses enough OS libraries to break with (at >> least) major OS upgrades but still requires a lot of stuff to be >> duplicated. Is it impossible for MacPorts to be entirely >> independent or is the restriction people time to fix/write stuff? >> If it's theoretically impossible, it seems like trying to use as >> few as possible puts us in a worst of both worlds of having to >> reinstall MacPorts and having to take the time and disk space to >> duplicate many OS things. >> >> (Compile time is an issue for me. So is disk space since I need to >> keep my disk usage under 40GB so I have enough swap space.) > > > It is not a goal for a set of ports installed on one Mac / Mac OS X > version to be usable on another Mac / Mac OS X version. It *is* a > goal for MacPorts to be able to notice when you have moved from one > Mac / Mac OS X version to another, and to offer to rebuild your > ports for you. But that's probably far down the road. I asked if it was a goal to have MacPorts entirely independent of OS libraries. > > As far as I'm concerned, compile time is not a major source of > concern for us in general because computers are getting faster and > faster, and disk usage is not a consideration because disks are > getting bigger and bigger. That's fine for you. However I typically keep a computer for at least 5 years during which time my speed and and hard drive space don't expand. I also have vague memories of people periodically wondering whether installation of this or that had died and the response being that it's just something that will take hours to days to compile. Another example: I don't use MacPorts very heavily at the moment so my /opt/local is only 1.4GB (and I do use all the recommended cleaning stuff up). However, that's a few 10s of archives of professional files or ~photos in tradeoff or about 3% of the space available to me on my hard drive for storage (as opposed to swap space). > > The FAQ explains why we like using our own libraries. It gives > consistency across OS releases and lets us update things on our > schedule instead of having it dictated to us by Apple. Take X11 for > example. It was an exception to the rule before; we used to use > Apple's X11. But in Tiger Apple's X11 was based on XFree86 and on > Leopard it was based on X.org. They're different, and we encountered > a lot of bugs -- first, bugs on Leopard from software that wasn't > expecting X.org. Later, once Leopard had been out for awhile, bugs > on Tiger from software that had been updated to work with X.org. Now > that we have an X.org-based X11 in MacPorts and always use it, no > more problems. Software builds the same on all OSes. I've read the FAQ. > > Ports are allowed to declare "platform" variants to do things on > different OS versions, e.g. a "platform darwin 9" section to take > effect only on Darwin 9 (a.k.a. Mac OS X 10.5 Leopard). MacPorts > does not know whether these differences will result in the files on > the hard drive being different. Perhaps for some port, the "platform > darwin 9" section enables a feature only applicable to Leopard. If > you move this installation over to Snow Leopard, you're now running > a program with a feature enabled on an OS that feature doesn't work > on. > > Aside from what can be done in a portfile, the software itself might > detect things about the OS and build itself differently as a result. > For example, CoreText was introduced in Leopard. If software is > built on Tiger, it might detect CoreText is not available and thus > not use it, whereas if you were to build it on Leopard, it would use > it. Or, a more modern example, Snow Leopard introduces OpenCL, and > something similar could happen there. In these examples, you would > merely be missing useful functionality on the newer OS, but it goes > both ways: APIs that used to exist get deprecated and removed. It > happens all the time that ports that used to work on one OS don't > work on the next. What the above paragraphs tell me I think is that there is no way for MacPorts to be independent of the OS. Since most of the non-MacPorts stuff I use works across several OS's and often on multiple architectures as well, I infer that the problem is that it's not possible for all possible programs to function this way and since MacPorts is one collection of interrelated stuff, even one program that won't work so broadly ruins it for everything else. Out of sheer curiosity, how, roughly, does the decision get made what stuff from the OS to use and what not? Is it proprietary Apple stuff that gets used and anything available open-source gets done w/in MP or is that too simple a division? > > Snow Leopard has the additional distinction of being the first Mac > OS X version to build things 64-bit by default, instead of 32-bit as > before. This isn't a matter of using or not using some system > libraries. MacPorts adopts this default as well (because it is error > prone not to do so) so anything you had installed from Leopard will > be 32-bit but now that you're on Snow Leopard anything you build > will be 64-bit. Try to build 64-bit software against 32-bit > dependencies and you won't get very far. You must rebuild everything > first. Not being a computer scientist, what's the quick explanation for why a machine that can run both 32-bit and 64-bit stuff can't have 64-bit stuff talk to 32-bit stuff? Thanks, Lenore From jdmuys at kleegroup.com Wed Oct 14 05:42:15 2009 From: jdmuys at kleegroup.com (Jean-Denis Muys) Date: Wed, 14 Oct 2009 14:42:15 +0200 Subject: Snow Leopard ate my ports In-Reply-To: Message-ID: On 10/14/09 14:03 , "Lenore Horner" wrote: >> Try to build 64-bit software against 32-bit >> dependencies and you won't get very far. You must rebuild everything >> first. > Not being a computer scientist, what's the quick explanation for why a > machine that can run both 32-bit and 64-bit stuff can't have 64-bit > stuff talk to 32-bit stuff? > The desire to learn is always a good thing. However this list might not be quite the best tool for that. "talking" isn't a very well defined term, and nor is "stuff". Building a non-trivial piece of software involves a number of steps. One of the last of those is "linking" whereby you connect a number of different pieces called "object files" in a way that they can call upon each other. For that to be possible, all the object files must be "link-compatible". To be link-compatible, object files must among other things have the same architecture. 32-bit object files and 64-bits object files are not link-compatible. The above description is vastly oversimplified, but I hope it can suggest why you need to rebuild you ports when going from a configuration where ports are 32-bit to another where they are 64-bit. For more details, Google is your friend. Jean-Denis From ventimig at msu.edu Wed Oct 14 06:06:47 2009 From: ventimig at msu.edu (David A. Ventimiglia) Date: Wed, 14 Oct 2009 09:06:47 -0400 Subject: "No such file or directory" using Macports on Tiger In-Reply-To: <9F6EC4A0-FF4A-4C31-8D7A-E77D633EFD61@macports.org> References: <1255481277.9147.5.camel@dventimi-laptop> <9F6EC4A0-FF4A-4C31-8D7A-E77D633EFD61@macports.org> Message-ID: <1255525607.9147.18.camel@dventimi-laptop> Hi Ryan, Thanks. I understand about not using that other site. Nonetheless, I still get this error when I try `sudo port install plplot', and I found nothing on the Wiki referring to this. If the error I'm getting is unfamiliar to anyone, ok, that's fine, I'll figure it out. But I was hoping someone would say, "oh, the 'libX11 no such directory' problem, I know how to fix that." Best, David ----- begin paste ----- legolas:~ ventimig$ sudo port install plplot ---> Computing dependencies for xorg-libX11 ---> Configuring xorg-libX11 Error: Target org.macports.configure returned: autoreconf failure: shell command " cd "/opt/local/var/macports/build/_opt_lo\ cal_var_macports_sources_rsync.macports.org_release_ports_x11_xorg-libX11/work/libX11-1.3" && autoreconf --install -fvi " re\ turned error 1 Command output: sh: line 1: cd: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_por\ ts_x11_xorg-libX11/work/libX11-1.3: No such file or directory On Wed, 2009-10-14 at 04:11 -0500, Ryan Schmidt wrote: > Hi David, > > > On Oct 13, 2009, at 19:47, David A. Ventimiglia wrote: > > > I tried installing plplot following these instructions, > > http://plplot.d*****p****.com/ > > Please do not refer to that web site for any information about > MacPorts. It is not authoritative, is inaccurate, and is not owned by > us. For more information about this situation please see: > > http://trac.macports.org/wiki/DarwinPorts > > Please refer to http://www.macports.org/ for all official information > about MacPorts. > > > > with the command: > > > > sudo port install plplot > > > > and got the error pasted in below. What does it mean, and how do I > > resolve it? I find I often (always?) get errors like this when using > > MacPorts. Perhaps my MacPorts is broken. Is there a way to fix it? > > Maybe reinstall it? Thanks. > > > > Best, > > David > > > > ---- BEGIN PASTE ----- > > > > Error: Target org.macports.configure returned: autoreconf failure: > > shell command " cd "/opt/local/var/macports/build/_opt_lo\ > > cal_var_macports_sources_rsync.macports.org_release_ports_x11_xorg- > > libX11/work/libX11-1.3" && autoreconf --install -fvi " re\ > > turned error 1 > > Command output: sh: line 1: cd: /opt/local/var/macports/build/ > > _opt_local_var_macports_sources_rsync.macports.org_release_por\ > > ts_x11_xorg-libX11/work/libX11-1.3: No such file or directory > > > > Error: Problem while installing xorg-libX11 > > Error: Unable to execute port: upgrade pango failed > > I'm not sure how you got in this situation. How did you initially > install MacPorts? On what machine, with what version of Mac OS X, > Xcode and MacPorts? Are you still on those versions or have you > upgraded (to what)? Have you run "sudo port selfupdate" to make sure > you have the latest MacPorts and port definitions? If you still > experience the issue, can you please clean the affected port ("sudo > port clean xorg-libX11") and then try again with the debug switch > ("sudo port -d install xorg-libX11") and send us all the output so we > can try to figure out what's going wrong? > > > > -- David A. Ventimiglia Michigan State University From ryandesign at macports.org Wed Oct 14 06:16:18 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 14 Oct 2009 08:16:18 -0500 Subject: "No such file or directory" using Macports on Tiger In-Reply-To: <1255525607.9147.18.camel@dventimi-laptop> References: <1255481277.9147.5.camel@dventimi-laptop> <9F6EC4A0-FF4A-4C31-8D7A-E77D633EFD61@macports.org> <1255525607.9147.18.camel@dventimi-laptop> Message-ID: <21D87096-1748-4C4D-9C07-3E00223FFD06@macports.org> On Oct 14, 2009, at 08:06, David A. Ventimiglia wrote: > Ryan Schmidt wrote: > >> I'm not sure how you got in this situation. How did you initially >> install MacPorts? On what machine, with what version of Mac OS X, >> Xcode and MacPorts? Are you still on those versions or have you >> upgraded (to what)? Have you run "sudo port selfupdate" to make sure >> you have the latest MacPorts and port definitions? If you still >> experience the issue, can you please clean the affected port ("sudo >> port clean xorg-libX11") and then try again with the debug switch >> ("sudo port -d install xorg-libX11") and send us all the output so we >> can try to figure out what's going wrong? > still get this error when I try `sudo port install plplot', and I > found > nothing on the Wiki referring to this. If the error I'm getting is > unfamiliar to anyone, ok, that's fine, I'll figure it out. But I was > hoping someone would say, "oh, the 'libX11 no such directory' > problem, I > know how to fix that." I haven't heard it mentioned before. First step would be to clean and try again. If it fails again and you need help, please show us the debug output. From bfarman at cems.uvm.edu Wed Oct 14 07:23:44 2009 From: bfarman at cems.uvm.edu (Blake Farman) Date: Wed, 14 Oct 2009 10:23:44 -0400 Subject: Perl Installation Issues Message-ID: <31d551100910140723v4f833c9co7024e4236d767320@mail.gmail.com> Hello, I've had some trouble lately getting Perl to install properly with macports (I need macports to install it since it's a dep for several packages I wish to install). I've included the output from port around where the install hangs below. I'm not sure why, but it seems that the perl installer isn't looking anywhere for my c lib. I know I have one, and I even recently upgraded the perl install in my base system without any troubles, but port can't seem to manage to figure things out. I'm a recent mac convert (coming from Gentoo) and I'm not terribly familiar with macports, so I'm a little lost on how to fix this one myself. If anyone could give me some idea of how to fix this, I'd be eternally grateful. ---> Computing dependencies for perl5.. ---> Configuring perl5.8 ... Operating system name? [sysv] Operating system version? [9.8.0] Installation prefix to use? (~name ok) [/opt/local] ... Any additional ld flags (NOT including libraries)? [-L/opt/local/lib -L/usr/local/lib] ... Checking for GNU C Library... Shall I use /usr/bin/nm to extract C symbols from the libraries? [y] I can't seem to find your C library. I've looked in the following places: Thanks, -- Blake Farman -------------- next part -------------- An HTML attachment was scrubbed... URL: From ventimig at msu.edu Wed Oct 14 07:40:33 2009 From: ventimig at msu.edu (David A. Ventimiglia) Date: Wed, 14 Oct 2009 10:40:33 -0400 Subject: "No such file or directory" using Macports on Tiger In-Reply-To: <21D87096-1748-4C4D-9C07-3E00223FFD06@macports.org> References: <1255481277.9147.5.camel@dventimi-laptop> <9F6EC4A0-FF4A-4C31-8D7A-E77D633EFD61@macports.org> <1255525607.9147.18.camel@dventimi-laptop> <21D87096-1748-4C4D-9C07-3E00223FFD06@macports.org> Message-ID: <1255531233.30584.6.camel@dventimi-laptop> Hi Ryan, Sorry, I hadn't seen the second paragraph in your first email. To answer your questions, I originally installed MacPorts from a disk image, onto an iMac, running Mac OS 10.4 (Tiger). I am still on Tiger, though I did (apparently, successfully) do a `sudo port selfupdate' and `sudo port upgrade outdated'. Running `sudo port clean xorg-libX11' appears to have fixed it, however, because after doing that I was able to install plplot without a problem. Thanks much, for the suggestion to run port clean. Best, David On Wed, 2009-10-14 at 08:16 -0500, Ryan Schmidt wrote: > On Oct 14, 2009, at 08:06, David A. Ventimiglia wrote: > > > Ryan Schmidt wrote: > > > >> I'm not sure how you got in this situation. How did you initially > >> install MacPorts? On what machine, with what version of Mac OS X, > >> Xcode and MacPorts? Are you still on those versions or have you > >> upgraded (to what)? Have you run "sudo port selfupdate" to make sure > >> you have the latest MacPorts and port definitions? If you still > >> experience the issue, can you please clean the affected port ("sudo > >> port clean xorg-libX11") and then try again with the debug switch > >> ("sudo port -d install xorg-libX11") and send us all the output so we > >> can try to figure out what's going wrong? > > > > still get this error when I try `sudo port install plplot', and I > > found > > nothing on the Wiki referring to this. If the error I'm getting is > > unfamiliar to anyone, ok, that's fine, I'll figure it out. But I was > > hoping someone would say, "oh, the 'libX11 no such directory' > > problem, I > > know how to fix that." > > I haven't heard it mentioned before. First step would be to clean and > try again. If it fails again and you need help, please show us the > debug output. > > > > -- David A. Ventimiglia Michigan State University From ryandesign at macports.org Wed Oct 14 07:49:12 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 14 Oct 2009 09:49:12 -0500 Subject: Perl Installation Issues In-Reply-To: <31d551100910140723v4f833c9co7024e4236d767320@mail.gmail.com> References: <31d551100910140723v4f833c9co7024e4236d767320@mail.gmail.com> Message-ID: <191689B1-E1AD-4511-88DB-8FEA9DBCF7CF@macports.org> On Oct 14, 2009, at 09:23, Blake Farman wrote: > I've had some trouble lately getting Perl to install properly with > macports (I need macports to install it since it's a dep for several > packages I wish to install). I've included the output from port > around where the install hangs below. I'm not sure why, but it > seems that the perl installer isn't looking anywhere for my c lib. > I know I have one, and I even recently upgraded the perl install in > my base system without any troubles, How do you mean, upgraded the perl install in your base system? > but port can't seem to manage to figure things out. I'm a recent > mac convert (coming from Gentoo) and I'm not terribly familiar with > macports, so I'm a little lost on how to fix this one myself. If > anyone could give me some idea of how to fix this, I'd be eternally > grateful. > > ---> Computing dependencies for perl5.. > ---> Configuring perl5.8 > ... > Operating system name? [sysv] > Operating system version? [9.8.0] > Installation prefix to use? (~name ok) [/opt/local] > ... > Any additional ld flags (NOT including libraries)? > [-L/opt/local/lib -L/usr/local/lib] > ... > Checking for GNU C Library... > Shall I use /usr/bin/nm to extract C symbols from the libraries? [y] > I can't seem to find your C library. I've looked in the following > places: I see you're running Mac OS X 10.5.8. What version of Xcode is installed? The latest version for Leopard is 3.1.4. From bfarman at cems.uvm.edu Wed Oct 14 08:30:52 2009 From: bfarman at cems.uvm.edu (Blake Farman) Date: Wed, 14 Oct 2009 11:30:52 -0400 Subject: Perl Installation Issues In-Reply-To: <191689B1-E1AD-4511-88DB-8FEA9DBCF7CF@macports.org> References: <31d551100910140723v4f833c9co7024e4236d767320@mail.gmail.com> <191689B1-E1AD-4511-88DB-8FEA9DBCF7CF@macports.org> Message-ID: <31d551100910140830t3481a626mdf28c437359f494@mail.gmail.com> On Wed, Oct 14, 2009 at 10:49 AM, Ryan Schmidt wrote: > On Oct 14, 2009, at 09:23, Blake Farman wrote: > > I've had some trouble lately getting Perl to install properly with >> macports (I need macports to install it since it's a dep for several >> packages I wish to install). I've included the output from port around >> where the install hangs below. I'm not sure why, but it seems that the perl >> installer isn't looking anywhere for my c lib. I know I have one, and I >> even recently upgraded the perl install in my base system without any >> troubles, >> > > How do you mean, upgraded the perl install in your base system? I built perl from source, uninstalled the old version (in /usr) and installed the new version where the old one was. > > but port can't seem to manage to figure things out. I'm a recent mac >> convert (coming from Gentoo) and I'm not terribly familiar with macports, so >> I'm a little lost on how to fix this one myself. If anyone could give me >> some idea of how to fix this, I'd be eternally grateful. >> >> ---> Computing dependencies for perl5.. >> ---> Configuring perl5.8 >> ... >> Operating system name? [sysv] >> Operating system version? [9.8.0] >> Installation prefix to use? (~name ok) [/opt/local] >> ... >> Any additional ld flags (NOT including libraries)? >> [-L/opt/local/lib -L/usr/local/lib] >> ... >> Checking for GNU C Library... >> Shall I use /usr/bin/nm to extract C symbols from the libraries? [y] >> I can't seem to find your C library. I've looked in the following places: >> > > I see you're running Mac OS X 10.5.8. What version of Xcode is installed? > The latest version for Leopard is 3.1.4. > > I'm using 3.1.13 -- Blake Farman -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Wed Oct 14 08:47:38 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 14 Oct 2009 10:47:38 -0500 Subject: Perl Installation Issues In-Reply-To: <31d551100910140830t3481a626mdf28c437359f494@mail.gmail.com> References: <31d551100910140723v4f833c9co7024e4236d767320@mail.gmail.com> <191689B1-E1AD-4511-88DB-8FEA9DBCF7CF@macports.org> <31d551100910140830t3481a626mdf28c437359f494@mail.gmail.com> Message-ID: On Oct 14, 2009, at 10:30, Blake Farman wrote: > On Wed, Oct 14, 2009 at 10:49 AM, Ryan Schmidt wrote: > >> On Oct 14, 2009, at 09:23, Blake Farman wrote: >> >>> I've had some trouble lately getting Perl to install properly >>> with macports (I need macports to install it since it's a dep for >>> several packages I wish to install). I've included the output >>> from port around where the install hangs below. I'm not sure why, >>> but it seems that the perl installer isn't looking anywhere for my >>> c lib. I know I have one, and I even recently upgraded the perl >>> install in my base system without any troubles, >> >> How do you mean, upgraded the perl install in your base system? > > I built perl from source, uninstalled the old version (in /usr) and > installed the new version where the old one was. That's what I thought you meant. It's probably not a good idea to mess with software in /usr because that was all provided by Apple. Not only is it probably integral to the proper functioning of your operating system, Apple believes it is in control of updating those components and might wipe out your changes in a future OS update. Better install your own versions of software elsewhere. >>> but port can't seem to manage to figure things out. I'm a recent >>> mac convert (coming from Gentoo) and I'm not terribly familiar >>> with macports, so I'm a little lost on how to fix this one >>> myself. If anyone could give me some idea of how to fix this, I'd >>> be eternally grateful. >>> >>> ---> Computing dependencies for perl5.. >>> ---> Configuring perl5.8 >>> ... >>> Operating system name? [sysv] >>> Operating system version? [9.8.0] >>> Installation prefix to use? (~name ok) [/opt/local] >>> ... >>> Any additional ld flags (NOT including libraries)? >>> [-L/opt/local/lib -L/usr/local/lib] >>> ... >>> Checking for GNU C Library... >>> Shall I use /usr/bin/nm to extract C symbols from the libraries? [y] >>> I can't seem to find your C library. I've looked in the following >>> places: >> >> I see you're running Mac OS X 10.5.8. What version of Xcode is >> installed? The latest version for Leopard is 3.1.4. > > I'm using 3.1.13 I assume you mean either 3.1.1 or 3.1.3. :) Either of those is probably fine. I don't know why perl wouldn't be able to find your C library. What "following places" did it say it looked for the C library in? I see one other report of this problem, which was closed as "worksforme" after the reporter provided no additional details: http://trac.macports.org/ticket/19244 Are you able to install other ports? Try something simple like expat or zlib. From bfarman at cems.uvm.edu Wed Oct 14 09:51:39 2009 From: bfarman at cems.uvm.edu (Blake Farman) Date: Wed, 14 Oct 2009 12:51:39 -0400 Subject: Perl Installation Issues In-Reply-To: References: <31d551100910140723v4f833c9co7024e4236d767320@mail.gmail.com> <191689B1-E1AD-4511-88DB-8FEA9DBCF7CF@macports.org> <31d551100910140830t3481a626mdf28c437359f494@mail.gmail.com> Message-ID: <31d551100910140951g40a0cbbdwfdee1e44fb970be8@mail.gmail.com> On Wed, Oct 14, 2009 at 11:47 AM, Ryan Schmidt wrote: > > On Oct 14, 2009, at 10:30, Blake Farman wrote: > > On Wed, Oct 14, 2009 at 10:49 AM, Ryan Schmidt wrote: >> >> On Oct 14, 2009, at 09:23, Blake Farman wrote: >>> >>> I've had some trouble lately getting Perl to install properly with >>>> macports (I need macports to install it since it's a dep for several >>>> packages I wish to install). I've included the output from port around >>>> where the install hangs below. I'm not sure why, but it seems that the perl >>>> installer isn't looking anywhere for my c lib. I know I have one, and I >>>> even recently upgraded the perl install in my base system without any >>>> troubles, >>>> >>> >>> How do you mean, upgraded the perl install in your base system? >>> >> >> I built perl from source, uninstalled the old version (in /usr) and >> installed the new version where the old one was. >> > > That's what I thought you meant. It's probably not a good idea to mess with > software in /usr because that was all provided by Apple. Not only is it > probably integral to the proper functioning of your operating system, Apple > believes it is in control of updating those components and might wipe out > your changes in a future OS update. Better install your own versions of > software elsewhere. > > > but port can't seem to manage to figure things out. I'm a recent mac >>>> convert (coming from Gentoo) and I'm not terribly familiar with macports, so >>>> I'm a little lost on how to fix this one myself. If anyone could give me >>>> some idea of how to fix this, I'd be eternally grateful. >>>> >>>> ---> Computing dependencies for perl5.. >>>> ---> Configuring perl5.8 >>>> ... >>>> Operating system name? [sysv] >>>> Operating system version? [9.8.0] >>>> Installation prefix to use? (~name ok) [/opt/local] >>>> ... >>>> Any additional ld flags (NOT including libraries)? >>>> [-L/opt/local/lib -L/usr/local/lib] >>>> ... >>>> Checking for GNU C Library... >>>> Shall I use /usr/bin/nm to extract C symbols from the libraries? [y] >>>> I can't seem to find your C library. I've looked in the following >>>> places: >>>> >>> >>> I see you're running Mac OS X 10.5.8. What version of Xcode is installed? >>> The latest version for Leopard is 3.1.4. >>> >> >> I'm using 3.1.13 >> > > I assume you mean either 3.1.1 or 3.1.3. :) Either of those is probably > fine. > > I don't know why perl wouldn't be able to find your C library. What > "following places" did it say it looked for the C library in? > > I see one other report of this problem, which was closed as "worksforme" > after the reporter provided no additional details: > > http://trac.macports.org/ticket/19244 > > Are you able to install other ports? Try something simple like expat or > zlib. > > Er, yeah, 3.1.3. Other ports work just fine, it's only Perl that's giving me trouble. I found that bug report as well, but didn't find anything useful in there. As far as "following places" goes, it doesn't list any (which I thought was kinda odd...)--it just hangs there forever. -- Blake Farman -------------- next part -------------- An HTML attachment was scrubbed... URL: From payam.minoofar at meissner.com Wed Oct 14 11:44:52 2009 From: payam.minoofar at meissner.com (Payam Minoofar) Date: Wed, 14 Oct 2009 11:44:52 -0700 Subject: kdelibs4.3.2 Message-ID: <7E275F15-D844-4B4D-B12D-1B022E59485A@meissner.com> I was excite to see this released today, but I couldn't get it to compile. Does this error have to do with architecture mismatch again? If yes, what would be a quick remedy? As always, thanks in advance. Payam [mac0023329b341a:~] payam% sudo port install amarok +universal Portfile changed since last build; discarding previous state. ---> Computing dependencies for amarok Portfile changed since last build; discarding previous state. ---> Fetching kdelibs4 ---> Verifying checksum(s) for kdelibs4 ---> Extracting kdelibs4 ---> Applying patches to kdelibs4 ---> Configuring kdelibs4 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_kde_kdelibs4 /work/build" && cmake -DCMAKE_INSTALL_PREFIX=/opt/local - DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON - DCMAKE_BUILD_TYPE=Release -DCMAKE_BUILD_WITH_INSTALL_RPATH=ON - DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DQT_QMAKE_EXECUTABLE=/opt/ local/libexec/qt4-mac/bin/qmake -Wno-dev -DBUILD_doc=OFF - DBUILD_SHARED_LIBS=ON -DBUNDLE_INSTALL_DIR=/Applications/MacPorts/KDE4 -DPHONON_INCLUDE_DIR=/opt/local/libexec/qt4-mac/include - DPHONON_LIBRARY=/opt/local/libexec/qt4-mac/lib/phonon.framework/phonon -DQT_QMAKE_EXECUTABLE=/opt/local/libexec/qt4-mac/bin/qmake - DKDE_DISTRIBUTION_TEXT="MacPorts/Mac OS X" ../kdelibs-4.3.2 - DWITH_ENCHANT=ON -DWITH_Soprano=ON -DWITH_Avahi=OFF - DKDE_DEFAULT_HOME=Library/Preferences/KDE -DWITH_FAM=OFF - DCMAKE_OSX_ARCHITECTURES="x86_64;i386" " returned error 1 Command output: * libjpeg - A library for reading and writing JPEG image files * giflib - A library for manipulating GIF format image files * libpng - A library for manipulating PNG image format files * JasPer - JasPer JPEG2000 Library * OpenEXR - OpenEXR Package * DNSSD - For MacOS and platforms without Avahi: A system which facilitates service discovery on a local network, based on the Zeroconf standard ----------------------------------------------------------------------------- -- The following OPTIONAL packages could NOT be located on your system. -- Consider installing them to enable more features from this software. ----------------------------------------------------------------------------- * LZMA/XZ A very high compression ratio data compressor Provides the ability to read and write xz compressed data files. * LibACL Access control list (ACL) support library STRONGLY RECOMMENDED: For manipulating access control lists. * FAM File Alteration Monitor Provides file alteration notification facilities using a separate service. * HSpell Hebrew spell checker Provides spell checking for Hebrew. * Avahi For Linux and BSDs: a system which facilitates service discovery on a local network, based on the Zeroconf standard Enables KDE applications access to multicast DNS/DNS-SD service discovery. ----------------------------------------------------------------------------- -- Configuring incomplete, errors occurred! Error: The following dependencies failed to build: kdebase4-runtime kdelibs4 kdepimlibs4 akonadi boost boost-jam gpgme gnupg libgpg-error pth libical openldap db44 oxygen-icons qimageblitz liblastfm fftw-3- single fftw-3 libsamplerate libsndfile flac libogg libvorbis ruby loudmouth gnutls libgcrypt libtasn1 lzo opencdk mysql5-devel qtscriptgenerator taglib taglib-extras Error: Status 1 encountered during processing. From fbartolom at gmail.com Wed Oct 14 12:37:43 2009 From: fbartolom at gmail.com (Fabrizio Bartolomucci) Date: Wed, 14 Oct 2009 21:37:43 +0200 Subject: Path problems In-Reply-To: <15536E86-F445-47CB-BBC4-3156A2811029@macports.org> References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> <4AD354C7.3080700@gmail.com> <15536E86-F445-47CB-BBC4-3156A2811029@macports.org> Message-ID: <4AD62887.5050700@gmail.com> Ryan Schmidt ha scritto: > > On Oct 12, 2009, at 11:09, Fabrizio Bartolomucci wrote: > >> checking abstract socket namespace... no >> checking for XML_ParserCreate_MM in -lexpat... no >> configure: error: Could not find expat.h, check config.log for failed >> attempts >> >> Error: Unable to upgrade port: 1 > > > Did you upgrade from Leopard, and if so did you previously have > MacPorts installed in Leopard, and if so did you follow the migration > procedure and reinstall all ports now that you're on Snow Leopard? See: > > http://trac.macports.org/wiki/Migration > > If that's not it, then please "sudo port clean PORT" where PORT is the > name of whatever port failed, and then "sudo port -d install PORT" > where PORT is whatever port you were trying to install, then send us > the complete debug output so that we can try to figure out what went > wrong. > > Those are the messages I receive: 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_devel_dbus/work/dbus-1.2.14" && ./configure --prefix=/opt/local --disable-doxygen-docs --disable-xml-docs --without-x --enable-launchd --with-launchd-agent-dir=/opt/local/Library/LaunchAgents --with-dbus-user=messagebus " returned error 1 Command output: checking for fpathconf... yes checking for setrlimit... yes checking for poll... yes checking for broken poll... yes checking for dirfd... yes checking execinfo.h usability... yes checking execinfo.h presence... yes checking for execinfo.h... yes checking for backtrace... yes checking errno.h usability... yes checking errno.h presence... yes checking for errno.h... yes checking for unistd.h... (cached) yes checking for posix getpwnam_r... yes checking whether socklen_t is defined... yes checking sys/uio.h usability... yes checking sys/uio.h presence... yes checking for sys/uio.h... yes checking for writev... yes checking sys/syslimits.h usability... yes checking sys/syslimits.h presence... yes checking for sys/syslimits.h... yes checking for ISO C99 varargs macros in C... yes checking for GNUC varargs macros... yes checking for struct cmsgcred... no checking for getpeerucred... no checking for getpeereid... yes checking abstract socket namespace... no checking for XML_ParserCreate_MM in -lexpat... no configure: error: Could not find expat.h, check config.log for failed attempts Error: Unable to upgrade port: 1 From trog24 at comcast.net Thu Oct 15 00:05:51 2009 From: trog24 at comcast.net (Frank J. R. Hanstick) Date: Thu, 15 Oct 2009 00:05:51 -0700 Subject: erlong failed to build during upgrade Message-ID: <2600D0BE-B8B6-4E89-A3F0-3CBC5CE5A153@comcast.net> Hello, The following build error occurred when upgrading: ---> Computing dependencies for erlang ---> Fetching erlang ---> Attempting to fetch otp_src_R13B02.tar.gz from http://distfiles.macports.org/erlang ---> Attempting to fetch otp_doc_man_R13B02.tar.gz from http://distfiles.macports.org/erlang ---> Attempting to fetch otp_doc_html_R13B02.tar.gz from http://distfiles.macports.org/erlang ---> Verifying checksum(s) for erlang ---> Extracting erlang ---> Applying patches to erlang ---> Configuring erlang ---> Building erlang Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_lang_erlang/work/erlang-R13B02" && /usr/ bin/make all " returned error 2 Command output: esock.c: In function 'do_accept': esock.c:1625: warning: pointer targets in passing argument 3 of 'accept' differ in signedness esock.c: In function 'dump_connections': esock.c:1719: warning: pointer targets in passing argument 3 of 'getsockname' differ in signedness esock.c:1725: warning: pointer targets in passing argument 3 of 'getsockname' differ in signedness esock.c:1730: warning: pointer targets in passing argument 3 of 'getpeername' differ in signedness /usr/bin/gcc-4.0 -c -o ../priv/obj/powerpc-apple-darwin9.8.0/ debuglog.o -Wall -Wstrict-prototypes -Wmissing-prototypes - Wdeclaration-after-statement -m32 -O2 -arch ppc -I/opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_lang_erlang/work/erlang-R13B02/erts/ powerpc-apple-darwin9.8.0 -no-cpp-precomp -I/opt/local/include - DHAVE_CONFIG_H -O2 debuglog.c /usr/bin/gcc-4.0 -c -o ../priv/obj/powerpc-apple-darwin9.8.0/ esock_poll.o -Wall -Wstrict-prototypes -Wmissing-prototypes - Wdeclaration-after-statement -m32 -O2 -arch ppc -I/opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_lang_erlang/work/erlang-R13B02/erts/ powerpc-apple-darwin9.8.0 -no-cpp-precomp -I/opt/local/include - DHAVE_CONFIG_H -O2 esock_poll.c /usr/bin/gcc-4.0 -c -o ../priv/obj/powerpc-apple-darwin9.8.0/ esock_osio.o -Wall -Wstrict-prototypes -Wmissing-prototypes - Wdeclaration-after-statement -m32 -O2 -arch ppc -I/opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_lang_erlang/work/erlang-R13B02/erts/ powerpc-apple-darwin9.8.0 -no-cpp-precomp -I/opt/local/include - DHAVE_CONFIG_H -O2 esock_osio.c /usr/bin/gcc-4.0 -c -o ../priv/obj/powerpc-apple-darwin9.8.0/ esock_utils.o -Wall -Wstrict-prototypes -Wmissing-prototypes - Wdeclaration-after-statement -m32 -O2 -arch ppc -I/opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_lang_erlang/work/erlang-R13B02/erts/ powerpc-apple-darwin9.8.0 -no-cpp-precomp -I/opt/local/include - DHAVE_CONFIG_H -O2 esock_utils.c esock_utils.c: In function 'esock_malloc': esock_utils.c:38: warning: format '%d' expects type 'int', but argument 3 has type 'size_t' esock_utils.c: In function 'esock_realloc': esock_utils.c:50: warning: format '%d' expects type 'int', but argument 3 has type 'size_t' /usr/bin/gcc-4.0 -c -o ../priv/obj/powerpc-apple-darwin9.8.0/ esock_posix_str.o -Wall -Wstrict-prototypes -Wmissing-prototypes - Wdeclaration-after-statement -m32 -O2 -arch ppc -I/opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_lang_erlang/work/erlang-R13B02/erts/ powerpc-apple-darwin9.8.0 -no-cpp-precomp -I/opt/local/include - DHAVE_CONFIG_H -O2 esock_posix_str.c /usr/bin/gcc-4.0 -c -o ../priv/obj/powerpc-apple-darwin9.8.0/ esock_openssl.o -Wall -Wstrict-prototypes -Wmissing-prototypes - Wdeclaration-after-statement -m32 -O2 -arch ppc -I/opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_lang_erlang/work/erlang-R13B02/erts/ powerpc-apple-darwin9.8.0 -no-cpp-precomp -I/opt/local/include - DHAVE_CONFIG_H -O2 -I/usr/include esock_openssl.c esock_openssl.c: In function 'set_ssl_parameters': esock_openssl.c:905: warning: pointer targets in initialization differ in signedness esock_openssl.c:906: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness /usr/bin/gcc-4.0 -m32 -O2 -arch ppc -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_lang_erlang/work/erlang-R13B02/erts/ powerpc-apple-darwin9.8.0 -no-cpp-precomp -I/opt/local/include - o ../priv/bin/powerpc-apple-darwin9.8.0/ssl_esock ../priv/obj/powerpc- apple-darwin9.8.0/esock.o ../priv/obj/powerpc-apple-darwin9.8.0/ debuglog.o ../priv/obj/powerpc-apple-darwin9.8.0/esock_poll.o ../priv/ obj/powerpc-apple-darwin9.8.0/esock_osio.o ../priv/obj/powerpc-apple- darwin9.8.0/esock_utils.o ../priv/obj/powerpc-apple-darwin9.8.0/ esock_posix_str.o ../priv/obj/powerpc-apple-darwin9.8.0/ esock_openssl.o -lutil -ldl -lm -L/usr/lib -lssl -lcrypto Undefined symbols: "_SSL_CTX_set_info_callback", referenced from: _set_ssl_parameters in esock_openssl.o ld: symbol(s) not found collect2: ld returned 1 exit status make[4]: *** [../priv/bin/powerpc-apple-darwin9.8.0/ssl_esock] Error 1 make[3]: *** [opt] Error 2 make[2]: *** [opt] Error 2 make[1]: *** [opt] Error 2 make: *** [libs] Error 2 Error: Unable to upgrade port: 1 Frank J. R. Hanstick trog24 at comcast.net From domiman at gmail.com Thu Oct 15 01:48:49 2009 From: domiman at gmail.com (Dominik Reichardt) Date: Thu, 15 Oct 2009 10:48:49 +0200 Subject: kdelibs4.3.2 In-Reply-To: <7E275F15-D844-4B4D-B12D-1B022E59485A@meissner.com> References: <7E275F15-D844-4B4D-B12D-1B022E59485A@meissner.com> Message-ID: > I was excite to see this released today, but I couldn't get it to > compile. Does this error have to do with architecture mismatch again? > If yes, what would be a quick remedy? > > As always, thanks in advance. > > Payam > > [mac0023329b341a:~] payam% sudo port install amarok +universal I presume you are on Snow Leopard, if so, then the above is the first culprit. kdelibs4 will not build on SL with the variant +universal set (and since you are building amarok with universal, kdelibs inherit this setting). I opened a ticket for this last week: http://trac.macports.org/ticket/21946 And now that I thought about it I wonder if it even makes sense to have the KDE stuff built with +universal. Other ports which are a dependency of ports make sense to be built with +universal, but I *think* KDEstufff is so self contained that building it in 64bit only will harm. Anyway, at the moment, kdelibs4 is still useless on SL even if built without +universal. See http://trac.macports.org/ticket/21973 I haven't tried the latest patch that sharky attached. The one in the port files is still crashing kdeinit all the time... So don't bother to build that stuff until this issue is out of the way.... -- Take care Dominik From bobbyw at logicblox.com Thu Oct 15 07:20:18 2009 From: bobbyw at logicblox.com (Bobby Williams) Date: Thu, 15 Oct 2009 10:20:18 -0400 Subject: Error installing gcc41 on 10.6 Message-ID: Has anyone else encountered this? Thanks! // // // [head ~/projects/head/LogicBlox]$ sudo port install gcc41 ---> Computing dependencies for gcc41 ---> Fetching gcc41 ---> Verifying checksum(s) for gcc41 ---> Extracting gcc41 ---> Applying patches to gcc41 ---> Configuring gcc41 ---> Building gcc41 Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc41/work/build" && /usr/bin/make -j2 profiledbootstrap " returned error 2 Command output: checking assembler for section merging support... no checking assembler for section merging support... (cached) no checking assembler for COMDAT group support... no checking assembler for COMDAT group support... no checking assembler for thread-local storage support... no checking linker -Bstatic/-Bdynamic option... no checking assembler for filds and fists mnemonics... no checking assembler for cmov syntax... no checking assembler for GOTOFF in data... no checking assembler for dwarf2 debug_line support... no checking assembler for buggy dwarf2 .file directive... no checking assembler for --gdwarf2 option... no checking assembler for --gstabs option... no checking linker read-only and read-write section mixing... unknown checking linker PT_GNU_EH_FRAME support... no checking linker position independent executable support... no checking linker --as-needed support... no checking linker --sysroot support... no Using ggc-page for garbage collection. checking whether to enable maintainer-specific portions of Makefiles... no Links are now set up to build (on x86_64-apple-darwin10) a native compiler for i386-apple-darwin10.2.0. updating cache ./config.cache configure: creating ./config.status config.status: creating Makefile config.status: creating gccbug config.status: creating mklibgcc config.status: creating libada-mk config.status: creating auto-host.h config.status: executing default commands Error: Status 1 encountered during processing. From bobbyw at logicblox.com Thu Oct 15 07:39:29 2009 From: bobbyw at logicblox.com (Bobby Williams) Date: Thu, 15 Oct 2009 10:39:29 -0400 Subject: Error installing gcc41 on 10.6? Message-ID: <7E1CB000-EE4B-4790-8BE6-B43CB8F95752@logicblox.com> (Tried to send a more complete message but was rejected --- twice.) Has anyone else encountered problems attempting to install gcc41 on Snow Leopard? In part I'm getting the following message from port: Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc41/work/build" && /usr/bin/make -j2 profiledbootstrap " returned error 2 Thanks! From bobbyw at logicblox.com Thu Oct 15 07:47:02 2009 From: bobbyw at logicblox.com (Bobby Williams) Date: Thu, 15 Oct 2009 10:47:02 -0400 Subject: Snow Leopard and gcc41 Message-ID: Tried to send a more complete message but was rejected --- thrise.) Has anyone else encountered problems attempting to install gcc41 on Snow Leopard? I've tried to include the actual error messages from port but the list server keeps rejected my messages. Thanks! From wbossons at MIT.EDU Thu Oct 15 08:08:27 2009 From: wbossons at MIT.EDU (Wendy Bossons) Date: Thu, 15 Oct 2009 11:08:27 -0400 Subject: Why should I use macports? Message-ID: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> I recently transitioned to a new software project, and I am using Mac now as a development platform instead of Windows. I keep seeing Macports come up as a way to install software, but I don't understand what it is and why I might need it. Can someone explain the purpose of Macports and why I might need it? ..\Wendy Wendy Bossons Web Developer Contact Information: wbossons at mit.edu 617-253-0770 From mark at blackmans.org Thu Oct 15 08:19:57 2009 From: mark at blackmans.org (Mark Blackman) Date: Thu, 15 Oct 2009 16:19:57 +0100 Subject: Why should I use macports? In-Reply-To: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> References: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> Message-ID: <4AD73D9D.9060605@blackmans.org> On 15/10/2009 16:08, Wendy Bossons wrote: > I recently transitioned to a new software project, and I am using Mac > now as a development platform instead of Windows. I keep seeing Macports > come up as a way to install software, but I don't understand what it is > and why I might need it. > > Can someone explain the purpose of Macports and why I might need it? It's a source-based framework for installing 3rd party software. You install macports, then it manages all the steps required to build and install lots of other software including some level of dependency management. - Mark From d.l.tDeContes at free.fr Thu Oct 15 08:21:33 2009 From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=) Date: Thu, 15 Oct 2009 17:21:33 +0200 Subject: readline In-Reply-To: <06BA46CE-8BF3-49DB-A717-75D870FF632F@macports.org> References: <06BA46CE-8BF3-49DB-A717-75D870FF632F@macports.org> Message-ID: Le 11 oct. 09 ? 22:23, Ryan Schmidt a ?crit : > > On Oct 11, 2009, at 09:43, Thomas De Contes wrote: > >> no, it made an error, and i just run it again > > Ah, ok. Still, the error you reported was caused by running it a > second time without cleaning. true (but it's unusual) > > >> port clean readline >> and then : >> >> + port selfupdate >> ... >> + port -u upgrade outdated >> MacPorts running without privileges. You may be unable to complete >> certain actions (eg install). >> ---> Computing dependencies for readline >> MacPorts running without privileges. You may be unable to complete >> certain actions (eg install). >> ---> Fetching readline >> MacPorts running without privileges. You may be unable to complete >> certain actions (eg install). >> ---> Verifying checksum(s) for readline >> MacPorts running without privileges. You may be unable to complete >> certain actions (eg install). >> ---> Extracting readline >> MacPorts running without privileges. You may be unable to complete >> certain actions (eg install). >> ---> Applying patches to readline >> Error: Target org.macports.patch returned: could not set group for >> file "/Users/thomas/Documents/prgm/bin/autoinstall/macports/var/ >> macports/build/ >> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_so >> urces_rsync.macports.org_release_ports_devel_readline/work/ >> readline-6.0/support/shobj-conf": not owner >> Error: Unable to upgrade port: 1 > > Ok, that's the first and real error, and is: > > http://trac.macports.org/ticket/20896 > > As shown in the ticket, I identified the change that caused that > problem. Joshua, what do you think we should do about this? We > could apply the patch I supplied, which would revert one of your > prior changes. Or we could try to figure out a way to allow your > change while still avoiding this issue. any news ? is it possible to upgrade readline nevertheless ? -- T?l?assistance / T?l?maintenance http://www.portparallele.com/ThomasDECONTES/ From mikel.king at olivent.com Thu Oct 15 08:28:38 2009 From: mikel.king at olivent.com (Mikel King) Date: Thu, 15 Oct 2009 11:28:38 -0400 Subject: Why should I use macports? In-Reply-To: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> References: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> Message-ID: On Oct 15, 2009, at 11:08 AM, Wendy Bossons wrote: > I recently transitioned to a new software project, and I am using > Mac now as a development platform instead of Windows. I keep seeing > Macports come up as a way to install software, but I don't > understand what it is and why I might need it. > > Can someone explain the purpose of Macports and why I might need it? > Because there are thousands of readily available applications only a 'port install' away. Say you want to install lighttpd + PHP + MySql to host websites you are developing directly from your laptop so that you can demo them for clients without the worry of suspect internet connectivity. The port system will retrieve the source for each port plus it's dependencies and build it for you. Obviously there are other ways to do this, but most are not as clean nor anywhere as flexible. > ..\Wendy > Wendy Bossons > Web Developer > > Contact Information: > wbossons at mit.edu > 617-253-0770 Regards, Mikel King CEO, Olivent Technologies Senior Editor, BSD News Network Columnist, BSD Magazine 6 Alpine Court, Medford, NY 11763 o: 631.627.3055 skype:mikel.king http://olivent.com http://bsdnews.net http://mikelking.com http://twitter.com/mikelking -------------- next part -------------- An HTML attachment was scrubbed... URL: From vince at macports.org Thu Oct 15 08:38:17 2009 From: vince at macports.org (vincent habchi) Date: Thu, 15 Oct 2009 17:38:17 +0200 Subject: Why should I use macports? In-Reply-To: References: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> Message-ID: Le 15 oct. 2009 ? 17:28, Mikel King a ?crit : > Because there are thousands of readily available applications only a > 'port install' away. Say you want to install lighttpd + PHP + MySql > to host I could add that the advantage of compiling instead of just downloading and adding binaries is that you can tweak your compilation to suit exactly the kind of processor you have (or other needs), resulting in a much more optimized code (in order to run in all platforms, binary code is inherently compiled for old CPU models). The drawback, of course, is increased installation time. Vincent From ben at cogs.com Thu Oct 15 08:38:30 2009 From: ben at cogs.com (Ben Greenfield) Date: Thu, 15 Oct 2009 11:38:30 -0400 Subject: Why should I use macports? In-Reply-To: <4AD73D9D.9060605@blackmans.org> References: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> <4AD73D9D.9060605@blackmans.org> Message-ID: <9BF5BF3D-35BC-4634-B0EE-58B90431F9F8@cogs.com> There is a lot of unix software out-there that is distributed in source form. If everyone who wanted to use the software had to have knowledge of all the intricacies involved in getting basic software,compiled, installed, and running we would lose a lot of efficiencies as users. Each operating system community has a volunteer based community for trying to insulate the users from all the complexity while still providing access to as much software as possible. Macports is one of OS X projects, Fink is another. If one wants to install apache they can get the source download compile with the options they want and install it and go, or one can install apache using macports (after they installed macports). The advantage to macports is that people who care about apache working on os x are maintaing the platform specific needs using the macports system. There for it should be easy to install software using macports as opposed to going it alone. The burden of install macports is dwarfed by the efficiency of not having to maintain the software you are trying to install. Good Luck, Ben On Oct 15, 2009, at 11:19 AM, Mark Blackman wrote: > On 15/10/2009 16:08, Wendy Bossons wrote: >> I recently transitioned to a new software project, and I am using Mac >> now as a development platform instead of Windows. I keep seeing >> Macports >> come up as a way to install software, but I don't understand what >> it is >> and why I might need it. >> >> Can someone explain the purpose of Macports and why I might need it? > > It's a source-based framework for installing 3rd party software. > > You install macports, then it manages all the steps required to > build and install lots of other software including some level of > dependency management. > > - Mark > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From ryandesign at macports.org Thu Oct 15 09:32:43 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 15 Oct 2009 11:32:43 -0500 Subject: Why should I use macports? In-Reply-To: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> References: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> Message-ID: On Oct 15, 2009, at 10:08, Wendy Bossons wrote: > I recently transitioned to a new software project, and I am using > Mac now as a development platform instead of Windows. I keep seeing > Macports come up as a way to install software, but I don't > understand what it is and why I might need it. > > Can someone explain the purpose of Macports and why I might need it? As others have said, MacPorts is a package management system, which is an easy way to install software without having to know the technical details and without having to know what other software is required; MacPorts manages it for you. What others have not said is how easy it is to also remove such software later -- simply "sudo port uninstall" it. When you install software by hand, often it's not clear where things have been installed, or how to uninstall it later. From ryandesign at macports.org Thu Oct 15 09:37:57 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 15 Oct 2009 11:37:57 -0500 Subject: readline In-Reply-To: References: <06BA46CE-8BF3-49DB-A717-75D870FF632F@macports.org> Message-ID: >>> ---> Applying patches to readline >>> Error: Target org.macports.patch returned: could not set group for >>> file "/Users/thomas/Documents/prgm/bin/autoinstall/macports/var/ >>> macports/build/ >>> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sources_rsync.macports.org_release_ports_devel_readline >>> /work/readline-6.0/support/shobj-conf": not owner >>> Error: Unable to upgrade port: 1 >> >> Ok, that's the first and real error, and is: >> >> http://trac.macports.org/ticket/20896 >> >> As shown in the ticket, I identified the change that caused that >> problem. Joshua, what do you think we should do about this? We >> could apply the patch I supplied, which would revert one of your >> prior changes. Or we could try to figure out a way to allow your >> change while still avoiding this issue. > > > any news ? > > is it possible to upgrade readline nevertheless ? You could apply the patch I attached to that ticket, and rebuild MacPorts. I would like to resolve this issue for MacPorts 1.8.2, and am awaiting feedback on whether or not this patch should be applied or if there is another solution. Or you could reinstall MacPorts so it's installed as root. From ryandesign at macports.org Thu Oct 15 09:39:07 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 15 Oct 2009 11:39:07 -0500 Subject: Error installing gcc41 on 10.6 In-Reply-To: References: Message-ID: <3AFB9D55-2868-4EF6-A51A-4F4A3769C507@macports.org> On Oct 15, 2009, at 09:20, Bobby Williams wrote: > Has anyone else encountered this? Thanks! Everybody who has tried this on Snow Leopard will have encountered this, yes. gcc43 is the earliest that builds on Snow Leopard at this time. There are tickets about these problems in the issue tracker, but they may not get fixed. These are very old versions of gcc. Is there a specific reason you want gcc41 and can't use e.g. gcc44? From ryandesign at macports.org Thu Oct 15 09:47:42 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 15 Oct 2009 11:47:42 -0500 Subject: Path problems In-Reply-To: <4AD62887.5050700@gmail.com> References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> <4AD354C7.3080700@gmail.com> <15536E86-F445-47CB-BBC4-3156A2811029@macports.org> <4AD62887.5050700@gmail.com> Message-ID: On Oct 14, 2009, at 14:37, Fabrizio Bartolomucci wrote: > 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_devel_dbus > /work/dbus-1.2.14" && ./configure --prefix=/opt/local --disable- > doxygen-docs --disable-xml-docs --without-x --enable-launchd --with- > launchd-agent-dir=/opt/local/Library/LaunchAgents --with-dbus- > user=messagebus " returned > error 1 Ok, so dbus is the port that's failing. I see you're using dbus 1.2.14. dbus was just updated to 1.2.16 so please "sudo port selfupdate" and try again and see if 1.2.16 works better. > Command output: checking for fpathconf... yes > checking for setrlimit... yes > checking for poll... yes > checking for broken poll... yes > checking for dirfd... yes > checking execinfo.h usability... yes > checking execinfo.h presence... yes > checking for execinfo.h... yes > checking for backtrace... yes > checking errno.h usability... yes > checking errno.h presence... yes > checking for errno.h... yes > checking for unistd.h... (cached) yes > checking for posix getpwnam_r... yes > checking whether socklen_t is defined... yes > checking sys/uio.h usability... yes > checking sys/uio.h presence... yes > checking for sys/uio.h... yes > checking for writev... yes > checking sys/syslimits.h usability... yes > checking sys/syslimits.h presence... yes > checking for sys/syslimits.h... yes > checking for ISO C99 varargs macros in C... yes > checking for GNUC varargs macros... yes > checking for struct cmsgcred... no > checking for getpeerucred... no > checking for getpeereid... yes > checking abstract socket namespace... no > checking for XML_ParserCreate_MM in -lexpat... no > configure: error: Could not find expat.h, check config.log for > failed attempts If 1.2.16 has this problem too, then please send us the aforementioned config.log. From ben at cogs.com Thu Oct 15 10:41:30 2009 From: ben at cogs.com (Ben Greenfield) Date: Thu, 15 Oct 2009 13:41:30 -0400 Subject: Why should I use macports? In-Reply-To: References: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> Message-ID: On Oct 15, 2009, at 12:32 PM, Ryan Schmidt wrote: > > On Oct 15, 2009, at 10:08, Wendy Bossons wrote: > >> I recently transitioned to a new software project, and I am using >> Mac now as a development platform instead of Windows. I keep seeing >> Macports come up as a way to install software, but I don't >> understand what it is and why I might need it. >> >> Can someone explain the purpose of Macports and why I might need it? > > > As others have said, MacPorts is a package management system, which > is an easy way to install software without having to know the > technical details and without having to know what other software is > required; MacPorts manages it for you. What others have not said is > how easy it is to also remove such software later -- simply "sudo > port uninstall" it. When you install software by hand, often it's > not clear where things have been installed, or how to uninstall it > later. > See us macports users never noticed the complexity of the uninstall. > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From trog24 at comcast.net Thu Oct 15 11:34:59 2009 From: trog24 at comcast.net (Frank J. R. Hanstick) Date: Thu, 15 Oct 2009 11:34:59 -0700 Subject: erlong failed to build during upgrade In-Reply-To: <21C9380A-D837-4E5D-8F9B-B94AD4F60341@macports.org> References: <2600D0BE-B8B6-4E89-A3F0-3CBC5CE5A153@comcast.net> <21C9380A-D837-4E5D-8F9B-B94AD4F60341@macports.org> Message-ID: Hello, Ticket #22092. On Oct 15, 2009, at 12:46 AM, Ryan Schmidt wrote: > You may want to file a ticket in the issue tracker for this problem > so it can be properly tracked. > > On Oct 15, 2009, at 02:05, Frank J. R. Hanstick wrote: > >> Hello, >> The following build error occurred when upgrading: >> >> ---> Computing dependencies for erlang >> ---> Fetching erlang >> ---> Attempting to fetch otp_src_R13B02.tar.gz from http://distfiles.macports.org/erlang >> ---> Attempting to fetch otp_doc_man_R13B02.tar.gz from http://distfiles.macports.org/erlang >> ---> Attempting to fetch otp_doc_html_R13B02.tar.gz from http://distfiles.macports.org/erlang >> ---> Verifying checksum(s) for erlang >> ---> Extracting erlang >> ---> Applying patches to erlang >> ---> Configuring erlang >> ---> Building erlang >> Error: Target org.macports.build returned: shell command " cd "/opt/ >> local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_lang_erlang/work/erlang-R13B02" && /usr/ >> bin/make all " returned error 2 >> Command output: esock.c: In function 'do_accept': >> esock.c:1625: warning: pointer targets in passing argument 3 of >> 'accept' differ in signedness >> esock.c: In function 'dump_connections': >> esock.c:1719: warning: pointer targets in passing argument 3 of >> 'getsockname' differ in signedness >> esock.c:1725: warning: pointer targets in passing argument 3 of >> 'getsockname' differ in signedness >> esock.c:1730: warning: pointer targets in passing argument 3 of >> 'getpeername' differ in signedness >> /usr/bin/gcc-4.0 -c -o ../priv/obj/powerpc-apple-darwin9.8.0/ >> debuglog.o -Wall -Wstrict-prototypes -Wmissing-prototypes - >> Wdeclaration-after-statement -m32 -O2 -arch ppc -I/opt/local/var/ >> macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_lang_erlang/work/erlang-R13B02/erts/ >> powerpc-apple-darwin9.8.0 -no-cpp-precomp -I/opt/local/include - >> DHAVE_CONFIG_H -O2 debuglog.c >> /usr/bin/gcc-4.0 -c -o ../priv/obj/powerpc-apple-darwin9.8.0/ >> esock_poll.o -Wall -Wstrict-prototypes -Wmissing-prototypes - >> Wdeclaration-after-statement -m32 -O2 -arch ppc -I/opt/local/var/ >> macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_lang_erlang/work/erlang-R13B02/erts/ >> powerpc-apple-darwin9.8.0 -no-cpp-precomp -I/opt/local/include - >> DHAVE_CONFIG_H -O2 esock_poll.c >> /usr/bin/gcc-4.0 -c -o ../priv/obj/powerpc-apple-darwin9.8.0/ >> esock_osio.o -Wall -Wstrict-prototypes -Wmissing-prototypes - >> Wdeclaration-after-statement -m32 -O2 -arch ppc -I/opt/local/var/ >> macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_lang_erlang/work/erlang-R13B02/erts/ >> powerpc-apple-darwin9.8.0 -no-cpp-precomp -I/opt/local/include - >> DHAVE_CONFIG_H -O2 esock_osio.c >> /usr/bin/gcc-4.0 -c -o ../priv/obj/powerpc-apple-darwin9.8.0/ >> esock_utils.o -Wall -Wstrict-prototypes -Wmissing-prototypes - >> Wdeclaration-after-statement -m32 -O2 -arch ppc -I/opt/local/var/ >> macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_lang_erlang/work/erlang-R13B02/erts/ >> powerpc-apple-darwin9.8.0 -no-cpp-precomp -I/opt/local/include - >> DHAVE_CONFIG_H -O2 esock_utils.c >> esock_utils.c: In function 'esock_malloc': >> esock_utils.c:38: warning: format '%d' expects type 'int', but >> argument 3 has type 'size_t' >> esock_utils.c: In function 'esock_realloc': >> esock_utils.c:50: warning: format '%d' expects type 'int', but >> argument 3 has type 'size_t' >> /usr/bin/gcc-4.0 -c -o ../priv/obj/powerpc-apple-darwin9.8.0/ >> esock_posix_str.o -Wall -Wstrict-prototypes -Wmissing-prototypes - >> Wdeclaration-after-statement -m32 -O2 -arch ppc -I/opt/local/var/ >> macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_lang_erlang/work/erlang-R13B02/erts/ >> powerpc-apple-darwin9.8.0 -no-cpp-precomp -I/opt/local/include - >> DHAVE_CONFIG_H -O2 esock_posix_str.c >> /usr/bin/gcc-4.0 -c -o ../priv/obj/powerpc-apple-darwin9.8.0/ >> esock_openssl.o -Wall -Wstrict-prototypes -Wmissing-prototypes - >> Wdeclaration-after-statement -m32 -O2 -arch ppc -I/opt/local/var/ >> macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_lang_erlang/work/erlang-R13B02/erts/ >> powerpc-apple-darwin9.8.0 -no-cpp-precomp -I/opt/local/include - >> DHAVE_CONFIG_H -O2 -I/usr/include esock_openssl.c >> esock_openssl.c: In function 'set_ssl_parameters': >> esock_openssl.c:905: warning: pointer targets in initialization >> differ in signedness >> esock_openssl.c:906: warning: pointer targets in passing argument 1 >> of 'strlen' differ in signedness >> /usr/bin/gcc-4.0 -m32 -O2 -arch ppc -I/opt/local/var/macports/ >> build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_lang_erlang/work/erlang-R13B02/erts/ >> powerpc-apple-darwin9.8.0 -no-cpp-precomp -I/opt/local/include - >> o ../priv/bin/powerpc-apple-darwin9.8.0/ssl_esock ../priv/obj/ >> powerpc-apple-darwin9.8.0/esock.o ../priv/obj/powerpc-apple- >> darwin9.8.0/debuglog.o ../priv/obj/powerpc-apple-darwin9.8.0/ >> esock_poll.o ../priv/obj/powerpc-apple-darwin9.8.0/esock_osio.o ../ >> priv/obj/powerpc-apple-darwin9.8.0/esock_utils.o ../priv/obj/ >> powerpc-apple-darwin9.8.0/esock_posix_str.o ../priv/obj/powerpc- >> apple-darwin9.8.0/esock_openssl.o -lutil -ldl -lm -L/usr/lib - >> lssl -lcrypto >> Undefined symbols: >> "_SSL_CTX_set_info_callback", referenced from: >> _set_ssl_parameters in esock_openssl.o >> ld: symbol(s) not found >> collect2: ld returned 1 exit status >> make[4]: *** [../priv/bin/powerpc-apple-darwin9.8.0/ssl_esock] >> Error 1 >> make[3]: *** [opt] Error 2 >> make[2]: *** [opt] Error 2 >> make[1]: *** [opt] Error 2 >> make: *** [libs] Error 2 >> >> Error: Unable to upgrade port: 1 >> _______________________________________________ >> macports-users mailing list >> macports-users at lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > Frank J. R. Hanstick trog24 at comcast.net From cfcaballero at gmail.com Thu Oct 15 18:02:52 2009 From: cfcaballero at gmail.com (Claudio Caballero) Date: Thu, 15 Oct 2009 21:02:52 -0400 Subject: Can I install an older version of MacPorts to easily compile i386 only on Snow Leopard? Message-ID: <004101ca4dfc$657b30b0$30719210$@com> Sorry if this is a dumb question, but after upgrading my Mac Mini with a fresh install of Snow Leopard, I can't figure out how to compile wine and some other ports. I've tried everything I could find by searching the web and lists to completely build MacPorts as 32-bit only, but keep running into the gettext/libintl issue. Rather than keep beating my head against that particular wall, I was wondering if there is an older version of MacPorts that doesn't know enough to try and build for x86_64 and will just build for i386 by default? TIA, Claudio -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Thu Oct 15 20:42:50 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 15 Oct 2009 22:42:50 -0500 Subject: Can I install an older version of MacPorts to easily compile i386 only on Snow Leopard? In-Reply-To: <004101ca4dfc$657b30b0$30719210$@com> References: <004101ca4dfc$657b30b0$30719210$@com> Message-ID: <85513EFE-4036-4164-833C-10336A7D788B@macports.org> On Oct 15, 2009, at 20:02, Claudio Caballero wrote: > Sorry if this is a dumb question, but after upgrading my Mac Mini > with a fresh install of Snow Leopard, I can?t figure out how to > compile wine and some other ports. > > I?ve tried everything I could find by searching the web and lists to > completely build MacPorts as 32-bit only, but keep running into the > gettext/libintl issue. What issue is that? > Rather than keep beating my head against that particular wall, I was > wondering if there is an older version of MacPorts that doesn?t know > enough to try and build for x86_64 and will just build for i386 by > default? You cannot run an earlier version of MacPorts. Ports are no longer compatible with older versions of MacPorts. Also, 1.8.0 is the first version of MacPorts that works at all on Snow Leopard. Also, 1.8.0 is the first version that knows about passing -arch flags. Prior versions did not pass anything and assume the compiler will do the right thing. On Snow Leopard, the compiler will build 64-bit by default so if you somehow managed to get MacPorts 1.7 to work on it, it would build 64- bit software for you, with no way to change it. To build 32-bit only in MacPorts 1.8, set build_arch to i386 in macports.conf. If you encounter problems, please report them. A better way to get wine on Snow Leopard is to build all of wine's dependencies with the +universal variant (which will build i386 and x86_64), then install wine (or, currently on Snow Leopard, you'll have to use wine-devel) (which will build i386 regardless of your build_arch because the wine software is not 64-bit ready at this time). It may be tricky to identify which dependencies you need to rebuild. Once you identify them, you would run sudo port upgrade --enforce-dependencies PORTNAME +universal for each identified port. I'm not sure what command would do this all for you automatically. If someone knows it, please let me know. From cfcaballero at gmail.com Thu Oct 15 21:03:14 2009 From: cfcaballero at gmail.com (Claudio Caballero) Date: Fri, 16 Oct 2009 00:03:14 -0400 Subject: Can I install an older version of MacPorts to easily compile i386 only on Snow Leopard? In-Reply-To: <85513EFE-4036-4164-833C-10336A7D788B@macports.org> References: <004101ca4dfc$657b30b0$30719210$@com> <85513EFE-4036-4164-833C-10336A7D788B@macports.org> Message-ID: <88682b530910152103t21adea78q41ecbaa493cf4691@mail.gmail.com> Thanks for your reply Ryan. On Thu, Oct 15, 2009 at 11:42 PM, Ryan Schmidt wrote: > On Oct 15, 2009, at 20:02, Claudio Caballero wrote: > > Sorry if this is a dumb question, but after upgrading my Mac Mini with a >> fresh install of Snow Leopard, I can?t figure out how to compile wine and >> some other ports. >> >> I?ve tried everything I could find by searching the web and lists to >> completely build MacPorts as 32-bit only, but keep running into the >> gettext/libintl issue. >> > > What issue is that? http://trac.macports.org/ticket/19381 & http://trac.macports.org/ticket/21215 One mentions that build_arch is not reliable, and I tried adding the universal variant and altering it to just i386. I also set compiler flag environment variables, no joy. This was all with rebuilding all ports. I guess the one option I haven't tried is building universal with both 32 and 64 bit. > > > Rather than keep beating my head against that particular wall, I was >> wondering if there is an older version of MacPorts that doesn?t know enough >> to try and build for x86_64 and will just build for i386 by default? >> > > You cannot run an earlier version of MacPorts. Ports are no longer > compatible with older versions of MacPorts. Also, 1.8.0 is the first version > of MacPorts that works at all on Snow Leopard. Also, 1.8.0 is the first > version that knows about passing -arch flags. Prior versions did not pass > anything and assume the compiler will do the right thing. On Snow Leopard, > the compiler will build 64-bit by default so if you somehow managed to get > MacPorts 1.7 to work on it, it would build 64-bit software for you, with no > way to change it. > > To build 32-bit only in MacPorts 1.8, set build_arch to i386 in > macports.conf. If you encounter problems, please report them. > I didn't encounter any problems in addition to the ones reported in the links above. > > A better way to get wine on Snow Leopard is to build all of wine's > dependencies with the +universal variant (which will build i386 and x86_64), > then install wine (or, currently on Snow Leopard, you'll have to use > wine-devel) (which will build i386 regardless of your build_arch because the > wine software is not 64-bit ready at this time). > > It may be tricky to identify which dependencies you need to rebuild. Once > you identify them, you would run > > sudo port upgrade --enforce-dependencies PORTNAME +universal > > for each identified port. > > I'm not sure what command would do this all for you automatically. If > someone knows it, please let me know. > I assume removing all installed ports and rebuilding everything works for this, right? I'm going to be starting over again, so it's really no loss. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rfritz333 at gmail.com Thu Oct 15 21:34:42 2009 From: rfritz333 at gmail.com (Randolph Fritz) Date: Fri, 16 Oct 2009 04:34:42 +0000 (UTC) Subject: Why should I use macports? References: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> Message-ID: On 2009-10-15, Wendy Bossons wrote: > > Can someone explain the purpose of Macports and why I might need it? > Broadly, because it's an easy-to-use library of useful free software. It provides, especially, dependency tracking, which means that when you install a package you want, you get the packages that that that package depends on automatically, without fuss. The value of the tool depends, of course, on what you are doing, but Macports has helped me greatly in my software development work. -- Randolph Fritz design machine group, architecture department, university of washington rfritz at u.washington.edu -or- rfritz333 at gmail.com From cfcaballero at gmail.com Fri Oct 16 00:12:45 2009 From: cfcaballero at gmail.com (Claudio Caballero) Date: Fri, 16 Oct 2009 03:12:45 -0400 Subject: Can I install an older version of MacPorts to easily compile i386 only on Snow Leopard? In-Reply-To: <88682b530910152103t21adea78q41ecbaa493cf4691@mail.gmail.com> References: <004101ca4dfc$657b30b0$30719210$@com> <85513EFE-4036-4164-833C-10336A7D788B@macports.org> <88682b530910152103t21adea78q41ecbaa493cf4691@mail.gmail.com> Message-ID: <88682b530910160012h4b8bfa6m7c6d3e54a7c0f317@mail.gmail.com> Sure enough, compiling with the universal variant instead of trying to specify the build_arch allowed me to install wine-devel just fine. Thanks again for your help Ryan. From hanche at math.ntnu.no Fri Oct 16 04:37:15 2009 From: hanche at math.ntnu.no (Harald Hanche-Olsen) Date: Fri, 16 Oct 2009 07:37:15 -0400 (EDT) Subject: Why should I use macports? In-Reply-To: References: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> Message-ID: <20091016.073715.74719286.hanche@math.ntnu.no> + Randolph Fritz : > On 2009-10-15, Wendy Bossons wrote: > > > > Can someone explain the purpose of Macports and why I might need it? > > > > Broadly, because it's an easy-to-use library of useful free > software. It provides, especially, dependency tracking, which means > that when you install a package you want, you get the packages that > that that package depends on automatically, without fuss. I beg to differ. Over the years I have used macports I have certainly seen my share of fuss. Enough so that I have started being careful taking a backup of /opt before doing an update, so I can roll back to an earlier version if needed. (I haven't needed to yet, but I have come close to doing it a couple times.) If you had said a minimum of fuss, I would agree. It's almost impossible to avoid problems in a system that is dragging in source code from all over the intertubes the way macports does, and I must say I am impressed and pleased that I don't see more problems than I do. But let's not oversell it. "No fuss"? No way. > The value of the tool depends, of course, on what you are doing, but > Macports has helped me greatly in my software development work. Amen to that. I don't do software development myself, but I know enough about programming that I can generally work my way around most problems that arise. The typical Mac user, whose idea of software installation involves dragging a .app to /Applications or double clicking a .mpkg, will however soon be out of their depths when a port command fails. And that will happen, if they use many ports and upgrade regularly. - Harald From j.van_den_hoff at fzd.de Fri Oct 16 06:34:15 2009 From: j.van_den_hoff at fzd.de (Joerg van den Hoff) Date: Fri, 16 Oct 2009 15:34:15 +0200 Subject: unison 2.32 declared stable Message-ID: <20091016133415.GB5131@marco.fz-rossendorf.de> hi there, unison 2.32 has been finally declared stable a few weeks ago. any chance to see this version soon in macports? regards, joerg From ryandesign at macports.org Fri Oct 16 07:31:22 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 16 Oct 2009 09:31:22 -0500 Subject: unison 2.32 declared stable In-Reply-To: <20091016133415.GB5131@marco.fz-rossendorf.de> References: <20091016133415.GB5131@marco.fz-rossendorf.de> Message-ID: On Oct 16, 2009, at 08:34, Joerg van den Hoff wrote: > unison 2.32 has been finally declared stable a few weeks ago. any > chance > to see this version soon in macports? I recommend you file a port request ticket in the issue tracker. If you can supply a patch to update the portfile to this version, even better. From ryandesign at macports.org Fri Oct 16 07:34:40 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 16 Oct 2009 09:34:40 -0500 Subject: Why should I use macports? In-Reply-To: <20091016.073715.74719286.hanche@math.ntnu.no> References: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> <20091016.073715.74719286.hanche@math.ntnu.no> Message-ID: <790B10C6-BF51-4C08-B4B7-E89B4BF11DCD@macports.org> On Oct 16, 2009, at 06:37, Harald Hanche-Olsen wrote: >> Broadly, because it's an easy-to-use library of useful free >> software. It provides, especially, dependency tracking, which means >> that when you install a package you want, you get the packages that >> that that package depends on automatically, without fuss. > > I beg to differ. Over the years I have used macports I have certainly > seen my share of fuss. [snip] > > If you had said a minimum of fuss, I would agree. It's almost > impossible to avoid problems in a system that is dragging in source > code from all over the intertubes the way macports does, and I must > say I am impressed and pleased that I don't see more problems than I > do. But let's not oversell it. "No fuss"? No way. Agreed. But I'm going to continue using it, because it's quite a whole lot less fuss than trying to figure out on your own everything that MacPorts port maintainers have already figured out for you. > The typical Mac user, whose idea of software > installation involves dragging a .app to /Applications or double > clicking a .mpkg, will however soon be out of their depths when a port > command fails. And that will happen, if they use many ports and > upgrade regularly. Hopefully port commands won't fail very often, or when they do, the error messages they print will be sufficient for the user to figure out how to proceed. For the times when they aren't, I hope users will write to macports-users or file tickets so that we can help them. From bobbyw at logicblox.com Fri Oct 16 09:11:00 2009 From: bobbyw at logicblox.com (Bobby Williams) Date: Fri, 16 Oct 2009 12:11:00 -0400 Subject: Error installing gcc41 on 10.6 In-Reply-To: <3AFB9D55-2868-4EF6-A51A-4F4A3769C507@macports.org> References: <3AFB9D55-2868-4EF6-A51A-4F4A3769C507@macports.org> Message-ID: We have a large multi-platform (Linux(primary), Windows (secondary) and OS/X (experimental) C++ project. The Linux team uses gcc41. gcc40 is used for building under OS/X. We would like to simplify things by normalizing compiler versions. (That is, we'd like to get rid of some the conditional compile stuff required because of compiler differences.) On Oct 15, 2009, at 12:39 PM, Ryan Schmidt wrote: > > On Oct 15, 2009, at 09:20, Bobby Williams wrote: > >> Has anyone else encountered this? Thanks! > > Everybody who has tried this on Snow Leopard will have encountered this, yes. gcc43 is the earliest that builds on Snow Leopard at this time. There are tickets about these problems in the issue tracker, but they may not get fixed. These are very old versions of gcc. Is there a specific reason you want gcc41 and can't use e.g. gcc44? > > > From ryandesign at macports.org Fri Oct 16 09:14:08 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 16 Oct 2009 11:14:08 -0500 Subject: Error installing gcc41 on 10.6 In-Reply-To: References: <3AFB9D55-2868-4EF6-A51A-4F4A3769C507@macports.org> Message-ID: <232A4F9D-C3C6-4E83-B489-495205E0D7FE@macports.org> On Oct 16, 2009, at 11:11, Bobby Williams wrote: > On Oct 15, 2009, at 12:39 PM, Ryan Schmidt wrote: > >> On Oct 15, 2009, at 09:20, Bobby Williams wrote: >> >>> Has anyone else encountered this? Thanks! >> >> Everybody who has tried this on Snow Leopard will have encountered >> this, yes. gcc43 is the earliest that builds on Snow Leopard at >> this time. There are tickets about these problems in the issue >> tracker, but they may not get fixed. These are very old versions of >> gcc. Is there a specific reason you want gcc41 and can't use e.g. >> gcc44? > > We have a large multi-platform (Linux(primary), Windows (secondary) > and OS/X (experimental) C++ project. The Linux team uses gcc41. > gcc40 is used for building under OS/X. We would like to simplify > things by normalizing compiler versions. (That is, we'd like to > get rid of some the conditional compile stuff required because of > compiler differences.) Note that Mac OS X (Tiger and later) does include gcc40 and (Leopard and later) gcc42 as part of Xcode, so if you can standardize on one of those versions, it's already there for you. Apple's gcc is of course different from the versions on other OSes. If you want to use plain gcc, you'll have to either use gcc43 or newer on Snow Leopard, or help us figure out how to make earlier gcc's compile again. From talklists at newgeo.com Fri Oct 16 11:09:59 2009 From: talklists at newgeo.com (Scott Haneda) Date: Fri, 16 Oct 2009 11:09:59 -0700 Subject: Why should I use macports? In-Reply-To: <790B10C6-BF51-4C08-B4B7-E89B4BF11DCD@macports.org> References: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> <20091016.073715.74719286.hanche@math.ntnu.no> <790B10C6-BF51-4C08-B4B7-E89B4BF11DCD@macports.org> Message-ID: This is how problems go... 1) port install foo 2) error 3) email mailing list, get advice 4) port -d install foo 5) email -d log to mailing list 6) profit Why can't macports always run a debug log, not to stdout, but to an install.log, that was perhaps rotated, or kept the last install at least. If (error) ui message: you may want to post your error log to the mailing list, it is located at /opt/local/var/log/macports/portname-debug.log Looking at the list archives, those 6 steps are repeated often, this would save list admins, members, users, etc an entire set of steps, and get resolution of port install issues solved much faster. -- Scott Iphone says hello. On Oct 16, 2009, at 7:34 AM, Ryan Schmidt wrote: > Hopefully port commands won't fail very often, or when they do, the > error messages they print will be sufficient for the user to figure > out how to proceed. For the times when they aren't, I hope users > will write to macports-users or file tickets so that we can help them. From jmr at macports.org Fri Oct 16 11:20:43 2009 From: jmr at macports.org (Joshua Root) Date: Sat, 17 Oct 2009 05:20:43 +1100 Subject: Why should I use macports? In-Reply-To: References: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> <20091016.073715.74719286.hanche@math.ntnu.no> <790B10C6-BF51-4C08-B4B7-E89B4BF11DCD@macports.org> Message-ID: <4AD8B97B.6070709@macports.org> On 2009-10-17 05:09, Scott Haneda wrote: > This is how problems go... > 1) port install foo > 2) error > 3) email mailing list, get advice > 4) port -d install foo > 5) email -d log to mailing list > 6) profit > > Why can't macports always run a debug log, not to stdout, but to an > install.log, that was perhaps rotated, or kept the last install at least. > > If (error) > ui message: you may want to post your error log to the mailing list, > it is located at /opt/local/var/log/macports/portname-debug.log > > Looking at the list archives, those 6 steps are repeated often, this > would save list admins, members, users, etc an entire set of steps, and > get resolution of port install issues solved much faster. - Josh From talklists at newgeo.com Fri Oct 16 11:47:30 2009 From: talklists at newgeo.com (Scott Haneda) Date: Fri, 16 Oct 2009 11:47:30 -0700 Subject: Why should I use macports? In-Reply-To: <4AD8B97B.6070709@macports.org> References: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> <20091016.073715.74719286.hanche@math.ntnu.no> <790B10C6-BF51-4C08-B4B7-E89B4BF11DCD@macports.org> <4AD8B97B.6070709@macports.org> Message-ID: <501B3305-4AA1-4281-AC89-B9F6CEC1F8AC@newgeo.com> On Oct 16, 2009, at 11:20 AM, Joshua Root wrote: > On 2009-10-17 05:09, Scott Haneda wrote: >> This is how problems go... >> 1) port install foo >> 2) error >> 3) email mailing list, get advice >> 4) port -d install foo >> 5) email -d log to mailing list >> 6) profit >> >> Why can't macports always run a debug log, not to stdout, but to an >> install.log, that was perhaps rotated, or kept the last install at >> least. >> >> If (error) >> ui message: you may want to post your error log to the mailing list, >> it is located at /opt/local/var/log/macports/portname-debug.log >> >> Looking at the list archives, those 6 steps are repeated often, this >> would save list admins, members, users, etc an entire set of steps, >> and >> get resolution of port install issues solved much faster. > > > > > - Josh Very nice proposal. Glad to see it on the roadmap. -- Scott Iphone says hello. From buffyg at mac.com Fri Oct 16 17:57:09 2009 From: buffyg at mac.com (Bayard Bell) Date: Sat, 17 Oct 2009 01:57:09 +0100 Subject: include problem building BDB 4.6.21 w/ /usr/local Message-ID: <8DCE25EA-5E75-4E99-8EE0-A5DA60C67EC7@mac.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been looking through tickets, trying to figure out what's going wrong. There's an open ticket for this, 19918. As far as I can see, the immediate problem occurs when you've got db.h in /usr/local/ include. Renaming the file certainly fixes the problem. (Three cheers to dtruss for giving me a handle on this.) What doesn't really make sense to me is why or how this is found in the first instance: I'd argue strongly that the pre-processor shouldn't be looking there by default, and it's not much evident to me that CPPFLAGS is being constructed to tell it to do so. Before digging around further, I thought I'd ask if anyone knew why this might be. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (Darwin) iEYEARECAAYFAkrZFmkACgkQcZQHT1XL9xlvzgCfQNmRMPHVRBB+0KO1j4jKQXKh 1ucAoI+tHafj5UfgG/Vc6hOf3tpFGusV =hh7t -----END PGP SIGNATURE----- From jmr at macports.org Sat Oct 17 02:19:24 2009 From: jmr at macports.org (Joshua Root) Date: Sat, 17 Oct 2009 20:19:24 +1100 Subject: include problem building BDB 4.6.21 w/ /usr/local In-Reply-To: <8DCE25EA-5E75-4E99-8EE0-A5DA60C67EC7@mac.com> References: <8DCE25EA-5E75-4E99-8EE0-A5DA60C67EC7@mac.com> Message-ID: <4AD98C1C.2040405@macports.org> On 2009-10-17 11:57, Bayard Bell wrote: > I've been looking through tickets, trying to figure out what's going > wrong. There's an open ticket for this, 19918. As far as I can see, the > immediate problem occurs when you've got db.h in /usr/local/include. > Renaming the file certainly fixes the problem. (Three cheers to dtruss > for giving me a handle on this.) > > What doesn't really make sense to me is why or how this is found in the > first instance: I'd argue strongly that the pre-processor shouldn't be > looking there by default, and it's not much evident to me that CPPFLAGS > is being constructed to tell it to do so. Before digging around further, > I thought I'd ask if anyone knew why this might be. We're not telling it to look there, it just does. The only way to avoid this would be to use -nostdinc, but then you have to somehow reconstruct the other default search paths and tell it to look in them. So basically, there's not much we can do about it, and the place to report the issue is and/or . (Note that upstream changes to GCC at this point will likely never be distributed by Apple, since they are moving to LLVM.) - Josh From trog24 at comcast.net Sat Oct 17 03:31:07 2009 From: trog24 at comcast.net (Frank J. R. Hanstick) Date: Sat, 17 Oct 2009 03:31:07 -0700 Subject: gnustep-make failed to install Message-ID: <22AD7BDD-8052-4320-8D61-3FDCA59D8757@comcast.net> Hello, When trying to install gnustep, the following error occurred: ---> Building gcc42 ---> Staging gcc42 into destroot ---> Installing gcc42 @4.2.4_1 ---> Activating gcc42 @4.2.4_1 ---> Cleaning gcc42 ---> Fetching gnustep-make ---> Attempting to fetch gnustep-make-2.2.0.tar.gz from http://distfiles.macports.org/gnustep-make ---> Verifying checksum(s) for gnustep-make ---> Extracting gnustep-make ---> Configuring gnustep-make 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_gnustep_gnustep-make/work/gnustep- make-2.2.0" && ./configure --prefix=/opt/local/GNUstep CC=gcc-mp-4.2 -- with-library-combo=gnu-gnu-gnu --with-objc-lib-flag=-lobjc-gnu --with- config-file=/opt/local/GNUstep/System/Library/GNUstep.conf " returned error 77 Command output: checking for gcc... gcc-mp-4.2 checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. Error: The following dependencies failed to build: ArtResources gnustep-core gnustep-back gnustep-gui gnustep-base gnustep-make libffi libxslt libxml2 gnutls libgcrypt libgpg-error libtasn1 lzo opencdk libungif libart_lgpl GMastermind GMines GNUMail Etoile SQLClient Performance oniguruma5 poppler gtk2 atk glib2 gtk-doc docbook-xml docbook-xml-4.1.2 xmlcatmgr docbook-xml-4.2 docbook-xml-4.3 docbook- xml-4.4 docbook-xml-4.5 docbook-xml-5.0 docbook-xsl gnome-doc-utils iso-codes p5-xml-parser py26-libxml2 python26 gdbm rarian getopt intltool gnome-common p5-getopt-long p5-pathtools p5-scalar-list-utils cairo libpixman jasper pango shared-mime-info xorg-libXcomposite xorg- compositeproto xorg-fixesproto xorg-libXfixes xorg-libXcursor xorg- libXdamage xorg-damageproto xorg-libXinerama xorg-xineramaproto openjpeg poppler-data Pantomime PRICE TalkSoup netclasses Yap.app ImageMagick p7zip a2ps psutils gworkspace system-preferences PreferencePanes windowmaker giflib xpm Error: Status 1 encountered during processing. I searched the bug data base and found #43915 which says the gnustep is not universal. Does that mean that it will not install on a PPC even though gcc42 installed? I am running MacOS 10.5.8 on a PPC G4. Frank J. R. Hanstick trog24 at comcast.net From fbartolom at gmail.com Sat Oct 17 07:27:41 2009 From: fbartolom at gmail.com (Fabrizio Bartolomucci) Date: Sat, 17 Oct 2009 16:27:41 +0200 Subject: Path problems In-Reply-To: References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> <4AD354C7.3080700@gmail.com> <15536E86-F445-47CB-BBC4-3156A2811029@macports.org> <4AD62887.5050700@gmail.com> Message-ID: <4AD9D45D.3010903@gmail.com> Ryan Schmidt ha scritto: > On Oct 14, 2009, at 14:37, Fabrizio Bartolomucci wrote: > >> 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_devel_dbus/work/dbus-1.2.14" >> && ./configure --prefix=/opt/local --disable-doxygen-docs >> --disable-xml-docs --without-x --enable-launchd >> --with-launchd-agent-dir=/opt/local/Library/LaunchAgents >> --with-dbus-user=messagebus " returned >> error 1 > > Ok, so dbus is the port that's failing. > > I see you're using dbus 1.2.14. dbus was just updated to 1.2.16 so > please "sudo port selfupdate" and try again and see if 1.2.16 works > better. I did but it still stucks. ---> Configuring dbus 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_devel_dbus/work/dbus-1.2.16" && ./configure --prefix=/opt/local --disable-doxygen-docs --disable-xml-docs --without-x --enable-launchd --with-launchd-agent-dir=/opt/local/Library/LaunchAgents --with-dbus-user=messagebus " returned error 1 Command output: checking for fpathconf... yes checking for setrlimit... yes checking for poll... yes checking for broken poll... yes checking for dirfd... yes checking execinfo.h usability... yes checking execinfo.h presence... yes checking for execinfo.h... yes checking for backtrace... yes checking errno.h usability... yes checking errno.h presence... yes checking for errno.h... yes checking for unistd.h... (cached) yes checking for posix getpwnam_r... yes checking whether socklen_t is defined... yes checking sys/uio.h usability... yes checking sys/uio.h presence... yes checking for sys/uio.h... yes checking for writev... yes checking sys/syslimits.h usability... yes checking sys/syslimits.h presence... yes checking for sys/syslimits.h... yes checking for ISO C99 varargs macros in C... yes checking for GNUC varargs macros... yes checking for struct cmsgcred... no checking for getpeerucred... no checking for getpeereid... yes checking abstract socket namespace... no checking for XML_ParserCreate_MM in -lexpat... no configure: error: Could not find expat.h, check config.log for failed attempts Error: Unable to upgrade port: 1 From ryandesign at macports.org Sat Oct 17 08:14:11 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 17 Oct 2009 10:14:11 -0500 Subject: Why should I use macports? In-Reply-To: References: <80622BA7-CC5B-483D-98D7-FF0082564976@mit.edu> <20091016.073715.74719286.hanche@math.ntnu.no> <790B10C6-BF51-4C08-B4B7-E89B4BF11DCD@macports.org> Message-ID: On Oct 16, 2009, at 13:09, Scott Haneda wrote: > This is how problems go... > 1) port install foo > 2) error > 3) email mailing list, get advice > 4) port -d install foo > 5) email -d log to mailing list > 6) profit > > Why can't macports always run a debug log, not to stdout, but to an > install.log, that was perhaps rotated, or kept the last install at > least. That would be what the GSoC '09 logging project was all about. http://trac.macports.org/wiki/SummerOfCode#logging Did that ever get done? From ryandesign at macports.org Sat Oct 17 08:17:48 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 17 Oct 2009 10:17:48 -0500 Subject: Path problems In-Reply-To: <4AD9D45D.3010903@gmail.com> References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> <4AD354C7.3080700@gmail.com> <15536E86-F445-47CB-BBC4-3156A2811029@macports.org> <4AD62887.5050700@gmail.com> <4AD9D45D.3010903@gmail.com> Message-ID: On Oct 17, 2009, at 09:27, Fabrizio Bartolomucci wrote: > Ryan Schmidt ha scritto: > >> I see you're using dbus 1.2.14. dbus was just updated to 1.2.16 so >> please "sudo port selfupdate" and try again and see if 1.2.16 works >> better. > > I did but it still stucks. > > ---> Configuring dbus > 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_devel_dbus > /work/dbus-1.2.16" && ./configure --prefix=/opt/local --disable- > doxygen-docs --disable-xml-docs --without-x --enable-launchd --with- > launchd-agent-dir=/opt/local/Library/LaunchAgents --with-dbus- > user=messagebus " returned error 1 > Command output: checking for fpathconf... yes > checking for setrlimit... yes > checking for poll... yes > checking for broken poll... yes > checking for dirfd... yes > checking execinfo.h usability... yes > checking execinfo.h presence... yes > checking for execinfo.h... yes > checking for backtrace... yes > checking errno.h usability... yes > checking errno.h presence... yes > checking for errno.h... yes > checking for unistd.h... (cached) yes > checking for posix getpwnam_r... yes > checking whether socklen_t is defined... yes > checking sys/uio.h usability... yes > checking sys/uio.h presence... yes > checking for sys/uio.h... yes > checking for writev... yes > checking sys/syslimits.h usability... yes > checking sys/syslimits.h presence... yes > checking for sys/syslimits.h... yes > checking for ISO C99 varargs macros in C... yes > checking for GNUC varargs macros... yes > checking for struct cmsgcred... no > checking for getpeerucred... no > checking for getpeereid... yes > checking abstract socket namespace... no > checking for XML_ParserCreate_MM in -lexpat... no > configure: error: Could not find expat.h, check config.log for > failed attempts > > Error: Unable to upgrade port: 1 Ok. Could you supply the config.log, please? From fbartolom at gmail.com Sat Oct 17 13:15:52 2009 From: fbartolom at gmail.com (Fabrizio Bartolomucci) Date: Sat, 17 Oct 2009 22:15:52 +0200 Subject: Path problems In-Reply-To: References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> <4AD354C7.3080700@gmail.com> <15536E86-F445-47CB-BBC4-3156A2811029@macports.org> <4AD62887.5050700@gmail.com> <4AD9D45D.3010903@gmail.com> Message-ID: <4ADA25F8.9090805@gmail.com> Ryan Schmidt ha scritto: > > Ok. Could you supply the config.log, please? > > It could look slightly recursive... but could you please me give the full path for this file? From ryandesign at macports.org Sat Oct 17 13:18:14 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 17 Oct 2009 15:18:14 -0500 Subject: Path problems In-Reply-To: <4ADA25F8.9090805@gmail.com> References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> <4AD354C7.3080700@gmail.com> <15536E86-F445-47CB-BBC4-3156A2811029@macports.org> <4AD62887.5050700@gmail.com> <4AD9D45D.3010903@gmail.com> <4ADA25F8.9090805@gmail.com> Message-ID: On Oct 17, 2009, at 15:15, Fabrizio Bartolomucci wrote: > Ryan Schmidt ha scritto: >> > >> Ok. Could you supply the config.log, please? >> > > It could look slightly recursive... but could you please me give the > full path for this file? "port work dbus" will tell you the path to dbus's work directory. The source directory is inside that, and the config.log is inside that. From ryandesign at macports.org Sat Oct 17 13:20:03 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 17 Oct 2009 15:20:03 -0500 Subject: gnustep-make failed to install In-Reply-To: <22AD7BDD-8052-4320-8D61-3FDCA59D8757@comcast.net> References: <22AD7BDD-8052-4320-8D61-3FDCA59D8757@comcast.net> Message-ID: <993B40D7-4303-4B6B-9858-7C28486DCB44@macports.org> On Oct 17, 2009, at 05:31, Frank J. R. Hanstick wrote: > When trying to install gnustep, the following error occurred: > > ---> Building gcc42 > ---> Staging gcc42 into destroot > ---> Installing gcc42 @4.2.4_1 > ---> Activating gcc42 @4.2.4_1 > ---> Cleaning gcc42 > ---> Fetching gnustep-make > ---> Attempting to fetch gnustep-make-2.2.0.tar.gz from http://distfiles.macports.org/gnustep-make > ---> Verifying checksum(s) for gnustep-make > ---> Extracting gnustep-make > ---> Configuring gnustep-make > 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_gnustep_gnustep > -make/work/gnustep-make-2.2.0" && ./configure --prefix=/opt/local/ > GNUstep CC=gcc-mp-4.2 --with-library-combo=gnu-gnu-gnu --with-objc- > lib-flag=-lobjc-gnu --with-config-file=/opt/local/GNUstep/System/ > Library/GNUstep.conf " returned error 77 > Command output: checking for gcc... gcc-mp-4.2 > checking for C compiler default output file name... > configure: error: C compiler cannot create executables > See `config.log' for more details. > > Error: The following dependencies failed to build: ArtResources > gnustep-core gnustep-back gnustep-gui gnustep-base gnustep-make > libffi libxslt libxml2 gnutls libgcrypt libgpg-error libtasn1 lzo > opencdk libungif libart_lgpl GMastermind GMines GNUMail Etoile > SQLClient Performance oniguruma5 poppler gtk2 atk glib2 gtk-doc > docbook-xml docbook-xml-4.1.2 xmlcatmgr docbook-xml-4.2 docbook- > xml-4.3 docbook-xml-4.4 docbook-xml-4.5 docbook-xml-5.0 docbook-xsl > gnome-doc-utils iso-codes p5-xml-parser py26-libxml2 python26 gdbm > rarian getopt intltool gnome-common p5-getopt-long p5-pathtools p5- > scalar-list-utils cairo libpixman jasper pango shared-mime-info xorg- > libXcomposite xorg-compositeproto xorg-fixesproto xorg-libXfixes > xorg-libXcursor xorg-libXdamage xorg-damageproto xorg-libXinerama > xorg-xineramaproto openjpeg poppler-data Pantomime PRICE TalkSoup > netclasses Yap.app ImageMagick p7zip a2ps psutils gworkspace system- > preferences PreferencePanes windowmaker giflib xpm > Error: Status 1 encountered during processing. > > I searched the bug data base and found #43915 which says the gnustep > is not universal. Does that mean that it will not install on a PPC > even though gcc42 installed? No, it means it will not install with the +universal variant, on any Mac, but should install without the +universal variant, on any may. > I am running MacOS 10.5.8 on a PPC G4. What does the config.log say? Can you attach it here? From fbartolom at gmail.com Sat Oct 17 13:23:14 2009 From: fbartolom at gmail.com (Fabrizio Bartolomucci) Date: Sat, 17 Oct 2009 22:23:14 +0200 Subject: Path problems In-Reply-To: References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> <4AD354C7.3080700@gmail.com> <15536E86-F445-47CB-BBC4-3156A2811029@macports.org> <4AD62887.5050700@gmail.com> <4AD9D45D.3010903@gmail.com> <4ADA25F8.9090805@gmail.com> Message-ID: <4ADA27B2.2090401@gmail.com> Ryan Schmidt ha scritto: > > On Oct 17, 2009, at 15:15, Fabrizio Bartolomucci wrote: > >> Ryan Schmidt ha scritto: >>> >> >>> Ok. Could you supply the config.log, please? >>> >> >> It could look slightly recursive... but could you please me give the >> full path for this file? > > "port work dbus" will tell you the path to dbus's work directory. The > source directory is inside that, and the config.log is inside that. > > Ok, here it is. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: config.log URL: From ryandesign at macports.org Sat Oct 17 13:40:32 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 17 Oct 2009 15:40:32 -0500 Subject: Path problems In-Reply-To: <4ADA27B2.2090401@gmail.com> References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> <4AD354C7.3080700@gmail.com> <15536E86-F445-47CB-BBC4-3156A2811029@macports.org> <4AD62887.5050700@gmail.com> <4AD9D45D.3010903@gmail.com> <4ADA25F8.9090805@gmail.com> <4ADA27B2.2090401@gmail.com> Message-ID: <16665FB2-686A-49A3-B004-E7300A0FB6D0@macports.org> On Oct 17, 2009, at 15:23, Fabrizio Bartolomucci wrote: >>> Ryan Schmidt ha scritto: >> >>> >>>> Ok. Could you supply the config.log, please? > This file contains any messages produced by compilers while > running configure, to aid debugging if configure makes a mistake. > configure:16745: checking for XML_ParserCreate_MM in -lexpat > configure:16770: /usr/bin/gcc-4.2 -o conftest -O2 -arch x86_64 -I/ > opt/local/include -L/opt/local/lib conftest.c -lexpat >&5 > ld: warning: in /opt/local/lib/libexpat.dylib, file is not of > required architecture Ok. Your libexpat is not of the required architecture. How did this occur? Perhaps you were using Leopard, and had MacPorts installed, and installed several ports including expat, and then you upgraded to Snow Leopard, but you did not uninstall and reinstall all your ports? If that's the case, please do that now. Read the Migration page for more information. http://trac.macports.org/wiki/Migration From fbartolom at gmail.com Sat Oct 17 13:45:54 2009 From: fbartolom at gmail.com (Fabrizio Bartolomucci) Date: Sat, 17 Oct 2009 22:45:54 +0200 Subject: Path problems In-Reply-To: <16665FB2-686A-49A3-B004-E7300A0FB6D0@macports.org> References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> <4AD354C7.3080700@gmail.com> <15536E86-F445-47CB-BBC4-3156A2811029@macports.org> <4AD62887.5050700@gmail.com> <4AD9D45D.3010903@gmail.com> <4ADA25F8.9090805@gmail.com> <4ADA27B2.2090401@gmail.com> <16665FB2-686A-49A3-B004-E7300A0FB6D0@macports.org> Message-ID: <4ADA2D02.20808@gmail.com> Ryan Schmidt ha scritto: > On Oct 17, 2009, at 15:23, Fabrizio Bartolomucci wrote: > >>>> Ryan Schmidt ha scritto: >>> >>>> >>>>> Ok. Could you supply the config.log, please? > >> This file contains any messages produced by compilers while >> running configure, to aid debugging if configure makes a mistake. > >> configure:16745: checking for XML_ParserCreate_MM in -lexpat >> configure:16770: /usr/bin/gcc-4.2 -o conftest -O2 -arch x86_64 >> -I/opt/local/include -L/opt/local/lib conftest.c -lexpat >&5 >> ld: warning: in /opt/local/lib/libexpat.dylib, file is not of >> required architecture > > Ok. Your libexpat is not of the required architecture. How did this > occur? Perhaps you were using Leopard, and had MacPorts installed, and > installed several ports including expat, and then you upgraded to Snow > Leopard, but you did not uninstall and reinstall all your ports? If > that's the case, please do that now. Read the Migration page for more > information. > > http://trac.macports.org/wiki/Migration > Actually, as I probably alrady said, I installed SnowLeopard on a perfectly working MacPort installation that did not work any longer on the new system. So I followed your suggestion up to this point: consequently just ask me to do whatever you like, but returning to the drawing board... From ryandesign at macports.org Sat Oct 17 13:50:03 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 17 Oct 2009 15:50:03 -0500 Subject: Path problems In-Reply-To: <4ADA2D02.20808@gmail.com> References: <4AD32B83.1070804@gmail.com> <4AD32EE3.2080203@macports.org> <4AD344EB.8040902@gmail.com> <4AD354C7.3080700@gmail.com> <15536E86-F445-47CB-BBC4-3156A2811029@macports.org> <4AD62887.5050700@gmail.com> <4AD9D45D.3010903@gmail.com> <4ADA25F8.9090805@gmail.com> <4ADA27B2.2090401@gmail.com> <16665FB2-686A-49A3-B004-E7300A0FB6D0@macports.org> <4ADA2D02.20808@gmail.com> Message-ID: <6FA1E0F2-E52C-428B-9062-B0161F7962C2@macports.org> On Oct 17, 2009, at 15:45, Fabrizio Bartolomucci wrote: > Ryan Schmidt ha scritto: > >> On Oct 17, 2009, at 15:23, Fabrizio Bartolomucci wrote: >> >>> configure:16745: checking for XML_ParserCreate_MM in -lexpat >>> configure:16770: /usr/bin/gcc-4.2 -o conftest -O2 -arch x86_64 -I/ >>> opt/local/include -L/opt/local/lib conftest.c -lexpat >&5 >>> ld: warning: in /opt/local/lib/libexpat.dylib, file is not of >>> required architecture >> >> Ok. Your libexpat is not of the required architecture. How did this >> occur? Perhaps you were using Leopard, and had MacPorts installed, >> and installed several ports including expat, and then you upgraded >> to Snow Leopard, but you did not uninstall and reinstall all your >> ports? If that's the case, please do that now. Read the Migration >> page for more information. >> >> http://trac.macports.org/wiki/Migration >> > > Actually, as I probably alrady said, I installed SnowLeopard on a > perfectly working MacPort installation that did not work any longer > on the new system. So I followed your suggestion up to this point: > consequently just ask me to do whatever you like, but returning to > the drawing board... If your perfectly working MacPorts installation was working on Leopard, then it is completely normal and expected that it will not work properly once you upgrade to Snow Leopard, and you must follow the instructions on the aforementioned Migration page to uninstall all your ports and reinstall them now on Snow Leopard. From trog24 at comcast.net Sat Oct 17 15:09:28 2009 From: trog24 at comcast.net (Frank J. R. Hanstick) Date: Sat, 17 Oct 2009 15:09:28 -0700 Subject: gnustep-make failed to install In-Reply-To: <993B40D7-4303-4B6B-9858-7C28486DCB44@macports.org> References: <22AD7BDD-8052-4320-8D61-3FDCA59D8757@comcast.net> <993B40D7-4303-4B6B-9858-7C28486DCB44@macports.org> Message-ID: <8F1E1D14-1C12-4B63-A467-42E3D4E04D33@comcast.net> Hello, In the log is: cc1: error: unrecognized command line option "-arch" Attached is the log. On Oct 17, 2009, at 1:20 PM, Ryan Schmidt wrote: > > On Oct 17, 2009, at 05:31, Frank J. R. Hanstick wrote: > >> When trying to install gnustep, the following error occurred: >> >> ---> Building gcc42 >> ---> Staging gcc42 into destroot >> ---> Installing gcc42 @4.2.4_1 >> ---> Activating gcc42 @4.2.4_1 >> ---> Cleaning gcc42 >> ---> Fetching gnustep-make >> ---> Attempting to fetch gnustep-make-2.2.0.tar.gz from http://distfiles.macports.org/gnustep-make >> ---> Verifying checksum(s) for gnustep-make >> ---> Extracting gnustep-make >> ---> Configuring gnustep-make >> 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_gnustep_gnustep-make/work/gnustep- >> make-2.2.0" && ./configure --prefix=/opt/local/GNUstep CC=gcc- >> mp-4.2 --with-library-combo=gnu-gnu-gnu --with-objc-lib-flag=-lobjc- >> gnu --with-config-file=/opt/local/GNUstep/System/Library/ >> GNUstep.conf " returned error 77 >> Command output: checking for gcc... gcc-mp-4.2 >> checking for C compiler default output file name... >> configure: error: C compiler cannot create executables >> See `config.log' for more details. >> >> Error: The following dependencies failed to build: ArtResources >> gnustep-core gnustep-back gnustep-gui gnustep-base gnustep-make >> libffi libxslt libxml2 gnutls libgcrypt libgpg-error libtasn1 lzo >> opencdk libungif libart_lgpl GMastermind GMines GNUMail Etoile >> SQLClient Performance oniguruma5 poppler gtk2 atk glib2 gtk-doc >> docbook-xml docbook-xml-4.1.2 xmlcatmgr docbook-xml-4.2 docbook- >> xml-4.3 docbook-xml-4.4 docbook-xml-4.5 docbook-xml-5.0 docbook-xsl >> gnome-doc-utils iso-codes p5-xml-parser py26-libxml2 python26 gdbm >> rarian getopt intltool gnome-common p5-getopt-long p5-pathtools p5- >> scalar-list-utils cairo libpixman jasper pango shared-mime-info >> xorg-libXcomposite xorg-compositeproto xorg-fixesproto xorg- >> libXfixes xorg-libXcursor xorg-libXdamage xorg-damageproto xorg- >> libXinerama xorg-xineramaproto openjpeg poppler-data Pantomime >> PRICE TalkSoup netclasses Yap.app ImageMagick p7zip a2ps psutils >> gworkspace system-preferences PreferencePanes windowmaker giflib xpm >> Error: Status 1 encountered during processing. >> >> I searched the bug data base and found #43915 which says the >> gnustep is not universal. Does that mean that it will not install >> on a PPC even though gcc42 installed? > > No, it means it will not install with the +universal variant, on any > Mac, but should install without the +universal variant, on any may. > >> I am running MacOS 10.5.8 on a PPC G4. > > What does the config.log say? Can you attach it here? > > Frank J. R. Hanstick trog24 at comcast.net -------------- next part -------------- A non-text attachment was scrubbed... Name: config.log Type: application/octet-stream Size: 7883 bytes Desc: not available URL: From dave at difference.com.au Sun Oct 18 05:20:46 2009 From: dave at difference.com.au (David Cake) Date: Sun, 18 Oct 2009 20:20:46 +0800 Subject: serf on SL Message-ID: Serf won't build for me, which is annoying because I really need subversion. One thing confuses me about the error (reproduced below) - it is complaining about 0386 architecture, but I am building for Snow Leopard, so shouldn't it be trying to build everything x86_64? I did previously have many things built as universal, but there seemed to be no point, so changed my default variants setting in variants.conf, clean all installed, removed all installed, and start building again - so why does it still appear to be trying to build i386 or universal versions, and how can I make it stop? Regards David 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_serf/work/serf-0.3.0" && /usr/bin/make -j2 all " returned error 2 Command output: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_apr_socket_close", referenced from: _reset_connection in libserf-0.a(context.o) _clean_skt in libserf-0.a(context.o) _serf_connection_close in libserf-0.a(context.o) "_CRYPTO_set_locking_callback", referenced from: _cleanup_ssl in libserf-0.a(ssl_buckets.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_SSLv23_client_method", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_BIO_new", referenced from: _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_PKCS12_parse", referenced from: _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_apr_array_push", referenced from: _serf_connection_create in libserf-0.a(context.o) "_apr_pool_userdata_setn", referenced from: _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_apr_file_open", referenced from: _setup_request in serf_get.o _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) ld: symbol(s) not found for architecture i386 collect2: ld returned 1 exit status lipo: can't open input file: /var/tmp//cc9kPVSt.out (No such file or directory) make: *** [test/serf_get] Error 1 Error: Status 1 encountered during processing. Here is a more detaild version Last login: Sun Oct 18 16:12:40 on ttys002 david-cakes-macbook-pro-2:~ $ sudo port -dv install serf DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/www/serf DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/www/serf DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Requested variant darwin is not provided by port serf. DEBUG: Requested variant i386 is not provided by port serf. DEBUG: Requested variant macosx is not provided by port serf. DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/apr DEBUG: epoch: in tree: 0 installed: 0 DEBUG: apr 1.3.9_0 exists in the ports tree DEBUG: apr 1.3.9_0 is the latest installed DEBUG: apr 1.3.9_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/apr DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Requested variant darwin is not provided by port apr. DEBUG: Requested variant i386 is not provided by port apr. DEBUG: Requested variant macosx is not provided by port apr. DEBUG: No need to upgrade! apr 1.3.9_0 >= apr 1.3.9_0 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/apr-util DEBUG: epoch: in tree: 0 installed: 0 DEBUG: apr-util 1.3.9_0 exists in the ports tree DEBUG: apr-util 1.3.9_0 is the latest installed DEBUG: apr-util 1.3.9_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/apr-util DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Requested variant darwin is not provided by port apr-util. DEBUG: Requested variant i386 is not provided by port apr-util. DEBUG: Requested variant macosx is not provided by port apr-util. DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/expat DEBUG: epoch: in tree: 0 installed: 0 DEBUG: expat 2.0.1_0 exists in the ports tree DEBUG: expat 2.0.1_0 is the latest installed DEBUG: expat 2.0.1_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/expat DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Requested variant darwin is not provided by port expat. DEBUG: Requested variant i386 is not provided by port expat. DEBUG: Requested variant macosx is not provided by port expat. DEBUG: No need to upgrade! expat 2.0.1_0 >= expat 2.0.1_0 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv DEBUG: epoch: in tree: 0 installed: 0 DEBUG: libiconv 1.13_0 exists in the ports tree DEBUG: libiconv 1.13_0 is the latest installed DEBUG: libiconv 1.13_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant darwin is not provided by port libiconv. DEBUG: Requested variant i386 is not provided by port libiconv. DEBUG: Requested variant macosx is not provided by port libiconv. DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gperf DEBUG: epoch: in tree: 0 installed: 0 DEBUG: gperf 3.0.4_0 exists in the ports tree DEBUG: gperf 3.0.4_0 is the latest installed DEBUG: gperf 3.0.4_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gperf DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant darwin is not provided by port gperf. DEBUG: Requested variant i386 is not provided by port gperf. DEBUG: Requested variant macosx is not provided by port gperf. DEBUG: No need to upgrade! gperf 3.0.4_0 >= gperf 3.0.4_0 DEBUG: No need to upgrade! libiconv 1.13_0 >= libiconv 1.13_0 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/databases/db46 DEBUG: epoch: in tree: 0 installed: 0 DEBUG: db46 4.6.21_5 exists in the ports tree DEBUG: db46 4.6.21_5 is the latest installed DEBUG: db46 4.6.21_5 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/databases/db46 DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant darwin is not provided by port db46. DEBUG: Requested variant i386 is not provided by port db46. DEBUG: Requested variant macosx is not provided by port db46. DEBUG: No need to upgrade! db46 4.6.21_5 >= db46 4.6.21_5 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/databases/sqlite3 DEBUG: epoch: in tree: 0 installed: 0 DEBUG: sqlite3 3.6.18_0 exists in the ports tree DEBUG: sqlite3 3.6.18_0 is the latest installed DEBUG: sqlite3 3.6.18_0 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/databases/sqlite3 DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Requested variant darwin is not provided by port sqlite3. DEBUG: Requested variant i386 is not provided by port sqlite3. DEBUG: Requested variant macosx is not provided by port sqlite3. DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/readline DEBUG: epoch: in tree: 0 installed: 0 DEBUG: readline 6.0.000_2 exists in the ports tree DEBUG: readline 6.0.000_2 +darwin is the latest installed DEBUG: readline 6.0.000_2 +darwin is active DEBUG: Merging existing variants darwin into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/readline DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant i386 is not provided by port readline. DEBUG: Requested variant macosx is not provided by port readline. DEBUG: Executing variant darwin provides darwin DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncurses DEBUG: epoch: in tree: 0 installed: 0 DEBUG: ncurses 5.7_0 exists in the ports tree DEBUG: ncurses 5.7_0 +darwin_10 is the latest installed DEBUG: ncurses 5.7_0 +darwin_10 is active DEBUG: Merging existing variants darwin_10 into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncurses DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant darwin is not provided by port ncurses. DEBUG: Requested variant i386 is not provided by port ncurses. DEBUG: Requested variant macosx is not provided by port ncurses. DEBUG: Executing variant darwin_10 provides darwin_10 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncursesw DEBUG: epoch: in tree: 0 installed: 0 DEBUG: ncursesw 5.7_0 exists in the ports tree DEBUG: ncursesw 5.7_0 +darwin_10 is the latest installed DEBUG: ncursesw 5.7_0 +darwin_10 is active DEBUG: Merging existing variants darwin_10 into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/ncursesw DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant darwin is not provided by port ncursesw. DEBUG: Requested variant i386 is not provided by port ncursesw. DEBUG: Requested variant macosx is not provided by port ncursesw. DEBUG: Executing variant darwin_10 provides darwin_10 DEBUG: No need to upgrade! ncursesw 5.7_0 >= ncursesw 5.7_0 DEBUG: No need to upgrade! ncurses 5.7_0 >= ncurses 5.7_0 DEBUG: No need to upgrade! readline 6.0.000_2 >= readline 6.0.000_2 DEBUG: No need to upgrade! sqlite3 3.6.18_0 >= sqlite3 3.6.18_0 DEBUG: No need to upgrade! apr-util 1.3.9_0 >= apr-util 1.3.9_0 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/openssl DEBUG: epoch: in tree: 1 installed: 1 DEBUG: openssl 0.9.8k_0 exists in the ports tree DEBUG: openssl 0.9.8k_0 +darwin is the latest installed DEBUG: openssl 0.9.8k_0 +darwin is active DEBUG: Merging existing variants darwin into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/openssl DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant i386 is not provided by port openssl. DEBUG: Requested variant macosx is not provided by port openssl. DEBUG: Executing variant darwin provides darwin DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/archivers/zlib DEBUG: epoch: in tree: 0 installed: 0 DEBUG: zlib 1.2.3_3 exists in the ports tree DEBUG: zlib 1.2.3_3 is the latest installed DEBUG: zlib 1.2.3_3 is active DEBUG: Merging existing variants into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/archivers/zlib DEBUG: OS Platform: darwin DEBUG: OS Version: 10.0.0 DEBUG: Mac OS X Version: 10.6 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Requested variant darwin is not provided by port zlib. DEBUG: Requested variant i386 is not provided by port zlib. DEBUG: Requested variant macosx is not provided by port zlib. DEBUG: No need to upgrade! zlib 1.2.3_3 >= zlib 1.2.3_3 DEBUG: No need to upgrade! openssl 0.9.8k_0 >= openssl 0.9.8k_0 ---> Computing dependencies for serf DEBUG: Searching for dependency: apr DEBUG: Found Dependency: receipt exists for apr DEBUG: Searching for dependency: apr-util DEBUG: Found Dependency: receipt exists for apr-util DEBUG: Searching for dependency: openssl DEBUG: Found Dependency: receipt exists for openssl DEBUG: Executing org.macports.main (serf) DEBUG: Skipping completed org.macports.fetch (serf) DEBUG: Skipping completed org.macports.checksum (serf) DEBUG: setting option extract.cmd to /usr/bin/bzip2 DEBUG: Skipping completed org.macports.extract (serf) DEBUG: Skipping completed org.macports.patch (serf) DEBUG: Skipping completed org.macports.configure (serf) ---> Building serf DEBUG: Executing org.macports.build (serf) DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.6' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_serf/work/serf-0.3.0" && /usr/bin/make -j2 all' /opt/local/share/apr-1/build/libtool --silent --mode=link /usr/bin/gcc-4.2 -L/opt/local/lib -arch x86_64 -arch i386 -L/opt/local/lib/db46 -static -o test/serf_get libserf-0.la test/serf_get.lo /opt/local/lib/libaprutil-1.la -ldb-4.6 -lexpat -liconv /opt/local/lib/libapr-1.la -lpthread -lz -lssl -lcrypto /opt/local/share/apr-1/build/libtool --silent --mode=link /usr/bin/gcc-4.2 -L/opt/local/lib -arch x86_64 -arch i386 -L/opt/local/lib/db46 -static -o test/serf_response libserf-0.la test/serf_response.lo /opt/local/lib/libaprutil-1.la -ldb-4.6 -lexpat -liconv /opt/local/lib/libapr-1.la -lpthread -lz -lssl -lcrypto ld: warning: in /opt/local/lib/libaprutil-1.dylib, file is not of required architecture ld: warning: in /opt/local/lib/db46/libdb-4.6.dylib, file is not of required architecture ld: warning: in /opt/local/lib/libexpat.dylib, file is not of required architecture ld: warning: in /opt/local/lib/libiconv.dylib, file is not of required architecture ld: warning: in /opt/local/lib/libapr-1.dylib, file is not of required architecture ld: warning: in /opt/local/lib/libz.dylib, file is not of required architecture ld: warning: in /opt/local/lib/libssl.dylib, file is not of required architecture ld: warning: in /opt/local/lib/libcrypto.dylib, file is not of required architecture Undefined symbols for architecture i386: "_apr_atomic_init", referenced from: _main in serf_response.o "_crc32", referenced from: _serf_deflate_read in libserf-0.a(deflate_buckets.o) _serf_deflate_read in libserf-0.a(deflate_buckets.o) "_apr_strtoi64", referenced from: _run_machine in libserf-0.a(response_buckets.o) _run_machine in libserf-0.a(response_buckets.o) _serf_dechunk_read in libserf-0.a(dechunk_buckets.o) "_apr_mmap_create", referenced from: _serf_bucket_file_create in libserf-0.a(file_buckets.o) "_apr_atomic_read32", referenced from: _main in serf_response.o _main in serf_response.o "_inflateEnd", referenced from: _serf_deflate_read in libserf-0.a(deflate_buckets.o) "_apr_allocator_free", referenced from: _serf_bucket_mem_free in libserf-0.a(allocator.o) _allocator_cleanup in libserf-0.a(allocator.o) "_apr_mmap_offset", referenced from: _serf_mmap_read in libserf-0.a(mmap_buckets.o) _serf_mmap_readline in libserf-0.a(mmap_buckets.o) "_apr_file_read", referenced from: _file_reader in libserf-0.a(file_buckets.o) "_inflate", referenced from: _serf_deflate_read in libserf-0.a(deflate_buckets.o) "_apr_pool_create_ex", referenced from: _main in serf_response.o "_apr_pstrmemdup", referenced from: _main in serf_response.o "_apr_initialize", referenced from: _main in serf_response.o "_apr_palloc", referenced from: _serf_bucket_allocator_create in libserf-0.a(allocator.o) "_apr_date_checkmask", referenced from: _run_machine in libserf-0.a(response_buckets.o) "_apr_pool_cleanup_register", referenced from: _serf_bucket_allocator_create in libserf-0.a(allocator.o) "_apr_file_name_get", referenced from: _serf_bucket_file_create in libserf-0.a(file_buckets.o) "_apr_allocator_alloc", referenced from: _serf_bucket_mem_alloc in libserf-0.a(allocator.o) _serf_bucket_mem_alloc in libserf-0.a(allocator.o) "_apr_terminate", referenced from: _apr_terminate$non_lazy_ptr in serf_response.o "_apr_pool_destroy", referenced from: _main in serf_response.o "_apr_atomic_dec32", referenced from: _main in serf_response.o "_inflateInit2_", referenced from: _serf_deflate_read in libserf-0.a(deflate_buckets.o) "_apr_atomic_inc32", referenced from: _main in serf_response.o "_apr_pool_allocator_get", referenced from: _serf_bucket_allocator_create in libserf-0.a(allocator.o) "_apr_stat", referenced from: _serf_bucket_file_create in libserf-0.a(file_buckets.o) "_apr_file_open", referenced from: _main in serf_response.o ld: symbol(s) not found for architecture i386 collect2: ld returned 1 exit status lipo: can't open input file: /var/tmp//cccdRPT1.out (No such file or directory) make: *** [test/serf_response] Error 1 make: *** Waiting for unfinished jobs.... ld: warning: in /opt/local/lib/libaprutil-1.dylib, file is not of required architecture ld: warning: in /opt/local/lib/db46/libdb-4.6.dylib, file is not of required architecture ld: warning: in /opt/local/lib/libexpat.dylib, file is not of required architecture ld: warning: in /opt/local/lib/libiconv.dylib, file is not of required architecture ld: warning: in /opt/local/lib/libapr-1.dylib, file is not of required architecture ld: warning: in /opt/local/lib/libz.dylib, file is not of required architecture ld: warning: in /opt/local/lib/libssl.dylib, file is not of required architecture ld: warning: in /opt/local/lib/libcrypto.dylib, file is not of required architecture Undefined symbols for architecture i386: "_apr_stat", referenced from: _serf_bucket_file_create in libserf-0.a(file_buckets.o) "_crc32", referenced from: _serf_deflate_read in libserf-0.a(deflate_buckets.o) _serf_deflate_read in libserf-0.a(deflate_buckets.o) "_PKCS12_free", referenced from: _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_X509_digest", referenced from: _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) "_SSL_CTX_ctrl", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_SSL_CTX_set_client_cert_cb", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_apr_strtoi64", referenced from: _main in serf_get.o _run_machine in libserf-0.a(response_buckets.o) _run_machine in libserf-0.a(response_buckets.o) _serf_dechunk_read in libserf-0.a(dechunk_buckets.o) "_apr_getopt_init", referenced from: _main in serf_get.o "_apr_file_write", referenced from: _bio_file_write in libserf-0.a(ssl_buckets.o) "_CRYPTO_set_dynlock_create_callback", referenced from: _cleanup_ssl in libserf-0.a(ssl_buckets.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_apr_uri_unparse", referenced from: _serf_connection_create2 in libserf-0.a(context.o) "_apr_snprintf", referenced from: _create_chunk in libserf-0.a(chunk_buckets.o) "_X509_cmp_current_time", referenced from: _validate_server_certificate in libserf-0.a(ssl_buckets.o) _validate_server_certificate in libserf-0.a(ssl_buckets.o) "_apr_atomic_inc32", referenced from: _setup_request in serf_get.o "_apr_thread_mutex_destroy", referenced from: _ssl_dyn_destroy in libserf-0.a(ssl_buckets.o) "_ERR_clear_error", referenced from: _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_SSL_library_init", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_apr_pool_cleanup_register", referenced from: _serf_context_prerun in libserf-0.a(context.o) _serf_event_trigger in libserf-0.a(context.o) _serf_connection_create in libserf-0.a(context.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) _serf_bucket_allocator_create in libserf-0.a(allocator.o) "_BIO_read", referenced from: _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) "_BIO_test_flags", referenced from: _ssl_encrypt in libserf-0.a(ssl_buckets.o) _ssl_encrypt in libserf-0.a(ssl_buckets.o) "_apr_pool_clear", referenced from: _serf_context_prerun in libserf-0.a(context.o) _serf_event_trigger in libserf-0.a(context.o) _serf_event_trigger in libserf-0.a(context.o) "_BIO_free", referenced from: _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) "_apr_socket_timeout_set", referenced from: _serf_context_prerun in libserf-0.a(context.o) "_apr_atomic_dec32", referenced from: _handle_response in serf_get.o "_apr_getopt", referenced from: _main in serf_get.o "_apr_socket_recv", referenced from: _socket_reader in libserf-0.a(socket_buckets.o) "_ERR_load_crypto_strings", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_inflate", referenced from: _serf_deflate_read in libserf-0.a(deflate_buckets.o) "_apr_file_read", referenced from: _file_reader in libserf-0.a(file_buckets.o) _bio_file_read in libserf-0.a(ssl_buckets.o) "_apr_socket_sendv", referenced from: _socket_writev in libserf-0.a(context.o) "_EVP_sha1", referenced from: _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) "_X509_STORE_set_default_paths", referenced from: _serf_ssl_use_default_certificates in libserf-0.a(ssl_buckets.o) "_apr_palloc", referenced from: _main in serf_get.o _serf_context_create_ex in libserf-0.a(context.o) _serf_context_create_ex in libserf-0.a(context.o) _serf_connection_create in libserf-0.a(context.o) _serf_ssl_cert_export in libserf-0.a(ssl_buckets.o) _serf_ssl_cert_export in libserf-0.a(ssl_buckets.o) _ssl_dyn_create in libserf-0.a(ssl_buckets.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) _validate_server_certificate in libserf-0.a(ssl_buckets.o) _serf_ssl_load_cert_file in libserf-0.a(ssl_buckets.o) _serf_bucket_allocator_create in libserf-0.a(allocator.o) "_BIO_s_mem", referenced from: _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) "_SSL_get_ex_data_X509_STORE_CTX_idx", referenced from: _validate_server_certificate in libserf-0.a(ssl_buckets.o) "_apr_pstrdup", referenced from: _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_X509_get_issuer_name", referenced from: _serf_ssl_cert_issuer in libserf-0.a(ssl_buckets.o) "_apr_pool_destroy", referenced from: _main in serf_get.o _cancel_request in libserf-0.a(context.o) _serf_event_trigger in libserf-0.a(context.o) _serf_event_trigger in libserf-0.a(context.o) _serf_event_trigger in libserf-0.a(context.o) _serf_ssl_destroy_and_data in libserf-0.a(ssl_buckets.o) _validate_server_certificate in libserf-0.a(ssl_buckets.o) "_apr_atomic_xchg32", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_apr_pollset_poll", referenced from: _serf_context_run in libserf-0.a(context.o) "_apr_pool_allocator_get", referenced from: _serf_bucket_allocator_create in libserf-0.a(allocator.o) "_SSL_get_error", referenced from: _ssl_decrypt in libserf-0.a(ssl_buckets.o) _ssl_encrypt in libserf-0.a(ssl_buckets.o) "_apr_mmap_create", referenced from: _serf_bucket_file_create in libserf-0.a(file_buckets.o) "_apr_pool_create_ex", referenced from: _main in serf_get.o _serf_event_trigger in libserf-0.a(context.o) _serf_event_trigger in libserf-0.a(context.o) _serf_connection_create in libserf-0.a(context.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) _validate_server_certificate in libserf-0.a(ssl_buckets.o) "_X509_STORE_CTX_get_error_depth", referenced from: _validate_server_certificate in libserf-0.a(ssl_buckets.o) "_SSL_set_bio", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_SSL_new", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_CRYPTO_set_id_callback", referenced from: _cleanup_ssl in libserf-0.a(ssl_buckets.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_inflateEnd", referenced from: _serf_deflate_read in libserf-0.a(deflate_buckets.o) "_apr_file_close", referenced from: _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_X509_STORE_CTX_get_ex_data", referenced from: _validate_server_certificate in libserf-0.a(ssl_buckets.o) "_apr_terminate", referenced from: _apr_terminate$non_lazy_ptr in serf_get.o "_i2d_X509", referenced from: _serf_ssl_cert_export in libserf-0.a(ssl_buckets.o) _serf_ssl_cert_export in libserf-0.a(ssl_buckets.o) "_apr_strerror", referenced from: _main in serf_get.o "_apr_hash_make", referenced from: _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) "_CRYPTO_set_mem_functions", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_apr_socket_create", referenced from: _serf_context_prerun in libserf-0.a(context.o) "_X509_STORE_CTX_get_error", referenced from: _validate_server_certificate in libserf-0.a(ssl_buckets.o) "_apr_uri_port_of_scheme", referenced from: _main in serf_get.o "_apr_atomic_init", referenced from: _main in serf_get.o "_apr_sockaddr_info_get", referenced from: _main in serf_get.o _serf_connection_create2 in libserf-0.a(context.o) "_apr_pollset_add", referenced from: _pollset_add in libserf-0.a(context.o) "_SSL_CTX_new", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_apr_thread_mutex_create", referenced from: _ssl_dyn_create in libserf-0.a(ssl_buckets.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_apr_date_checkmask", referenced from: _run_machine in libserf-0.a(response_buckets.o) "_X509_get_subject_name", referenced from: _serf_ssl_cert_subject in libserf-0.a(ssl_buckets.o) "_SSL_write", referenced from: _ssl_encrypt in libserf-0.a(ssl_buckets.o) "_apr_pool_cleanup_null", referenced from: _apr_pool_cleanup_null$non_lazy_ptr in libserf-0.a(ssl_buckets.o) "_apr_pool_userdata_get", referenced from: _serf_ssl_client_cert_password_set in libserf-0.a(ssl_buckets.o) _serf_ssl_client_cert_provider_set in libserf-0.a(ssl_buckets.o) "_X509_STORE_CTX_get_current_cert", referenced from: _validate_server_certificate in libserf-0.a(ssl_buckets.o) "_apr_uri_parse", referenced from: _main in serf_get.o "_CRYPTO_num_locks", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_SSL_CTX_set_verify", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_SSL_get_ex_data", referenced from: _validate_server_certificate in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_SSL_load_error_strings", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_apr_thread_mutex_unlock", referenced from: _ssl_lock in libserf-0.a(ssl_buckets.o) _ssl_dyn_lock in libserf-0.a(ssl_buckets.o) "_apr_os_thread_current", referenced from: _ssl_id in libserf-0.a(ssl_buckets.o) "_apr_array_make", referenced from: _serf_context_create_ex in libserf-0.a(context.o) "_BIO_clear_flags", referenced from: _bio_bucket_write in libserf-0.a(ssl_buckets.o) _bio_file_read in libserf-0.a(ssl_buckets.o) _bio_file_write in libserf-0.a(ssl_buckets.o) _bio_bucket_read in libserf-0.a(ssl_buckets.o) "_OPENSSL_add_all_algorithms_noconf", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_ERR_get_error", referenced from: _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_SSL_CTX_free", referenced from: _serf_ssl_destroy_and_data in libserf-0.a(ssl_buckets.o) "_apr_pollset_create", referenced from: _serf_context_create_ex in libserf-0.a(context.o) "_apr_hash_set", referenced from: _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) "_apr_socket_opt_set", referenced from: _serf_context_prerun in libserf-0.a(context.o) "_X509_NAME_get_text_by_NID", referenced from: _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) _convert_X509_NAME_to_table in libserf-0.a(ssl_buckets.o) "_apr_initialize", referenced from: _main in serf_get.o "_apr_allocator_alloc", referenced from: _serf_bucket_mem_alloc in libserf-0.a(allocator.o) _serf_bucket_mem_alloc in libserf-0.a(allocator.o) "_apr_mmap_offset", referenced from: _serf_mmap_read in libserf-0.a(mmap_buckets.o) _serf_mmap_readline in libserf-0.a(mmap_buckets.o) "_ASN1_TIME_print", referenced from: _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) "_apr_thread_mutex_lock", referenced from: _ssl_lock in libserf-0.a(ssl_buckets.o) _ssl_dyn_lock in libserf-0.a(ssl_buckets.o) "_apr_allocator_free", referenced from: _serf_bucket_mem_free in libserf-0.a(allocator.o) _allocator_cleanup in libserf-0.a(allocator.o) "_apr_file_name_get", referenced from: _serf_bucket_file_create in libserf-0.a(file_buckets.o) "_apr_pollset_remove", referenced from: _pollset_rm in libserf-0.a(context.o) "_inflateInit2_", referenced from: _serf_deflate_read in libserf-0.a(deflate_buckets.o) "_PEM_read_X509", referenced from: _serf_ssl_load_cert_file in libserf-0.a(ssl_buckets.o) "_SSL_set_connect_state", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_apr_pstrcatv", referenced from: _serialize_data in libserf-0.a(request_buckets.o) "_SSL_set_ex_data", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_apr_atomic_read32", referenced from: _main in serf_get.o "_BIO_set_flags", referenced from: _bio_file_read in libserf-0.a(ssl_buckets.o) _bio_bucket_read in libserf-0.a(ssl_buckets.o) "_X509_STORE_add_cert", referenced from: _serf_ssl_trust_cert in libserf-0.a(ssl_buckets.o) "_d2i_PKCS12_bio", referenced from: _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_SSL_read", referenced from: _ssl_decrypt in libserf-0.a(ssl_buckets.o) _ssl_decrypt in libserf-0.a(ssl_buckets.o) "_apr_base64_encode", referenced from: _main in serf_get.o _serf_ssl_cert_export in libserf-0.a(ssl_buckets.o) "_apr_pstrcat", referenced from: _serf_bucket_request_set_root in libserf-0.a(request_buckets.o) "_SSL_CTX_get_cert_store", referenced from: _serf_ssl_trust_cert in libserf-0.a(ssl_buckets.o) _serf_ssl_use_default_certificates in libserf-0.a(ssl_buckets.o) "_SSL_free", referenced from: _serf_ssl_destroy_and_data in libserf-0.a(ssl_buckets.o) "_apr_socket_connect", referenced from: _serf_context_prerun in libserf-0.a(context.o) "_apr_base64_encode_len", referenced from: _main in serf_get.o _serf_ssl_cert_export in libserf-0.a(ssl_buckets.o) "_CRYPTO_set_dynlock_lock_callback", referenced from: _cleanup_ssl in libserf-0.a(ssl_buckets.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_CRYPTO_set_dynlock_destroy_callback", referenced from: _cleanup_ssl in libserf-0.a(ssl_buckets.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_apr_socket_close", referenced from: _reset_connection in libserf-0.a(context.o) _clean_skt in libserf-0.a(context.o) _serf_connection_close in libserf-0.a(context.o) "_CRYPTO_set_locking_callback", referenced from: _cleanup_ssl in libserf-0.a(ssl_buckets.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_SSLv23_client_method", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_BIO_new", referenced from: _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_PKCS12_parse", referenced from: _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_apr_array_push", referenced from: _serf_connection_create in libserf-0.a(context.o) "_apr_pool_userdata_setn", referenced from: _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_apr_file_open", referenced from: _setup_request in serf_get.o _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) ld: symbol(s) not found for architecture i386 collect2: ld returned 1 exit status lipo: can't open input file: /var/tmp//ccLeFhxC.out (No such file or directory) make: *** [test/serf_get] Error 1 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_serf/work/serf-0.3.0" && /usr/bin/make -j2 all " returned error 2 Command output: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_apr_socket_close", referenced from: _reset_connection in libserf-0.a(context.o) _clean_skt in libserf-0.a(context.o) _serf_connection_close in libserf-0.a(context.o) "_CRYPTO_set_locking_callback", referenced from: _cleanup_ssl in libserf-0.a(ssl_buckets.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_SSLv23_client_method", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_BIO_new", referenced from: _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_PKCS12_parse", referenced from: _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_apr_array_push", referenced from: _serf_connection_create in libserf-0.a(context.o) "_apr_pool_userdata_setn", referenced from: _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_apr_file_open", referenced from: _setup_request in serf_get.o _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) ld: symbol(s) not found for architecture i386 collect2: ld returned 1 exit status lipo: can't open input file: /var/tmp//ccLeFhxC.out (No such file or directory) make: *** [test/serf_get] Error 1 DEBUG: Backtrace: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_serf/work/serf-0.3.0" && /usr/bin/make -j2 all " returned error 2 Command output: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_apr_socket_close", referenced from: _reset_connection in libserf-0.a(context.o) _clean_skt in libserf-0.a(context.o) _serf_connection_close in libserf-0.a(context.o) "_CRYPTO_set_locking_callback", referenced from: _cleanup_ssl in libserf-0.a(ssl_buckets.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_SSLv23_client_method", referenced from: _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) "_BIO_new", referenced from: _serf_ssl_cert_certificate in libserf-0.a(ssl_buckets.o) _serf_bucket_ssl_create in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_PKCS12_parse", referenced from: _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_apr_array_push", referenced from: _serf_connection_create in libserf-0.a(context.o) "_apr_pool_userdata_setn", referenced from: _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) "_apr_file_open", referenced from: _setup_request in serf_get.o _ssl_need_client_cert in libserf-0.a(ssl_buckets.o) ld: symbol(s) not found for architecture i386 collect2: ld returned 1 exit status lipo: can't open input file: /var/tmp//ccLeFhxC.out (No such file or directory) make: *** [test/serf_get] Error 1 while executing "command_exec build" (procedure "portbuild::build_main" line 9) invoked from within "$procedure $targetname" Warning: the following items did not execute (for serf): org.macports.activate org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing. david-cakes-macbook-pro-2:~ dave$ From ryandesign at macports.org Sun Oct 18 10:13:59 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 18 Oct 2009 12:13:59 -0500 Subject: serf on SL In-Reply-To: References: Message-ID: <9ABDE209-872E-4BDA-A1F5-086DC93E309C@macports.org> On Oct 18, 2009, at 07:20, David Cake wrote: > Serf won't build for me, which is annoying because I really need > subversion. > > One thing confuses me about the error (reproduced below) > - it is complaining about 0386 architecture, but I am building for > Snow Leopard, so shouldn't it be trying to build everything x86_64? Yes, it should. I'm unable to explain why it's not. It works fine for me. > I did previously have many things built as universal, but there > seemed to be no point, so changed my default variants setting in > variants.conf, clean all installed, removed all installed, and start > building again - so why does it still appear to be trying to build > i386 or universal versions, and how can I make it stop? You should provide more of the output. Clean serf and try again with the debug output, and show is all of it. Hopefully that will show what's wrong. sudo port clean serf sudo port -d install serf From peter at softwolves.pp.se Sun Oct 18 12:31:14 2009 From: peter at softwolves.pp.se (Peter Krefting) Date: Sun, 18 Oct 2009 20:31:14 +0100 (CET) Subject: MacPorts privoxy and autostart on Snow Leopard In-Reply-To: <2B29EFF2-0120-4AAE-9B69-057E69E89057@Clauzel.nom.fr> References: <2B29EFF2-0120-4AAE-9B69-057E69E89057@Clauzel.nom.fr> Message-ID: Hi! > I am using this plist for launchd. > > It lives in /Library/LaunchDaemons/fr.nom.Clauzel.privoxy.plist and starts > automatically privoxy on startup. I found that MacPorts has installed an org.macports.Privoxy.plist in that directory (symlinked to a file under /opt/local/), but it still doesn't start automatically. Is there something I need to to in the GUI to enable it? -- \\// Peter - http://www.softwolves.pp.se/ From Damien at Clauzel.nom.fr Sun Oct 18 12:59:39 2009 From: Damien at Clauzel.nom.fr (Damien Clauzel) Date: Sun, 18 Oct 2009 21:59:39 +0200 Subject: MacPorts privoxy and autostart on Snow Leopard In-Reply-To: References: <2B29EFF2-0120-4AAE-9B69-057E69E89057@Clauzel.nom.fr> Message-ID: Le 18 oct. 2009 ? 21:31, Peter Krefting a ?crit : >> I am using this plist for launchd. >> >> It lives in /Library/LaunchDaemons/fr.nom.Clauzel.privoxy.plist and >> starts automatically privoxy on startup. > > I found that MacPorts has installed an org.macports.Privoxy.plist in > that directory (symlinked to a file under /opt/local/), but it still > doesn't start automatically. Is there something I need to to in the > GUI to enable it? No idea for the default plist. With the given plist, simply run this command : ___ sudo launchctl load -w /Library/LaunchDaemons/ fr.nom.Clauzel.privoxy.plist ___ It will load the plist, start privoxy, and modify the plist in order to have it loaded at boot time. Good luck, Damien Clauzel From k.fomin at gmail.com Sun Oct 18 13:08:52 2009 From: k.fomin at gmail.com (Konstantin Fomin) Date: Sun, 18 Oct 2009 22:08:52 +0200 Subject: trafshow on Snow Leopard Message-ID: <64ee80170910181308ga875202pfc79a6a6bcc77e8c@mail.gmail.com> Hello, all, I have a problem running the trafshow on MBP5.5 Mac OS 10.6.1. Installed from the latest macports. After the startup it does not show packets on the interface. Sometimes, rarely tcp flows appear for a couple of seconds and then again blank screen as there is no traffic. Any suggestion how to solve it? -- Sincerely yours, Konstantin. From ryandesign at macports.org Sun Oct 18 17:10:03 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 18 Oct 2009 19:10:03 -0500 Subject: Building MacPorts on a Linux system In-Reply-To: <5B917DAB-4023-419B-8227-1A6A17D2BFC2@macports.org> References: <821E0F76-FCB0-4FB0-926D-EE0148E07A01@sentex.net> <5B917DAB-4023-419B-8227-1A6A17D2BFC2@macports.org> Message-ID: <8F27F734-D0D1-474C-AF28-9F8222B0AE3C@macports.org> On Aug 20, 2009, at 00:38, Ryan Schmidt wrote: >> On Aug 19, 2009, at 23:17, Sumner Trammell wrote: >> >>> checking objc/objc.h usability... no >>> checking objc/objc.h presence... no >>> checking for objc/objc.h... no >>> configure: error: Can't locate Objective C runtime headers As it happens, I want to install MacPorts on Linux today. I encountered the above error, and got by it with "--without-objc- runtime --without-objc-foundation", as mentioned previously in this thread. But then I ran into this: checking for Tcl configuration... configure: error: Can't find Tcl configuration definitions I believe this is looking for tclConfig.sh, but I can find no such file on the system I'm using (though some kind of tcl must be there because tclsh exists and seems to work). Is this system's tcl hopelessly inadequate or is there a way around this? From jmr at macports.org Sun Oct 18 17:24:35 2009 From: jmr at macports.org (Joshua Root) Date: Mon, 19 Oct 2009 11:24:35 +1100 Subject: Building MacPorts on a Linux system In-Reply-To: <8F27F734-D0D1-474C-AF28-9F8222B0AE3C@macports.org> References: <821E0F76-FCB0-4FB0-926D-EE0148E07A01@sentex.net> <5B917DAB-4023-419B-8227-1A6A17D2BFC2@macports.org> <8F27F734-D0D1-474C-AF28-9F8222B0AE3C@macports.org> Message-ID: <4ADBB1C3.6040101@macports.org> On 2009-10-19 11:10, Ryan Schmidt wrote: > > On Aug 20, 2009, at 00:38, Ryan Schmidt wrote: > >>> On Aug 19, 2009, at 23:17, Sumner Trammell wrote: >>> >>>> checking objc/objc.h usability... no >>>> checking objc/objc.h presence... no >>>> checking for objc/objc.h... no >>>> configure: error: Can't locate Objective C runtime headers > > > As it happens, I want to install MacPorts on Linux today. I encountered > the above error, and got by it with "--without-objc-runtime > --without-objc-foundation", as mentioned previously in this thread. But > then I ran into this: > > > checking for Tcl configuration... configure: error: Can't find Tcl > configuration definitions > > > I believe this is looking for tclConfig.sh, but I can find no such file > on the system I'm using (though some kind of tcl must be there because > tclsh exists and seems to work). Is this system's tcl hopelessly > inadequate or is there a way around this? Probably need to install a tcl-dev package? - Josh From afalquina at mac.com Mon Oct 19 02:48:04 2009 From: afalquina at mac.com (=?iso-8859-1?Q?=C1lvaro_Falquina_Garrido?=) Date: Mon, 19 Oct 2009 11:48:04 +0200 Subject: gdc-0.24 problems on Snow Leopard Message-ID: <9495A069-D105-4362-A25C-E4C2AC3B8DB6@mac.com> Hello, This is my first post to the list. First of all I would like to congratulate everybody for this very nice piece of software. Unfortunately, I am experiencing some problems... I have recently installed Snow Leopard and I am now trying to install gdc. When I execute: $ sudo port -v install gdc the command fails: /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc /work/build/./gcc/xgcc -B/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc /work/build/./gcc/ -B/opt/local/i386-apple-darwin10.0.0/bin/ -B/opt/ local/i386-apple-darwin10.0.0/lib/ -isystem /opt/local/i386-apple- darwin10.0.0/include -isystem /opt/local/i386-apple-darwin10.0.0/sys- include -O2 -O2 -arch x86_64 -DIN_GCC -W -Wall -Wwrite-strings - Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition - isystem ./include -I. -I. -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc /work/gcc-4.1.2/gcc -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc /work/gcc-4.1.2/gcc/. -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc /work/gcc-4.1.2/gcc/../include -I/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc /work/gcc-4.1.2/gcc/../libcpp/include \ -c /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc /work/gcc-4.1.2/gcc/config/darwin-crt2.c -o crt2.o cc1: error: unrecognized command line option "-arch" gnumake[2]: *** [crt2.o] Error 1 gnumake[1]: *** [all-gcc] Error 2 gnumake: *** [all] Error 2 Warning: the following items did not execute (for gdc): org.macports.activate org.macports.build org.macports.destroot org.macports.install I have been looking for a reference to this error in the archives, to no avail. Any hints? Is it OK to send a .gz file containing the whole output generated by port -v? This is some information about my system: $ sw_vers ProductName: Mac OS X ProductVersion: 10.6.1 BuildVersion: 10B504 $ uname -a Darwin MacBookPro.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31 22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386 i386 $ port version Version: 1.8.1 About XCode: Version 3.2 64-bit Component versions Xcode IDE: 1610.0 Xcode Core: 1608.0 ToolSupport: 1591.0 Thanks in advance for any help. Alvaro From klloyd at email.unc.edu Mon Oct 19 05:03:08 2009 From: klloyd at email.unc.edu (Karen Lloyd) Date: Mon, 19 Oct 2009 14:03:08 +0200 Subject: Trouble upgrading MacPorts in Snow Leopard Message-ID: Hi all, I just upgraded from Leopard (where MacPorts was working fine) to Snow Leopard. I tried to follow the instructions on http://trac.macports.org/wiki/Migration. But, after typing in the lines on that page (I am not anywhere close to being a developer, I just need to use MacPorts to download some scientific software), I couldn?t see that my myports.txt file had anything in it; it was blank. So, I just downloaded the .dmg for the new MacPorts version for Snow Leopard (I already upgraded my Xcode to 3.2.1) and it acted as if it installed correctly. Now when I try to install the scientific program (called ?arb?), I get the following error: ---> Extracting libpng Error: You cannot install libpng for the architecture(s) x86_64 Error: because /opt/local/lib/libz.dylib only contains the architecture(s) i386. Error: Did you upgrade to a new version of Mac OS X? If so, please see Error: http://trac.macports.org/wiki/Migration Error: Target org.macports.extract returned: incompatible architectures in dependencies Error: Unable to upgrade port: 1 Error: Unable to execute port: upgrade openmotif failed I have no idea what any of this means. I get the same message when I type When I did this on Leopard it worked fine. Is there any way I can just erase everything and start all over again as if I were starting out in Snow Leopard (not upgrading)? I also tried the following: biomunk162:~ Karen$ sudo port install macports ---> Computing dependencies for MacPorts ---> Fetching MacPorts ---> Attempting to fetch MacPorts-1.8.1.tar.bz2 from http://distfiles.macports.org/MacPorts ---> Verifying checksum(s) for MacPorts ---> Extracting MacPorts ---> Configuring MacPorts ---> Building MacPorts ---> Staging MacPorts into destroot Note: MacPorts installs files outside the common directory structure. ---> Installing MacPorts @1.8.1_0+darwin_10 ---> Activating MacPorts @1.8.1_0+darwin_10 Error: Target org.macports.activate returned: Image error: /Library/Tcl/macports1.0/MacPorts.dylib already exists and does not belong to a registered port. Unable to activate port MacPorts. Error: Status 1 encountered during processing. Thank you, Karen -- Karen G. Lloyd, Ph.D. Center for Geomicrobiology Aarhus University Ny Munkegade 114 DK-8000 Aarhus C Denmark Tel: +45 8942 3280 Fax: +45 8942 2722 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Mon Oct 19 10:03:35 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 19 Oct 2009 12:03:35 -0500 Subject: Trouble upgrading MacPorts in Snow Leopard In-Reply-To: References: Message-ID: On Oct 19, 2009, at 07:03, Karen Lloyd wrote: > I just upgraded from Leopard (where MacPorts was working fine) to > Snow Leopard. I tried to follow the instructions on http://trac.macports.org/wiki/Migration > . But, after typing in the lines on that page (I am not anywhere > close to being a developer, I just need to use MacPorts to download > some scientific software), I couldn?t see that my myports.txt file > had anything in it; it was blank. So, I just downloaded the .dmg > for the new MacPorts version for Snow Leopard (I already upgraded my > Xcode to 3.2.1) and it acted as if it installed correctly. Yes, MacPorts itself is now installed correctly for Snow Leopard. But all the ports you already have installed are still installed in a way that was correct for Leopard, but is incorrect for Snow Leopard. As explained in the "Reinstall Xcode and MacPorts" section of the Migration page, you need to reinstall MacPorts and Xcode. You've reinstalled MacPorts using the .dmg -- good. Have you also installed the latest Xcode? Version 3.2 should be on your Snow Leopard DVD, or you can download version 3.2.1 from Apple. After you do that, you can use the commands in the "Reinstall ports" section of the Migration page to reinstall your ports. From ryandesign at macports.org Mon Oct 19 10:05:27 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 19 Oct 2009 12:05:27 -0500 Subject: gdc-0.24 problems on Snow Leopard In-Reply-To: <9495A069-D105-4362-A25C-E4C2AC3B8DB6@mac.com> References: <9495A069-D105-4362-A25C-E4C2AC3B8DB6@mac.com> Message-ID: <64EDD17D-2EDC-45BA-8319-F2E13F12EFFE@macports.org> On Oct 19, 2009, at 04:48, ?lvaro Falquina Garrido wrote: > I have recently installed Snow Leopard and I am now trying to > install gdc. When I execute: > > $ sudo port -v install gdc > > the command fails: > > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc > /work/build/./gcc/xgcc -B/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc > /work/build/./gcc/ -B/opt/local/i386-apple-darwin10.0.0/bin/ -B/opt/ > local/i386-apple-darwin10.0.0/lib/ -isystem /opt/local/i386-apple- > darwin10.0.0/include -isystem /opt/local/i386-apple-darwin10.0.0/sys- > include -O2 -O2 -arch x86_64 -DIN_GCC -W -Wall -Wwrite-strings - > Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition - > isystem ./include -I. -I. -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc > /work/gcc-4.1.2/gcc -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc > /work/gcc-4.1.2/gcc/. -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc > /work/gcc-4.1.2/gcc/../include -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc > /work/gcc-4.1.2/gcc/../libcpp/include \ > -c /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc > /work/gcc-4.1.2/gcc/config/darwin-crt2.c -o crt2.o > cc1: error: unrecognized command line option "-arch" > gnumake[2]: *** [crt2.o] Error 1 > gnumake[1]: *** [all-gcc] Error 2 > gnumake: *** [all] Error 2 > Warning: the following items did not execute (for gdc): > org.macports.activate org.macports.build org.macports.destroot > org.macports.install > > I have been looking for a reference to this error in the archives, > to no avail. Any hints? Is it OK to send a .gz file containing the > whole output generated by port -v? The best thing to do would be to file a ticket in the issue tracker with this information. From yardcat at comcast.net Mon Oct 19 16:03:04 2009 From: yardcat at comcast.net (Arden) Date: Mon, 19 Oct 2009 16:03:04 -0700 Subject: installing gimp2 fails with mp4v2 on 10.4.11 Message-ID: <9B7E8FC9-62F0-4451-885B-0994B64CC89D@comcast.net> I have Xcode 2.5 on Tiger ran selfupdate, upgrade outdated, but can't get past building mp4v2. It fails with the following: ---> Building mp4v2 Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_multime dia_mp4v2/work/mp4v2-1.9.1" && /usr/bin/make -j1 all " returned error 2 Command output: /bin/sh ./libtool --tag=CXX --mode=link /usr/bin/g+ +-4.0 -Wall -Wformat -O2 -arch ppc -fvisibility=hidden -L/opt/local/ lib -o libmp4v2.la -rpath /opt/local/lib -version-number 1:9:1 -Wl,- current_version,1.9.1 -Wl,-compatibility_version,1.0.0 src/3gp.lo src/ atom_ac3.lo src/atom_amr.lo src/atom_avc1.lo src/atom_avcC.lo src/ atom_chpl.lo src/atom_colr.lo src/atom_d263.lo src/atom_dac3.lo src/ atom_damr.lo src/atom_dref.lo src/atom_elst.lo src/atom_enca.lo src/ atom_encv.lo src/atom_free.lo src/atom_ftyp.lo src/atom_ftab.lo src/ atom_gmin.lo src/atom_hdlr.lo src/atom_hinf.lo src/atom_hnti.lo src/ atom_href.lo src/atom_mdat.lo src/atom_mdhd.lo src/atom_meta.lo src/ atom_mp4s.lo src/atom_mp4v.lo src/atom_mvhd.lo src/atom_nmhd.lo src/ atom_ohdr.lo src/atom_pasp.lo src/atom_root.lo src/atom_rtp.lo src/ atom_s263.lo src/atom_sdp.lo src/atom_sdtp.lo src/atom_smi.lo src/ atom_sound.lo src/atom_standard.lo src/atom_stbl.lo src/atom_stdp.lo src/atom_stsc.lo src/atom_stsd.lo src/atom_stsz.lo src/atom_stz2.lo src/atom_text.lo src/atom_tfhd.lo src/atom_tkhd.lo src/ atom_treftype.lo src/atom_trun.lo src/atom_tx3g.lo src/atom_udta.lo src/atom_url.lo src/atom_urn.lo src/atom_uuid.lo src/atom_video.lo src/atom_vmhd.lo src/cmeta.lo src/descriptors.lo src/exception.lo src/ isma.lo src/mp4.lo src/mp4atom.lo src/mp4container.lo src/ mp4descriptor.lo src/mp4file.lo src/mp4file_io.lo src/mp4info.lo src/ mp4meta.lo src/mp4property.lo src/mp4track.lo src/mp4util.lo src/ ocidescriptors.lo src/odcommands.lo src/qosqualifiers.lo src/ rtphint.lo src/text.lo src/bmff/typebmff.lo src/itmf/CoverArtBox.lo src/itmf/Tags.lo src/itmf/generic.lo src/itmf/type.lo src/qtff/ ColorParameterBox.lo src/qtff/PictureAspectRatioBox.lo src/qtff/ coding.lo libplatform/io/File.lo libplatform/io/FileSystem.lo libplatform/prog/option.lo libplatform/sys/error.lo libplatform/time/ time.lo libplatform/io/File_posix.lo libplatform/io/ FileSystem_posix.lo libplatform/number/random_posix.lo libplatform/ process/process_posix.lo libplatform/time/time_posix.lo libutil/ Database.lo libutil/Timecode.lo libutil/TrackModifier.lo libutil/ Utility.lo libutil/crc.lo libutil/other.lo /usr/bin/g++-4.0 -dynamiclib ${wl}-undefined ${wl}dynamic_lookup - o .libs/libmp4v2.1.9.1.dylib src/.libs/3gp.o src/.libs/atom_ac3.o src/.libs/atom_amr.o src/.libs/atom_avc1.o src/.libs/atom_avcC.o src/.libs/atom_chpl.o src/.libs/atom_colr.o src/.libs/atom_d263.o src/.libs/atom_dac3.o src/.libs/atom_damr.o src/.libs/atom_dref.o src/.libs/atom_elst.o src/.libs/atom_enca.o src/.libs/atom_encv.o src/.libs/atom_free.o src/.libs/atom_ftyp.o src/.libs/atom_ftab.o src/.libs/atom_gmin.o src/.libs/atom_hdlr.o src/.libs/atom_hinf.o src/.libs/atom_hnti.o src/.libs/atom_href.o src/.libs/atom_mdat.o src/.libs/atom_mdhd.o src/.libs/atom_meta.o src/.libs/atom_mp4s.o src/.libs/atom_mp4v.o src/.libs/atom_mvhd.o src/.libs/atom_nmhd.o src/.libs/atom_ohdr.o src/.libs/atom_pasp.o src/.libs/atom_root.o src/.libs/atom_rtp.o src/.libs/atom_s263.o src/.libs/atom_sdp.o src/.libs/atom_sdtp.o src/.libs/atom_smi.o src/.libs/atom_sound.o src/.libs/atom_standard.o src/.libs/atom_stbl.o src/.libs/atom_stdp.o src/.libs/atom_stsc.o src/.libs/atom_stsd.o src/.libs/atom_stsz.o src/.libs/atom_stz2.o src/.libs/atom_text.o src/.libs/atom_tfhd.o src/.libs/atom_tkhd.o src/.libs/atom_treftype.o src/.libs/atom_trun.o src/.libs/atom_tx3g.o src/.libs/atom_udta.o src/.libs/atom_url.o src/.libs/atom_urn.o src/.libs/atom_uuid.o src/.libs/atom_video.o src/.libs/atom_vmhd.o src/.libs/cmeta.o src/.libs/descriptors.o src/.libs/exception.o src/.libs/isma.o src/.libs/mp4.o src/.libs/ mp4atom.o src/.libs/mp4container.o src/.libs/mp4descriptor.o src/.libs/mp4file.o src/.libs/mp4file_io.o src/.libs/mp4info.o src/.libs/mp4meta.o src/.libs/mp4property.o src/.libs/mp4track.o src/.libs/mp4util.o src/.libs/ocidescriptors.o src/.libs/odcommands.o src/.libs/qosqualifiers.o src/.libs/rtphint.o src/.libs/text.o src/ bmff/.libs/typebmff.o src/itmf/.libs/CoverArtBox.o src/itmf/.libs/ Tags.o src/itmf/.libs/generic.o src/itmf/.libs/type.o src/qtff/.libs/ ColorParameterBox.o src/qtff/.libs/PictureAspectRatioBox.o src/ qtff/.libs/coding.o libplatform/io/.libs/File.o libplatform/io/.libs/ FileSystem.o libplatform/prog/.libs/option.o libplatform/sys/.libs/ error.o libplatform/time/.libs/time.o libplatform/io/.libs/ File_posix.o libplatform/io/.libs/FileSystem_posix.o libplatform/ number/.libs/random_posix.o libplatform/process/.libs/process_posix.o libplatform/time/.libs/time_posix.o libutil/.libs/Database.o libutil/.libs/Timecode.o libutil/.libs/TrackModifier.o libutil/.libs/ Utility.o libutil/.libs/crc.o libutil/.libs/other.o -L/opt/local/ lib -arch ppc -Wl,-current_version -Wl,1.9.1 -Wl,- compatibility_version -Wl,1.0.0 -install_name /opt/local/lib/ libmp4v2.1.dylib -compatibility_version 11 -current_version 11.1 -Wl,- single_module /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool: more than one: - current_version option specified Usage: /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool -static [-] file [...] [-filelist listfile[,dirname]] [-arch_only arch] [-sacLT] Usage: /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool -dynamic [-] file [...] [-filelist listfile[,dirname]] [-arch_only arch] [-o output] [-install_name name] [-compatibility_version #] [- current_version #] [-seg1addr 0x#] [-segs_read_only_addr 0x#] [- segs_read_write_addr 0x#] [-seg_addr_table ] [- seg_addr_table_filename ] [-all_load] [-noall_load] make: *** [libmp4v2.la] Error 1 Error: The following dependencies failed to build: gimp2 gegl ffmpeg faac mp4v2 faad2 gmake lame libogg libsdl libtheora libvorbis schroedinger liboil x264 graphviz gd2 xpm urw-fonts xorg-libXaw xorg- libXmu libopenraw boost boost-jam libspiro lua libexif libgnomeui gnome-icon-theme hicolor-icon-theme icon-naming-utils p5-xml-simple p5-xml-namespacesupport p5-xml-sax gnome-keyring libgcrypt libgpg- error libtasn1 libbonoboui libglade2 libgnome esound audiofile libgnomecanvas libwmf poppler openjpeg poppler-data py25-gtk py25- cairo py25-numpy py25-nose py25-setuptools python25 py25-gobject Error: Status 1 encountered during processing. yardcatsmac-2:~ yardcat$ Any ideas? thanks, Arden From cssdev at mac.com Mon Oct 19 19:25:33 2009 From: cssdev at mac.com (cssdev at mac.com) Date: Mon, 19 Oct 2009 22:25:33 -0400 Subject: unison 2.32 declared stable In-Reply-To: <20091016133415.GB5131@marco.fz-rossendorf.de> References: <20091016133415.GB5131@marco.fz-rossendorf.de> Message-ID: On Oct 16, 2009, at 9:34 AM, Joerg van den Hoff wrote: > unison 2.32 has been finally declared stable a few weeks ago. any > chance > to see this version soon in macports? It looks like it takes some patching to get 2.32 to work properly on Snow Leopard. See http://trac.macports.org/ticket/21862 Chris From ryandesign at macports.org Mon Oct 19 21:27:12 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 19 Oct 2009 23:27:12 -0500 Subject: installing gimp2 fails with mp4v2 on 10.4.11 In-Reply-To: <9B7E8FC9-62F0-4451-885B-0994B64CC89D@comcast.net> References: <9B7E8FC9-62F0-4451-885B-0994B64CC89D@comcast.net> Message-ID: <6D75D8D4-830B-4460-8734-0EBC787AFC8F@macports.org> On Oct 19, 2009, at 18:03, Arden wrote: > I have Xcode 2.5 on Tiger ran selfupdate, upgrade outdated, but > can't get past building mp4v2. It fails with the following: > /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool: more than one: > -current_version option specified > Any ideas? thanks, Arden As for any bug in any port, you would file a ticket in the issue tracker. In this case, one has already been filed: http://trac.macports.org/ticket/21007 There is a patch attached to the ticket that allegedly fixes the problem. From gdimatteo at voo.be Tue Oct 20 00:10:37 2009 From: gdimatteo at voo.be (Giuseppe Di Matteo) Date: Tue, 20 Oct 2009 09:10:37 +0200 Subject: Unable to upgrade xorg-libX11 Message-ID: <96246DD1-C0C5-4252-8C91-9452112EC9BB@voo.be> Hello, My system: iMac G4; OS X 10.4.11; XCode 2.5; MacPorts 1.8.1 The problem when upgrading xorg-libX11(it seems that a pkgIndex file is missing somewhere): Making all in specs Making all in libX11 GEN libX11.txt make[2]: *** [libX11.txt] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libX11/work/libX11-1.3.1" && /usr/bin/make -j1 all " returned error 2 Command output: GEN XcmsQueryColors.3 GEN XcmsLookupColor.3 GEN XcmsStoreColors.3 GEN XcmsSetWhiteAdjustProc.3 GEN XcmsTekHVCQueryMaxV.3 GEN XcmsTekHVCQueryMaxVC.3 GEN XcmsTekHVCQueryMaxVSamples.3 GEN XcmsTekHVCQueryMinV.3 GEN XwcDrawImageString.3 GEN Xutf8DrawImageString.3 GEN XwcDrawString.3 GEN Xutf8DrawString.3 GEN XwcDrawText.3 GEN Xutf8DrawText.3 GEN XwcLookupString.3 GEN Xutf8LookupString.3 GEN XwcResetIC.3 GEN Xutf8ResetIC.3 GEN XwcTextEscapement.3 GEN Xutf8TextEscapement.3 GEN XwcTextExtents.3 GEN Xutf8TextExtents.3 GEN XwcTextPerCharExtents.3 GEN Xutf8TextPerCharExtents.3 Making all in specs Making all in libX11 GEN libX11.txt make[2]: *** [libX11.txt] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 DEBUG: Backtrace: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libX11/work/libX11-1.3.1" && /usr/bin/make -j1 all " returned error 2 Command output: GEN XcmsQueryColors.3 GEN XcmsLookupColor.3 GEN XcmsStoreColors.3 GEN XcmsSetWhiteAdjustProc.3 GEN XcmsTekHVCQueryMaxV.3 GEN XcmsTekHVCQueryMaxVC.3 GEN XcmsTekHVCQueryMaxVSamples.3 GEN XcmsTekHVCQueryMinV.3 GEN XwcDrawImageString.3 GEN Xutf8DrawImageString.3 GEN XwcDrawString.3 GEN Xutf8DrawString.3 GEN XwcDrawText.3 GEN Xutf8DrawText.3 GEN XwcLookupString.3 GEN Xutf8LookupString.3 GEN XwcResetIC.3 GEN Xutf8ResetIC.3 GEN XwcTextEscapement.3 GEN Xutf8TextEscapement.3 GEN XwcTextExtents.3 GEN Xutf8TextExtents.3 GEN XwcTextPerCharExtents.3 GEN Xutf8TextPerCharExtents.3 Making all in specs Making all in libX11 GEN libX11.txt make[2]: *** [libX11.txt] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 while executing "command_exec build" (procedure "portbuild::build_main" line 9) invoked from within "$procedure $targetname" Warning: the following items did not execute (for xorg-libX11): org.macports.destroot org.macports.build DEBUG: couldn't read file "/opt/local/share/macports/Tcl/ darwintrace1.0/pkgIndex.tcl": no such file or directory while executing "source [file join $dir pkgIndex.tcl]" Error: Unable to upgrade port: 1 Giuseppe Di Matteo gdimatteo at voo.be gdimatt at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Tue Oct 20 00:36:31 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 20 Oct 2009 02:36:31 -0500 Subject: Unable to upgrade xorg-libX11 In-Reply-To: <96246DD1-C0C5-4252-8C91-9452112EC9BB@voo.be> References: <96246DD1-C0C5-4252-8C91-9452112EC9BB@voo.be> Message-ID: <0957F0DB-385E-4EC8-BD5D-237E2FFDF39D@macports.org> On Oct 20, 2009, at 02:10, Giuseppe Di Matteo wrote: > My system: iMac G4; OS X 10.4.11; XCode 2.5; MacPorts 1.8.1 > The problem when upgrading xorg-libX11(it seems that a pkgIndex file > is missing somewhere): No, the message about a pkgIndex file is not relevant, and I think the relevant error message is not shown at all because it is more than 30 lines up. Please clean and try again with the debug flag and post the whole output. Since this may be large, compress it first. You may also wish to file this as a ticket in the issue tracker instead of posting it to the mailing list. sudo port clean xorg-libX11 sudo port -d install xorg-libX11 From j.van_den_hoff at fzd.de Tue Oct 20 01:20:47 2009 From: j.van_den_hoff at fzd.de (joerg van den hoff) Date: Tue, 20 Oct 2009 10:20:47 +0200 Subject: unison 2.32 declared stable In-Reply-To: References: <20091016133415.GB5131@marco.fz-rossendorf.de> Message-ID: On Tue, 20 Oct 2009 04:25:33 +0200, wrote: > On Oct 16, 2009, at 9:34 AM, Joerg van den Hoff wrote: > >> unison 2.32 has been finally declared stable a few weeks ago. any chance >> to see this version soon in macports? > > It looks like it takes some patching to get 2.32 to work properly on > Snow Leopard. See http://trac.macports.org/ticket/21862 thanks for responding. but the ticket seems to say that it refers to a problem with 2.27 on snow leopard which could be fixed by moving to 2.32? the problem being related to the aqua interface? well, I would be happy with a command line only anyway (and for the time being for 10.4.11...) regards, joerg From afalquina at mac.com Tue Oct 20 02:22:54 2009 From: afalquina at mac.com (=?iso-8859-1?Q?=C1lvaro_Falquina_Garrido?=) Date: Tue, 20 Oct 2009 11:22:54 +0200 Subject: gdc-0.24 problems on Snow Leopard In-Reply-To: <64EDD17D-2EDC-45BA-8319-F2E13F12EFFE@macports.org> References: <9495A069-D105-4362-A25C-E4C2AC3B8DB6@mac.com> <64EDD17D-2EDC-45BA-8319-F2E13F12EFFE@macports.org> Message-ID: <1A10D1D8-0CF6-454C-ADB3-F5D0707271BA@mac.com> On 19-10-2009, at 7.05 pm, Ryan Schmidt wrote: > On Oct 19, 2009, at 04:48, ?lvaro Falquina Garrido wrote: > >> I have recently installed Snow Leopard and I am now trying to >> install gdc. When I execute: >> >> $ sudo port -v install gdc >> >> the command fails: >> >> /opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc >> /work/build/./gcc/xgcc -B/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc >> /work/build/./gcc/ -B/opt/local/i386-apple-darwin10.0.0/bin/ -B/opt/ >> local/i386-apple-darwin10.0.0/lib/ -isystem /opt/local/i386-apple- >> darwin10.0.0/include -isystem /opt/local/i386-apple-darwin10.0.0/ >> sys-include -O2 -O2 -arch x86_64 -DIN_GCC -W -Wall -Wwrite- >> strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style- >> definition -isystem ./include -I. -I. -I/opt/local/var/macports/ >> build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc >> /work/gcc-4.1.2/gcc -I/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc >> /work/gcc-4.1.2/gcc/. -I/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc >> /work/gcc-4.1.2/gcc/../include -I/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc >> /work/gcc-4.1.2/gcc/../libcpp/include \ >> -c /opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gdc >> /work/gcc-4.1.2/gcc/config/darwin-crt2.c -o crt2.o >> cc1: error: unrecognized command line option "-arch" >> gnumake[2]: *** [crt2.o] Error 1 >> gnumake[1]: *** [all-gcc] Error 2 >> gnumake: *** [all] Error 2 >> Warning: the following items did not execute (for gdc): >> org.macports.activate org.macports.build org.macports.destroot >> org.macports.install >> >> I have been looking for a reference to this error in the archives, >> to no avail. Any hints? Is it OK to send a .gz file containing the >> whole output generated by port -v? > > The best thing to do would be to file a ticket in the issue tracker > with this information. I have done exactly that. Thanks a lot for your help. From yardcat at comcast.net Tue Oct 20 18:44:08 2009 From: yardcat at comcast.net (Arden) Date: Tue, 20 Oct 2009 18:44:08 -0700 Subject: make libXaw fails Message-ID: I have Xcode 2.5 on Tiger , build of libXaw fails. How should I know if this is a bug or not? and why should I learn how to report it? Arden ---> Building xorg-libXaw Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libXaw/work/libXaw-1.0.7" && /usr/bin/make -j1 all " returned error 2 Command output: CC libXaw7_la-TextAction.lo CC libXaw7_la-TextPop.lo TextPop.c: In function 'CreateDialog': TextPop.c:1436: warning: cast from function call of type 'Widget' to non-matching type 'long int' CC libXaw7_la-TextTr.lo CC libXaw7_la-Toggle.lo CC libXaw7_la-Tree.lo CC libXaw7_la-Vendor.lo CC libXaw7_la-Viewport.lo CC libXaw7_la-XawIm.lo CC libXaw7_la-XawInit.lo CC libXaw7_la-XawI18n.lo CC libXaw7_la-Tip.lo CCLD libXaw7.la ld: warning multiple definitions of symbol _vendorShellWidgetClass .libs/libXaw7_la-Vendor.o definition of _vendorShellWidgetClass in section (__DATA,__data) /opt/local/lib/libXt.dylib(single module) definition of _vendorShellWidgetClass ld: warning multiple definitions of symbol _vendorShellClassRec .libs/libXaw7_la-Vendor.o definition of _vendorShellClassRec in section (__DATA,__data) /opt/local/lib/libXt.dylib(single module) definition of _vendorShellClassRec warning: no debug map in executable (-arch ppc) Making all in man GEN Xaw.3 Making all in spec GEN widgets.ps make[2]: [widgets.ps] Error 1 (ignored) tbl:./Template:427:fatal error: output error make[2]: *** [widgets.ps] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 From jasperfrumau at gmail.com Tue Oct 20 21:41:29 2009 From: jasperfrumau at gmail.com (Jasper Frumau) Date: Wed, 21 Oct 2009 11:41:29 +0700 Subject: Gedit and Gnome X11 Gconf Error Message-ID: <56cc1b0a0910202141i1a093f3clf08d567ffebb9737@mail.gmail.com> I just installed Gedit after installing all the necessary packages on my brand new Mac Book Pro. When I enter gedit from the command line it prints a whole bunch of errors and then launches Gedit. Here are the errors: GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) I did some research and found someone with a similar problem @ http://www.nabble.com/Meld-fails-to-start--complains-about-launchd-not-providing-socket--path-td23618152.html I executed the following commands from the command line: sudo launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist sudo launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus-system.plist then I restarted. But still I get the same errors when I start up Gedit from the command line. Any ideas how to fix this? -------------- next part -------------- An HTML attachment was scrubbed... URL: From drechsel at verkehrsplanung.com Wed Oct 21 01:44:08 2009 From: drechsel at verkehrsplanung.com (Wolf Drechsel) Date: Wed, 21 Oct 2009 10:44:08 +0200 Subject: CVS compilation Message-ID: <8F915C6C-9350-4080-97F5-1299430D9F42@verkehrsplanung.com> Hello everybody, I have to apologize for a probabely quite stupid question: I'd like to use gnuplot 4.3 on my Mac 10.4.11 - which is not yet available as a port. One can obtain it via CVS - but on my machine the compilation results in several errors I cannot resolve. So I wonder whether it would be the easier way to do it using macports. The CVS commands to obtain gnuplots are: cvs -d:pserver:anonymous at gnuplot.cvs.sourceforge.net:/cvsroot/gnuplot login cvs -z3 -d:pserver:anonymous at gnuplot.cvs.sourceforge.net:/cvsroot/ gnuplot co -P gnuplot Can anybody give me a hint whether it is possible to compile from that source using the macports basis - and how to do it? Thanks and greetings, Wolf P.S.: There is a script to install th gnuplot CVS version. It gave me the errors I wrote above, but maybe anybody can read something from it: #! /bin/sh # cd /Users/"$(whoami)"/Desktop/ echo "Gnuplot svn compilation: aquaterm support only, to have x11 simply delete -with-x=no option" echo "You need automake newer 1.8 (fink helps)!!" echo "To have gnu readline support, install readline5-shlibs from fink and check if there is the sym link in /usr/lib : libreadline.dylib -> /sw/lib/libreadline.5.0.dylib" echo "Press ENTER when asked for cvs pwd" echo cvs -d:pserver:anonymous at gnuplot.cvs.sourceforge.net:/cvsroot/gnuplot login cvs -z3 -d:pserver:anonymous at gnuplot.cvs.sourceforge.net:/cvsroot/ gnuplot co -P gnuplot cd gnuplot/ sudo ./prepare ./configure -with-x=no --without-tutorial CFLAGS=-DDEFAULTTERM=\\ \"aqua\\\" --with-readline=gnu make cd src/ sudo cp gnuplot /Users/"$(whoami)"/Desktop/gnuplot_svn cd /Users/"$(whoami)"/Desktop/ version=`gnuplot_svn --version | awk '{print $2}'` date=`date | awk '{print $3 $2 $6}'` mv gnuplot_svn gnuplot-"$version"_svn"$date" echo "Removing compilation folder and moving binary file to Desktop..." sudo rm -r gnuplot/ From vincent.diemunsch at gmail.com Wed Oct 21 02:51:49 2009 From: vincent.diemunsch at gmail.com (Vincent DIEMUNSCH) Date: Wed, 21 Oct 2009 11:51:49 +0200 Subject: GNAT-GCC Message-ID: <1e0dec580910210251o50d3a4f4ha769b2be81bb860e@mail.gmail.com> Hi everybody, Little questioni regarding GNAT-GCC : If I install this port, what will be the default compiler for MacPorts ? and for the rest of the system ? (XCode for instance). And what if I install or re-install XCode ? Is it safe enough to use this gcc instead of the one provided by Apple ? Thanks for your responses. Vincent OSX 10.6.1 Intel 32 bits . -------------- next part -------------- An HTML attachment was scrubbed... URL: From lanceboyle at qwest.net Wed Oct 21 14:35:35 2009 From: lanceboyle at qwest.net (Jerry) Date: Wed, 21 Oct 2009 14:35:35 -0700 Subject: gnat-gcc Ada GNAT on 10.6 Snow Leopard Message-ID: <14FF725D-06BD-46F9-9C07-CA95C1602A88@qwest.net> Is there a GNAT (Ada) compiler that is known to work with Snow Leopard, OS X 10.6? If so, what version(s) of Xcode works with it? I'm on the macada.org list and will gladly report any discussion there back to that list. I recall that someone, not too long ago, managed to bootstrap GNAT into Macports. I'm just wondering if that effort has succeeded with Snow Leopard. Jerry From robince at gmail.com Wed Oct 21 14:39:45 2009 From: robince at gmail.com (Robin) Date: Wed, 21 Oct 2009 22:39:45 +0100 Subject: py26-numpy with veclib Message-ID: <2d5132a50910211439o22e37567jfb95e1f46618244b@mail.gmail.com> Hi, Is it possible to build py26-numpy against veclib with macports? I had assumed that specifying +no_atlas variant would fall back to using veclib (from reading tickets it looks like thats what it did before) but instead it seems to use no accelerated library. This is the result of numpy.show_config() when built with +no_atlas: Python 2.6.3 (r263:75183, Oct 21 2009, 13:12:29) [GCC 4.2.1 (Apple Inc. build 5646)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import numpy >>> numpy.show_config() blas_info: libraries = ['blas'] library_dirs = ['/usr/lib'] language = f77 lapack_info: libraries = ['lapack'] library_dirs = ['/usr/lib'] language = f77 atlas_threads_info: NOT AVAILABLE blas_opt_info: libraries = ['blas'] library_dirs = ['/usr/lib'] language = f77 define_macros = [('NO_ATLAS_INFO', 1)] atlas_blas_threads_info: NOT AVAILABLE lapack_opt_info: libraries = ['lapack', 'blas'] library_dirs = ['/usr/lib'] language = f77 define_macros = [('NO_ATLAS_INFO', 1)] atlas_info: NOT AVAILABLE lapack_mkl_info: NOT AVAILABLE blas_mkl_info: NOT AVAILABLE atlas_blas_info: NOT AVAILABLE mkl_info: NOT AVAILABLE If linked against veclib the output should look like this: >>> numpy.show_config() lapack_opt_info: extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] extra_compile_args = ['-msse3'] define_macros = [('NO_ATLAS_INFO', 3)] blas_opt_info: extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] extra_compile_args = ['-msse3', '-I/System/Library/Frameworks/vecLib.framework/Headers'] define_macros = [('NO_ATLAS_INFO', 3)] Cheers Robin From ryandesign at macports.org Wed Oct 21 14:48:26 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 21 Oct 2009 16:48:26 -0500 Subject: CVS compilation In-Reply-To: <8F915C6C-9350-4080-97F5-1299430D9F42@verkehrsplanung.com> References: <8F915C6C-9350-4080-97F5-1299430D9F42@verkehrsplanung.com> Message-ID: <0A19B979-F86A-480B-AFDB-7837D63CD0EB@macports.org> On Oct 21, 2009, at 03:44, Wolf Drechsel wrote: > I'd like to use gnuplot 4.3 on my Mac 10.4.11 - which is not yet > available as a port 4.2.x appears to be the latest stable version, according to the web site, therefore that's what MacPorts provides. > One can obtain it via CVS - but on my machine the compilation > results in several errors I cannot resolve. What errors do you get? > So I wonder whether it would be the easier way to do it using > macports. MacPorts is for taking software that can already be compiled on Mac OS X and making it easier to install. Unless the errors you're getting relate to being unable to find dependencies provided by MacPorts, I doubt it will be any more possible to build it in MacPorts than it was by hand. > The CVS commands to obtain gnuplots are: > > cvs -d:pserver:anonymous at gnuplot.cvs.sourceforge.net:/cvsroot/ > gnuplot login > cvs -z3 -d:pserver:anonymous at gnuplot.cvs.sourceforge.net:/cvsroot/ > gnuplot co -P gnuplot > > Can anybody give me a hint whether it is possible to compile from > that source using the macports basis - and how to do it? The Guide explains how to write portfiles: http://guide.macports.org/ So if you really must have 4.3 now and cannot wait for it to be released, and want to see if you can get it working in MacPorts, you can create a local port repository and make a copy of the existing gnuplot 4.2.x portfile and try updating it. From vince at macports.org Wed Oct 21 20:49:25 2009 From: vince at macports.org (vincent habchi) Date: Thu, 22 Oct 2009 05:49:25 +0200 Subject: py26-numpy with veclib In-Reply-To: <2d5132a50910211439o22e37567jfb95e1f46618244b@mail.gmail.com> References: <2d5132a50910211439o22e37567jfb95e1f46618244b@mail.gmail.com> Message-ID: Hi, > Is it possible to build py26-numpy against veclib with macports? > > If linked against veclib the output should look like this: > >>>> numpy.show_config() > lapack_opt_info: > extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] > extra_compile_args = ['-msse3'] > define_macros = [('NO_ATLAS_INFO', 3)] > > blas_opt_info: > extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] > extra_compile_args = ['-msse3', > '-I/System/Library/Frameworks/vecLib.framework/Headers'] > define_macros = [('NO_ATLAS_INFO', 3)] My config shows this: Python 2.6.3 (r263:75183, Oct 13 2009, 08:46:50) [GCC 4.2.1 (Based on Apple Inc. build 5646) (LLVM build 2118)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import numpy >>> numpy.show_config () lapack_opt_info: extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] extra_compile_args = ['-faltivec'] define_macros = [('NO_ATLAS_INFO', 3)] blas_opt_info: extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] extra_compile_args = ['-faltivec', '-I/System/Library/Frameworks/ vecLib.framework/Headers'] define_macros = [('NO_ATLAS_INFO', 3)] >>> Note that I am on x86_64, so that looks a bit strange. Vincent From ryandesign at macports.org Wed Oct 21 21:41:31 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 21 Oct 2009 23:41:31 -0500 Subject: GNAT-GCC In-Reply-To: <1e0dec580910210251o50d3a4f4ha769b2be81bb860e@mail.gmail.com> References: <1e0dec580910210251o50d3a4f4ha769b2be81bb860e@mail.gmail.com> Message-ID: On Oct 21, 2009, at 04:51, Vincent DIEMUNSCH wrote: > Little questioni regarding GNAT-GCC : > > If I install this port, what will be the default compiler for > MacPorts ? and for the rest > of the system ? (XCode for instance). And what if I install or re- > install XCode ? Nothing will change on those counts by installing gnat-gcc or any other port. Ports will use Apple's gcc 4.0 on Tiger and Leopard and Apple's gcc 4.2 on Snow Leopard -- unless the port requests otherwise. > Is it safe enough to use this gcc instead of the one provided by > Apple ? I haven't used it. Presumably you would use gnat-gcc if you need the special features it offers, and otherwise you would use Apple's gcc or one of the standard gcc4* ports. From ryandesign at macports.org Wed Oct 21 21:43:31 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 21 Oct 2009 23:43:31 -0500 Subject: make libXaw fails In-Reply-To: References: Message-ID: On Oct 20, 2009, at 20:44, Arden wrote: > I have Xcode 2.5 on Tiger , build of libXaw fails. How should I know > if this is a bug or not? and why should I learn how to report it? > Arden > > ---> Building xorg-libXaw > Error: Target org.macports.build returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xorg > -libXaw/work/libXaw-1.0.7" && /usr/bin/make -j1 all " returned error 2 > Command output: CC libXaw7_la-TextAction.lo > CC libXaw7_la-TextPop.lo > TextPop.c: In function 'CreateDialog': > TextPop.c:1436: warning: cast from function call of type 'Widget' to > non-matching type 'long int' > CC libXaw7_la-TextTr.lo > CC libXaw7_la-Toggle.lo > CC libXaw7_la-Tree.lo > CC libXaw7_la-Vendor.lo > CC libXaw7_la-Viewport.lo > CC libXaw7_la-XawIm.lo > CC libXaw7_la-XawInit.lo > CC libXaw7_la-XawI18n.lo > CC libXaw7_la-Tip.lo > CCLD libXaw7.la > ld: warning multiple definitions of symbol _vendorShellWidgetClass > .libs/libXaw7_la-Vendor.o definition of _vendorShellWidgetClass in > section (__DATA,__data) > /opt/local/lib/libXt.dylib(single module) definition of > _vendorShellWidgetClass > ld: warning multiple definitions of symbol _vendorShellClassRec > .libs/libXaw7_la-Vendor.o definition of _vendorShellClassRec in > section (__DATA,__data) > /opt/local/lib/libXt.dylib(single module) definition of > _vendorShellClassRec > warning: no debug map in executable (-arch ppc) > Making all in man > GEN Xaw.3 > Making all in spec > GEN widgets.ps > make[2]: [widgets.ps] Error 1 (ignored) > tbl:./Template:427:fatal error: output error > make[2]: *** [widgets.ps] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 I was able to install the latest xorg-libXaw on Tiger PPC so I'm not sure what happened on your system. I'm not sure what "fatal error: output error" means. Is your hard drive OK? Does it have enough free space? If you "sudo port clean xorg-libXaw" and try again, do you get the same error? From felix at laas.fr Wed Oct 21 22:06:36 2009 From: felix at laas.fr (Felix Ingrand) Date: Thu, 22 Oct 2009 07:06:36 +0200 Subject: xcb fails to install on SnowLeopard MacPort 1.8.1 Message-ID: I was truing to install glade3, which depends on xcb and get this: [Zig:~] felix% sudo port -v install glade3 ---> Computing dependencies for glade3............................................................... ---> Staging xcb 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) install -c xcb /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb /work/destroot/opt/local/bin/xcb + mkdir -p /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb /work/destroot/opt/local/lib/X11/app-defaults install -c -m 0444 Xcb.ad /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb /work/destroot/opt/local/share/X11/app-defaults/Xcb install in . done install -c -m 0444 xcb._man /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb /work/destroot/opt/local/share/man/man1/xcb.1 install.man in . done Error: Target org.macports.destroot returned: no such file or directory Warning: the following items did not execute (for xcb): org.macports.activate org.macports.destroot org.macports.install Error: The following dependencies failed to build: devhelp libwnck startup-notification xcb xorg-libxcb xorg-libpthread-stubs xorg-xcb- proto xorg-xcb-util xorg-libXres xorg-resourceproto python25 webkit- gtk enchant aspell hunspell gst-plugins-base gnome-vfs desktop-file- utils gnome-mime-data gstreamer gzip libogg liboil libtheora libvorbis icu libsoup gnutls libgcrypt libgpg-error libtasn1 lzo opencdk libproxy hicolor-icon-theme libgnomeui gnome-icon-theme icon-naming- utils p5-xml-simple p5-xml-namespacesupport p5-xml-sax gnome-keyring libbonoboui libbonobo libglade2 libgnome esound audiofile libgnomecanvas libart_lgpl py26-gtk py26-cairo py26-numpy atlas gcc43 gmp mpfr fftw-3 py26-nose py26-setuptools py26-gobject libffi Error: Status 1 encountered during processing. [Zig:~] felix% sudo port -v install xcb ---> Computing dependencies for xcb. ---> Staging xcb 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) install -c xcb /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb /work/destroot/opt/local/bin/xcb + mkdir -p /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb /work/destroot/opt/local/lib/X11/app-defaults install -c -m 0444 Xcb.ad /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb /work/destroot/opt/local/share/X11/app-defaults/Xcb install in . done install -c -m 0444 xcb._man /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb /work/destroot/opt/local/share/man/man1/xcb.1 install.man in . done Error: Target org.macports.destroot returned: no such file or directory Warning: the following items did not execute (for xcb): org.macports.activate org.macports.destroot org.macports.install Error: Status 1 encountered during processing. -- Felix You have one hour, forty six minutes and forty three seconds of peace of mind left: http://tinyurl.com/6fz2pw From ryandesign at macports.org Wed Oct 21 23:18:42 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 22 Oct 2009 01:18:42 -0500 Subject: xcb fails to install on SnowLeopard MacPort 1.8.1 In-Reply-To: References: Message-ID: <3B8A280D-C5E4-45FB-A05C-A7016A6B59A4@macports.org> On Oct 22, 2009, at 00:06, Felix Ingrand wrote: > ---> Staging xcb 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) > install -c xcb /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb > /work/destroot/opt/local/bin/xcb > + mkdir -p /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb > /work/destroot/opt/local/lib/X11/app-defaults > install -c -m 0444 Xcb.ad /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb > /work/destroot/opt/local/share/X11/app-defaults/Xcb > install in . done > install -c -m 0444 xcb._man /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb > /work/destroot/opt/local/share/man/man1/xcb.1 > install.man in . done > Error: Target org.macports.destroot returned: no such file or > directory > Warning: the following items did not execute (for xcb): > org.macports.activate org.macports.destroot org.macports.install > Error: The following dependencies failed to build: devhelp libwnck > startup-notification xcb xorg-libxcb xorg-libpthread-stubs xorg-xcb- > proto xorg-xcb-util xorg-libXres xorg-resourceproto python25 webkit- > gtk enchant aspell hunspell gst-plugins-base gnome-vfs desktop-file- > utils gnome-mime-data gstreamer gzip libogg liboil libtheora > libvorbis icu libsoup gnutls libgcrypt libgpg-error libtasn1 lzo > opencdk libproxy hicolor-icon-theme libgnomeui gnome-icon-theme icon- > naming-utils p5-xml-simple p5-xml-namespacesupport p5-xml-sax gnome- > keyring libbonoboui libbonobo libglade2 libgnome esound audiofile > libgnomecanvas libart_lgpl py26-gtk py26-cairo py26-numpy atlas > gcc43 gmp mpfr fftw-3 py26-nose py26-setuptools py26-gobject libffi > Error: Status 1 encountered during processing. I see the same problem. Would you please file a ticket in the issue tracker? From ryandesign at macports.org Wed Oct 21 23:21:08 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 22 Oct 2009 01:21:08 -0500 Subject: xcb fails to install on SnowLeopard MacPort 1.8.1 In-Reply-To: <3B8A280D-C5E4-45FB-A05C-A7016A6B59A4@macports.org> References: <3B8A280D-C5E4-45FB-A05C-A7016A6B59A4@macports.org> Message-ID: <43530BBA-412E-4BEB-8348-AFB7A343D6C0@macports.org> On Oct 22, 2009, at 01:18, Ryan Schmidt wrote: > On Oct 22, 2009, at 00:06, Felix Ingrand wrote: > >> ---> Staging xcb 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) >> install -c xcb /opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb >> /work/destroot/opt/local/bin/xcb >> + mkdir -p /opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb >> /work/destroot/opt/local/lib/X11/app-defaults >> install -c -m 0444 Xcb.ad /opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb >> /work/destroot/opt/local/share/X11/app-defaults/Xcb >> install in . done >> install -c -m 0444 xcb._man /opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xcb >> /work/destroot/opt/local/share/man/man1/xcb.1 >> install.man in . done >> Error: Target org.macports.destroot returned: no such file or >> directory >> Warning: the following items did not execute (for xcb): >> org.macports.activate org.macports.destroot org.macports.install >> Error: The following dependencies failed to build: devhelp libwnck >> startup-notification xcb xorg-libxcb xorg-libpthread-stubs xorg-xcb- >> proto xorg-xcb-util xorg-libXres xorg-resourceproto python25 webkit- >> gtk enchant aspell hunspell gst-plugins-base gnome-vfs desktop-file- >> utils gnome-mime-data gstreamer gzip libogg liboil libtheora >> libvorbis icu libsoup gnutls libgcrypt libgpg-error libtasn1 lzo >> opencdk libproxy hicolor-icon-theme libgnomeui gnome-icon-theme >> icon-naming-utils p5-xml-simple p5-xml-namespacesupport p5-xml-sax >> gnome-keyring libbonoboui libbonobo libglade2 libgnome esound >> audiofile libgnomecanvas libart_lgpl py26-gtk py26-cairo py26-numpy >> atlas gcc43 gmp mpfr fftw-3 py26-nose py26-setuptools py26-gobject >> libffi >> Error: Status 1 encountered during processing. > > I see the same problem. Would you please file a ticket in the issue > tracker? It looks like Jeremy accidentally committed this along with his multiport maintainer change in r59685. From kuepper.jochen at googlemail.com Thu Oct 22 00:55:50 2009 From: kuepper.jochen at googlemail.com (=?iso-8859-1?Q?Jochen_K=FCpper?=) Date: Thu, 22 Oct 2009 09:55:50 +0200 Subject: py26-numpy with veclib In-Reply-To: <2d5132a50910211439o22e37567jfb95e1f46618244b@mail.gmail.com> References: <2d5132a50910211439o22e37567jfb95e1f46618244b@mail.gmail.com> Message-ID: <76DA5B7B-49E4-42E0-8E5D-1377969DB53D@googlemail.com> On 21.10.2009, at 23:39, Robin wrote: > Hi, > > Is it possible to build py26-numpy against veclib with macports? It does for me: > /opt/local/bin/python2.6 Python 2.6.3 (r263:75183, Oct 17 2009, 11:35:55) [GCC 4.2.1 (Apple Inc. build 5646)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import numpy >>> numpy.show_config() lapack_opt_info: extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] extra_compile_args = ['-faltivec'] define_macros = [('NO_ATLAS_INFO', 3)] blas_opt_info: extra_link_args = ['-Wl,-framework', '-Wl,Accelerate'] extra_compile_args = ['-faltivec', '-I/System/Library/Frameworks/ vecLib.framework/Headers'] define_macros = [('NO_ATLAS_INFO', 3)] >>> This is actually for the default variants? Then, however, the question is why it used -faltivec instead of -msse3 or such on my Mac Pro (x86_64)... Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de Libert?, ?galit?, Fraternit? GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll From robince at gmail.com Thu Oct 22 03:38:43 2009 From: robince at gmail.com (Robin) Date: Thu, 22 Oct 2009 11:38:43 +0100 Subject: py26-numpy with veclib In-Reply-To: <76DA5B7B-49E4-42E0-8E5D-1377969DB53D@googlemail.com> References: <2d5132a50910211439o22e37567jfb95e1f46618244b@mail.gmail.com> <76DA5B7B-49E4-42E0-8E5D-1377969DB53D@googlemail.com> Message-ID: <2d5132a50910220338n3a5d4b71ud3b70a8194d038d2@mail.gmail.com> On Thu, Oct 22, 2009 at 8:55 AM, Jochen K?pper wrote: > On 21.10.2009, at 23:39, Robin wrote: > >> Hi, >> >> Is it possible to build py26-numpy against veclib with macports? > > It does for me: > > This is actually for the default variants? > Ah, thanks. I wonder why it doesn't for me. I am using up to date macports with snow leopard. For me the default variants leads to being built with atlas. If I specify no_atlas variant then I get the no external blas shown earlier. I wonder if something has changed recently to stop building against veclib. Shall I open a ticket? In [4]: numpy.show_config() atlas_threads_info: libraries = ['lapack', 'ptf77blas', 'ptcblas', 'atlas'] library_dirs = ['/opt/local/lib'] language = f77 include_dirs = ['/opt/local/include'] blas_opt_info: libraries = ['ptf77blas', 'ptcblas', 'atlas'] library_dirs = ['/opt/local/lib'] define_macros = [('ATLAS_INFO', '"\\"3.8.3\\""')] language = c include_dirs = ['/opt/local/include'] atlas_blas_threads_info: libraries = ['ptf77blas', 'ptcblas', 'atlas'] library_dirs = ['/opt/local/lib'] language = c include_dirs = ['/opt/local/include'] lapack_opt_info: libraries = ['lapack', 'ptf77blas', 'ptcblas', 'atlas'] library_dirs = ['/opt/local/lib'] define_macros = [('ATLAS_INFO', '"\\"3.8.3\\""')] language = f77 include_dirs = ['/opt/local/include'] lapack_mkl_info: NOT AVAILABLE blas_mkl_info: NOT AVAILABLE mkl_info: NOT AVAILABLE From vincent.diemunsch at gmail.com Thu Oct 22 04:07:58 2009 From: vincent.diemunsch at gmail.com (Vincent DIEMUNSCH) Date: Thu, 22 Oct 2009 13:07:58 +0200 Subject: GNAT-GCC In-Reply-To: References: <1e0dec580910210251o50d3a4f4ha769b2be81bb860e@mail.gmail.com> Message-ID: <1e0dec580910220407g76439bban10f82cb548c968f3@mail.gmail.com> Thanks Ryan for your response. What are the differences between Apple's gcc and the standard gcc 4.* ports ? And to use gnat-gcc, I simply need to invoke gnatmake or do I need to use gcc-select ? Vincent 2009/10/22 Ryan Schmidt > On Oct 21, 2009, at 04:51, Vincent DIEMUNSCH wrote: > > Little questioni regarding GNAT-GCC : >> >> If I install this port, what will be the default compiler for MacPorts ? >> and for the rest >> of the system ? (XCode for instance). And what if I install or re-install >> XCode ? >> > > Nothing will change on those counts by installing gnat-gcc or any other > port. Ports will use Apple's gcc 4.0 on Tiger and Leopard and Apple's gcc > 4.2 on Snow Leopard -- unless the port requests otherwise. > > > > Is it safe enough to use this gcc instead of the one provided by Apple ? >> > > I haven't used it. Presumably you would use gnat-gcc if you need the > special features it offers, and otherwise you would use Apple's gcc or one > of the standard gcc4* ports. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kuepper.jochen at googlemail.com Thu Oct 22 04:09:27 2009 From: kuepper.jochen at googlemail.com (=?windows-1252?Q?Jochen_K=FCpper?=) Date: Thu, 22 Oct 2009 13:09:27 +0200 Subject: py26-numpy with veclib In-Reply-To: <2d5132a50910220338n3a5d4b71ud3b70a8194d038d2@mail.gmail.com> References: <2d5132a50910211439o22e37567jfb95e1f46618244b@mail.gmail.com> <76DA5B7B-49E4-42E0-8E5D-1377969DB53D@googlemail.com> <2d5132a50910220338n3a5d4b71ud3b70a8194d038d2@mail.gmail.com> Message-ID: On 22.10.2009, at 12:38, Robin wrote: > On Thu, Oct 22, 2009 at 8:55 AM, Jochen K?pper > wrote: >> On 21.10.2009, at 23:39, Robin wrote: >> >>> Hi, >>> >>> Is it possible to build py26-numpy against veclib with macports? >> >> It does for me: >> >> This is actually for the default variants? >> > > Ah, thanks. I wonder why it doesn't for me. I am using up to date > macports with snow leopard. Me too > For me the default variants leads to being > built with atlas. If I specify no_atlas variant then I get the no > external blas shown earlier. Actually, I don't have ATLAS installed, so that's the difference... > I wonder if something has changed > recently to stop building against veclib. > > Shall I open a ticket? yes > > In [4]: numpy.show_config() > atlas_threads_info: > libraries = ['lapack', 'ptf77blas', 'ptcblas', 'atlas'] > library_dirs = ['/opt/local/lib'] > language = f77 > include_dirs = ['/opt/local/include'] > > blas_opt_info: > libraries = ['ptf77blas', 'ptcblas', 'atlas'] > library_dirs = ['/opt/local/lib'] > define_macros = [('ATLAS_INFO', '"\\"3.8.3\\""')] > language = c > include_dirs = ['/opt/local/include'] > > atlas_blas_threads_info: > libraries = ['ptf77blas', 'ptcblas', 'atlas'] > library_dirs = ['/opt/local/lib'] > language = c > include_dirs = ['/opt/local/include'] > > lapack_opt_info: > libraries = ['lapack', 'ptf77blas', 'ptcblas', 'atlas'] > library_dirs = ['/opt/local/lib'] > define_macros = [('ATLAS_INFO', '"\\"3.8.3\\""')] > language = f77 > include_dirs = ['/opt/local/include'] > > lapack_mkl_info: > NOT AVAILABLE > > blas_mkl_info: > NOT AVAILABLE > > mkl_info: > NOT AVAILABLE From robince at gmail.com Thu Oct 22 04:51:04 2009 From: robince at gmail.com (Robin) Date: Thu, 22 Oct 2009 12:51:04 +0100 Subject: py26-numpy with veclib In-Reply-To: References: <2d5132a50910211439o22e37567jfb95e1f46618244b@mail.gmail.com> <76DA5B7B-49E4-42E0-8E5D-1377969DB53D@googlemail.com> <2d5132a50910220338n3a5d4b71ud3b70a8194d038d2@mail.gmail.com> Message-ID: <2d5132a50910220451ube8211aj6e503c15f530a607@mail.gmail.com> On Thu, Oct 22, 2009 at 12:09 PM, Jochen K?pper wrote: > On 22.10.2009, at 12:38, Robin wrote: > >> On Thu, Oct 22, 2009 at 8:55 AM, Jochen K?pper >> wrote: > > Actually, I don't have ATLAS installed, so that's the difference... I don't think so - I can't build +no_atlas with atlas installed - if its there it gets used regardless of the variant : http://trac.macports.org/ticket/22201 So when I build +no_atlas without atlas installed I get no external blas (not veclib) http://trac.macports.org/ticket/22200 I don't know what to do to get veclib... Cheers Robin From and.damore at macports.org Thu Oct 22 04:59:54 2009 From: and.damore at macports.org (Andrea D'Amore) Date: Thu, 22 Oct 2009 13:59:54 +0200 Subject: xcb fails to install on SnowLeopard MacPort 1.8.1 In-Reply-To: <3B8A280D-C5E4-45FB-A05C-A7016A6B59A4@macports.org> References: <3B8A280D-C5E4-45FB-A05C-A7016A6B59A4@macports.org> Message-ID: On 22/ott/09, at 08:18, Ryan Schmidt wrote: > I see the same problem. Would you please file a ticket in the issue > tracker? I had the same issue while upgrading outdated, I could reproduce a couple times then I ran a clean xcb and this time it built fine. The problem was that while destrooting a couple directory were created as symlinks instead, in my case ${destroot}/${prefix}/lib/X11/app- defaults was a link to ../../lib/X11/app-defaults, I checked the debug output but wasn't able to see any offending line, just regular install and mkdir -p. -- Andrea From kuepper.jochen at googlemail.com Thu Oct 22 05:03:05 2009 From: kuepper.jochen at googlemail.com (=?iso-8859-1?Q?Jochen_K=FCpper?=) Date: Thu, 22 Oct 2009 14:03:05 +0200 Subject: py26-numpy with veclib In-Reply-To: <2d5132a50910220451ube8211aj6e503c15f530a607@mail.gmail.com> References: <2d5132a50910211439o22e37567jfb95e1f46618244b@mail.gmail.com> <76DA5B7B-49E4-42E0-8E5D-1377969DB53D@googlemail.com> <2d5132a50910220338n3a5d4b71ud3b70a8194d038d2@mail.gmail.com> <2d5132a50910220451ube8211aj6e503c15f530a607@mail.gmail.com> Message-ID: <4506649F-5610-4E46-9CEB-EA2795478248@googlemail.com> On 22.10.2009, at 13:51, Robin wrote: > On Thu, Oct 22, 2009 at 12:09 PM, Jochen K?pper > wrote: >> On 22.10.2009, at 12:38, Robin wrote: >> >>> On Thu, Oct 22, 2009 at 8:55 AM, Jochen K?pper >>> wrote: >> >> Actually, I don't have ATLAS installed, so that's the difference... > > I don't think so - I can't build +no_atlas with atlas installed - if > its there it gets used regardless of the variant : > http://trac.macports.org/ticket/22201 > > So when I build +no_atlas without atlas installed I get no external > blas (not veclib) http://trac.macports.org/ticket/22200 > > I don't know what to do to get veclib? What do you get if you have no ATLAS around and do not specify any variant? Do you have the latest XCode updates? /Jochen From robince at gmail.com Thu Oct 22 05:05:46 2009 From: robince at gmail.com (Robin) Date: Thu, 22 Oct 2009 13:05:46 +0100 Subject: py26-numpy with veclib In-Reply-To: <4506649F-5610-4E46-9CEB-EA2795478248@googlemail.com> References: <2d5132a50910211439o22e37567jfb95e1f46618244b@mail.gmail.com> <76DA5B7B-49E4-42E0-8E5D-1377969DB53D@googlemail.com> <2d5132a50910220338n3a5d4b71ud3b70a8194d038d2@mail.gmail.com> <2d5132a50910220451ube8211aj6e503c15f530a607@mail.gmail.com> <4506649F-5610-4E46-9CEB-EA2795478248@googlemail.com> Message-ID: <2d5132a50910220505w424e1781k22518552180bc7d7@mail.gmail.com> On Thu, Oct 22, 2009 at 1:03 PM, Jochen K?pper wrote: > > What do you get if you have no ATLAS around and do not specify any variant? Atlas gets installed as a dependency if I don't specify any variant. > Do you have the latest XCode updates? I have xcode 3.2, core: 1608 Cheers Robin From kuepper.jochen at googlemail.com Thu Oct 22 05:21:53 2009 From: kuepper.jochen at googlemail.com (=?iso-8859-1?Q?Jochen_K=FCpper?=) Date: Thu, 22 Oct 2009 14:21:53 +0200 Subject: py26-numpy with veclib In-Reply-To: <2d5132a50910220505w424e1781k22518552180bc7d7@mail.gmail.com> References: <2d5132a50910211439o22e37567jfb95e1f46618244b@mail.gmail.com> <76DA5B7B-49E4-42E0-8E5D-1377969DB53D@googlemail.com> <2d5132a50910220338n3a5d4b71ud3b70a8194d038d2@mail.gmail.com> <2d5132a50910220451ube8211aj6e503c15f530a607@mail.gmail.com> <4506649F-5610-4E46-9CEB-EA2795478248@googlemail.com> <2d5132a50910220505w424e1781k22518552180bc7d7@mail.gmail.com> Message-ID: <92116B8B-7355-4284-9F8D-48B1C2AD940D@googlemail.com> Hi Robin, a) please file a ticket. b) we are apparently talking about different versions of the Portfile, although nobody told MacPorts about it! The following changes (and probably a few more) were made without changing the revision in the Portfile? I picked these latest two because they are the suspects for the problems you are seeing ------------------------------------------------------------------------ r59616 | jameskyle at macports.org | 2009-10-18 00:56:16 +0200 (So, 18 Okt 2009) | 2 lines Changed paths: M /trunk/dports/python/py26-numpy/Portfile Added proper deletion of default opts for no_gcc43 and no_atlas variants. ------------------------------------------------------------------------ r59608 | jameskyle at macports.org | 2009-10-18 00:55:57 +0200 (So, 18 Okt 2009) | 2 lines Changed paths: M /trunk/dports/python/py26-numpy/Portfile Added ATLAS, LAPACK, and BLAS build environment to point to macports libs. c) Please file a ticket, unless already done. /Jochen From buffyg at mac.com Thu Oct 22 17:07:51 2009 From: buffyg at mac.com (Bayard Bell) Date: Fri, 23 Oct 2009 01:07:51 +0100 Subject: include problem building BDB 4.6.21 w/ /usr/local In-Reply-To: <4AD98C1C.2040405@macports.org> References: <8DCE25EA-5E75-4E99-8EE0-A5DA60C67EC7@mac.com> <4AD98C1C.2040405@macports.org> Message-ID: <7F284633-04C5-4E98-AE33-7654CA23831D@mac.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Did a bit more digging. The problem looks to be with Apple's build of make. Extracted from "make -dp" output: # default .INCLUDE_DIRS = /usr/include /usr/local/include /usr/include Filing bug report now. Again dtruss gives me a clue to put it together. Looking at the top of the output, there's some other sloppiness in how Apple is maintaining their make port: # GNU Make 3.81 # Copyright (C) 2006 Free Software Foundation, Inc. # This is free software; see the source for copying conditions. # There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A # PARTICULAR PURPOSE. # This program built for powerpc-apple-darwin9.0 Pretty sure it wasn't built for PPC, at least not PPC alone: precious:Downloads bayard$ file -L /usr/bin/make /usr/bin/make: Mach-O universal binary with 2 architectures /usr/bin/make (for architecture i386): Mach-O executable i386 /usr/bin/make (for architecture ppc7400): Mach-O executable ppc Am 17 Oct 2009 um 10:19 schrieb Joshua Root: > On 2009-10-17 11:57, Bayard Bell wrote: >> I've been looking through tickets, trying to figure out what's going >> wrong. There's an open ticket for this, 19918. As far as I can see, >> the >> immediate problem occurs when you've got db.h in /usr/local/include. >> Renaming the file certainly fixes the problem. (Three cheers to >> dtruss >> for giving me a handle on this.) >> >> What doesn't really make sense to me is why or how this is found in >> the >> first instance: I'd argue strongly that the pre-processor shouldn't >> be >> looking there by default, and it's not much evident to me that >> CPPFLAGS >> is being constructed to tell it to do so. Before digging around >> further, >> I thought I'd ask if anyone knew why this might be. > > We're not telling it to look there, it just does. The only way to > avoid > this would be to use -nostdinc, but then you have to somehow > reconstruct > the other default search paths and tell it to look in them. > > So basically, there's not much we can do about it, and the place to > report the issue is and/or > . (Note that upstream changes to GCC at > this point will likely never be distributed by Apple, since they are > moving to LLVM.) > > - Josh -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (Darwin) iEYEARECAAYFAkrg890ACgkQcZQHT1XL9xllHwCgspk79GtWAk9lWbA0betUE3bZ a5gAoLnPUcOoq1dqiwnRshfFhNYX9Ne3 =+00p -----END PGP SIGNATURE----- From ryandesign at macports.org Thu Oct 22 18:25:00 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 22 Oct 2009 20:25:00 -0500 Subject: include problem building BDB 4.6.21 w/ /usr/local In-Reply-To: <7F284633-04C5-4E98-AE33-7654CA23831D@mac.com> References: <8DCE25EA-5E75-4E99-8EE0-A5DA60C67EC7@mac.com> <4AD98C1C.2040405@macports.org> <7F284633-04C5-4E98-AE33-7654CA23831D@mac.com> Message-ID: <06175660-15BF-4F82-82AE-C841C8C2D174@macports.org> On Oct 22, 2009, at 19:07, Bayard Bell wrote: > Did a bit more digging. The problem looks to be with Apple's build > of make. Extracted from "make -dp" output: > > # default > .INCLUDE_DIRS = /usr/include /usr/local/include /usr/include > > Filing bug report now. I guess they've fixed that already; this is what I get on Snow Leopard: $ /usr/bin/make -dp | grep INCLUDE make: *** No targets specified and no makefile found. Stop. .INCLUDE_DIRS = /usr/include /usr/include > Again dtruss gives me a clue to put it together. Looking at the top > of the output, there's some other sloppiness in how Apple is > maintaining their make port: > > # GNU Make 3.81 > # Copyright (C) 2006 Free Software Foundation, Inc. > # This is free software; see the source for copying conditions. > # There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A > # PARTICULAR PURPOSE. > > # This program built for powerpc-apple-darwin9.0 > > Pretty sure it wasn't built for PPC, at least not PPC alone: > > precious:Downloads bayard$ file -L /usr/bin/make > /usr/bin/make: Mach-O universal binary with 2 architectures > /usr/bin/make (for architecture i386): Mach-O executable i386 > /usr/bin/make (for architecture ppc7400): Mach-O executable ppc Doesn't look sloppy; looks like what is totally expected to happen if you build a program on PowerPC for multiple architectures. The build machine was powerpc-apple-darwin9.0 and it was told to build for both - arch i386 and -arch ppc. It's the fault of the developers of make for assuming that printing the triple of the build machine in the version output would be useful for anything. For comparison, on Snow Leopard, I get: $ /usr/bin/make -v GNU Make 3.81 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This program built for i386-apple-darwin10.0 And of course it contains not only i386 but also x86_64 code. $ lipo -info /usr/bin/make Architectures in the fat file: /usr/bin/make are: x86_64 i386 From face at CentosPrime.COM Fri Oct 23 06:20:56 2009 From: face at CentosPrime.COM (Chris Janton) Date: Fri, 23 Oct 2009 06:20:56 -0700 Subject: include problem building BDB 4.6.21 w/ /usr/local In-Reply-To: <06175660-15BF-4F82-82AE-C841C8C2D174@macports.org> References: <8DCE25EA-5E75-4E99-8EE0-A5DA60C67EC7@mac.com> <4AD98C1C.2040405@macports.org> <7F284633-04C5-4E98-AE33-7654CA23831D@mac.com> <06175660-15BF-4F82-82AE-C841C8C2D174@macports.org> Message-ID: On 2009-10-22 , at 18:25 , Ryan Schmidt wrote: > I guess they've fixed that already; this is what I get on Snow > Leopard: > > > $ /usr/bin/make -dp | grep INCLUDE > make: *** No targets specified and no makefile found. Stop. > .INCLUDE_DIRS = /usr/include /usr/include Snow Leopard here. This is what I see face at mac:~:124 $ /usr/bin/make -dp | grep INCLUDE make: *** No targets specified and no makefile found. Stop. .INCLUDE_DIRS = /usr/include /usr/local/include /usr/include The deal is - if /usr/local/include *exists* it will be included mac:~ root# echo $PATH /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin mac:~ root# /usr/bin/make -dp | grep INCLUDE make: *** No targets specified and no makefile found. Stop. .INCLUDE_DIRS = /usr/include /usr/local/include /usr/include mac:~ root# mv /usr/local/include /usr/local/no-include mac:~ root# /usr/bin/make -dp | grep INCLUDE make: *** No targets specified and no makefile found. Stop. .INCLUDE_DIRS = /usr/include /usr/include mac:~ root# 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From domiman at gmail.com Fri Oct 23 06:29:28 2009 From: domiman at gmail.com (Dominik Reichardt) Date: Fri, 23 Oct 2009 15:29:28 +0200 Subject: glibtool vs libtool Message-ID: <0C612F6F-E7BE-4C11-8D18-CDD744D7D583@gmail.com> Hi all, I have the port libtool (2.2.6a_0) installed. But that only gives me glibtool/glibtoolize. Now I have encountered some programs that I compile myself that need libtool/libtoolize. For those I have simply symlinked glibtool/glibtoolize to libtool/ize. My questions are, - will I run into problems because of doing that? - why is it that some need libtool/ize and others are contend with glibtool/ize? Thanks Domiinik From buffyg at mac.com Fri Oct 23 06:32:00 2009 From: buffyg at mac.com (Bayard Bell) Date: Fri, 23 Oct 2009 14:32:00 +0100 Subject: include problem building BDB 4.6.21 w/ /usr/local In-Reply-To: References: <8DCE25EA-5E75-4E99-8EE0-A5DA60C67EC7@mac.com> <4AD98C1C.2040405@macports.org> <7F284633-04C5-4E98-AE33-7654CA23831D@mac.com> <06175660-15BF-4F82-82AE-C841C8C2D174@macports.org> Message-ID: <0A68D0BB-942E-4432-B755-A10776987024@mac.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 That makes sense of the dtruss output that showed the default paths being stat()'ed very early in starting make. Am 23 Oct 2009 um 14:20 schrieb Chris Janton: > On 2009-10-22 , at 18:25 , Ryan Schmidt wrote: > >> I guess they've fixed that already; this is what I get on Snow >> Leopard: >> >> >> $ /usr/bin/make -dp | grep INCLUDE >> make: *** No targets specified and no makefile found. Stop. >> .INCLUDE_DIRS = /usr/include /usr/include > > Snow Leopard here. This is what I see > > face at mac:~:124 $ /usr/bin/make -dp | grep INCLUDE > make: *** No targets specified and no makefile found. Stop. > .INCLUDE_DIRS = /usr/include /usr/local/include /usr/include > > The deal is - if /usr/local/include *exists* it will be included > > mac:~ root# echo $PATH > /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin > mac:~ root# /usr/bin/make -dp | grep INCLUDE > make: *** No targets specified and no makefile found. Stop. > .INCLUDE_DIRS = /usr/include /usr/local/include /usr/include > mac:~ root# mv /usr/local/include /usr/local/no-include > mac:~ root# /usr/bin/make -dp | grep INCLUDE > make: *** No targets specified and no makefile found. Stop. > .INCLUDE_DIRS = /usr/include /usr/include > mac:~ root# > > 8) > ---------------------------------- > Chris Janton - face at CentosPrime dot COM > Netminder for Opus1.COM > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (Darwin) iEYEARECAAYFAkrhsFAACgkQcZQHT1XL9xmo0wCgqEXKuLej+ne/uE5/m1mwDmoQ PlwAnjjJ52o8jOCFq/WZJ71JP95AuNzC =Qfum -----END PGP SIGNATURE----- From jmr at macports.org Fri Oct 23 08:17:48 2009 From: jmr at macports.org (Joshua Root) Date: Sat, 24 Oct 2009 02:17:48 +1100 Subject: include problem building BDB 4.6.21 w/ /usr/local In-Reply-To: <7F284633-04C5-4E98-AE33-7654CA23831D@mac.com> References: <8DCE25EA-5E75-4E99-8EE0-A5DA60C67EC7@mac.com> <4AD98C1C.2040405@macports.org> <7F284633-04C5-4E98-AE33-7654CA23831D@mac.com> Message-ID: <4AE1C91C.7080306@macports.org> On 2009-10-23 11:07, Bayard Bell wrote: > Did a bit more digging. The problem looks to be with Apple's build of > make. Extracted from "make -dp" output: > > # default > .INCLUDE_DIRS = /usr/include /usr/local/include /usr/include >From the make manual: .INCLUDE_DIRS Expands to a list of directories that make searches for included makefiles This does not affect the C preprocessor at all. - Josh From buffyg at mac.com Fri Oct 23 08:20:09 2009 From: buffyg at mac.com (Bayard Bell) Date: Fri, 23 Oct 2009 16:20:09 +0100 Subject: include problem building BDB 4.6.21 w/ /usr/local In-Reply-To: <4AE1C91C.7080306@macports.org> References: <8DCE25EA-5E75-4E99-8EE0-A5DA60C67EC7@mac.com> <4AD98C1C.2040405@macports.org> <7F284633-04C5-4E98-AE33-7654CA23831D@mac.com> <4AE1C91C.7080306@macports.org> Message-ID: <54866473-8B91-48A2-8331-58B973165CD7@mac.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hmm. Digging will continue. I'll look into modifications to dtruss to capture more of the environment and args. Am 23 Oct 2009 um 16:17 schrieb Joshua Root: > On 2009-10-23 11:07, Bayard Bell wrote: >> Did a bit more digging. The problem looks to be with Apple's build of >> make. Extracted from "make -dp" output: >> >> # default >> .INCLUDE_DIRS = /usr/include /usr/local/include /usr/include > > From the make manual: > .INCLUDE_DIRS > Expands to a list of directories that make searches for included > makefiles > > This does not affect the C preprocessor at all. > > - Josh -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (Darwin) iEYEARECAAYFAkrhybgACgkQcZQHT1XL9xmFZQCeM4zqbeCn6xQzr3wOU5xlE2eD j+sAoLzvo9XDL3omC8deJoviyMM8Jj91 =d1Q2 -----END PGP SIGNATURE----- From jmr at macports.org Fri Oct 23 08:54:13 2009 From: jmr at macports.org (Joshua Root) Date: Sat, 24 Oct 2009 02:54:13 +1100 Subject: include problem building BDB 4.6.21 w/ /usr/local In-Reply-To: <54866473-8B91-48A2-8331-58B973165CD7@mac.com> References: <8DCE25EA-5E75-4E99-8EE0-A5DA60C67EC7@mac.com> <4AD98C1C.2040405@macports.org> <7F284633-04C5-4E98-AE33-7654CA23831D@mac.com> <4AE1C91C.7080306@macports.org> <54866473-8B91-48A2-8331-58B973165CD7@mac.com> Message-ID: <4AE1D1A5.3030000@macports.org> On 2009-10-24 02:20, Bayard Bell wrote: > Hmm. Digging will continue. I'll look into modifications to dtruss to > capture more of the environment and args. Like I said, it's a gcc thing. The list of default include paths is defined here: As you can see, LOCAL_INCLUDE_DIR is in there, which is defined in: as '$(local_prefix)/include', where local_prefix comes from: and defaults to /usr/local. - Josh From buffyg at mac.com Fri Oct 23 08:59:00 2009 From: buffyg at mac.com (Bayard Bell) Date: Fri, 23 Oct 2009 16:59:00 +0100 Subject: include problem building BDB 4.6.21 w/ /usr/local In-Reply-To: <4AE1D1A5.3030000@macports.org> References: <8DCE25EA-5E75-4E99-8EE0-A5DA60C67EC7@mac.com> <4AD98C1C.2040405@macports.org> <7F284633-04C5-4E98-AE33-7654CA23831D@mac.com> <4AE1C91C.7080306@macports.org> <54866473-8B91-48A2-8331-58B973165CD7@mac.com> <4AE1D1A5.3030000@macports.org> Message-ID: <2D7DF258-99A9-4978-B426-60EF7B801255@mac.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks, Josh. I was trying to confirm that all the reported details were supported in the bug report by using the dtruss output, which wasn't as clean as plain old truss. I was struggling with that, but this is exactly the information I needed to feel comfortable with the submission. Am 23 Oct 2009 um 16:54 schrieb Joshua Root: > On 2009-10-24 02:20, Bayard Bell wrote: >> Hmm. Digging will continue. I'll look into modifications to dtruss to >> capture more of the environment and args. > > Like I said, it's a gcc thing. The list of default include paths is > defined here: > > > > As you can see, LOCAL_INCLUDE_DIR is in there, which is defined in: > > > > as '$(local_prefix)/include', where local_prefix comes from: > > > > and defaults to /usr/local. > > - Josh -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (Darwin) iEYEARECAAYFAkrh0ssACgkQcZQHT1XL9xlxnwCfQEwPSyTRhhVazwN40/F3Gtt+ fwkAniIFKyKfBccYhLBfPiWoSMK+qtUy =Ev35 -----END PGP SIGNATURE----- From i.cue at dsl.pipex.com Fri Oct 23 10:51:40 2009 From: i.cue at dsl.pipex.com (Mine) Date: Fri, 23 Oct 2009 18:51:40 +0100 Subject: Lost links to macPorts Message-ID: Hi, I recently had some problems with my system and had to reinstall it, now it appears that I have lost links to macPorts. I first noticed a problem when I opened Porticus and found that a lot of my ports were outdated and I could not update them. I used Terminal to try and get a list of port and got the following error: $ port list can't find package macports while executing "package require macports" (file "/opt/local/bin/port" line 39) I searched for macPorts in the finder and found that there are macPorts folder in opt/local/etc, opt/local/var, opt/local/share, etc., so I assume macPorts is still installed. Is there a way to relink to macPorts. Alternatively, if I install the latest version of macPorts will it over-write the current version? Thanks, Terrence -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Fri Oct 23 11:45:04 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 23 Oct 2009 13:45:04 -0500 Subject: Lost links to macPorts In-Reply-To: References: Message-ID: On Oct 23, 2009, at 12:51, Mine wrote: > I recently had some problems with my system and had to reinstall it, > now it appears that I have lost links to macPorts. I first noticed a > problem when I opened Porticus and found that a lot of my ports were > outdated and I could not update them. I used Terminal to try and get a > list of port and got the following error: > > $ port list > can't find package macports > while executing > "package require macports" > (file "/opt/local/bin/port" line 39) > > I searched for macPorts in the finder and found that there are > macPorts > folder in opt/local/etc, opt/local/var, opt/local/share, etc., so I > assume > macPorts is still installed. Is there a way to relink to macPorts. > Alternatively, > if I install the latest version of macPorts will it over-write the > current version? It sounds like you've lost the directory /Library/Tcl/macports1.0. I recommend you download the latest MacPorts disk image for your OS from www.macports.org and install it. It will replace that directory and update you to the latest, while not touching any ports you have installed. Then you can "port outdated" and "sudo port upgrade" things, or use Porticus, to get your ports upgraded. From ryandesign at macports.org Fri Oct 23 11:49:59 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 23 Oct 2009 13:49:59 -0500 Subject: glibtool vs libtool In-Reply-To: <0C612F6F-E7BE-4C11-8D18-CDD744D7D583@gmail.com> References: <0C612F6F-E7BE-4C11-8D18-CDD744D7D583@gmail.com> Message-ID: <2B857854-33DB-415C-B772-B0CF137AF03E@macports.org> On Oct 23, 2009, at 08:29, Dominik Reichardt wrote: > I have the port libtool (2.2.6a_0) installed. But that only gives me > glibtool/glibtoolize. Now I have encountered some programs that I > compile myself that need libtool/libtoolize. For those I have simply > symlinked glibtool/glibtoolize to libtool/ize. > My questions are, > - will I run into problems because of doing that? > > - why is it that some need libtool/ize and others are contend with > glibtool/ize? The difference, of course, is that glibtool/glibtoolize is definitely the GNU version of libtool, while on Mac OS X libtool/libtoolize happen not to be, while on some other OSes like maybe Linux, libtool/ libtoolize are the GNU version. Some software written with Linux in mind might assume libtool/libtoolize are GNU, and have problems when they're not, like on Mac OS X. When we encounter software like that in MacPorts and are writing ports for them, we often patch the configure script (or whatever is looking for libtool/libtoolize) and change it to look for glibtool/ glibtoolize. Or sometimes there are environment variables (e.g. LIBTOOL) that can be set. Other times we symlink glibtool into the worksrcpath as libtool. If it's easier for you, you can create global symlinks libtool/ libtoolize linked to glibtool/glibtoolize if you promise to remove them after successfully compiling your software. I would not recommend leaving these links in place, because yet other software might detect it's running on Mac OS X and assume libtool/libtoolize are not GNU, and have problems if they are. From i.cue at dsl.pipex.com Fri Oct 23 12:22:32 2009 From: i.cue at dsl.pipex.com (Mine) Date: Fri, 23 Oct 2009 20:22:32 +0100 Subject: Lost links to macPorts In-Reply-To: References: Message-ID: Hi Ryan, I have installed the latest version of macPorts. "port upgrade" gave me a list of outdated ports, but "sudo port upgrade" gave the following error: Can't map the URL 'file://.' to a port description file ("Could not find Portfile in /Users/mycomputer"). Please verify that the directory and portfile syntax are correct. To use the current port, you must be in a port's directory. (you might also see this message if a pseudo-port such as outdated or installed expands to no ports). Not sure how to solve this error. Thanks, Terrence On 23 Oct 2009, at 19:45, Ryan Schmidt wrote: > > On Oct 23, 2009, at 12:51, Mine wrote: > >> I recently had some problems with my system and had to reinstall it, >> now it appears that I have lost links to macPorts. I first noticed a >> problem when I opened Porticus and found that a lot of my ports were >> outdated and I could not update them. I used Terminal to try and >> get a >> list of port and got the following error: >> >> $ port list >> can't find package macports >> while executing >> "package require macports" >> (file "/opt/local/bin/port" line 39) >> >> I searched for macPorts in the finder and found that there are >> macPorts >> folder in opt/local/etc, opt/local/var, opt/local/share, etc., so >> I assume >> macPorts is still installed. Is there a way to relink to macPorts. >> Alternatively, >> if I install the latest version of macPorts will it over-write the >> current version? > > It sounds like you've lost the directory /Library/Tcl/macports1.0. > > I recommend you download the latest MacPorts disk image for your OS > from www.macports.org and install it. It will replace that > directory and update you to the latest, while not touching any > ports you have installed. Then you can "port outdated" and "sudo > port upgrade" things, or use Porticus, to get your ports upgraded. > From ryandesign at macports.org Fri Oct 23 12:27:37 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 23 Oct 2009 14:27:37 -0500 Subject: Lost links to macPorts In-Reply-To: References: Message-ID: On Oct 23, 2009, at 14:22, Mine wrote: > I have installed the latest version of macPorts. > "port upgrade" gave me a list of outdated ports, but "sudo port > upgrade" > gave the following error: > > Can't map the URL 'file://.' to a port description file ("Could not > find Portfile in /Users/mycomputer"). > Please verify that the directory and portfile syntax are correct. > To use the current port, you must be in a port's directory. > (you might also see this message if a pseudo-port such as > outdated or installed expands to no ports). > > Not sure how to solve this error. You didn't tell it what port to upgrade. Use e.g. "sudo port upgrade zlib" to upgrade zlib. Or if you're sure you want to upgrade everything, you can try "sudo port upgrade outdated" to upgrade all outdated ports. From jasperfrumau at gmail.com Fri Oct 23 21:42:32 2009 From: jasperfrumau at gmail.com (Jasper Frumau) Date: Sat, 24 Oct 2009 11:42:32 +0700 Subject: Gedit Gconf Socket path and RANDR Therrors at launch Message-ID: <56cc1b0a0910232142o48dc7d29w720c807a4382cdef@mail.gmail.com> I posted about errors I keep getting when I launch Gedit from the Terminal. After an uninstall reinstall The error messages changed a bit but there are still several that are excacly the same and I don't know how to remedy this. These are the current errors: me-macbook-pro:Desktop me$ gedit Xlib: extension "RANDR" missing on display "/tmp/launch-mo9MMj/:0". Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Not enough memory) Orbit and Orbit2 are installed as is xorg-libXrandr @1.3.0_1 (active). How do I check if TCP/IP networking is enabled for Orbit? What is a stale NFS? How do I verify that org.freedesktop.dbus-session.plist is loaded? Thanks for any help you guys can provide me with. Jasper -------------- next part -------------- An HTML attachment was scrubbed... URL: From talklists at newgeo.com Fri Oct 23 22:20:56 2009 From: talklists at newgeo.com (Scott Haneda) Date: Fri, 23 Oct 2009 22:20:56 -0700 Subject: Gedit Gconf Socket path and RANDR Therrors at launch In-Reply-To: <56cc1b0a0910232142o48dc7d29w720c807a4382cdef@mail.gmail.com> References: <56cc1b0a0910232142o48dc7d29w720c807a4382cdef@mail.gmail.com> Message-ID: <46F9ABB5-FF2D-44EA-B5C9-BC55F22BF2D3@newgeo.com> On Oct 23, 2009, at 9:42 PM, Jasper Frumau wrote: > How do I verify that org.freedesktop.dbus-session.plist is loaded? This is the only one of your questions I know. In your shell: sudo launchctl list | grep 'freedesktop' If it comes back empty, it is not loaded, if it comes back with a result, it is, see the man page for what each column means. You can load it with sudo launchctl load /Library/LaunchAgents/org.freedesktop.dbus- session.plist Or, if it has the disabled key set, which you can see by looking at the file at the path listed below, you will need to add the -w flag to write it enabled... sudo launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus- session.plist Conversely, you can unload it, so that it will not reload even after a reboot with sudo launchctl unload -w /Library/LaunchAgents/org.freedesktop.dbus- session.plist The rest of your issues are beyond my knowledge, but if I had to wager I guess, I would start googling how to resolve this error: Xlib: extension "RANDR" missing on display "/tmp/launch-mo9MMj/:0". -- Scott * If you contact me off list replace talklists@ with scott@ * From ryandesign at macports.org Fri Oct 23 23:29:00 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 24 Oct 2009 01:29:00 -0500 Subject: Gedit Gconf Socket path and RANDR Therrors at launch In-Reply-To: <46F9ABB5-FF2D-44EA-B5C9-BC55F22BF2D3@newgeo.com> References: <56cc1b0a0910232142o48dc7d29w720c807a4382cdef@mail.gmail.com> <46F9ABB5-FF2D-44EA-B5C9-BC55F22BF2D3@newgeo.com> Message-ID: On Oct 24, 2009, at 00:20, Scott Haneda wrote: > The rest of your issues are beyond my knowledge, but if I had to > wager I guess, I would start googling how to resolve this error: > Xlib: extension "RANDR" missing on display "/tmp/launch-mo9MMj/:0". The missing RANDR extension warning is harmless. It will occur with every X program you try to use on Mac OS X. Ignore it. It is not related to the problem you're experiencing. http://www.nabble.com/Xlib:--extension-%22RANDR%22-missing-on-display-%22-tmp-launch-zP0Uvj-:0%22.-td23585151.html From ryandesign at macports.org Fri Oct 23 23:43:31 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 24 Oct 2009 01:43:31 -0500 Subject: Gedit Gconf Socket path and RANDR Therrors at launch In-Reply-To: References: <56cc1b0a0910232142o48dc7d29w720c807a4382cdef@mail.gmail.com> <46F9ABB5-FF2D-44EA-B5C9-BC55F22BF2D3@newgeo.com> Message-ID: <6C046467-5EE9-4D14-A930-09233D008DCE@macports.org> On Oct 24, 2009, at 01:29, Ryan Schmidt wrote: > The missing RANDR extension warning is harmless. It will occur with > every X program you try to use on Mac OS X. Ignore it. It is not > related to the problem you're experiencing. I've now added a FAQ entry about this. http://trac.macports.org/wiki/FAQ#randr From ludwig at fh-worms.de Sat Oct 24 09:43:55 2009 From: ludwig at fh-worms.de (Christoph Ludwig) Date: Sat, 24 Oct 2009 18:43:55 +0200 Subject: mutt-devel fix for incompatibility with gpgme 1.2.0 (Ticket #22009) Message-ID: <20091024164354.GA10888@castellio.local> Hi, the current mutt-devel port generates runtime errors if used with variant +gpgme. The reason is that gpgme requires since release 1.2.0 that applications call gpgme_check_version() at least once before they call any gpgme operations. mutt 1.5.20 fails to do so whence it will abort as soon as the user tries to open any signed or encrypted email. (Presuming that mutt is configured to use the GPGME backend, of course, but that's likely if the user asked for the gpgme variant when he installed the mutt-devel port.) Ticket #22009 (created 2009-10-12) has a patch that fixes the issue. It has not yet been applied, though. The mutt-devel port is marked as "openmaintainer"; may I therefore ask that someone with the necessary privileges reviews and commits the patch? FWIW, I use it on my notebook without problems. Thanks a lot! Christoph From jasperfrumau at gmail.com Sat Oct 24 20:55:52 2009 From: jasperfrumau at gmail.com (Jasper Frumau) Date: Sun, 25 Oct 2009 10:55:52 +0700 Subject: Gedit Gconf Socket path and RANDR Therrors at launch In-Reply-To: <6C046467-5EE9-4D14-A930-09233D008DCE@macports.org> References: <56cc1b0a0910232142o48dc7d29w720c807a4382cdef@mail.gmail.com> <46F9ABB5-FF2D-44EA-B5C9-BC55F22BF2D3@newgeo.com> <6C046467-5EE9-4D14-A930-09233D008DCE@macports.org> Message-ID: <56cc1b0a0910242055u3c7d9cb5i367e618beda52cda@mail.gmail.com> Thanks Ryan. Ar least that is something I don't have to worry about. On Sat, Oct 24, 2009 at 1:43 PM, Ryan Schmidt wrote: > > On Oct 24, 2009, at 01:29, Ryan Schmidt wrote: > > The missing RANDR extension warning is harmless. It will occur with every >> X program you try to use on Mac OS X. Ignore it. It is not related to the >> problem you're experiencing. >> > > I've now added a FAQ entry about this. > > http://trac.macports.org/wiki/FAQ#randr > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jasperfrumau at gmail.com Sat Oct 24 21:02:55 2009 From: jasperfrumau at gmail.com (Jasper Frumau) Date: Sun, 25 Oct 2009 11:02:55 +0700 Subject: Gedit Gconf Socket path and RANDR Therrors at launch In-Reply-To: <46F9ABB5-FF2D-44EA-B5C9-BC55F22BF2D3@newgeo.com> References: <56cc1b0a0910232142o48dc7d29w720c807a4382cdef@mail.gmail.com> <46F9ABB5-FF2D-44EA-B5C9-BC55F22BF2D3@newgeo.com> Message-ID: <56cc1b0a0910242102p61482c2dw23ff0cace2de7f7b@mail.gmail.com> Thanks Scott. It is loaded now for non sudo users. When I want to start Gedit as sudo user to work on a restricted file I get the same errors again. I tried to add the rg.freedesktop.dbus-session.plist before with sudo, but then it did not allow me because it was already loaded which is proven here: me-macbook-pro:bin me$ sudo launchctl list | grep 'freedesktop' Password: 43 - org.freedesktop.dbus-system So how can I add it so it works for me as sudo user and normal user? On Sat, Oct 24, 2009 at 12:20 PM, Scott Haneda wrote: > On Oct 23, 2009, at 9:42 PM, Jasper Frumau wrote: > > How do I verify that org.freedesktop.dbus-session.plist is loaded? >> > > This is the only one of your questions I know. In your shell: > sudo launchctl list | grep 'freedesktop' > > If it comes back empty, it is not loaded, if it comes back with a result, > it is, see the man page for what each column means. > > You can load it with > sudo launchctl load > /Library/LaunchAgents/org.freedesktop.dbus-session.plist > > Or, if it has the disabled key set, which you can see by looking at the > file at the path listed below, you will need to add the -w flag to write it > enabled... > sudo launchctl load -w > /Library/LaunchAgents/org.freedesktop.dbus-session.plist > > Conversely, you can unload it, so that it will not reload even after a > reboot with > sudo launchctl unload -w > /Library/LaunchAgents/org.freedesktop.dbus-session.plist > > The rest of your issues are beyond my knowledge, but if I had to wager I > guess, I would start googling how to resolve this error: > > Xlib: extension "RANDR" missing on display "/tmp/launch-mo9MMj/:0". > -- > Scott * If you contact me off list replace talklists@ with scott@ * > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cssdev at mac.com Sun Oct 25 05:09:00 2009 From: cssdev at mac.com (Chris Scharver) Date: Sun, 25 Oct 2009 08:09:00 -0400 Subject: unison 2.32 declared stable In-Reply-To: References: <20091016133415.GB5131@marco.fz-rossendorf.de> Message-ID: <6575F860-20A6-4713-B583-5D99E92AA55B@mac.com> On Oct 20, 2009, at 4:20 AM, joerg van den hoff wrote: > On Tue, 20 Oct 2009 04:25:33 +0200, wrote: > >> On Oct 16, 2009, at 9:34 AM, Joerg van den Hoff wrote: >> >>> unison 2.32 has been finally declared stable a few weeks ago. any >>> chance >>> to see this version soon in macports? >> >> It looks like it takes some patching to get 2.32 to work properly >> on Snow Leopard. See http://trac.macports.org/ticket/21862 > > thanks for responding. but the ticket seems to say that it refers to > a problem with 2.27 on snow leopard which could be fixed by moving > to 2.32? > the problem being related to the aqua interface? > > well, I would be happy with a command line only anyway (and for the > time being for 10.4.11...) There appear to be some extra patches required to make 2.32 compile on Snow Leopard. I had to apply the patches in the ticket just to get the command line version to compile. But it worked, although the compatibility problems with previous versions might give pause to committing the new version. Chris From flylm.ml at gmail.com Mon Oct 26 06:26:37 2009 From: flylm.ml at gmail.com (FlyLM [ML]) Date: Mon, 26 Oct 2009 14:26:37 +0100 Subject: Keep the MySQL 5.0.x branche installed Message-ID: Hi, I notice that macports wants to update MySQL 5.0.x to 5.1.40. I wonder if developers have planned a way to keep the install of the MySQL 5.0.x possible (a port named mysql50 ???) ? I would like to stay as near as the configuration my production host. Thx From d.l.tDeContes at free.fr Mon Oct 26 07:55:08 2009 From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=) Date: Mon, 26 Oct 2009 15:55:08 +0100 Subject: readline In-Reply-To: References: <06BA46CE-8BF3-49DB-A717-75D870FF632F@macports.org> Message-ID: Le 15 oct. 09 ? 18:37, Ryan Schmidt a ?crit : >> is it possible to upgrade readline nevertheless ? > > You could apply the patch I attached to that ticket, and rebuild > MacPorts. > > I would like to resolve this issue for MacPorts 1.8.2, and am > awaiting feedback on whether or not this patch should be applied or > if there is another solution. thank you :-) is there a date for MacPorts 1.8.2 ? -- T?l?assistance / T?l?maintenance http://www.portparallele.com/ThomasDECONTES/ From bjorn at swift.is Mon Oct 26 10:41:13 2009 From: bjorn at swift.is (=?ISO-8859-1?Q?Bj=F6rn_Swift?=) Date: Mon, 26 Oct 2009 18:41:13 +0100 Subject: Problems installing i386-elf-gcc on Snow Leopard Message-ID: I've been trying to get i386-elf-gcc working on my machine, without much luck. 1) i386-elf-binutils Failed with: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_cross_i386-elf-binutils/work/binutils-2.18.50.0.9/binutils/strings.c:100:8: Fixed by editing string.c, as described in http://thread.gmane.org/gmane.os.apple.macports.user/16155 2) i386-elf-gcc Had to patch Make-lang.in, like http://trac.macports.org/changeset/57794 does for lang/gcc43, and update the Portfile, like http://trac.macports.org/changeset/59653 does for cross/i386-mingw32-gcc. I suppose these should be ported to i386-elf-gcc, right? If so, I can provide patch were that to be of interest. After this, the compilation succeeded, but then I got the following error: ---> Activating i386-elf-gcc @4.3.2_0 Error: Unable to execute port: Image error: /opt/local/lib/x86_64/libiberty.a is being used by the active i386-elf-binutils port. Please deactivate this port first, or use 'port -f activate i386-elf-gcc' to force the activation. I decided to force the activation, without really knowing the consequences. That seemed to work. I tried two gcc binaries (see below), both of which throw errors. One can't find cc1 and the other crt0.o: $ /opt/local/i386-elf/bin/gcc -o test-i386 test-i386.c gcc: error trying to exec 'cc1': execvp: No such file or directory $ /opt/local/bin/i386-elf-gcc-4.3.2 -o test-i386 test-i386.c /opt/local/lib/gcc/i386-elf/4.3.2/../../../../i386-elf/bin/ld: crt0.o: No such file: No such file or directory collect2: ld returned 1 exit status Does anyone have any ideas? Thanks in advance, Bjorn Swift From darrell.usenet7 at telus.net Mon Oct 26 11:56:41 2009 From: darrell.usenet7 at telus.net (darrellgreenwood) Date: Mon, 26 Oct 2009 11:56:41 -0700 (PDT) Subject: trafshow on Snow Leopard In-Reply-To: <64ee80170910181308ga875202pfc79a6a6bcc77e8c@mail.gmail.com> References: <64ee80170910181308ga875202pfc79a6a6bcc77e8c@mail.gmail.com> Message-ID: <26065414.post@talk.nabble.com> Konstantin Fomin wrote: > > Hello, all, > > I have a problem running the trafshow on MBP5.5 Mac OS 10.6.1. > Installed from the latest macports. > > After the startup it does not show packets on the interface. > > Sometimes, rarely tcp flows appear for a couple of seconds and then > again blank screen as there is no traffic. > > I just installed* trafshow from the latest macports. I have the same problem. Leopard 10.5.8, iBook G4. Also looking for any hints or solution. Cheers, Darrell *trafshow Version 5.2.3 compiled for powerpc-apple-darwin9.8.0 with /usr/bin/gcc-4.0 -O2 -I/opt/local/include -arch ppc -Wall -I. -DHAVE_CONFIG_H -lncurses -ltermcap -lpcap -lresolv libpcap version 1.0.0 ncurses version 5.5 colors support your current terminal has color capability MacPorts 1.8.1 -- View this message in context: http://www.nabble.com/trafshow-on-Snow-Leopard-tp25949946p26065414.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From ryandesign at macports.org Mon Oct 26 12:44:30 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 26 Oct 2009 14:44:30 -0500 Subject: Keep the MySQL 5.0.x branche installed In-Reply-To: References: Message-ID: <3E617485-E224-4A4A-B5D8-E1B1CB862D3A@macports.org> On Oct 26, 2009, at 08:26, FlyLM [ML] wrote: > I notice that macports wants to update MySQL 5.0.x to 5.1.40. I wonder > if developers have planned a way to keep the install of the MySQL > 5.0.x possible (a port named mysql50 ???) ? I would like to stay as > near as the configuration my production host. No, I had not planned to do that. If enough people request it, I could reconsider. For now, you can simply not upgrade the port. For others who need 5.0 but have already upgraded to 5.1, or never had 5.0 installed while it was the current version, the wiki explains how to install it: http://trac.macports.org/wiki/howto/InstallingOlderPort From ryandesign at macports.org Mon Oct 26 12:45:02 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 26 Oct 2009 14:45:02 -0500 Subject: readline In-Reply-To: References: <06BA46CE-8BF3-49DB-A717-75D870FF632F@macports.org> Message-ID: On Oct 26, 2009, at 09:55, Thomas De Contes wrote: > > Le 15 oct. 09 ? 18:37, Ryan Schmidt a ?crit : > >>> is it possible to upgrade readline nevertheless ? >> >> You could apply the patch I attached to that ticket, and rebuild >> MacPorts. >> >> I would like to resolve this issue for MacPorts 1.8.2, and am >> awaiting feedback on whether or not this patch should be applied or >> if there is another solution. > > > thank you :-) > > is there a date for MacPorts 1.8.2 ? No, and we have not yet decided whether the patch I provided in that ticket is the correct solution to the problem. From jmr at macports.org Mon Oct 26 14:04:42 2009 From: jmr at macports.org (Joshua Root) Date: Tue, 27 Oct 2009 08:04:42 +1100 Subject: Problems installing i386-elf-gcc on Snow Leopard In-Reply-To: References: Message-ID: <4AE60EEA.6020407@macports.org> On 2009-10-27 04:41, Bj?rn Swift wrote: > I've been trying to get i386-elf-gcc working on my machine, without much luck. > > 1) i386-elf-binutils > > Failed with: > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_cross_i386-elf-binutils/work/binutils-2.18.50.0.9/binutils/strings.c:100:8: > > Fixed by editing string.c, as described in > http://thread.gmane.org/gmane.os.apple.macports.user/16155 > > 2) i386-elf-gcc > > Had to patch Make-lang.in, like > http://trac.macports.org/changeset/57794 does for lang/gcc43, and > update the Portfile, like http://trac.macports.org/changeset/59653 > does for cross/i386-mingw32-gcc. I suppose these should be ported to > i386-elf-gcc, right? If so, I can provide patch were that to be of > interest. I believe there are tickets for both of these in trac, which you should be able to find by searching. Please attach your patches to them. - Josh From bjorn at swift.is Mon Oct 26 14:49:08 2009 From: bjorn at swift.is (=?ISO-8859-1?Q?Bj=F6rn_Swift?=) Date: Mon, 26 Oct 2009 22:49:08 +0100 Subject: Problems installing i386-elf-gcc on Snow Leopard In-Reply-To: <4AE60EEA.6020407@macports.org> References: <4AE60EEA.6020407@macports.org> Message-ID: Hey Joshua 2009/10/26 Joshua Root : > I believe there are tickets for both of these in trac, which you should > be able to find by searching. Please attach your patches to them. Could you be referring to #20816 and #21194? Both of these are closed and refer to ports other than i386-elf-gcc. Should I still attach patches to those tickets, rather than opening a new ticket? In any case, I'd prefer to get the compiler working before submitting a patch - just in case anything else needs to be added to the patch. Do you have any idea what could be causing the cc1 or crt0.o errors described in my previous email? Thanks for your time, Bj?rn Swift From jmr at macports.org Mon Oct 26 15:25:20 2009 From: jmr at macports.org (Joshua Root) Date: Tue, 27 Oct 2009 09:25:20 +1100 Subject: Problems installing i386-elf-gcc on Snow Leopard In-Reply-To: References: <4AE60EEA.6020407@macports.org> Message-ID: <4AE621D0.10504@macports.org> On 2009-10-27 08:49, Bj?rn Swift wrote: > Hey Joshua > > 2009/10/26 Joshua Root : >> I believe there are tickets for both of these in trac, which you should >> be able to find by searching. Please attach your patches to them. > > Could you be referring to #20816 and #21194? Both of these are closed > and refer to ports other than i386-elf-gcc. Should I still attach > patches to those tickets, rather than opening a new ticket? The open tickets about these ports that I was thinking of are: (looks like the one you want) (looks like the other one) I found these using the "Ticket Search" link that is on the left of every trac page. > In any case, I'd prefer to get the compiler working before submitting > a patch - just in case anything else needs to be added to the patch. Better a partial patch submitted than none. The maintainer may be able to work out the rest of what needs to be done more easily once these initial problems are taken care of. > Do you have any idea what could be causing the cc1 or crt0.o errors > described in my previous email? No, sorry. - Josh From bjorn at swift.is Mon Oct 26 16:45:58 2009 From: bjorn at swift.is (=?ISO-8859-1?Q?Bj=F6rn_Swift?=) Date: Tue, 27 Oct 2009 00:45:58 +0100 Subject: Problems installing i386-elf-gcc on Snow Leopard In-Reply-To: <4AE621D0.10504@macports.org> References: <4AE60EEA.6020407@macports.org> <4AE621D0.10504@macports.org> Message-ID: 2009/10/26 Joshua Root : > The open tickets about these ports that I was thinking of are: > (looks like the one you want) > > > (looks like the other one) I've updated tickets #21411, #21706 and #21682 - #18161 seems to be something else. > I found these using the "Ticket Search" link that is on the left of > every trac page. Yes, sorry about that. I'd seen these before, but then somehow forgot and .. hmm. > Better a partial patch submitted than none. The maintainer may be able > to work out the rest of what needs to be done more easily once these > initial problems are taken care of. Fair enough. As I used the patches from the previous changesets to other ports unchanged, I referred to those changesets instead of copy pasting the patch. >> Do you have any idea what could be causing the cc1 or crt0.o errors >> described in my previous email? > > No, sorry. Alright, I'll keep my fingers crossed. Thanks for your time, Bjorn Swift From brooks at clarksonline.net Mon Oct 26 20:52:38 2009 From: brooks at clarksonline.net (M. Brooks Clark) Date: Mon, 26 Oct 2009 22:52:38 -0500 Subject: php5-gd: imagettftext -- can't find fonts Message-ID: I have installed php5 and php5-gd, and I'm now getting an error when I try to use the imagettftext() function: Warning: imagettfbbox(): Could not find/open font in /Users/mbclark/ Sites/wview/banner.php on line 32 Warning: imagettftext(): Could not find/open font in /Users/mbclark/ Sites/wview/banner.php on line 35 I've set the fontfile location to '/Library/Fonts/Arial' and '/Library/ Fonts/Arial.ttf', but neither of these variations seems to work. Is there another trick to specifying the fontfile? Brooks http://www.clarkwx.net ________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From talklists at newgeo.com Mon Oct 26 23:28:26 2009 From: talklists at newgeo.com (Scott Haneda) Date: Mon, 26 Oct 2009 23:28:26 -0700 Subject: php5-gd: imagettftext -- can't find fonts In-Reply-To: References: Message-ID: Have you checked the permissions on the files to be sure the www server can read them? Set them to use and group of the www server, and for now, chmod 777 as a test. If that works, restrict them back down to your liking for your setup. -- Scott * If you contact me off list replace talklists@ with scott@ * On Oct 26, 2009, at 8:52 PM, M. Brooks Clark wrote: > I have installed php5 and php5-gd, and I'm now getting an error when > I try to use the imagettftext() function: > > Warning: imagettfbbox(): Could not find/open font in /Users/mbclark/ > Sites/wview/banner.php on line 32 > > Warning: imagettftext(): Could not find/open font in /Users/mbclark/ > Sites/wview/banner.php on line 35 > > I've set the fontfile location to '/Library/Fonts/Arial' and '/ > Library/Fonts/Arial.ttf', but neither of these variations seems to > work. Is there another trick to specifying the fontfile? > From ryandesign at macports.org Mon Oct 26 23:51:41 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 27 Oct 2009 01:51:41 -0500 Subject: php5-gd: imagettftext -- can't find fonts In-Reply-To: References: Message-ID: <51280B8B-C091-4976-A458-D5A60F5B8158@macports.org> On Oct 26, 2009, at 22:52, M. Brooks Clark wrote: > I have installed php5 and php5-gd, and I'm now getting an error when > I try to use the imagettftext() function: > > Warning: imagettfbbox(): Could not find/open font in /Users/mbclark/ > Sites/wview/banner.php on line 32 > > Warning: imagettftext(): Could not find/open font in /Users/mbclark/ > Sites/wview/banner.php on line 35 > > I've set the fontfile location to '/Library/Fonts/Arial' and '/ > Library/Fonts/Arial.ttf', but neither of these variations seems to > work. Is there another trick to specifying the fontfile? I don't think there should be any trick. Where is the font file actually located -- /Library/Fonts/Arial or /Library/Fonts/Arial.ttf? What OS version is this? Have you tried other fonts? If you can't get it to work, can you post a snippet of PHP code that reproduces the problem, that I could try on my system? From vincent-opdarw at vinc17.org Tue Oct 27 14:21:23 2009 From: vincent-opdarw at vinc17.org (Vincent Lefevre) Date: Tue, 27 Oct 2009 22:21:23 +0100 Subject: MacPorts 1.8.1 has been released In-Reply-To: <4AC14BA8.8090807@macports.org> References: <4AC14BA8.8090807@macports.org> Message-ID: <20091027212123.GA17863@prunille.vinc17.org> On 2009-09-29 09:50:00 +1000, Joshua Root wrote: > If you already have MacPorts installed, the preferred method for > updating is to run: > > sudo port selfupdate On Tiger: [...] ===> making install in src/programs ===> making install in src/programs/daemondo mkdir -p build /usr/bin/install -c -o root -g admin -m 555 build/daemondo /opt/local/bin [ ! -f /opt/local/etc/macports/mp_version ] || rm -vf /opt/local/etc/macports/mp_version /usr/bin/install -c -o root -g admin -m 444 setupenv.bash /opt/local/share/macports/ /usr/bin/tclsh src/upgrade_sources_conf_default.tcl /opt/local couldn't execute "svn": no such file or directory while executing "while {[gets $sourcesConfChannel line] >= 0} { set addDefault false if {!$defaultSeen && ![regexp {^\s*#|^$} $line]} { if {[regexp {^([\w-..." (file "src/upgrade_sources_conf_default.tcl" line 34) make: *** [install] Error 1 zsh: exit 1 sudo port selfupdate -- Vincent Lef?vre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / Ar?naire project (LIP, ENS-Lyon) From brooks at clarksonline.net Tue Oct 27 15:23:15 2009 From: brooks at clarksonline.net (M. Brooks Clark) Date: Tue, 27 Oct 2009 17:23:15 -0500 Subject: php5-gd: imagettftext -- can't find fonts In-Reply-To: References: Message-ID: Thanks. Changing the /Library/Fonts directory and contents to group www did the trick. Brooks http://www.clarkwx.net ________________________ On Oct 27, 2009, at 1:28 AM, Scott Haneda wrote: > Have you checked the permissions on the files to be sure the www > server can read them? Set them to use and group of the www server, > and for now, chmod 777 as a test. If that works, restrict them back > down to your liking for your setup. From dcswest at gmail.com Tue Oct 27 16:56:44 2009 From: dcswest at gmail.com (Dennis C) Date: Tue, 27 Oct 2009 16:56:44 -0700 Subject: Bad CPU type in executable Message-ID: Greetings; Am in the process of making the switch from dual-boot PCs including FreeBSD, so kind of new to this, but am now running Snow Leopard and one of the first MacPorts I installed was psycopg2 and was able to run the python2.6 and successfully import the aforementioned module, but now the following's happening: DCSs-Mac-mini:bin DCSWest$ python2.6 -bash: /opt/local/bin/python2.6: Bad CPU type in executable So not quite sure what happened in between, but wondering if it wasn't something with the following attempt to update software: DCSs-Mac-mini:~ DCSWest$ sudo port selfupdate Password: ---> Updating the ports tree ---> Updating MacPorts base sources using rsync MacPorts base version 1.8.1 installed, MacPorts base version 1.8.1 downloaded. ---> MacPorts base is already the latest version The ports tree has been updated. To upgrade your installed ports, you should run port upgrade outdated DCSs-Mac-mini:~ DCSWest$ sudo port upgrade outdated ---> Computing dependencies for dbus ---> Configuring dbus Error: Target org.macports.configure returned: autoreconf failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_dbus/work/dbus-1.2.16" && autoreconf --install " returned error 126 Command output: sh: /opt/local/bin/autoreconf: /opt/local/bin/perl: bad interpreter: Bad CPU type in executable Error: Unable to upgrade port: 1 Thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Tue Oct 27 20:32:23 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 27 Oct 2009 22:32:23 -0500 Subject: Bad CPU type in executable In-Reply-To: References: Message-ID: <830DA4CA-FE4A-4847-AECB-A1992827D20E@macports.org> On Oct 27, 2009, at 18:56, Dennis C wrote: > Am in the process of making the switch from dual-boot PCs including > FreeBSD, so kind of new to this, but am now running Snow Leopard and > one of the first MacPorts I installed was psycopg2 and was able to > run the python2.6 and successfully import the aforementioned module, > but now the following's happening: > > DCSs-Mac-mini:bin DCSWest$ python2.6 > -bash: /opt/local/bin/python2.6: Bad CPU type in executable > > > So not quite sure what happened in between, but wondering if it > wasn't something with the following attempt to update software: > > DCSs-Mac-mini:~ DCSWest$ sudo port selfupdate > Password: > ---> Updating the ports tree > ---> Updating MacPorts base sources using rsync > MacPorts base version 1.8.1 installed, > MacPorts base version 1.8.1 downloaded. > ---> MacPorts base is already the latest version > > The ports tree has been updated. To upgrade your installed ports, > you should run > port upgrade outdated > > DCSs-Mac-mini:~ DCSWest$ sudo port upgrade outdated > ---> Computing dependencies for dbus > ---> Configuring dbus > Error: Target org.macports.configure returned: autoreconf failure: > shell command " cd "/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_dbus > /work/dbus-1.2.16" && autoreconf --install " returned error 126 > Command output: sh: /opt/local/bin/autoreconf: /opt/local/bin/perl: > bad interpreter: Bad CPU type in executable > > Error: Unable to upgrade port: 1 What kind of computer is this? I'm wondering if you have a 32-bit or 64-bit processor. All but the very first Macs have 64-bit processors. What is the architecture of, say, /opt/local/bin/perl? Use "lipo - info /opt/local/bin/perl" to find out. Did you recently upgrade to Snow Leopard -- or did you recently migrate your MacPorts installation from a different Mac -- and if so, did you uninstall and reinstall all ports? See the Migration page for more instructions: http://trac.macports.org/wiki/Migration From ryandesign at macports.org Tue Oct 27 20:38:46 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 27 Oct 2009 22:38:46 -0500 Subject: Bad CPU type in executable In-Reply-To: <830DA4CA-FE4A-4847-AECB-A1992827D20E@macports.org> References: <830DA4CA-FE4A-4847-AECB-A1992827D20E@macports.org> Message-ID: <3AF9B206-EA2F-4225-9A9F-D3C448390C62@macports.org> On Oct 27, 2009, at 22:32, Ryan Schmidt wrote: > What kind of computer is this? I'm wondering if you have a 32-bit or > 64-bit processor. All but the very first Macs have 64-bit processors. Um, what I was trying to say here was all Intel Macs except for the very first Intel Macs have 64-bit processors. From dcswest at gmail.com Wed Oct 28 07:31:53 2009 From: dcswest at gmail.com (Dennis C) Date: Wed, 28 Oct 2009 07:31:53 -0700 Subject: Bad CPU type in executable In-Reply-To: <3AF9B206-EA2F-4225-9A9F-D3C448390C62@macports.org> References: <830DA4CA-FE4A-4847-AECB-A1992827D20E@macports.org> <3AF9B206-EA2F-4225-9A9F-D3C448390C62@macports.org> Message-ID: It's a Mini Mac with an Intel Core 2 Duo CPU and also in response to the prior message, since I forgot to include the list, am reasonably assured that I downloaded the Snow Leopard "dmg" which I thought can only be for Intel like the OS itself and the ported programs did run at first, but how can I maybe confirm it? On Tue, Oct 27, 2009 at 8:38 PM, Ryan Schmidt wrote: > > On Oct 27, 2009, at 22:32, Ryan Schmidt wrote: > > What kind of computer is this? I'm wondering if you have a 32-bit or >> 64-bit processor. All but the very first Macs have 64-bit processors. >> > > Um, what I was trying to say here was all Intel Macs except for the very > first Intel Macs have 64-bit processors. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcswest at gmail.com Wed Oct 28 07:41:41 2009 From: dcswest at gmail.com (Dennis C) Date: Wed, 28 Oct 2009 07:41:41 -0700 Subject: Bad CPU type in executable In-Reply-To: <830DA4CA-FE4A-4847-AECB-A1992827D20E@macports.org> References: <830DA4CA-FE4A-4847-AECB-A1992827D20E@macports.org> Message-ID: Sorry I missed this part of the thread, but I'll check the Perl architecture as soon as I get back to the machine and I did purchase a Snow Leopard upgrade, but I just did a "clean install" and then followed suit with the other software such as some MacPorts too which did run for a while, before "something happened..." On Tue, Oct 27, 2009 at 8:32 PM, Ryan Schmidt wrote: > On Oct 27, 2009, at 18:56, Dennis C wrote: > > Am in the process of making the switch from dual-boot PCs including >> FreeBSD, so kind of new to this, but am now running Snow Leopard and one of >> the first MacPorts I installed was psycopg2 and was able to run the >> python2.6 and successfully import the aforementioned module, but now the >> following's happening: >> >> DCSs-Mac-mini:bin DCSWest$ python2.6 >> -bash: /opt/local/bin/python2.6: Bad CPU type in executable >> >> >> So not quite sure what happened in between, but wondering if it wasn't >> something with the following attempt to update software: >> >> DCSs-Mac-mini:~ DCSWest$ sudo port selfupdate >> Password: >> ---> Updating the ports tree >> ---> Updating MacPorts base sources using rsync >> MacPorts base version 1.8.1 installed, >> MacPorts base version 1.8.1 downloaded. >> ---> MacPorts base is already the latest version >> >> The ports tree has been updated. To upgrade your installed ports, you >> should run >> port upgrade outdated >> >> DCSs-Mac-mini:~ DCSWest$ sudo port upgrade outdated >> ---> Computing dependencies for dbus >> ---> Configuring dbus >> Error: Target org.macports.configure returned: autoreconf failure: shell >> command " cd >> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_dbus/work/dbus-1.2.16" >> && autoreconf --install " returned error 126 >> Command output: sh: /opt/local/bin/autoreconf: /opt/local/bin/perl: bad >> interpreter: Bad CPU type in executable >> >> Error: Unable to upgrade port: 1 >> > > What kind of computer is this? I'm wondering if you have a 32-bit or 64-bit > processor. All but the very first Macs have 64-bit processors. > > What is the architecture of, say, /opt/local/bin/perl? Use "lipo -info > /opt/local/bin/perl" to find out. > > Did you recently upgrade to Snow Leopard -- or did you recently migrate > your MacPorts installation from a different Mac -- and if so, did you > uninstall and reinstall all ports? See the Migration page for more > instructions: > > http://trac.macports.org/wiki/Migration > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From macports at tprfct.net Wed Oct 28 10:15:51 2009 From: macports at tprfct.net (Kastus Shchuka) Date: Wed, 28 Oct 2009 10:15:51 -0700 Subject: xorg-libX11 now depends on groff, why? Message-ID: I just noticed that xorg-libX11 was upgraded: xorg-libX11 1.3.1_0 < 1.3.2_0 When I tried to upgrade it, groff was pulled in. I checked dependencies of xorg-libX11 and it was true, now groff is listed as a dependency: port deps xorg-libX11 Full Name: xorg-libX11 @1.3.2 Build Dependencies: pkgconfig, xorg-util-macros, xorg-xtrans, xorg-bigreqsproto, xorg-xcmiscproto, xorg-xproto, xorg-xextproto, xorg-xf86bigfontproto, xorg- inputproto, xorg-kbproto, groff Library Dependencies: xorg-libXdmcp, xorg-libXau I wonder why a library has to depend on a typesetting package? Is it by mistake? I also checked changeset 59847 (listed as Bump to 1.3.2) and found that groff was present in previous changeset 59718 already. The version in 59718 is 1.3.1, the one that I had installed already without groff. Is that possible that port file changes without incrementing version number? Sorry for too many questions, I am just confused. Thanks, -Kastus From jeremyhu at macports.org Wed Oct 28 10:35:58 2009 From: jeremyhu at macports.org (Jeremy Huddleston) Date: Wed, 28 Oct 2009 10:35:58 -0700 Subject: xorg-libX11 now depends on groff, why? In-Reply-To: References: Message-ID: On Oct 28, 2009, at 10:15, Kastus Shchuka wrote: > ... > I checked dependencies of xorg-libX11 and it was true, now groff is listed as a dependency: > > port deps xorg-libX11 > Full Name: xorg-libX11 @1.3.2 > Build Dependencies: ..., groff > ... > I wonder why a library has to depend on a typesetting package? Is it by mistake? Notice it's a build dependency. It's used to build the documentation. > ... > The version in 59718 is 1.3.1, the one that I had installed already without groff. Is that possible that port file changes without incrementing version number? Yes. The earlier version used the system's version of groff to build documentation, but there is a bug with the version of groff on Leopard and Tiger... so MP's groff needs to be pulled in. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5820 bytes Desc: not available URL: From ryandesign at macports.org Wed Oct 28 15:28:45 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 28 Oct 2009 17:28:45 -0500 Subject: Bad CPU type in executable In-Reply-To: References: <830DA4CA-FE4A-4847-AECB-A1992827D20E@macports.org> Message-ID: <398582BB-CEE1-4A3A-8523-5F6274533BEC@macports.org> On Oct 28, 2009, at 09:41, Dennis C wrote: > Sorry I missed this part of the thread, but I'll check the Perl > architecture as soon as I get back to the machine and I did purchase > a Snow Leopard upgrade, but I just did a "clean install" and then > followed suit with the other software such as some MacPorts too > which did run for a while, before "something happened..." It might help to know what that "something" was. Because if you did a clean install, and (this is important) did not migrate your MacPorts installation to this machine from somewhere else, but instead installed MacPorts fresh using the MacPorts Snow Leopard dmg, as you said, then all your software should have been built on this machine on Snow Leopard, so it should all be the correct CPU architecture. From ryandesign at macports.org Wed Oct 28 15:30:39 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 28 Oct 2009 17:30:39 -0500 Subject: Bad CPU type in executable In-Reply-To: References: <830DA4CA-FE4A-4847-AECB-A1992827D20E@macports.org> <3AF9B206-EA2F-4225-9A9F-D3C448390C62@macports.org> Message-ID: <71550C65-A7AE-4304-B2E7-41A367C06986@macports.org> On Oct 28, 2009, at 09:31, Dennis C wrote: > It's a Mini Mac with an Intel Core 2 Duo CPU and also in response to > the prior message, since I forgot to include the list, am reasonably > assured that I downloaded the Snow Leopard "dmg" which I thought can > only be for Intel like the OS itself and the ported programs did run > at first, but how can I maybe confirm it? The three MacPorts 1.8.1 disk image installers will check the OS version is correct before allowing you to proceed. So if you were able to install MacPorts on Snow Leopard using it, then that is confirmation that you downloaded the Snow Leopard version. From ryandesign at macports.org Wed Oct 28 15:38:06 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 28 Oct 2009 17:38:06 -0500 Subject: xorg-libX11 now depends on groff, why? In-Reply-To: References: Message-ID: <715E78BE-37AB-4A9D-AA2F-CE6999E63D0E@macports.org> On Oct 28, 2009, at 12:15, Kastus Shchuka wrote: > I just noticed that xorg-libX11 was upgraded: > > xorg-libX11 1.3.1_0 < 1.3.2_0 > > When I tried to upgrade it, groff was pulled in. > > I checked dependencies of xorg-libX11 and it was true, now groff is > listed as a dependency: > > port deps xorg-libX11 > Full Name: xorg-libX11 @1.3.2 > Build Dependencies: pkgconfig, xorg-util-macros, xorg-xtrans, > xorg-bigreqsproto, xorg-xcmiscproto, xorg-xproto, > xorg-xextproto, xorg-xf86bigfontproto, xorg- > inputproto, > xorg-kbproto, groff > Library Dependencies: xorg-libXdmcp, xorg-libXau > > I wonder why a library has to depend on a typesetting package? Is it > by mistake? > > I also checked changeset 59847 (listed as Bump to 1.3.2) and found > that groff was present in previous changeset 59718 already. > > The version in 59718 is 1.3.1, the one that I had installed already > without groff. Is that possible that port file changes without > incrementing version number? groff was added as a build dependency in revision r59680 to fix ticket #22153. http://trac.macports.org/changeset/59680 http://trac.macports.org/ticket/22153 Yes, a port can change without its version or revision being incremented, and without the user being told the port is outdated. This is done for changes where there would be no benefit in forcing the user to rebuild. In this case, you either already had MacPorts groff installed (or you were on Snow Leopard which has a new-enough groff built-in), so xorg-libX11 built successfully, or you did not have it installed (and were on Leopard or Tiger), in which case xorg- libX11 did not complete building. So increasing the port's revision would only force those who already had it correctly installed to needlessly rebuild it again. From drowe at roden.myzen.co.uk Wed Oct 28 16:03:49 2009 From: drowe at roden.myzen.co.uk (David Rowe) Date: Wed, 28 Oct 2009 23:03:49 +0000 Subject: Gnucash not starting properly- probably gconf & dbus related Message-ID: <4AE8CDD5.4070306@roden.myzen.co.uk> Have just encountered a problem that seems to have come and gone several times in the last year It seems to be back again: After upgrading several ports, Gnucash does not start up properly. Two warning windows appear saying: "An error occured while loading or saving configuration information for Gnucash. Some of your configuration settings may not work properly" & "Cannot find default values: The configuration data used to specify default values for Gnucash cannot be found in the default system locations. Without this data GnuCash will still operate properly but it may require some extra time to setup. Do you wish to setup the configuration data?" The terminal log reports: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<< wombat-on-outback:~ david$ gnucash gnc.bin-Message: main: binreloc relocation support was disabled at configure time. Xlib: extension "RANDR" missing on display "/tmp/launch-ruNqs3/:0". Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> After this you can get Gnucash to run but you have to set up all preferences and no preferences are saved for the next run. In the past, the problems seem to be caused - not by GnuCash itself - but by Gconf not being able to interact properly with dbus. My normal Gnucash installation had been working OK for several months. Configuration details: MacBookPro (Intel CPU), MacOS Leopard 10.5.8, MacPorts 1.8.1 About 2 weeks ago after some routine updates the above problem occurred again. I noticed that dbus had just been updated from 1.2.14_1 to 1.2.16_1 so I tried reverting to 1.2.14_1 and the problem seemed to go away. (You have to restart MacOS to restart the dbus daemon). I could live with that situation. However I have decided to transition to Snow Leopard and so I created a new MacOS 10.6.1 system on an external drive and then created a new, clean MacPorts installation to go with it. Gnucash was the first application I installed and it does NOT work - with the above symptoms. I tried retro installing dbus 1.2.14_1, but this time it did not cure the problem. The levels for the relevant ports on Snow Leopard are: gnucash @2.2.9, Revision 3, gconf @2.26.2, dbus @1.2.16, Revision 1 So - Has anyone else encountered this problem? Does anyone have GnuCash running under Snow Leopard + MacPorts 1.8.1 ? Can anyone suggest a fix for the above problem? David Rowe From dersh at alum.mit.edu Wed Oct 28 16:21:30 2009 From: dersh at alum.mit.edu (Adam Dershowitz) Date: Wed, 28 Oct 2009 16:21:30 -0700 Subject: Link issue Message-ID: I am not really sure if this is a Macports issue, a specific port issue, or something else entirely, but I figured I would ask here, because maybe someone can help. I just upgraded to a new Mac and also upgraded from 10.5 to 10.6. I did a reinstall of macports and my ports, as instructed on the migration page. One of the ports that I re-installed is qt4-mac. The problem is now when I try to build sqliteman (an application that uses qt4, but that doesn't yet have a port) I get a link error: Linking CXX executable sqliteman ld: library not found for -lcrt1.10.6.o collect2: ld returned 1 exit status make[2]: *** [sqliteman/sqliteman] Error 1 make[1]: *** [sqliteman/CMakeFiles/sqliteman.dir/all] Error 2 make: *** [all] Error 2 Now, I have found crt1.10.6.o in /usr/lib. So it seems that something is wrong in my search paths. I also tried doing this before my build: export LIBRARY_PATH=/usr/lib:$LIBRARY_PATH but I got the same error. So it seems that for some reason some combination of cmake, make and ld are not searching in the correct location. I was able to go back and look at my old machine and didn't see anything in PATH or LIBRARY_PATH about /usr/lib either, so I am not sure where this path should be indicated? Is it set in an environment variable, in qt, in cmake, in macports? Is something wrong with Macports, qt4, cmake, XCode (I did upgrade that to the newest as well), my .profile, something specific to sqliteman? It clearly is something that recently changed, but that could be going to 10.6, or a new install of macports, or something else. The one thing that did not change is that I am actually using the identical source code for sqliteman. I am somewhat stumped, so figured I would ask. Thanks for any suggestions, --Adam From ben at cogs.com Wed Oct 28 16:28:57 2009 From: ben at cogs.com (Ben Greenfield) Date: Wed, 28 Oct 2009 19:28:57 -0400 Subject: Gnucash not starting properly- probably gconf & dbus related In-Reply-To: <4AE8CDD5.4070306@roden.myzen.co.uk> References: <4AE8CDD5.4070306@roden.myzen.co.uk> Message-ID: On Oct 28, 2009, at 7:03 PM, David Rowe wrote: > > So - > Has anyone else encountered this problem? > Does anyone have GnuCash running under Snow Leopard + MacPorts 1.8.1 ? > Can anyone suggest a fix for the above problem? I just spent a couple of days trying to get it to work on the above +quartz. I got it to build and launch but all the characters came out as rectangles. So I downloaded the .dmg from sourceforge and it was a drag and drop install to applications for a quartz install. Works like a charm. Ben > > David Rowe > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcswest at gmail.com Wed Oct 28 17:18:19 2009 From: dcswest at gmail.com (Dennis C) Date: Wed, 28 Oct 2009 17:18:19 -0700 Subject: Bad CPU type in executable In-Reply-To: <71550C65-A7AE-4304-B2E7-41A367C06986@macports.org> References: <830DA4CA-FE4A-4847-AECB-A1992827D20E@macports.org> <3AF9B206-EA2F-4225-9A9F-D3C448390C62@macports.org> <71550C65-A7AE-4304-B2E7-41A367C06986@macports.org> Message-ID: The only other thing I can think of is that I tried and failed installing from source a program called "Qtstalker" and so maybe that did "who knows what..." Sorry I forgot to mention it, but thought the error message could be obvious enough anyway... Thanks for your help though and maybe I'll just have to reinstall everything and hope that Qtstalker or something similar shows up in MacPorts soon because that's what's still keeping me tied to a PC, using that software to manage some market trading... On Wed, Oct 28, 2009 at 3:30 PM, Ryan Schmidt wrote: > > On Oct 28, 2009, at 09:31, Dennis C wrote: > > It's a Mini Mac with an Intel Core 2 Duo CPU and also in response to the >> prior message, since I forgot to include the list, am reasonably assured >> that I downloaded the Snow Leopard "dmg" which I thought can only be for >> Intel like the OS itself and the ported programs did run at first, but how >> can I maybe confirm it? >> > > The three MacPorts 1.8.1 disk image installers will check the OS version is > correct before allowing you to proceed. So if you were able to install > MacPorts on Snow Leopard using it, then that is confirmation that you > downloaded the Snow Leopard version. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dersh at alum.mit.edu Wed Oct 28 17:27:11 2009 From: dersh at alum.mit.edu (Adam Dershowitz) Date: Wed, 28 Oct 2009 17:27:11 -0700 Subject: Link issue In-Reply-To: References: Message-ID: I figured out the solution, and other people could run into it, so I figured I would pass it on. It was not actually a macports problem. But it seems that something from my old computer was being cached, even after doing make clean and a new cmake. I found that going back to the original source code and then doing a cmake and make did the job. My guess is that it was CMakeCache.txt that was not being regenerated. Anyway, just a caution about odd link errors after upgrading from 10.5 to 10.6. --Adam On Oct 28, 2009, at 4:21 PM, Adam Dershowitz wrote: > I am not really sure if this is a Macports issue, a specific port > issue, or something else entirely, but I figured I would ask here, > because maybe someone can help. > > I just upgraded to a new Mac and also upgraded from 10.5 to 10.6. I > did a reinstall of macports and my ports, as instructed on the > migration page. One of the ports that I re-installed is qt4-mac. > The problem is now when I try to build sqliteman (an application > that uses qt4, but that doesn't yet have a port) I get a link error: > > Linking CXX executable sqliteman > ld: library not found for -lcrt1.10.6.o > collect2: ld returned 1 exit status > make[2]: *** [sqliteman/sqliteman] Error 1 > make[1]: *** [sqliteman/CMakeFiles/sqliteman.dir/all] Error 2 > make: *** [all] Error 2 > > Now, I have found crt1.10.6.o in /usr/lib. So it seems that > something is wrong in my search paths. I also tried doing this > before my build: > export LIBRARY_PATH=/usr/lib:$LIBRARY_PATH > > but I got the same error. So it seems that for some reason some > combination of cmake, make and ld are not searching in the correct > location. I was able to go back and look at my old machine and > didn't see anything in PATH or LIBRARY_PATH about /usr/lib either, > so I am not sure where this path should be indicated? Is it set in > an environment variable, in qt, in cmake, in macports? > Is something wrong with Macports, qt4, cmake, XCode (I did upgrade > that to the newest as well), my .profile, something specific to > sqliteman? > > It clearly is something that recently changed, but that could be > going to 10.6, or a new install of macports, or something else. The > one thing that did not change is that I am actually using the > identical source code for sqliteman. > > I am somewhat stumped, so figured I would ask. > > Thanks for any suggestions, > > --Adam > > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From ryandesign at macports.org Wed Oct 28 19:29:09 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 28 Oct 2009 21:29:09 -0500 Subject: Bad CPU type in executable In-Reply-To: References: <830DA4CA-FE4A-4847-AECB-A1992827D20E@macports.org> <3AF9B206-EA2F-4225-9A9F-D3C448390C62@macports.org> <71550C65-A7AE-4304-B2E7-41A367C06986@macports.org> Message-ID: On Oct 28, 2009, at 19:18, Dennis C wrote: > The only other thing I can think of is that I tried and failed > installing from source a program called "Qtstalker" and so maybe > that did "who knows what..." Sorry I forgot to mention it, but > thought the error message could be obvious enough anyway... Thanks > for your help though and maybe I'll just have to reinstall everything Before you do, if you can provide the information I requested earlier about the architectures your installed software has, maybe that will clue us in about what happened. Try using both "lipo -info /opt/local/ bin/perl" and "file /opt/local/bin/perl" to try to find out why your perl is not satisfactory to your Mac. > and hope that Qtstalker or something similar shows up in MacPorts > soon because that's what's still keeping me tied to a PC, using that > software to manage some market trading... You could file a port request ticket in the issue tracker. I looked into qtstalker briefly just now, and didn't get very far, because it requires qt3 (is not compatible with qt4), whereas qt3 is not compatible with Snow Leopard (see #21459). Then again, I can't get the current qt4 to build on Snow Leopard either; there are tickets for this as well. Qt is an unimaginably huge piece of library, which probably means it has a bazillion things that could go wrong. To get qtstalker in MacPorts, you should either work with the authors of qt to get qt3 working properly on Snow Leopard, or work with the authors of qtstalker to get it working with qt4 and work with the authors of qt to get qt4 working properly in MacPorts. In the mean time, someone who still uses Leopard could work on the portfile. (I don't have Leopard with me at the moment.) From olaf at foellinger.de Thu Oct 29 05:40:54 2009 From: olaf at foellinger.de (Olaf Foellinger) Date: Thu, 29 Oct 2009 13:40:54 +0100 Subject: Gnucash not starting properly- probably gconf & dbus related In-Reply-To: <4AE8CDD5.4070306@roden.myzen.co.uk> References: <4AE8CDD5.4070306@roden.myzen.co.uk> Message-ID: <20091029124054.GB13476@foellinger.de> Hi, * David Rowe [29.10.09 09:32]wrote: > Have just encountered a problem that seems to have come and gone > several times in the last year It seems to be back again: > > After upgrading several ports, Gnucash does not start up properly. > Two warning windows appear saying: > > "An error occured while loading or saving configuration information > for Gnucash. Some of your configuration settings may not work > properly" > & > "Cannot find default values: The configuration data used to specify > default values for Gnucash cannot be found in the default system > locations. Without this data GnuCash will still operate properly but > it may require some extra time to setup. Do you wish to setup the > configuration data?" here GnuCash quartz is running fine as a quartz build with macports. The error message above shows indeed problems with dbus. At the end of the installation of dbus a message appears to tell about two startup items that must be activated (one as root, one as user). After doing this gnucash works fine here. Do oyu have problems with the X11 or the quartz version? Gru? Olaf From drowe at roden.myzen.co.uk Thu Oct 29 15:21:32 2009 From: drowe at roden.myzen.co.uk (David Rowe) Date: Thu, 29 Oct 2009 22:21:32 +0000 Subject: Gnucash not starting properly- probably gconf & dbus related - SOLVED In-Reply-To: <20091029124054.GB13476@foellinger.de> References: <4AE8CDD5.4070306@roden.myzen.co.uk> <20091029124054.GB13476@foellinger.de> Message-ID: <4AEA156C.2080106@roden.myzen.co.uk> Thanks Ben & Olaf - now I have two solutions! Ben - I hadn't realised that a bundled .dmg was now available. I downloaded and installed it and it works just fine. I now rely on Gnucash for my accounts and a bundled solution is more dependable, so I will probably stick with it. however Olaf - your comments gave me the clue to what I was doing wrong - it was my mistake: I got a bit weary with sudo-ing every port command in a long session of MacPorts maintenance - so I got into the habit of starting with 'sudo bash' and then working as superuser for the session. (Yes I know the dangers but I am used to being careful). I had indeed noted the comments in the port install log about executing the commands to activate the two startup items. However, as you say, the first item must be activated as root but the second as user. What I was doing was activating both as root and presumably the result of that was that the user-mode application was unable to talk to the root dbus daemon. When I killed the dbus process and reactivated exactly as specified in the log, then Gnucash started just fine. After restarting MacOS X, Gnucash still works OK so presumably the startup items are now right. PS - It was the X11 version I built. Thanks to both of you for your help David Rowe ------------------------------------------------------------ Ben Greenfield wrote: . . . > I just spent a couple of days trying to get it to work on the above > +quartz. I got it to build and launch but all the characters came out > as rectangles. > So I downloaded the .dmg from sourceforge and it was a drag and drop > install to applications for a quartz install. Olaf Foellinger wrote: > . . . > > here GnuCash quartz is running fine as a quartz build with macports. The > error message above shows indeed problems with dbus. At the end of the > installation of dbus a message appears to tell about two startup items > that must be activated (one as root, one as user). After doing this > gnucash works fine here. Do oyu have problems with the X11 or the quartz > version? > > Gru? Olaf > > ------------------------------------------------------------------------ > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcswest at gmail.com Thu Oct 29 15:21:29 2009 From: dcswest at gmail.com (Dennis C) Date: Thu, 29 Oct 2009 15:21:29 -0700 Subject: Bad CPU type in executable In-Reply-To: References: <830DA4CA-FE4A-4847-AECB-A1992827D20E@macports.org> <3AF9B206-EA2F-4225-9A9F-D3C448390C62@macports.org> <71550C65-A7AE-4304-B2E7-41A367C06986@macports.org> Message-ID: Cannot believe it! I just realized that the Apple store where I had this Mini Mac in for repair apparently replaced the board with a Core Duo CPU instead of the Core 2 Duo CPU I took it in with! Not exactly sure why only the MacPorts programs crashed and not any of the Quartz ones, but at least it explains the immediate problem... I did also start a discussion on the Qtstalker mailing list and the development version's based on Qt4 where someone even has it all running on their Mac albeit on Tiger, so it may be totally doable once we hopefully resolve this Qt4 on Snow Leopard issue... On Wed, Oct 28, 2009 at 7:29 PM, Ryan Schmidt wrote: > > On Oct 28, 2009, at 19:18, Dennis C wrote: > > The only other thing I can think of is that I tried and failed installing >> from source a program called "Qtstalker" and so maybe that did "who knows >> what..." Sorry I forgot to mention it, but thought the error message could >> be obvious enough anyway... Thanks for your help though and maybe I'll just >> have to reinstall everything >> > > Before you do, if you can provide the information I requested earlier about > the architectures your installed software has, maybe that will clue us in > about what happened. Try using both "lipo -info /opt/local/bin/perl" and > "file /opt/local/bin/perl" to try to find out why your perl is not > satisfactory to your Mac. > > > and hope that Qtstalker or something similar shows up in MacPorts soon >> because that's what's still keeping me tied to a PC, using that software to >> manage some market trading... >> > > You could file a port request ticket in the issue tracker. I looked into > qtstalker briefly just now, and didn't get very far, because it requires qt3 > (is not compatible with qt4), whereas qt3 is not compatible with Snow > Leopard (see #21459). Then again, I can't get the current qt4 to build on > Snow Leopard either; there are tickets for this as well. Qt is an > unimaginably huge piece of library, which probably means it has a bazillion > things that could go wrong. To get qtstalker in MacPorts, you should either > work with the authors of qt to get qt3 working properly on Snow Leopard, or > work with the authors of qtstalker to get it working with qt4 and work with > the authors of qt to get qt4 working properly in MacPorts. In the mean time, > someone who still uses Leopard could work on the portfile. (I don't have > Leopard with me at the moment.) > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From atma at convalesco.org Fri Oct 30 14:55:56 2009 From: atma at convalesco.org (Panagiotis Atmatzidis) Date: Fri, 30 Oct 2009 23:55:56 +0200 Subject: A few pointers about launchd and daemondo Message-ID: Greetings, I've created my first launchd script. It's for OpenVPN2. Here are the files I've created so far: devo:/opt/local/etc/LaunchDaemons root# ls -l org.macports.OpenVPN2/ total 16 -rwxr-xr-x 1 root admin 957 Oct 30 23:06 OpenVPN2.wrapper -rw-r--r-- 1 root admin 1026 Oct 30 23:39 org.macports.OpenVPN2.plist The Wrapper ----- #!/bin/sh . /etc/rc.common load() { if [ -d /System/Library/Extensions/tun.kext ]; then kextload -q /System/Library/Extensions/ tun.kext; else echo "tun.kext not found in /System/Library/ Extensions/" fi } StartService() { load; # first load the module if [[ $( kextstat -l | grep -q 'tun' )$? == 0 ]]; then /opt/local/sbin/openvpn2 --config /opt/local/etc/ovpn/ server.conf --writepid /opt/local/etc/ovpn/ovpn.pid --daemon OpenVPN2 /usr/bin/logger "OpenVPN is loaded" else /usr/bin/logger "tun extensions is not loaded." fi } StopService() { if [[ $( kextstat -l | grep -q 'tun' )$? == 0 ]]; then kextunload /System/Library/Extensions/tun.kext # first unload the module fi pid=`cat /opt/local/etc/ovpn/ovpn.pid` # get the pid number if [ $? -eq 0 ]; then kill $pid fi } RestartService() { StopService "$@" StartService "$@" } RunService "$1" the .plist which is an: ln -sf /opt/local/etc/LaunchDaemons/ org.macports.OpenVPN2/org.macports.OpenVPN2.plist /Library/ LaunchDaemons/.... ------------------------ Labelorg.macports.OpenVPN2 ProgramArguments /opt/local/bin/daemondo --label=OpenVPN2 --start-cmd /opt/local/etc/LaunchDaemons/org.macports.OpenVPN2/ OpenVPN2.wrapper start ; --stop-cmd /opt/local/etc/LaunchDaemons/org.macports.OpenVPN2/ OpenVPN2.wrapper stop ; --restart-cmd /opt/local/etc/LaunchDaemons/org.macports.OpenVPN2/ OpenVPN2.wrapper restart ; --pid=none Debug Disabled OnDemand RunAtLoad NetworkState However, there are two issues that I can't seem to be able to manage right now. The first is that OpenVPN does not start at boot while the module is loaded succesfully. When I login to the system and kill daemondo, it relaunches itself and ovpn works fine. I suspect that the problem is en0. Launchd tries to launchd openvpn before en0 comes up. That's why I put the NetworkState keyword, but it does not seem to effect *any* startup script. I had issues with dnsmasq also in the recent past. The second problem with this script is that when I unload it via launchd it does not kill the process. Launchd unloads the script and (probably) will not be launchd (if -w is added) in the next boot but daemondo keeps running the process nevertheless. Is this a normal behaviour? I'm not *that* worried about the second. I'd prefer to have a solution about the first one, which is the most important for me. Best regards & thanks in advance Panagiotis (atmosx) Atmatzidis email: atma at convalesco.org URL: http://www.convalesco.org GnuPG key id: 0xFC4E8BB4 -- The wise man said: "Never argue with an idiot. They bring you down to their level and beat you with experience." From pengyu.ut at gmail.com Fri Oct 30 21:03:12 2009 From: pengyu.ut at gmail.com (Peng Yu) Date: Fri, 30 Oct 2009 23:03:12 -0500 Subject: Where is findutils installed? Message-ID: <366c6f340910302103h135149a9jd5771bf1a3de2c0a@mail.gmail.com> I installed findutils on macports. But I don't find where the commands find, locate, updatedb and xargs are. Could somebody let me know where they are? sudo port install findutils From arno at alum.wpi.edu Fri Oct 30 21:15:11 2009 From: arno at alum.wpi.edu (Arno Hautala) Date: Sat, 31 Oct 2009 00:15:11 -0400 Subject: Where is findutils installed? In-Reply-To: <366c6f340910302103h135149a9jd5771bf1a3de2c0a@mail.gmail.com> References: <366c6f340910302103h135149a9jd5771bf1a3de2c0a@mail.gmail.com> Message-ID: <6adc49070910302115p73e381f0r66c92727e4f35b55@mail.gmail.com> On Sat, Oct 31, 2009 at 00:03, Peng Yu wrote: > I installed findutils on macports. But I don't find where the commands > find, locate, updatedb and xargs are. Could somebody let me know where > they are? They are installed, by default, under /opt/local/bin with "g" prefixing each program name (ie. gxargs instead of xargs). The "with_default_names" variant is available which uses the names you're more likely to be familiar with, though this may cause problems with scripts which expect a specific version of findutils provided by Mac OS X. In general, you can discover the installed files of a port by using the following command. port contents ie. $ port contents findutils Port findutils contains: /opt/local/bin/gfind /opt/local/bin/glocate /opt/local/bin/goldfind ... -- arno s hautala /-\ arno at alum.wpi.edu pgp eabb6fe6 d47c500f b2458f5d a7cc7abb f81c4e00 From jeremyhu at macports.org Fri Oct 30 21:16:24 2009 From: jeremyhu at macports.org (Jeremy Huddleston) Date: Fri, 30 Oct 2009 21:16:24 -0700 Subject: Where is findutils installed? In-Reply-To: <366c6f340910302103h135149a9jd5771bf1a3de2c0a@mail.gmail.com> References: <366c6f340910302103h135149a9jd5771bf1a3de2c0a@mail.gmail.com> Message-ID: <8D07C6B3-F100-471D-A81E-2583CD8CEB53@macports.org> They install with the 'g' prefix... run gfind. On Oct 30, 2009, at 21:03, Peng Yu wrote: > I installed findutils on macports. But I don't find where the commands > find, locate, updatedb and xargs are. Could somebody let me know where > they are? > > sudo port install findutils > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5820 bytes Desc: not available URL: From atma at convalesco.org Sat Oct 31 04:51:42 2009 From: atma at convalesco.org (Panagiotis Atmatzidis) Date: Sat, 31 Oct 2009 13:51:42 +0200 Subject: A few pointers about launchd and daemondo In-Reply-To: References: Message-ID: <343CC984-B73B-4074-9F01-A018893515E6@convalesco.org> Hello, I solved both issues adjusting the wrapper accordingly. Should I throw a ticket for this wrapper for this to be added on macports? I don't know how to edit the port though... # openvpn configuration file #!/bin/sh . /etc/rc.common load() { if [ -d /System/Library/Extensions/tun.kext ]; then kextload -q /System/Library/Extensions/tun.kext; else echo "tun.kext not found in /System/Library/Extensions/" fi } StartService() { # # Use the "ipconfig waitall" command to wait for all the # interfaces to come up: # ipconfig waitall load; # first load the module if [[ $( kextstat -l | grep -q 'tun' )$? == 0 ]]; then /opt/local/sbin/openvpn2 --config /opt/local/etc/ovpn/ server.conf --writepid /opt/local/etc/ovpn/ovpn.pid --daemon OpenVPN2 /usr/bin/logger "OpenVPN is loaded" else /usr/bin/logger "tun extensions is not loaded." fi } StopService() { pid=`cat /opt/local/etc/ovpn/ovpn.pid` if [ $? -eq 0 ]; then kill $pid fi if [[ $( kextstat -l | grep -q 'tun' )$? == 0 ]]; then kextunload /System/Library/Extensions/tun.kext if [[ $( kextstat -l | grep -q 'tun' )$? == 0 ]]; then /usr/bin/logger "The tun module is unloaded successfully" else /usr/bin/logger "There was a problem. I was not able to unload tun module!!!" fi fi } RestartService() { StopService "$@" StartService "$@" } RunService "$1" Panagiotis (atmosx) Atmatzidis email: atma at convalesco.org URL: http://www.convalesco.org GnuPG key id: 0xFC4E8BB4 -- The wise man said: "Never argue with an idiot. They bring you down to their level and beat you with experience." From cskinnaman42 at gmail.com Sat Oct 31 07:37:26 2009 From: cskinnaman42 at gmail.com (Carrie S. Miller) Date: Sat, 31 Oct 2009 10:37:26 -0400 Subject: "unrecognized action" error when trying to use an installed port Message-ID: <9F51759B-542E-4DC6-8A84-15CEB2FF5193@gmail.com> I have just installed macports (1.8.1) for snow leopard. I also installed xcode, so all of these programs are up to date. When I try to install a port (e.g. xmgr), the port installs fine and shows up as active when I use "port installed." However, when I try to run it using either "port xmgr" or "sudo port xmgr" it returns the error: unrecognized action "xmgr" This error occurs when I try to run any port that I've installed. Any help would be much appreciated. Thanks From atma at convalesco.org Sat Oct 31 07:48:07 2009 From: atma at convalesco.org (Panagiotis Atmatzidis) Date: Sat, 31 Oct 2009 16:48:07 +0200 Subject: "unrecognized action" error when trying to use an installed port In-Reply-To: <9F51759B-542E-4DC6-8A84-15CEB2FF5193@gmail.com> References: <9F51759B-542E-4DC6-8A84-15CEB2FF5193@gmail.com> Message-ID: Greetings, On 31 ??? 2009, at 4:37 ?.?., Carrie S. Miller wrote: > I have just installed macports (1.8.1) for snow leopard. I also > installed xcode, so all of these programs are up to date. When I try > to install a port (e.g. xmgr), the port installs fine and shows up > as active when I use "port installed." However, when I try to run it > using either "port xmgr" or "sudo port xmgr" it returns the error: > > unrecognized action "xmgr" > > This error occurs when I try to run any port that I've installed. > Any help would be much appreciated. > > Thanks > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users Yes of course it does, becuase port only handles installation not execution. So for port the the options are are: atma at devo:~/ > sudo port help Password: port [-bcdfknopqRstuvy] [-D portdir] [-F cmdfile] action [privopts] [actionflags] [[portname|pseudo-portname|port-url] [@version] [+- variant]... [option=value]...]... [...] When you type for instance "sudo port install irssi" it does install irssi. Then you run irssi by running the proram itself. The port command has nothing to do with this. In order to run the programs installed by macports you need to add the path to your .profile. For more info on that take a look here http://trac.macports.org/wiki/InstallingMacPorts#a3.Settheshellenvironment In your case you should run just "xmgr" or the binary names of the executables of the package, just like any other command line program. regards Panagiotis (atmosx) Atmatzidis email: atma at convalesco.org URL: http://www.convalesco.org GnuPG key id: 0xFC4E8BB4 -- The wise man said: "Never argue with an idiot. They bring you down to their level and beat you with experience."