Re: gcc43 not completing upgrade.

Hello, Sorry about not mentioning the platform. It is Leopard (MacOS 10.5.8) on a G4. I will make a bug report. On May 3, 2012, at 9:17 PM, Ryan Schmidt wrote: On May 3, 2012, at 22:40, Frank J. R. Hanstick wrote: On May 2, 2012, at 8:23 PM, Frank J. R. Hanstick wrote: gcc43 is

Re: gcc43 not completing upgrade.

On May 3, 2012, at 22:40, Frank J. R. Hanstick wrote: > On May 2, 2012, at 8:23 PM, Frank J. R. Hanstick wrote: > >> gcc43 is completing upgrade due to libgfortran having no symbols. I remember >> seeing notations from previous postings about gfortran effecting builds and &g

Re: gcc43 not completing upgrade.

Hello, This should have been "gcc43 is not completing upgrade" instead of "gcc43 is completing upgrade". On May 2, 2012, at 8:23 PM, Frank J. R. Hanstick wrote: Hello, gcc43 is completing upgrade due to libgfortran having no symbols. I remember seeing notations fr

gcc43 not completing upgrade.

Hello, gcc43 is completing upgrade due to libgfortran having no symbols. I remember seeing notations from previous postings about gfortran effecting builds and wondered if a bug had already been created (I did not find such a bug when doing a bug search) or whether another solution had

Re: Linking 'gfortran' command to compiler in gcc43

On 2010-10-07 03:37 , Mark wrote: > 1) What is the difference between gfortran vs gcc vs gfortran-mp-*.*? GCC is the Gnu Compiler Collection. It contains compilers for C, C++, Objective-C and others. As that is a modular approach, not everything is always included. For example, Apple does not ship

Re: Linking 'gfortran' command to compiler in gcc43

