June 2007 - macports-dev - lists.macosforge.org

Configure & build environment flags
by Juan Manuel Palacios 26 Jun '07

26 Jun '07

Hello Paul! I'm curious about why we provide facilities to alter the configure environment in many ways but practically none to alter the build environment. I know that in the ideal case (a properly written build system for any given software package) the configure environment should either cascade down to the build one (Makefiles inheriting and passing the same env flags that were given during the configure stage, for instance) or its results should be reflected there (the setting of some variable in generated Makefiles), but we all know there are quite a handful of broken build systems in which neither of these two is true. Therefore some Portfiles have the need of passing some (if not the same) flags to the environment during build (build.env) as they do in the configure stage. So, onto my specific questions, is there any reason why we don't provide the build.xxflags-{append,delete} equivalents that we do for configure.xxflags-{append,delete}? How these would work (inheriting values, replicating them, overriding them,...) I'm not entirely sure, but you can easily spot Portfiles out there using build.env construct that may tread on what's set through the configure.xxflags if not used carefully. Also, if we're deprecating configure.env, shouldn't we be doing the same for build.env? And lastly, again on the deprecation of configure.env, what's our stand with respect to {configure,build}.env- {append,delete}? I would completely understand if you told me none of these things have been implemented yet 'cause simply you've had "no time" ;-) But I was wondering if there were intead any type of technical decisions behind the lack of a build environment tweaking facility. Regards,... -jmpp

4 5

Re: [26328] trunk/dports/gnustep/Etoile/Portfile
by Juan Manuel Palacios 25 Jun '07

25 Jun '07

Hi Yves! A couple of notes about this commit, if you don't mind: On Jun 19, 2007, at 5:17 PM, source_changes(a)macosforge.org wrote: > Revision > 26328 > Author > yves(a)macports.org > Date > 2007-06-19 14:17:05 -0700 (Tue, 19 Jun 2007) > Log Message > > Add a devel variant to keep the unstable stuff out of the stable > (Oh boy !) I couldn't make it out from your edits, so I'm not sure if the devel variant changes the port version number (a big NO-NO!!), but even if it doesn't everybody is much better off if you turn it (the devel variant) into a different port. Even if for consistency with other - devel ports. Also: > Modified Paths > > trunk/dports/gnustep/Etoile/Portfile > Diff > > Modified: trunk/dports/gnustep/Etoile/Portfile (26327 => 26328) > > --- trunk/dports/gnustep/Etoile/Portfile 2007-06-19 20:56:13 UTC > (rev 26327) > +++ trunk/dports/gnustep/Etoile/Portfile 2007-06-19 21:17:05 UTC > (rev 26328) ---snip--- > + system " > + cd GNUstep/Local/Tools && > + ln -s ../Applications/Calc.app/Calc && > + cd ../Library/Headers && > + rm -f AddressBook && > + ln -s Addresses AddressBook > + " > } You don't need a "system" call to do any of those things. Portfiles understand cd, we have an internal implementation for ln and one for delete > > > +variant devel { > + build.args-delete etoile-extensions=no menuserver=yes > jabber=no outerspace=no sketch=no > + destroot.args-delete etoile-extensions=no menuserver=yes > jabber=no outerspace=no sketch=no > + build.args-append debug=yes corner=no > + destroot.args-append debug=yes corner=no > + > + post-destroot { > + cd ${destroot}${prefix} > + xinstall -d GNUstep/System/Library/Etoile > + xinstall -m 644 ${worksrcpath}/Services/Private/System/ > SystemTaskList.plist \ > + GNUstep/System/Library/Etoile > + xinstall -d share/xsessions > + xinstall -m 644 ${worksrcpath}/Services/Private/System/ > etoile.desktop \ > + share/xsessions > + system " > + echo \". ${prefix}/GNUstep/System/Library/Makefiles/ > GNUstep.sh; \ > + etoile_system\" > bin/etoile && > + chmod 755 bin/etoile > + Maybe you can use xinstall here to tweak those permissions...? -jmpp

4 7

Re: [26461] users/pipping/merge.rb
by Kevin Ballard 25 Jun '07

25 Jun '07

