Re: Error installing gnu cash with xquartz: "libcanberra must be installed with +x11"

2014-06-04 Thread Jason Swails
On Wed, Jun 4, 2014 at 10:15 PM, Gustavo Seabra wrote: > Hi Guys, > I’m trying to install gnucash by following the instructions here: > > http://wiki.gnucash.org/wiki/MacOSX/MacPortsDetail > > According to them, it gnucash needs to use xquartz, so that’s what I’m > using. > > However, after a lon

Re: Error installing gnu cash with xquartz: "libcanberra must be installed with +x11"

2014-06-04 Thread David Evans
On 6/4/14 7:15 PM, Gustavo Seabra wrote: > Hi Guys, > I’m trying to install gnucash by following the instructions here: > > http://wiki.gnucash.org/wiki/MacOSX/MacPortsDetail > > According to them, it gnucash needs to use xquartz, so that’s what I’m using. > > However, after a long, long time, the

Error installing gnu cash with xquartz: "libcanberra must be installed with +x11"

2014-06-04 Thread Gustavo Seabra
Hi Guys, I’m trying to install gnucash by following the instructions here: http://wiki.gnucash.org/wiki/MacOSX/MacPortsDetail According to them, it gnucash needs to use xquartz, so that’s what I’m using. However, after a long, long time, the installation stops with the message below. Isn’t it

Re: ld64 regressed?

2014-06-04 Thread Eric Gallager
On Wed, Jun 4, 2014 at 4:07 PM, "René J.V. Bertin" wrote: > On Jun 04, 2014, at 20:51, Eric Gallager wrote: > > > Isn't 236.3_1 the broken one that failed to build? How did you manage to > get it installed in the first place? > > I had an exchange (on here or via the bug tracker) and had even pre

Re: Boost.Python and g++

2014-06-04 Thread René J.V. Bertin
On Jun 04, 2014, at 20:21, Eric Gallager wrote: > Wow, that looks a lot simpler than I thought that it would be... I was > expecting something like this would have to be fixed upstream by gcc, because > that is how they handle the GNU vs. NeXT Objective C runtime issues, but if > all it takes

Re: ld64 regressed?

2014-06-04 Thread René J.V. Bertin
On Jun 04, 2014, at 20:51, Eric Gallager wrote: > Isn't 236.3_1 the broken one that failed to build? How did you manage to get > it installed in the first place? I had an exchange (on here or via the bug tracker) and had even prepared my own patched portfile that version-locked to 136 on 10.6,

Re: ktimetracker and akonadi's googlecontacts/googlecalendar

2014-06-04 Thread René J.V. Bertin
On Jun 04, 2014, at 20:05, Nicolas Pavillon wrote: > > I don’t think I could do that in this case. I had typically missed the use of > kioslaves in kdepim* ports, so that I disabled them to enable the binary > distribution, at the cost of usability of some programs as you pointed out > later.

Re: Package open-cobol not working for me

2014-06-04 Thread Michael Peternell
Maybe important: clang is used on OSX, because it has no gcc installed anymore. But clang is the new gcc. To clarify: --- on the command line --- $ gcc clang: error: no input files --- end of command line --- (my system: OSX 10.8.5) Regards, Michael Am 04.06.2014 um 18:38 schrieb Eric Gallage

Re: ld64 regressed?

2014-06-04 Thread Eric Gallager
Isn't 236.3_1 the broken one that failed to build? How did you manage to get it installed in the first place? On Tue, Jun 3, 2014 at 4:48 PM, "René J.V. Bertin" wrote: > On OS X 10.6.8: > {{{ > $ port installed ld64 > The following ports are currently installed: > ld64 @236.3_1+llvm34 (activ

Re: Boost.Python and g++

2014-06-04 Thread Eric Gallager
Wow, that looks a lot simpler than I thought that it would be... I was expecting something like this would have to be fixed upstream by gcc, because that is how they handle the GNU vs. NeXT Objective C runtime issues, but if all it takes in this case is this script, it seems like just using this sc

Re: Package open-cobol not working for me

2014-06-04 Thread Eric Gallager
Maybe I'll install clang 3.4 and 3.5 once I have some spare cycles; my computer just finished rebuilding llvm 3.3 and gcc 4.7 and 4.8 due to the recent updates, and those all took a long time on their own... Anyways, doing the latter of the things you suggested, I seem to have managed to remove the

Re: ktimetracker and akonadi's googlecontacts/googlecalendar

2014-06-04 Thread René J.V. Bertin
On Jun 04, 2014, at 14:53, Nicolas Pavillon wrote: > I had a quick look at the Portfile, and apart some small things which could > be simplified, it seems fine to me. One thing missing though are the > maintainers. Should I put you, René, as you proposed it, or should I take it > as an additio

Re: ktimetracker and akonadi's googlecontacts/googlecalendar

2014-06-04 Thread Nicolas Pavillon
Hello, I had a quick look at the Portfile, and apart some small things which could be simplified, it seems fine to me. One thing missing though are the maintainers. Should I put you, René, as you proposed it, or should I take it as an additional dependency of KDE, or put both ? In case I take

Problem reinstalling packages after Mavericks upgrade - variants conflict

2014-06-04 Thread Peter Brommer
Hi, I’ve ran into a problem when reinstalling my macports packages after the upgrade to Mavericks (as suggested in the Migration guide). I’m only installing the packages I actually requested, but now I’ve hit a behaviour which may be a bug. What I did was the following: Compile a list of of pa

Re: Package open-cobol not working for me

2014-06-04 Thread Ryan Schmidt
On Jun 3, 2014, at 8:24 PM, Eric Gallager wrote: > open-cobol is actually a source-to-source compiler (or "transpiler") that > compiles to C code, and then uses the host C compiler to compile the > generated C code, which means that something that looks like an open-cobol > error might actuall