January 2008 - macports-dev - lists.macosforge.org

'port build' different than 'make all'
by jcharum 04 Jan '08

04 Jan '08

I have altered the GHC Portfile to have no build section (and no pre-build or post-build sections) and to set (amongst other things): build.cmd make build.type gnu build.args "" build.target all (1) $ sudo port configure $ cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ghc/work/ghc-6.6.1 $ sudo make all (2) $ sudo port configure $ sudo port build I think that running (1) and (2) should be equivalent. However, when I do this, I do not get the same object files. Namely, when I install with (1), my GHC works (at least for trivial examples). When I install with (2), I get weird errors (that I can describe further if requested). I have built GHC about 25 times (at ~4 hours/build) to narrow it down to this. Can someone shed some light on why there is any difference? I think it must be somewhere in my environment, but I can't figure out what - I have at least set the PATHs to be the same. I am new to Portfile development and was interested in helping to get a good build for GHC 6.6.1 on Leopard. If any more information is needed, I will happily provide it. Thanks in advance for any help at all. -- View this message in context: http://www.nabble.com/%27port-build%27-different-than-%27make-all%27-tp1460… Sent from the MacPorts - Developer mailing list archive at Nabble.com.

3 3

Re: [32470] trunk/dports/python/py25-gtk/Portfile
by Ryan Schmidt 03 Jan '08

03 Jan '08

On Jan 3, 2008, at 06:03, afb(a)macports.org wrote: > +platform darwin 9 { > + post-patch { > + reinplace "s| -export-symbols-regex.*||g" ${worksrcpath}/ > Makefile.am > + reinplace "s| -export-symbols-regex.*||g" ${worksrcpath}/ > Makefile.in > + reinplace "s| -export-symbols-regex.*||g" ${worksrcpath}/ > gtk/Makefile.am > + reinplace "s| -export-symbols-regex.*||g" ${worksrcpath}/ > gtk/Makefile.in > + } > +} reinplace does accept multiple files to patch, so you could just do: reinplace "s| -export-symbols-regex.*||g" ${worksrcpath}/Makefile.am \ ${worksrcpath}/Makefile.in \ ${worksrcpath}/gtk/Makefile.am \ ${worksrcpath}/gtk/Makefile.in >

1 0

Workaround for PyGTK missing symbols under Leopard
by Guido Soranzio 02 Jan '08

02 Jan '08

I tried to compile the latest Deluge (a BitTorrent client) and XPN (an experimental Python newsreader) after applying a workaround to py25-gobject, py25-cairo, py25-gtk and dbus-python25, all of which were reporting missing symbols under Leopard: the patches simply exclude the option "-export-symbols-regex" from the Makefile.am and Makefile.in files, as suggested successfully by several reports. Unfortunately all these fine ports are currently unmaintained, so I am reporting here the corresponding Trac submissions: http://trac.macosforge.org/projects/macports/ticket/13781 http://trac.macosforge.org/projects/macports/ticket/13763 http://trac.macosforge.org/projects/macports/ticket/13782 http://trac.macosforge.org/projects/macports/ticket/13792 http://trac.macosforge.org/projects/macports/ticket/13791 http://trac.macosforge.org/projects/macports/ticket/13784 Regards, Guido

1 0

Fwd: macforge.org via https?
by js 02 Jan '08

02 Jan '08

Forwarding to macports developers. ---------- Forwarded message ---------- From: js <ebgssth(a)gmail.com> Date: Dec 25, 2007 12:19 AM Subject: macforge.org via https? To: MacPorts Users <macports-users(a)lists.macosforge.org> Hi list, A simple question. is there any reason http://www.macosforge.org/wp-login.php is not HTTPS?

5 7

Re: [32441] trunk/base/src/port1.0/portchecksum.tcl
by Ryan Schmidt 02 Jan '08

02 Jan '08

On Jan 1, 2008, at 11:09, jberry(a)macports.org wrote: > Revision: 32441 > http://trac.macosforge.org/projects/macports/changeset/32441 > Author: jberry(a)macports.org > Date: 2008-01-01 09:09:21 -0800 (Tue, 01 Jan 2008) > > Log Message: > ----------- > If checksum is mismatched, and in verbose mode, present a corrected > pre-fabricated > checksum statement to make it easy to update a port. That does, of course, make it easier for people to just blindly copy and paste, rather than thinking about whether they should be changing the portfile checksum at all. http://trac.macosforge.org/projects/macports/wiki/ FAQ#IgetError:checksummd5sha1rmd160mismatchforport.WhatcanIdoaboutit

3 2

doxygen vs libiconv oddity
by cssdev＠mac.com 02 Jan '08

02 Jan '08

Hi all, I'm having a heck of a time with what should be a simple bug. http://trac.macosforge.org/projects/macports/ticket/13156 Several people have reported the same problem, but I cannot replicate it on my MacBook Pro running Mac OS X 10.4.11. I have tested both with and without the libiconv port installed, and it looks like my libiconv simply doesn't match the results that others are seeing. What could make the libiconv port yield different function signatures? My iconv.h installed for libiconv @1.12_0+darwin_8 works fine, but it looks like others are getting different headers without the const parameter. I tried reinstalling the developer tools as well as XCode, but the port as is builds fine on my machine. I don't have a /usr/local. I could use some help trying to identify why the libiconv port is behaving differently. Thanks, Chris

1 0

Version Update Patch: iverilog
by Michael Witten 01 Jan '08

01 Jan '08

Hello, The included patch updates the iverilog version from 0.8.2. to 0.8.6. Just apply as follows: # cd /opt/local/var/macports/sources/rsync.macports.org/release/ports/ science/iverilog # patch -p0 < path/to/Portfile-iverilog.diff I've sent the patch into the mailing list rather than using the Trac system, because this portfile is unmaintained, and because it feels like any submission to Trac would get lost. Also, I did not paste the diff directly into this email, because some clients automatically remove lines with only whitespace. Sincerely, Michael Witten

2 2