You are aware that the Mozilla project has a script that does exactly this, right? IIRC it's called unify.pl. -Kevin Ballard On Jun 24, 2007, at 6:57 AM, source_changes(a)macosforge.org wrote: > Revision > 26461 > Author > pipping(a)macports.org > Date > 2007-06-24 06:57:23 -0700 (Sun, 24 Jun 2007) > Log Message > > initial upload of <merge.rb> > > merge.rb is designed to merge two or more trees of single-arch > destdirs > into a single destdir of universal binaries. > > build_coreutils.sh serves as a test, 'port destroot openssl > +universal' can > be used as well (port install zlib +universal is required) > > see ./merge.rb --help for the usage > Added Paths > > users/pipping/merge.rb > Diff > > Added: users/pipping/merge.rb (0 => 26461) > > --- users/pipping/merge.rb (rev 0) > +++ users/pipping/merge.rb 2007-06-24 13:57:23 UTC (rev 26461) > @@ -0,0 +1,221 @@ > +#!/usr/bin/env ruby -w > + > +# Copyright (c) 2007 Elias Pipping > +# > +# Permission is hereby granted, free of charge, to any person > obtaining a copy > +# of this software and associated documentation files (the > "Software"), to deal > +# in the Software without restriction, including without > limitation the rights > +# to use, copy, modify, merge, publish, distribute, sublicense, > and/or sell > +# copies of the Software, and to permit persons to whom the > Software is > +# furnished to do so, subject to the following conditions: > +# > +# The above copyright notice and this permission notice shall be > included in > +# all copies or substantial portions of the Software. > +# > +# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, > EXPRESS OR > +# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF > MERCHANTABILITY, > +# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO > EVENT SHALL THE > +# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR > OTHER > +# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, > ARISING FROM, > +# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER > DEALINGS IN > +# THE SOFTWARE. > + > +require 'fileutils' > +require 'find' > +require 'optparse' > +require 'set' > + > +### > +# we need GNU file with Apple's patches applied, available here: > +# http://www.opensource.apple.com/darwinsource/Current/file-6.2/ > patches/ > +# > +# Its output might span multiple lines, causing problems when > parsing, even > +# with `file -b`, hence we'll assume we're not passed universal > binaries > +# TODO: do a real check, maybe using `lipo -info` (fails on non- > Mach-O files) > +FILE="/usr/bin/file" > + > +class MergeArguments < Hash > + def initialize(args) > + super() > + > + # set up defaults > + self[:dry_run] = false > + self[:force] = false > + self[:verbose] = false > + > + self[:exclude] = Set.new << '.svn' << 'CVS' > + self[:root] = Dir.pwd > + > + opts = OptionParser.new do |opts| > + opts.banner = "Usage: #$0 [options] <arch> <arch> [<arch> ...]" > + > + opts.on('-r', '--root DIRECTORY', 'specify root directory') > do |root| > + self[:root] = root || Dir.pwd > + end > + > +# opts.on('-o', '--output DIRECTORY', 'specify output > directory') do |out| > +# self[:output] = File.expand_path(out) || File.join(self > [:root], 'out') > +# end > + > + opts.on('-e', '--exclude NAMES', 'specify names of files/ > directories to exclude') do |exclude| > + self[:exclude] = Set.new > + exclude.split(" ").each do |item| > + self[:exclude] << item > + end > + end > + > + opts.on('-d', '--dry-run', 'perform a dry run') do > + self[:dry_run] = true > + end > + > + opts.on('-f', '--force', 'force writing, ignoring > collisions') do > + self[:force] = true > + end > + > + opts.on('-v', '--verbose', 'enable verbose output') do > + self[:verbose] = true > + end > + > + opts.on_tail('-h', '--help', 'display this help and exit') do > + puts opts > + exit > + end > + end > + > + opts.parse!(args) > + end > +end > + > +arguments = MergeArguments.new(ARGV) > + > +ARGS=ARGV.uniq > + > +def true_for_all? (filepath, args, &block) > + result=true > + ARGS.each {|arch| > + result=false unless yield(File.join(args[:root], arch), > filepath, arch) > + } > + return result > +end > + > +def lipo (filepath,architectures,args) > + lipoargs = Array.new > + architectures.each {|arch| > + lipoargs << sprintf('-arch %s %s', arch, File.join( > + args[:root], arch, filepath > + )) > + } > + lipotarget=File.join(args[:root], 'out', filepath) > + lipocmd = sprintf( > + 'lipo %s -create -o %s', > + lipoargs.join(' '), > + lipotarget > + ) > + if !File.exist?(lipotarget) or args[:force] > + puts lipocmd if args[:verbose] > + system lipocmd if !args[:dry_run] > + end > +end > + > +original_dir=Dir.pwd > +processed=Set.new > + > +if File.directory?(File.expand_path(arguments[:root])) > + ARGS.each {|architecture| > + FileUtils.cd original_dir, :verbose => false > + if File.directory? File.join( > + File.expand_path(arguments[:root]), architecture > + ) > + FileUtils.cd( > + File.join(arguments[:root], architecture), > + :verbose => arguments[:verbose] > + ) > + Find.find('.') {|path| > + arguments[:exclude].each {|exclude_me| > + Find.prune if File.basename(path) == exclude_me > + } > + unless processed.include? path > + my_dir=File.dirname(File.join(arguments[:root], 'out', > path)) > + # TODO: what if ppc/foo is a dir and i386/foo is a file > (symlink)? (1) > + unless File.exist? my_dir > + FileUtils.mkdir_p( > + my_dir, > + :verbose => arguments[:verbose], > + :noop => arguments[:dry_run] > + ) > + end > + if true_for_all?(path, arguments) {|dir,filename,arch| > + File.exist?(File.join(dir, filename)) > + } > + unless true_for_all?(path, arguments) {| > dir,filename,arch| > + File.directory?(File.join(dir, filename)) > + } > + > + if true_for_all?(path, arguments) {|dir,filename,arch| > + FileUtils.identical?( > + File.join(dir, path), > + File.join(arguments[:root], ARGS[0], path) > + ) > + } > + copytarget=File.join(arguments[:root],'out',path) > + if !File.exist?(copytarget) or arguments[:force] > + FileUtils.cp( > + File.join(arguments[:root],ARGS[0],path), > + copytarget, > + :preserve => !arguments[:force], > + :verbose => arguments[:verbose], > + :noop => arguments [:dry_run] > + ) > + end > + else > + # TODO: make this not-blindly lipo but check > filetypes / archs > + # TODO: beware of symlinks! > + case File.basename path > + when /\.dylib(\.\d*)*/, /\.so(\.\d*)*/, /\.a$/ > + lipo(path,ARGS,arguments) > + when /\.h$/, /\.hpp$/ > + # TODO: handle header files > + when /\.pc$/ > + # TODO: handle pkgconfig files > + when /\.sh$/ > + # TODO: handle shell scripts > + else > + case %x{#{FILE} -b "#{File.join(arguments > [:root],ARGS[0],path)}"} > + when sprintf("Mach-O executable %s\n", ARGS[0]) > + if true_for_all?(path, arguments) {| > dir,filename,arch| > + %x{#{FILE} -b "#{File.join(dir,path)}"} == > sprintf("Mach-O executable %s\n", arch) > + } > + lipo(path,ARGS,arguments) > + else > + # one of the files is a mach-o file that > matches its > + # desired architecture but one of the others > doesn't > + end > + # else > + # TODO: deal with whatever else can differ > + end > + end > + end > + else > + # TODO: at least one of the files is a directory (1) > + end > + else > + # TODO: a file is not present in all trees. what's wrong? > + end > + processed << path > + end > + } > + else > + raise sprintf( > + 'architecture missing from root directory: %s', > + architecture > + ) > + end > + } > +else > + raise sprintf( > + 'invalid root directory: %s', > + arguments[:root] > + ) > +end > + > +FileUtils.cd original_dir, :verbose => false > Property changes on: users/pipping/merge.rb > ___________________________________________________________________ > Name: svn:executable > + * > _______________________________________________ > macports-changes mailing list > macports-changes(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-changes -- Kevin Ballard http://kevin.sb.org eridius(a)macports.org http://www.tildesoft.com

