Re: Incompatible library version

Do not set DYLD_LIBRARY_PATH, doing so is a bad idea. If MatLab requires this (is it really needed ??, I am quite surprised this is done into internals inside an application in /Applications), report this as a bug against MatLab... On 08/10/15 08:21, Michel Perez wrote: Jeremy, Indeed, the

Re: Incompatible library version

Contact Matlab. There's no reason that they should require you setting DYLD_LIBRARY_PATH globally. Was this done by an installer? If so, shame on them big time. Or was this done by you following some bad advise from some website? If so, can you point me to that website, so I can help point

Re: Incompatible library version

Jeremy, Indeed, the DYLD_LIBRARY_PATH is set… by MATLAB ! mperez$ set | grep DYLD DYLD_LIBRARY_PATH=/Applications/MATLAB_R2015a.app/bin/maci64:/Applications/MATLAB_R2015a.app/sys/os/maci64:/usr/local/qwt-6.0.1/lib: Will I have to choose between matlab and macport? What should I do? Michel > On 08

Re: Incompatible library version

Michel Perez wrote on 08.10.2015 09:21: Will I have to choose between matlab and macport? Try removing it from the MATLAB script yourself and see if it still runs. ___ macports-users mailing list macports-users@lists.macosforge.org

Re: Incompatible library version

Indeed, cleaning .bash_profile file fixed this issue. The bug has been reported to matlab. Hat’s off to the macport-users team ! Michel Perez > On 08 Oct 2015, at 10:36, Bachsau wrote: > > Michel Perez wrote on 08.10.2015 09:21: >> Will I have to choose between matlab and

Re: pet project : LnxPorts

On Thursday October 08 2015 07:16:51 Alejandro Imass wrote: > Perhaps it's a good time to evaluate a switch to PCBSD and ditch the Linux > ;-) Why? I've already checked the temp of those waters. I know MacPorts comes from BSD originally, but I cannot say I felt right at home at once on PC-BSD

Re: pet project : LnxPorts

On Wed, Oct 7, 2015 at 1:59 PM, René J.V. wrote: > Morning! > > OK now, don't get me wrong, this is not an announcement that I'll be > forking off MacPorts to begin a fully supported Linux variant! :) > > However, if anyone on here is like me (a developer's not to say

Re: Rebuild old version of port?

On Oct 8, 2015, at 8:34 AM, Adam Dershowitz wrote: > On Oct 8, 2015, at 8:57 AM, Ryan Schmidt wrote: > >> On Oct 7, 2015, at 9:53 AM, Adam Dershowitz wrote: >> >>> Is there a way that I can rebuild and reactivate an older version of a >>> port? I know about this link: >>>

Re: pet project : LnxPorts

On Wed, Oct 7, 2015 at 1:59 PM, René J.V. wrote: > Morning! > > OK now, don't get me wrong, this is not an announcement that I'll be > forking off MacPorts to begin a fully supported Linux variant! :) > Also, why no use Gentoo or other existing ports-based Linux variants ?

Re: pet project : LnxPorts

On Wed, Oct 7, 2015 at 8:36 PM, Sven Kolja Heinemann wrote: > MacPorts exists to make OS X a complete BSD distribution > That seems to be a wonderful aim… Thank you! -- Eneko Gotzon Ares enekogot...@gmail.com ___ macports-users

Re: pet project : LnxPorts

On Thu, Oct 8, 2015 at 7:33 AM, René J.V. wrote: > On Thursday October 08 2015 07:16:51 Alejandro Imass wrote: > > > Perhaps it's a good time to evaluate a switch to PCBSD and ditch the > Linux > > ;-) > > Why? > > I've already checked the temp of those waters. I know

Re: Rebuild old version of port?

On Oct 7, 2015, at 9:53 AM, Adam Dershowitz wrote: > Is there a way that I can rebuild and reactivate an older version of a port? > I know about this link: > https://trac.macports.org/wiki/howto/InstallingOlderPort but the problem I > have is a little bit different. > I have the old

Re: Rebuild old version of port?

> On Oct 8, 2015, at 8:57 AM, Ryan Schmidt wrote: > > > On Oct 7, 2015, at 9:53 AM, Adam Dershowitz wrote: > >> Is there a way that I can rebuild and reactivate an older version of a >> port? I know about this link: >>

Re: pet project : LnxPorts

On Thursday October 08 2015 09:22:19 Alejandro Imass wrote: > Also, why no use Gentoo or other existing ports-based Linux variants ? I don't need to have a front-row seat for everything. In fact, I much prefer a stable OS with LTS, one that I can work done on/with, rather than one on which I

Re: pet project : LnxPorts

- On 8 Oct, 2015, at 16:57, René J.V. Bertin rjvber...@gmail.com wrote: > For me, MacPorts is just an additional distribution system (and more of a > build > system) for certain things that I would otherwise build "by hand". See, that's where you're wrong. MacPorts actively tries to NOT