Joshua Root macports.org> writes: > > On 2010-4-24 05:41 , Andrew Lambe wrote: > > When I first installed gcc43 through Macports, I noticed that the command gfortran was undefined, even > though gfortran comes with the package (for some reason gcc did work as expected.

Re: MacPorts update of ports after upgrade to 1.9.1 >> GCC43 builds forever

Brazil vs Portugal should be good. And hopefully Switzerland will get into the next round, too... The bad news (macports-wise) is that gcc44 seems to take at least as long as gcc43. DN Jasper Frumau wrote: On Fri, Jun 25, 2010 at 4:24 PM, David Nicholls <mailto:da...@mso.anu.edu

Re: MacPorts update of ports after upgrade to 1.9.1 >> GCC43 builds forever

On Fri, Jun 25, 2010 at 4:24 PM, David Nicholls wrote: > gcc43 does take a long time to build - took an hour or so on my MBP Will try again shortly and just let it run while I go out and watch some World cup 2010 games. Thanks for your input David! > > > Jasper Frumau wrot

Re: MacPorts update of ports after upgrade to 1.9.1 >> GCC43 builds forever

gcc43 does take a long time to build - took an hour or so on my MBP Jasper Frumau wrote: Just upgraded MacPorts to 1.9.1. The as suggested to me I decided to update all outdated ports: $ sudo port upgrade outdated .. ---> Computing dependencies for gcc43 ---> Fetching

Re: MacPorts update of ports after upgrade to 1.9.1 >> GCC43 builds forever

>> - >> ---> Computing dependencies for gcc43 >> ---> Fetching gcc43 >> ---> Verifying checksum(s) for gcc43 >> ---> Extracting gcc43 >> ---> Applying patches to gcc43 >> ---> Configuring gcc43 >> ---> Building gcc43

Re: MacPorts update of ports after upgrade to 1.9.1 >> GCC43 builds forever

On Fri, Jun 25, 2010 at 4:07 PM, Jasper Frumau wrote: > Just upgraded MacPorts to 1.9.1. The as suggested to me I decided to update > all outdated ports: > > $ sudo port upgrade outdated > - > ---> Computing dependencies for gcc43 > ---> Fetching gcc43 &

MacPorts update of ports after upgrade to 1.9.1 >> GCC43 builds forever

for mpfr ---> Extracting mpfr ---> Applying patches to mpfr ---> Configuring mpfr ---> Building mpfr ---> Staging mpfr into destroot ---> Computing dependencies for mpfr ---> Installing mpfr @3.0.0-p1_0 ---> Deactivating mpfr @2.4.2-p1_0 ---> Activating mpfr @3

Re: atlas depends on gcc43 *and* gcc44 ???

Haven't filed a report. Just ran into the error when they updated atlas to use gcc44. Will do. -- D. M. Monarres On Sat, Jun 5, 2010 at 11:23 AM, Adam Mercer wrote: > On Sat, Jun 5, 2010 at 12:46, D. M. Monarres wrote: >> The gcc44 build with port 1.8.2 on 10.6.3 isn't building for me. It >>

Re: atlas depends on gcc43 *and* gcc44 ???

On Sat, Jun 5, 2010 at 12:46, D. M. Monarres wrote: > The gcc44 build with port 1.8.2 on 10.6.3 isn't building for me. It > looks like it is failing while building gcj. Which ticket is this? Cheers Adam ___ macports-users mailing list macports-users@l

Re: atlas depends on gcc43 *and* gcc44 ???

The gcc44 build with port 1.8.2 on 10.6.3 isn't building for me. It looks like it is failing while building gcj. Switching compilers is often a ticket to trouble, is there a reason for the switch to gcc44? -- D. M. Monarres On Fri, Jun 4, 2010 at 10:06 AM, Bradley Giesbrecht wrote: > > On J

Re: atlas depends on gcc43 *and* gcc44 ???

On Jun 2, 2010, at 4:37 PM, Ryan Schmidt wrote: What about this ticket where gcc44 can't be built on (some?) Leopard machines? Anybody else see this problem? http://trac.macports.org/ticket/20635 To help close this ticket I built gcc44 on the following 2 systems without errors. port

Re: atlas depends on gcc43 *and* gcc44 ???

On Jun 2, 2010, at 5:37 PM, Ryan Schmidt wrote: > Do we care about Tiger anymore? No. -- Up the airy mountains, down the rushy glen... From ghosties and bogles and long-leggity beasties... My mother said I never should... We dare not go a-hunting for fear... And things that go bump... P

Re: atlas depends on gcc43 *and* gcc44 ???

should be more efficient than Apple blas or lapack, most > probably generated with gcc42 (the last GPL2 version) and backward-compatible > with MacOS 10.4 or 10.5; Maybe they can get better efficiency with > Clang/LLVM. However, I faintly remember comparing the Atlas built-in tests,

Re: atlas depends on gcc43 *and* gcc44 ???

(the last GPL2 version) and backward-compatible with MacOS 10.4 or 10.5; Maybe they can get better efficiency with Clang/LLVM. However, I faintly remember comparing the Atlas built-in tests, and there was a clear gap between gcc43 and gcc44. It should not be very difficult to build up a test, li

Re: atlas depends on gcc43 *and* gcc44 ???

On Jun 2, 2010, Stephen Langer wrote: > I was wondering why anything depends on atlas at all. Is atlas noticeably > better than the lapack and blas routines in the > Accelerate framework? I > couldn't find any comparisons on-line. I was wondering the same thing as well. Since I am only insta

Re: atlas depends on gcc43 *and* gcc44 ???

On Wed, Jun 2, 2010 at 18:37, Ryan Schmidt wrote: >> That was a while ago so maybe it's time we revisit this? With my >> py25-numpy and py2{5,6}-scipy maintainers hat on I'd vote for a switch >> to gcc44 as the default compiler for scientific ports. > > Great! Now we're getting somewhere. :) > >

Re: atlas depends on gcc43 *and* gcc44 ???

On Jun 2, 2010, at 18:05, Adam Mercer wrote: > On Wed, Jun 2, 2010 at 17:40, Ryan Schmidt wrote: > >> AFAIK there *was* a consensus to use gcc43 by default for science ports. I >> had not heard any update on that decision, and pointed this discrepancy out >> to Marc

Re: atlas depends on gcc43 *and* gcc44 ???

On Wed, Jun 2, 2010 at 17:40, Ryan Schmidt wrote: > AFAIK there *was* a consensus to use gcc43 by default for science ports. I > had not heard any update on that decision, and pointed this discrepancy out > to Marcus who updated atlas and qrupdate to use gcc44 instead. See the >

Re: atlas depends on gcc43 *and* gcc44 ???

gt; standard OSX ones, but it would be nice if they could agree on which one ;) AFAIK there *was* a consensus to use gcc43 by default for science ports. I had not heard any update on that decision, and pointed this discrepancy out to Marcus who updated atlas and qrupdate to use gcc44 instead. See