1 0

GSoC Project commits (Was "Re: [26439] users")
by Juan Manuel Palacios 25 Jun '07

25 Jun '07

Hey Chris! Good to see you're making progress in your GSoC project, most excited to see it completed! About this commit though.... it was discussed on the this list some time ago whether GSoC work should be committed to trunk or to a branch, and the consensus was that, this being SCM and therefore moving back and forth being an easy operation, GSoC students should commit to either based on their own judgement. Seems to me like you clearly don't feel comfortable enough to commit this work to trunk, so why not put it in an appropriate branch? Seems to me like a more standard and expected place to find experimental code like this. Regards,... -jmpp On Jun 23, 2007, at 9:10 AM, source_changes(a)macosforge.org wrote: > Revision > 26439 > Author > sfiera(a)macports.org > Date > 2007-06-23 06:10:09 -0700 (Sat, 23 Jun 2007) > Log Message > > Chris Pickel, GSoC project 2007 > * Currently very messy; obviously this will change > * Lots of warnings still > * This can be safely built into MacPorts (as I have on my system), > though I'm not yet putting it into trunk > Added Paths > > users/sfiera/ > users/sfiera/registry2.0/ > users/sfiera/registry2.0/.gdb_history > users/sfiera/registry2.0/:w > users/sfiera/registry2.0/Makefile > users/sfiera/registry2.0/README > users/sfiera/registry2.0/centry.c > users/sfiera/registry2.0/centry.h > users/sfiera/registry2.0/entry.c > users/sfiera/registry2.0/entry.h > users/sfiera/registry2.0/entryobj.c > users/sfiera/registry2.0/entryobj.h > users/sfiera/registry2.0/foo.db > users/sfiera/registry2.0/graph.c > users/sfiera/registry2.0/graph.h > users/sfiera/registry2.0/graphobj.c > users/sfiera/registry2.0/graphobj.h > users/sfiera/registry2.0/item.c > users/sfiera/registry2.0/item.h > users/sfiera/registry2.0/itemobj.c > users/sfiera/registry2.0/itemobj.h > users/sfiera/registry2.0/registry.c > users/sfiera/registry2.0/registry.dylib > users/sfiera/registry2.0/registry.h > users/sfiera/registry2.0/sql.c > users/sfiera/registry2.0/sql.h > users/sfiera/registry2.0/test.db > users/sfiera/registry2.0/tests/ > users/sfiera/registry2.0/tests/common.tcl > users/sfiera/registry2.0/tests/entry.tcl > users/sfiera/registry2.0/tests/item.tcl > users/sfiera/registry2.0/util.c > users/sfiera/registry2.0/util.h