port not installed according to registry, yet depends_lib didn't "react"?

Hey, Something weird just happened. I had triggered an incremental rebuild (build and destroot) of a KDE4 port that depends on port:libical via depends_lib. The build system uses cmake, which detected that a re-configure was in order: - cmake failed to detect libibcal - upon verification,

Re: pet project : LnxPorts

Gentoo currently has 1240 orphaned packages and there only exists a very small group of active proxy maintainers. So I would not use Gentoo as any alternative...which pains me to say because I used to love Gentoo. On Thu, Oct 8, 2015 at 8:22 AM, Alejandro Imass wrote: > >

Re: pet project : LnxPorts

Cal You are misinterpreting what Rene is saying. He is not trying to garner support for a Linux based Ports system, he is just sharing - after all he did state 'pet project' in the title and also states very clearly that "... this is not an announcement that I'll be forking off MacPorts to

Re: pet project : LnxPorts

On Thursday October 08 2015 17:44:37 Clemens Lang wrote: > See, that's where you're wrong. MacPorts actively tries to NOT be a build > system, > but a package manager. That's why we focus on getting things done the right > way > and ensuring the tuple (os, port, variants) always behaves the

Re: port not installed according to registry, yet depends_lib didn't "react"?

On Oct 8, 2015, at 11:03 AM, Brandon Allbery wrote: > On Thu, Oct 8, 2015 at 11:55 AM, René J.V. wrote: >> I *really* that my update to 2.3.4 yesterday (from source) didn't cause >> ports to be dropped from the registry! > > An update to a python module port broke portindex. I believe they're

Re: port not installed according to registry, yet depends_lib didn't "react"?

On Thu, Oct 8, 2015 at 11:55 AM, René J.V. wrote: > I *really* that my update to 2.3.4 yesterday (from source) didn't cause > ports to be dropped from the registry! An update to a python module port broke portindex. I believe they're working on getting it fixed. --

Re: port not installed according to registry, yet depends_lib didn't "react"?

On Thursday October 08 2015 12:03:32 Brandon Allbery wrote: > On Thu, Oct 8, 2015 at 11:55 AM, René J.V. wrote: > > > I *really* that my update to 2.3.4 yesterday (from source) didn't cause > > ports to be dropped from the registry! I meant the registry of installed ports,

Re: port not installed according to registry, yet depends_lib didn't "react"?

On Thu, Oct 8, 2015 at 12:36 PM, René J.V. wrote: > Ouch, that's what you get from depending on "internal" software and not on > something stable provided by the host :) > I sure hope they're working to fix what they broke! > The problem with Tcl is you can't just read a

Re: port not installed according to registry, yet depends_lib didn't "react"?

On Thursday October 08 2015 12:04:18 Ryan Schmidt wrote: > I know I've encountered situations where a port failed to build because one > of its dependencies was inactive. I'm sure I had forcibly deactivated it at > some prior time for some forgotten reason. I don't know why MacPorts wouldn't >

Re: port not installed according to registry, yet depends_lib didn't "react"?

> On Oct 8, 2015, at 11:36 AM, René J.V. Bertin wrote: > > On Thursday October 08 2015 12:03:32 Brandon Allbery wrote: >> On Thu, Oct 8, 2015 at 11:55 AM, René J.V. wrote: >> >>> I *really* that my update to 2.3.4 yesterday (from source) didn't cause

GIMP latest version

Hi Byte Masters. The download page of the GIMP states that there is a 2.8.2 version for OS X , but both MacPorts and the available disk images only offer the 2.8.14 one. Please, why? (Sorry about this kind of questions and) thank you. -- Eneko Gotzon Ares

Re: GIMP latest version

Eneko, The .dmg package for Gimp 2.8.2 is rather out of date. The MacPorts version 2.8.14 corresponds to currently available source code. Also note: you will want to install Gimp-app as well (this adds the OS X icon, etc.) On Oct 8, 2015, at 3:38 PM, Eneko Gotzon

Re: GIMP latest version

Hi, 14 is a higher number than 2, so 2.8.14 is newer than 2.8.2 - You will encounter this kind of numbering a lot with software. Take care Dom > On 08.10.2015, at 22:38, Eneko Gotzon wrote: > > Hi Byte Masters. > > The download page of the GIMP states that there is

Re: pet project : LnxPorts

On Thu, 8 Oct 2015, Alejandro Imass wrote: > Perhaps it's a good time to evaluate a switch to PCBSD and ditch the > Linux ;-) Anything that ditches Linux is fine by me :-) I'm a bit of a BSD snob, after all... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."

Re: port not installed according to registry, yet depends_lib didn't "react"?

On Oct 8, 2015, at 1:09 PM, René J.V. Bertin wrote: > On Thursday October 08 2015 12:04:18 Ryan Schmidt wrote: > >> I know I've encountered situations where a port failed to build because one >> of its dependencies was inactive. I'm sure I had forcibly deactivated it at >> some prior time for