Re: atlas depends on gcc43 *and* gcc44 ???

On 06/02/2010 11:13 PM, Stephen Langer wrote: > On Jun 2, 2010, at 3:35 PM, Chris Jones wrote: >> Its just a little annoying that a package like atlas, which is a >> dependency of a dependency drags in a big build like gcc when I >> have no other reason for it... I understand that some packages

Re: atlas depends on gcc43 *and* gcc44 ???

On Jun 2, 2010, at 3:35 PM, Chris Jones wrote: > Hi, > >> Is there a downside to having atlas depend on gcc44 while everything >> else depends on gcc43? > > Its just a little annoying that a package like atlas, which is a dependency > of a dependency drags in

Re: atlas depends on gcc43 *and* gcc44 ???

Hi, > Is there a downside to having atlas depend on gcc44 while everything > else depends on gcc43? Its just a little annoying that a package like atlas, which is a dependency of a dependency drags in a big build like gcc when I have no other reason for it... I understand tha

Re: atlas depends on gcc43 *and* gcc44 ???

> On 2010-6-1 05:48 , Chris Jones wrote: >> Does it make sense that atlas requires two different compilers ?? >> > It doesn't actually, the flat registry just thinks it does. > <http://trac.macports.org/ticket/13054> > > The default compiler used by atl

Re: atlas depends on gcc43 *and* gcc44 ???

On 2010-6-1 05:48 , Chris Jones wrote: > Hi, > > Does it make sense that atlas requires two different compilers ?? > > Chris-Jones-Macbook-Pro /opt/local > sudo port uninstall gcc43 > ---> Unable to uninstall gcc43 4.3.5_0, the following ports depend on i

Re: atlas depends on gcc43 *and* gcc44 ???

On May 31, 2010, at 14:48, Chris Jones wrote: > Does it make sense that atlas requires two different compilers ?? > > Chris-Jones-Macbook-Pro /opt/local > sudo port uninstall gcc43 > ---> Unable to uninstall gcc43 4.3.5_0, the following ports depend on it: >

atlas depends on gcc43 *and* gcc44 ???

Hi, Does it make sense that atlas requires two different compilers ?? Chris-Jones-Macbook-Pro /opt/local > sudo port uninstall gcc43 ---> Unable to uninstall gcc43 4.3.5_0, the following ports depend on it: --->atlas --->py26-numpy Error: port uninstall failed: Please u

Re: Linking 'gfortran' command to compiler in gcc43

Thanks a lot! That saved a lot of Internet searching. Andrew On 2010-04-23, at 3:59 PM, Rainer Müller wrote: > On 2010-04-23 21:41 , Andrew Lambe wrote: >> When I first installed gcc43 through Macports, I noticed that the >> command gfortran was undefined, even though gfortran

Re: Linking 'gfortran' command to compiler in gcc43

On 2010-4-24 05:41 , Andrew Lambe wrote: > When I first installed gcc43 through Macports, I noticed that the command > gfortran was undefined, even though gfortran comes with the package (for some > reason gcc did work as expected.) To compensate, I downloaded gfortran > separa

Re: Linking 'gfortran' command to compiler in gcc43

On 2010-04-23 21:41 , Andrew Lambe wrote: > When I first installed gcc43 through Macports, I noticed that the > command gfortran was undefined, even though gfortran comes with the > package (for some reason gcc did work as expected.) To compensate, I > downloaded gfortran separa

Linking 'gfortran' command to compiler in gcc43

When I first installed gcc43 through Macports, I noticed that the command gfortran was undefined, even though gfortran comes with the package (for some reason gcc did work as expected.) To compensate, I downloaded gfortran separately using a precompiled binary. I found out too late that

Re: Problems installing py26-scipy -> gcc43