5 6

Controlling $PATH of build?
by Hagen Overdick 23 Jun '07

23 Jun '07

Hello all, just getting my feeds wet in writing Ports... Here is a tricky question: Postgres has it's own infrastructure for add-ons, see: http://www.postgresql.org/docs/8.2/static/xfunc-c.html This system relies on: /opt/local/lib/postgresql82/bin/pg_config Unfortunately, it's not in the $PATH, when the Makefile is called. I tried patching the Makefile, but the error seems to come from Postgres itself. Long question short: How do I control the $PATH exposed to the Makefile? It's the last puzzle to having a PL/Java port. Thanks, Hagen -- Dissertations are a successful walk through a minefield -- summarizing them is not. - Roy Fielding

2 2

Slang upgrade
by Sbranzo 23 Jun '07

23 Jun '07

Can someone confirm that the slang2 port works? I get this error upgrading slang2 from 2.0.4_0 to 2.1.0_0 on os x 10.4.10 and 10.4.9 ppc. ---> Building slang2 with target all Error: Target com.apple.build returned: shell command " cd "/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_lang_slang2/work/slang-2.1.0" && make all " returned error 2 Command output: cd src; make static make[1]: Nothing to be done for `static'. cd slsh; make all gcc -O2 slsh.o readline.o -o slsh_exe -L/opt/local/lib -L/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_lang_slang2/work/slang-2.1.0/src/objs -L/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_lang_slang2/work/slang-2.1.0/src/elfobjs -lslang -ldl -lm /usr/bin/ld: warning -L: directory name (/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_lang_slang2/work/slang-2.1.0/src/elfobjs) does not exist /usr/bin/ld: warning prebinding disabled because of undefined symbols /usr/bin/ld: Undefined symbols: _SLrline_init _SLrline_open2 collect2: ld returned 1 exit status make[1]: *** [slsh_exe] Error 1 make: *** [static] Error 2 Thanks, Gufo

2 4

New milestone: Feature Requests
by Juan Manuel Palacios 23 Jun '07

23 Jun '07

Good afternoon everyone! I've recently created two new milestones in our trac roadmap, http://trac.macports.org/projects/macports/roadmap, called "Feature Requests" and "Port Requests". From their descriptions: -) Feature Requests: Where requests for new features in the MacPorts base infrastructure should go. -) Port Requests: Where requests for software packages that are not yet in our ports tree nor in milestone:"New Ports" should go. More specifically, milestone:"New Ports" is for submissions from non- committers that come complete with a Portfile, whereas this milestone is simply for requests to write Portfiles for certain software packages. I think their explanations are rather self explanatory so I wont go on about them here. In any case, do let me know if you'd like to see improved descriptions for them and/or if you have any questions. Other than that, start filling them up! Regards,... -jmpp

3 2

Re: [26399] trunk/dports/math/nestedsums/Portfile
by Ryan Schmidt 22 Jun '07

22 Jun '07

On Jun 21, 2007, at 00:53, source_changes(a)macosforge.org wrote: > Revision: 26399 > http://trac.macosforge.org/projects/macports/changeset/26399 > Author: gwright(a)macports.org > Date: 2007-06-20 22:53:34 -0700 (Wed, 20 Jun 2007) > > Log Message: > ----------- > Build only on darwin_8 or later. This eliminates the need for > a macports g++ compiler, and since cln (a dependency via > GiNaC) only works on darwin_8 or later, we don't lose anything. > > Modified Paths: > -------------- > trunk/dports/math/nestedsums/Portfile > > Modified: trunk/dports/math/nestedsums/Portfile > =================================================================== > --- trunk/dports/math/nestedsums/Portfile 2007-06-21 05:40:45 UTC > (rev 26398) > +++ trunk/dports/math/nestedsums/Portfile 2007-06-21 05:53:34 UTC > (rev 26399) > @@ -5,7 +5,7 @@ > version 1.4.9 > categories math > platforms darwin > -maintainers nomaintainer(a)macports.org > +maintainers gwright(a)macports.org > description nestedsums library > long_description \ > A Library for the Symbolic Expansion of a Class of \ > @@ -21,9 +21,14 @@ > #user_notes On Tiger (10.4.x), Xcode 2.1 is required to avoid a bug > # in gcc which causes one of the tests to fail. > > +platform darwin 6 { > + ui_msg "nesteedsums is not supported on Jaguar (OS X 10.2.x)." > + exit 1 > +} > + > platform darwin 7 { > - depends_build port:gcc40 > - configure.env CXX=g++-dp-4.0 > + ui_msg "nesteedsums is not supported on Panther (OS X 10.3.x)." > + exit 1 > } > > default_variants +test On Jun 21, 2007, at 00:58, source_changes(a)macosforge.org wrote: > Revision: 26400 > http://trac.macosforge.org/projects/macports/changeset/26400 > Author: gwright(a)macports.org > Date: 2007-06-20 22:58:03 -0700 (Wed, 20 Jun 2007) > > Log Message: > ----------- > Don't build on darwin 6 and 7 anymore. Since GiNaC depends on cln > which doesn't build on these versions, we don't lose anything. > > Modified Paths: > -------------- > trunk/dports/math/GiNaC/Portfile > > Modified: trunk/dports/math/GiNaC/Portfile > =================================================================== > --- trunk/dports/math/GiNaC/Portfile 2007-06-21 05:53:34 UTC (rev > 26399) > +++ trunk/dports/math/GiNaC/Portfile 2007-06-21 05:58:03 UTC (rev > 26400) > @@ -40,12 +40,14 @@ > depends_lib port:readline \ > port:cln > > +platform darwin 6 { > + ui_msg "GiNaC is not supported on Jaguar (OS X 10.2.x)." > + exit 1 > +} > + > platform darwin 7 { > - depends_build port:gcc40 > - > - configure.env CXX=g++-dp-4.0 \ > - CPPFLAGS=-I${prefix}/include \ > - LDFLAGS=-L${prefix}/lib > + ui_msg "GiNaC is not supported on Panther (OS X 10.3.x)." > + exit 1 > } > > platform darwin 8 { But could you please not output messages and exit merely in a platform statement? Please do so only within a stage such as pre- fetch, e.g.: platfrom darwin 7 { pre-fetch { ui_msg "GiNaC is not supported on Panther (OS X 10.3.x)." exit 1 } } Otherwise, people running port info, portindex, etc. on darwin 7 will be inconvenienced by the exit.

4 6

New milestones: Feature Requests & Port Requests
by Juan Manuel Palacios 22 Jun '07

22 Jun '07

RESENT: with a proper title this time! (second time this has happened in the last couple days, but I'm not drunk though, I promise!) Good afternoon everyone! I've recently created two new milestones in our trac roadmap, http://trac.macports.org/projects/macports/roadmap, called "Feature Requests" and "Port Requests". From their descriptions: -) Feature Requests: Where requests for new features in the MacPorts base infrastructure should go. -) Port Requests: Where requests for software packages that are not yet in our ports tree nor in milestone:"New Ports" should go. More specifically, milestone:"New Ports" is for submissions from non- committers that come complete with a Portfile, whereas this milestone is simply for requests to write Portfiles for certain software packages. I think their explanations are rather self explanatory so I wont go on about them here. In any case, do let me know if you'd like to see improved descriptions for them and/or if you have any questions. Other than that, start filling them up! Regards,... -jmpp

1 0

Requesting commit for port: redland-1.0.5
by Lyle Johnson 22 Jun '07

22 Jun '07

http://trac.macosforge.org/projects/macports/ticket/11746 I submitted this port a few months ago now and was wondering if it someone could commit it (or, let me know if something else needs to be done with it before that can happen). Thanks in advance, Lyle

2 1