15 maj 2009 kl. 00.17 skrev Ryan Schmidt:
[...]
As to other ports, most of them probably do not explicitly mention /
sw in their configure scripts.
I'm sure it's a tricky situation for software developers: if they
do add paths like /sw and /opt/local to their configure scripts,
they make
On May 17, 2009, at 09:35, Bjarne Bäckström wrote:
15 maj 2009 kl. 00.17 skrev Ryan Schmidt:
[...]
As to other ports, most of them probably do not explicitly
mention /sw in their configure scripts.
I'm sure it's a tricky situation for software developers: if they
do add paths like /sw
14 maj 2009 kl. 19.21 skrev Bjarne Bäckström:
14 maj 2009 kl. 05.08 skrev Ryan Schmidt:
On May 13, 2009, at 08:25, Bjarne Bäckström wrote:
On OS X 10.4.11 (intel) with a freshly installed MacPorts:
[...]
/usr/bin/g++-4.0 -O2 -pipe -fno-exceptions -fno-check-new -L/
opt/local/lib -o
On May 14, 2009, at 16:59, Bjarne Bäckström wrote:
Now I'm wondering, where does it get /sw from? ;-)
OK, temporarily renaming /sw made qucs and its dependencies
build fine. Question is, why hasn't this been a problem with
earlier versions of qucs (or other ports)?
I checked the