On Apr 18, 2010, at 10:05, Robert Wilson wrote: > As a result of trying to install py26-scipy @0.7.1 I need gcc43. The > compilation was failing because of a conflict between the type of > pointer_t in /usr/include/mach/vm_types.h and that in the module.c > file. > ../../gcc-4.

Problems installing py26-scipy -> gcc43

The following is on an iMac running Mac OS X 10.6.3. As a result of trying to install py26-scipy @0.7.1 I need gcc43. The compilation was failing because of a conflict between the type of pointer_t in /usr/include/mach/vm_types.h and that in the module.c file. I introduced the following change

Re: can't install gcc43 or gcc44

On Sep 1, 2009, at 02:11, Rob Mahurin wrote: On Mon, Aug 31, 2009 at 04:01:28PM -0500, Adam Mercer wrote: Looks the same as: So it does, thanks. I was able to compile gcc44 after changing the Portfile as attached. It's not obvious to me how to add

Re: can't install gcc43 or gcc44

On Mon, Aug 31, 2009 at 04:01:28PM -0500, Adam Mercer wrote: > On Mon, Aug 31, 2009 at 13:07, Rob Mahurin wrote: > > > I'm trying to use MacPorts to install Octave and its dependencies on a > > new Mac running 10.5.8.  The install fails during the build of gcc. > >

Re: can't install gcc43 or gcc44

On Mon, Aug 31, 2009 at 13:07, Rob Mahurin wrote: > I'm trying to use MacPorts to install Octave and its dependencies on a > new Mac running 10.5.8.  The install fails during the build of gcc. > (I have tried gcc43 and gcc44.)  Attached is the output of > >        sudo port i

can't install gcc43 or gcc44

Hi, I'm trying to use MacPorts to install Octave and its dependencies on a new Mac running 10.5.8. The install fails during the build of gcc. (I have tried gcc43 and gcc44.) Attached is the output of sudo port install octave +gcc44 It looks like last err

Re: hdf5 and gcc43 option?

On Mar 14, 2009, at 12:59 AM, Yolande Serra wrote: Did you install hdf5-18 or hdf5? -Y. On Mar 13, 2009, at 7:05 PM, William Davis wrote: On Mar 13, 2009, at 5:12 PM, Yolande Serra wrote: Hi, has anyone gotten the hdf5 port with the gcc43 and fortran variants to compile on an intel mac

Re: hdf5 and gcc43 option?

Did you install hdf5-18 or hdf5? -Y. On Mar 13, 2009, at 7:05 PM, William Davis wrote: On Mar 13, 2009, at 5:12 PM, Yolande Serra wrote: Hi, has anyone gotten the hdf5 port with the gcc43 and fortran variants to compile on an intel mac running 10.5.6? thanks, Yolande Just did

Re: hdf5 and gcc43 option?

On Mar 13, 2009, at 5:12 PM, Yolande Serra wrote: Hi, has anyone gotten the hdf5 port with the gcc43 and fortran variants to compile on an intel mac running 10.5.6? thanks, Yolande Just did. smooth as silk. First time I've used gcc43 and Im impressed. William

hdf5 and gcc43 option?

Hi, has anyone gotten the hdf5 port with the gcc43 and fortran variants to compile on an intel mac running 10.5.6? thanks, Yolande ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi

