Re: [73849] trunk/dports/devel/icu

2010-11-27 Thread Ryan Schmidt
On Nov 27, 2010, at 02:37, takan...@macports.org wrote: > Revision: 73849 > http://trac.macports.org/changeset/73849 > Author: takan...@macports.org > Date: 2010-11-27 00:37:19 -0800 (Sat, 27 Nov 2010) > Log Message: > --- > icu: > - Updated to the latest stable version (4.

Re: [73849] trunk/dports/devel/icu

2010-11-27 Thread Takanori Yamamoto
> Variant names should not begin with "with_" (or "without_" or "enable_" or > "disable_"). > They should either begin with nothing (preferred), or "no_". As you say, +with_doxygen may be a bit redundant. > Why is build_arch relevant for the universal variant? Shouldn't only > universal_archs

Howto "sudo port install" without cleaning the build directory?

2010-11-27 Thread Marko Käning
Is it possible to "sudo port install" without cleaning the build directory for debugging purposes? Is the keep mode option '-k' my friend here? ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.

Re: Howto "sudo port install" without cleaning the build directory?

2010-11-27 Thread Bradley Giesbrecht
On Nov 27, 2010, at 12:04 PM, Marko Käning wrote: Is it possible to "sudo port install" without cleaning the build directory for debugging purposes? Is the keep mode option '-k' my friend here? Yes, -k will not auto clean your $workpath. If you are wanting to make Portfile edits without r

Re: Howto "sudo port install" without cleaning the build directory?

2010-11-27 Thread Marko Käning
> Yes, -k will not auto clean your $workpath. Thanks to let me know, Brad. :-) > If you are wanting to make Portfile edits without rebuilding look at -o. Yep, that I remembered. :) Still fighting with Xcode and gdb to allow for debugging… Somehow it always starts with lazy loading, i.e. would n

Re: Using Xcode debugger on executable installed via "port install" possible?

2010-11-27 Thread Marko Käning
Solved it. After telling Xcode DYLD_FALLBACK_LIBRARY_PATH and the folders where to find the source code it worked eventually. Could be that it was also important to leave the source files in the build directory where "port -k install" was my friend. _

Re: [73888] trunk/dports/devel/soprano/Portfile

2010-11-27 Thread Jeremy Lavergne
> soprano: update to 2.5.63 (needed for KDE 4.6) This is effectively a beta of 2.6 and it should be fine; if anyone has issues I'll drop it back and slap on an epoch. ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosfor

Kismet and Tiger

2010-11-27 Thread Jeremy Lavergne
Anyone have a moment to check out kismet on a Tiger box? Specifically I've got issues with -fnested-functions not working. I don't have Tiger, but #24951 builds for me on a Leopard ppc box as-is with the same compiler as the OP (gcc-4.0). Thanks. ___