Stop in /usr/ports/lang/gcc43

2009-06-01 Thread Leslie Jensen
I originally posted this in questions but I think this list is more relevant! I can't get gcc43 to compile. I've deinstalled and reinstalled all its dependencies but it still fails. I'm on a 7.2-RELEASE system with all ports installed from a clean install. The problem turned up when an update

Re: Stop in /usr/ports/lang/gcc43

2009-06-13 Thread Dan Allen
I am trying to upgrade Ruby, and build Firefox 3.0.11, and they both want to build gcc43 because of gfortran. Really? Firefox needs gfortran to build? I bet not. Anyway, when they try and build gcc43 (of May 31st) on my system, I get into an infinite loop by the pkg system saying that gc

Re: Stop in /usr/ports/lang/gcc43

2009-06-13 Thread b. f.
>I am trying to upgrade Ruby, and build Firefox 3.0.11, and they both >want to build gcc43 because of gfortran. Really? Firefox needs >gfortran to build? I bet not. I bet not, too. I took a cursory look through my ports tree, and the recent changes, and I can't see how such a dependency was int

Re: Stop in /usr/ports/lang/gcc43

2009-06-14 Thread Dan Allen
On 13 Jun 2009, at 10:55 PM, b. f. wrote: Some care is taken to avoid introducing circular dependencies in Ports, so this shouldn't happen. It sounds to me as if you have mistakenly introduced a USE_FORTRAN=yes into your build environment somehow. I DO have USE_FORTRAN=yes in /etc/make.c

Re: Stop in /usr/ports/lang/gcc43

2009-06-14 Thread Jeremy Messenger
On Sun, 14 Jun 2009 14:05:10 -0500, Dan Allen wrote: On 13 Jun 2009, at 10:55 PM, b. f. wrote: Some care is taken to avoid introducing circular dependencies in Ports, so this shouldn't happen. It sounds to me as if you have mistakenly introduced a USE_FORTRAN=yes into your build envir

Re: Stop in /usr/ports/lang/gcc43

2009-06-14 Thread Dan Allen
On 14 Jun 2009, at 3:03 PM, Jeremy Messenger wrote: On Sun, 14 Jun 2009 14:05:10 -0500, Dan Allen wrote: On 13 Jun 2009, at 10:55 PM, b. f. wrote: Some care is taken to avoid introducing circular dependencies in Ports, so this shouldn't happen. It sounds to me as if you have mistakenl