Re: [Ticket #16549] gcc43: patch to add Ada support

On Oct 7, 2008, at 11:30 PM, Martin Krischik wrote: > The Trac Ticket #16549 [1] now open for 3 weeks and it seem to be > stalled. And it seems that the ticket is stalled over the fundamental > problem on how to handle self hosted systems [2]. Now I still would > like to go ahead so I would like

[Ticket #16549] gcc43: patch to add Ada support

art. And they should have the experience as well to deal with it. However MacPorts is source based so one need a "user friendly" which is a little trickier. My current solution is a variant in gcc43 which can only be used when certain pre-condition are meed. However it was suggested

gcc43 and openmp???

Hello everyone, Is there a chance that the macports provided gcc43 is not compiled with openmp support? I've been trying to run a very simple C++ program with openmp to see if I can take advantage of both cores. The program is as follows: #include #include using namespace std; int

Re: Compiling hdf5 1.6.7 with gcc43

On 11.04.2008, at 09:17, Marcus Calhoun-Lopez wrote: I believe this was fixed a couple of days ago in MacPorts (http://trac.macports.org/projects/macports/changeset/35904 ). Yes, that was me;-) However, it should be changed upstream in hdf5 directly. On Apr 11, 2008, at 12:20 AM, Jochen Küp

Compiling hdf5 1.6.7 with gcc43

To whom it may concern. When compiling hdf5-1.6.7 on Mac OS X using gcc-4.3 with C++ support an include for cstdlib is missing, see attached patch. Greetings, Jochen -- Einigkeit und Recht und Freiheithttp://www.Jochen-Kuepper.de Liberté, Égalité, Fraternité

Re: gcc43 Released?

ersion creates bad binaries > that cause problems for the 64 bit ld. Below is the error: > name /opt/local/lib/gcc43/x86_64/libgcj.9.dylib -compatibility_version 10 > -current_version 10.0 > /usr/bin/ld: fatal error in /usr/bin/ld64 > collect2: ld returned 1 exit status > make[

Re: gcc43 Released?

ave found > that the 64 bit version creates bad binaries that cause problems > for the 64 bit ld. Below is the error: > name /opt/local/lib/gcc43/x86_64/libgcj.9.dylib - > compatibility_version 10 -current_version 10.0 > /usr/bin/ld: fatal error in /usr/bin/ld64 > collect2

gcc43 Released?

/local/lib/gcc43/x86_64/libgcj.9.dylib -compatibility_version 10 -current_version 10.0 /usr/bin/ld: fatal error in /usr/bin/ld64 collect2: ld returned 1 exit status make[5]: *** [libgcj.la] Error 1 make[4]: *** [all-recursive] Error 1 make[3]: *** [multi-do] Error 1 make[2]: *** [all-multi] Error 2 make

gcc43 and Java/GCJ

Hi, I noticed that the gcc43 port does not have java configured. Are there issues with building the Java language in this build? The fortran language is also not configured, but it is listed as variant. If no one has already requested the java support, I would like to be the first. I have tried

Re: ?typo in portfile for gcc43 with gfortran

On Dec 27, 2007, at 12:37 AM, George Nurser wrote: On 26/12/2007, Ryan Schmidt <[EMAIL PROTECTED]> wrote: On Dec 26, 2007, at 09:55, George Nurser wrote: I have just tried to install the latest snapshot (20071221) of gcc43. I did sudo port -v install gcc43 +gfortran & got a f

Re: ?typo in portfile for gcc43 with gfortran

On 26/12/2007, Ryan Schmidt <[EMAIL PROTECTED]> wrote: > On Dec 26, 2007, at 09:55, George Nurser wrote: > > > I have just tried to install the latest snapshot (20071221) of gcc43. > > I did > > sudo port -v install gcc43 +gfortran > > > > & got a

Re: ?typo in portfile for gcc43 with gfortran

On Dec 26, 2007, at 09:55, George Nurser wrote: I have just tried to install the latest snapshot (20071221) of gcc43. I did sudo port -v install gcc43 +gfortran & got a failure The following requested languages could not be built: objc++ Supported languages are: c,c++,fortran,java,objc,o

?typo in portfile for gcc43 with gfortran

I have just tried to install the latest snapshot (20071221) of gcc43. I did sudo port -v install gcc43 +gfortran & got a failure The following requested languages could not be built: objc++ Supported languages are: c,c++,fortran,java,objc,obj-c++,treelang Error: Target org.macports.confi

gcc43

option =0 its target was i386-darwin So I could only build my program for that target. How can I use "port" to perhaps configure gcc43 before its build? Rds, ___ macports-users mailing list macports-users@lists.macosforg

GCC43 install fails and GCC42 64-bit problems

While this was visited before, there still seems to be a problem installing gcc43 dumping out with the error /usr/bin/ld: fatal error in /usr/bin/ld64 collect2: ld returned 1 exit status make[5]: *** [libgcj.la] Error 1 make[4]: *** [all-recursive] Error 1 make[3]: *** [multi-do] Error 1 make