Re: g95 suggestion
Please keep your replies on-list ;) You are welcome. Chris On 15 Feb 2014, at 3:17pm, Paolo Denti wrote: > It works fine. > Thank you very much. > Paolo Denti > Il giorno 15/feb/2014, alle ore 15:32, Christopher Jones > ha scritto: > >> >> >>> sudo port install gcc48 >> >> This will give you 'gfortran-mp-4.8’ as the compiler to use >> >> MacBookPro ~ > gfortran-mp-4.8 --version >> GNU Fortran (MacPorts gcc48 4.8.2_0) 4.8.2 >> Copyright (C) 2013 Free Software Foundation, Inc. >> >> GNU Fortran comes with NO WARRANTY, to the extent permitted by law. >> You may redistribute copies of GNU Fortran >> under the terms of the GNU General Public License. >> >> For more information about these matters, see the file named COPYINGOn 15 >> Feb 2014, at 2:14pm, io wrote: >> >>> Dear CRJ, thanks for suggestion. >>> However, I am only an unexperienced final user of fortran. So it would be >>> very useful for me if you mention an electable port to be installed. >>> Begging pardon for my naiveness, >>> Paolo Denti >>> ___ >>> macports-users mailing list >>> macports-users@lists.macosforge.org >>> https://lists.macosforge.org/mailman/listinfo/macports-users >> > smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: g95 suggestion
> sudo port install gcc48 This will give you 'gfortran-mp-4.8’ as the compiler to use MacBookPro ~ > gfortran-mp-4.8 --version GNU Fortran (MacPorts gcc48 4.8.2_0) 4.8.2 Copyright (C) 2013 Free Software Foundation, Inc. GNU Fortran comes with NO WARRANTY, to the extent permitted by law. You may redistribute copies of GNU Fortran under the terms of the GNU General Public License. For more information about these matters, see the file named COPYINGOn 15 Feb 2014, at 2:14pm, io wrote: > Dear CRJ, thanks for suggestion. > However, I am only an unexperienced final user of fortran. So it would be > very useful for me if you mention an electable port to be installed. > Begging pardon for my naiveness, > Paolo Denti > ___ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
g95 suggestion
Dear CRJ, thanks for suggestion. However, I am only an unexperienced final user of fortran. So it would be very useful for me if you mention an electable port to be installed. Begging pardon for my naiveness, Paolo Denti ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: g95
Try using gfortran from one of the numerous gccXY ports. On 15 Feb 2014, at 12:32pm, io wrote: > g95 with Mavericks 9.2 and Xcode 5.0.2 compiles but does not links to build > runtime, releasing the messages > paolodenti in ~/Desktop/incorso/130331/stnd $ g95 cluzwa.f -O0 -C -Wall > ld: library not found for -lcrt1.o > What should I do? > Thanks for suggestions. > Paolo Denti > ___ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
g95
g95 with Mavericks 9.2 and Xcode 5.0.2 compiles but does not links to build runtime, releasing the messages paolodenti in ~/Desktop/incorso/130331/stnd $ g95 cluzwa.f -O0 -C -Wall ld: library not found for -lcrt1.o What should I do? Thanks for suggestions. Paolo Denti___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: [MacPorts-announce] Update hangs configuring g95
Glad to hear it worked. Scott On Thu, Aug 4, 2011 at 5:43 PM, martin cohen wrote: > > > --- On *Wed, 8/3/11, Scott Webster * wrote: > > > From: Scott Webster > Subject: Re: [MacPorts-announce] Update hangs configuring g95 > To: macports-users@lists.macosforge.org > Cc: mjco...@acm.org > Date: Wednesday, August 3, 2011, 4:05 PM > > On Wed, Aug 3, 2011 at 4:00 PM, David Moreno > http://mc/compose?to=da...@axiombox.com>> > wrote: > > On Aug 3, 2011 6:45 PM, "martin cohen" > > http://mc/compose?to=mj...@yahoo.com>> > wrote: > >> This is what happens: > >> ---> Computing dependencies for g95 > >> ---> Fetching archive for g95 > >> ---> Attempting to fetch g95-0.92_2+gcc42.darwin_10.x86_64.tgz from > >> http://packages.macports.org/g95 > >> ---> Fetching g95 > >> ---> Attempting to fetch g95_source.tgz from http://ftp.g95.org/v0.92/ > >> ---> Verifying checksum(s) for g95 > >> ---> Extracting g95 > >> ---> Applying patches to g95 > >> ---> Configuring g95 > >> > > How long did you wait? I would try again in debug mode to get more info. > > sudo port clean g95 > sudo port -d install g95 > > You could also try posting the log file on the web somewhere and > sending the link to the mailing list for analysis and searching the > macports trac system for open tickets (bug reports) about g95 to see > if this is a known issue. > > Scott > > Scott, > > Thanks. I did this and it seemed to work. At least it made it through with > only warnings, but a surprising number of them. My macports update then ran > ok. > > I was impressed with how long the g95 update took. I guess software is a > third thing we should not watch being made. > > Marty Cohen > > ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: [MacPorts-announce] Update hangs configuring g95
On Wed, Aug 3, 2011 at 4:00 PM, David Moreno wrote: > On Aug 3, 2011 6:45 PM, "martin cohen" wrote: >> This is what happens: >> ---> Computing dependencies for g95 >> ---> Fetching archive for g95 >> ---> Attempting to fetch g95-0.92_2+gcc42.darwin_10.x86_64.tgz from >> http://packages.macports.org/g95 >> ---> Fetching g95 >> ---> Attempting to fetch g95_source.tgz from http://ftp.g95.org/v0.92/ >> ---> Verifying checksum(s) for g95 >> ---> Extracting g95 >> ---> Applying patches to g95 >> ---> Configuring g95 >> How long did you wait? I would try again in debug mode to get more info. sudo port clean g95 sudo port -d install g95 You could also try posting the log file on the web somewhere and sending the link to the mailing list for analysis and searching the macports trac system for open tickets (bug reports) about g95 to see if this is a known issue. Scott ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Gdb and g95
No, I did not use -ggdb. However I tried it and that does not seem to work.
Here is the resolution: the -g3 option. The set up that works is the Apple
build of gdb (6.5.3) and the -g3 compiler option with either gfortran or g95.
Debugging then works with the apple gdb but not the macports gdb (7.1). This
appears to be a very complex issue. I am thinking that machoread.c is
specifically for Darwin (see the error message below). Something is broken in
it, however. Apple's build seems to fix this.
I consider the matter resolved: use the -g3 option and the Apple-supplied gdb.
The wizards at macports might address the macports version of gdb at some
point. By the way, this sort of problem appears to affect fortran. C, C++, etc.
appears to have much less problem (my experience).
Much thanks.
-Tony
Message: 6
Date: Sun, 23 May 2010 19:47:50 -0400
From: Jean-Francois Gobin
To: "Mannucci, Anthony J (335G)"
Cc: "macports-users@lists.macosforge.org"
Subject: Re: Gdb and g95
Message-ID: <1274658470.2502.29.ca...@ubuntu01>
Content-Type: text/plain; charset="utf-8"
Could you try using "-ggdb" instead?
J.
On Sun, 2010-05-23 at 16:09 -0700, Mannucci, Anthony J (335G) wrote:
> I have installed gdb and fortran compiler g95 using macports. The debugger
> does not function with the fortran compiler. It does function with gcc
> compiling c programs.
>
> Nor does the standard gdb that ships with Apple developer tools work. The
> Apple gdb cannot set breakpoints in the fortran code. I have tried both the
> gfortran and g95 (Macports) compilers, and neither works with gdb.
>
> This is OS X leopard 10.5.x.
>
> Compiling as follows:
> g95 -g -c test4.f
> g95 -g test4.o -o test4.e
>
> Macintosh-10:382:tests $ which gdb
> /opt/local/bin/gdb
>
> Invoking gdb on the file test4.e yields the following error message.
>
> Macintosh-10:383:tests $ gdb test4.e
> GNU gdb (GDB) 7.1
> Copyright (C) 2010 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i386-apple-darwin9.8.0".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from
> /Users/mannucci/timegcm/tests/test4.e...machoread.c:169: internal-error:
> macho_symtab_read: Assertion `oso_file != NULL' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
>
>
> This is the error I received trying to build gdb on my own. Debugging
> fortran code on Darwin has proved to be a challenge.
>
> -Tony
>
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.macosforge.org/pipermail/macports-users/attachments/20100523/d090972e/attachment-0001.bin>
--
Message: 7
Date: Mon, 24 May 2010 09:34:11 +0300
From: Panayotis Katsaloulis
To: MacPorts Users
Subject: Re: xmlto fails to build with macports 1.90 beta
Message-ID:
Content-Type: text/plain; charset=iso-8859-7
On 23 ??? 2010, at 10:15 ?.?., Panayotis Katsaloulis wrote:
> Hello!
>
> I decided to have a go with 1.90 and I tried to compile a couple of things,
> being xmlto one of them.
> With this package I didn't have any luck.
As a follow up, I tried to download the source code from the developer's site
and compile it myself.
I had the same problems as with my previous email.
Any help?
--
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
End of macports-users Digest, Vol 45, Issue 24
**
--
Tony Mannucci
Supervisor, Ionospheric and Atmospheric Remote Sensing Group
Mail-Stop 138-308, Tel > (818) 354-1699
Jet Propulsion Laboratory, Fax > (818) 393-5115
California Institute of Technology, Email > tony.mannu...@jpl.nasa.gov
4800 Oak Grove Drive, http://genesis.jpl.nasa.gov
Pasadena, CA 91109
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Gdb and g95
Could you try using "-ggdb" instead? J. On Sun, 2010-05-23 at 16:09 -0700, Mannucci, Anthony J (335G) wrote: > I have installed gdb and fortran compiler g95 using macports. The debugger > does not function with the fortran compiler. It does function with gcc > compiling c programs. > > Nor does the standard gdb that ships with Apple developer tools work. The > Apple gdb cannot set breakpoints in the fortran code. I have tried both the > gfortran and g95 (Macports) compilers, and neither works with gdb. > > This is OS X leopard 10.5.x. > > Compiling as follows: > g95 -g -c test4.f > g95 -g test4.o -o test4.e > > Macintosh-10:382:tests $ which gdb > /opt/local/bin/gdb > > Invoking gdb on the file test4.e yields the following error message. > > Macintosh-10:383:tests $ gdb test4.e > GNU gdb (GDB) 7.1 > Copyright (C) 2010 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "i386-apple-darwin9.8.0". > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>... > Reading symbols from > /Users/mannucci/timegcm/tests/test4.e...machoread.c:169: internal-error: > macho_symtab_read: Assertion `oso_file != NULL' failed. > A problem internal to GDB has been detected, > further debugging may prove unreliable. > > > This is the error I received trying to build gdb on my own. Debugging > fortran code on Darwin has proved to be a challenge. > > -Tony > signature.asc Description: This is a digitally signed message part ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Gdb and g95
I have installed gdb and fortran compiler g95 using macports. The debugger does not function with the fortran compiler. It does function with gcc compiling c programs. Nor does the standard gdb that ships with Apple developer tools work. The Apple gdb cannot set breakpoints in the fortran code. I have tried both the gfortran and g95 (Macports) compilers, and neither works with gdb. This is OS X leopard 10.5.x. Compiling as follows: g95 -g -c test4.f g95 -g test4.o -o test4.e Macintosh-10:382:tests $ which gdb /opt/local/bin/gdb Invoking gdb on the file test4.e yields the following error message. Macintosh-10:383:tests $ gdb test4.e GNU gdb (GDB) 7.1 Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i386-apple-darwin9.8.0". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /Users/mannucci/timegcm/tests/test4.e...machoread.c:169: internal-error: macho_symtab_read: Assertion `oso_file != NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. This is the error I received trying to build gdb on my own. Debugging fortran code on Darwin has proved to be a challenge. -Tony -- Tony Mannucci Supervisor, Ionospheric and Atmospheric Remote Sensing Group Mail-Stop 138-308, Tel > (818) 354-1699 Jet Propulsion Laboratory, Fax > (818) 393-5115 California Institute of Technology, Email > tony.mannu...@jpl.nasa.gov 4800 Oak Grove Drive, http://genesis.jpl.nasa.gov Pasadena, CA 91109 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: g95 netcdf / mac architectures
Sorry, my fault. Best, Felipe. On Mon, Mar 22, 2010 at 9:04 AM, Ryan Schmidt wrote: > Ok. Don't forget to reply all so your reply goes to the mailing list too, not > just to me. > > > On Mar 22, 2010, at 06:57, Felipe Pimenta wrote: > >> Hi Ryan, >> >> Yes, just warnings. Yes, the build completes, and the executable runs >> well, in both machines. I wrote to G95 team about it, but I have not >> received their answer yet. I will let you know if they reply to this >> problem. >> >> Thanks, >> >> F. >> >> On Mon, Mar 22, 2010 at 7:19 AM, Ryan Schmidt wrote: >>> >> >>> On Mar 21, 2010, at 12:49, Felipe Pimenta wrote: >>> >>>> The PowerPC compilation is smooth. The Intel generates a long list of >>>> warnings during the compilation. Here's a piece of these warnings: >>>> >>>> g95 -O5 -c -o areas_masks.o areas_masks.f >>>> areas_masks.f: In function ‘areas_masks__’: >>>> areas_masks.f:44: warning: will never be executed >>>> areas_masks.f:37: warning: will never be executed >>>> areas_masks.f:32: warning: will never be executed >>>> areas_masks.f:25: warning: will never be executed >>>> areas_masks.f:17: warning: will never be executed >>>> g95 -O5 -c -o advave.o advave.f >>>> advave.f: In function ‘advave_’: >>>> advave.f:160: warning: will never be executed >>>> advave.f:151: warning: will never be executed >>>> ...etc >>>> >>>> I've noticed that some lines are in the start of a "do loop". Both >>>> generate an executable, however. >>>> >>>> Are the warnings related to their architectures? Any hints on how to fix >>>> this? >>> >>> Warnings only -- not errors? The build completes? >>> >>> You may want to report this to the developers of the software. > > -- == Felipe M. Pimenta R. Murta 147, Campeche, Florianópolis Santa Catarina, Brasil, 88066-125 Phone: (55) 48 3334-1636 == ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: g95 netcdf / mac architectures
Ok. Don't forget to reply all so your reply goes to the mailing list too, not just to me. On Mar 22, 2010, at 06:57, Felipe Pimenta wrote: > Hi Ryan, > > Yes, just warnings. Yes, the build completes, and the executable runs > well, in both machines. I wrote to G95 team about it, but I have not > received their answer yet. I will let you know if they reply to this > problem. > > Thanks, > > F. > > On Mon, Mar 22, 2010 at 7:19 AM, Ryan Schmidt wrote: >> > >> On Mar 21, 2010, at 12:49, Felipe Pimenta wrote: >> >>> The PowerPC compilation is smooth. The Intel generates a long list of >>> warnings during the compilation. Here's a piece of these warnings: >>> >>> g95-O5 -c -o areas_masks.o areas_masks.f >>> areas_masks.f: In function ‘areas_masks__’: >>> areas_masks.f:44: warning: will never be executed >>> areas_masks.f:37: warning: will never be executed >>> areas_masks.f:32: warning: will never be executed >>> areas_masks.f:25: warning: will never be executed >>> areas_masks.f:17: warning: will never be executed >>> g95-O5 -c -o advave.o advave.f >>> advave.f: In function ‘advave_’: >>> advave.f:160: warning: will never be executed >>> advave.f:151: warning: will never be executed >>> ...etc >>> >>> I've noticed that some lines are in the start of a "do loop". Both >>> generate an executable, however. >>> >>> Are the warnings related to their architectures? Any hints on how to fix >>> this? >> >> Warnings only -- not errors? The build completes? >> >> You may want to report this to the developers of the software. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: g95 netcdf / mac architectures
On Mar 21, 2010, at 12:49, Felipe Pimenta wrote: > The PowerPC compilation is smooth. The Intel generates a long list of > warnings during the compilation. Here's a piece of these warnings: > > g95-O5 -c -o areas_masks.o areas_masks.f > areas_masks.f: In function ‘areas_masks__’: > areas_masks.f:44: warning: will never be executed > areas_masks.f:37: warning: will never be executed > areas_masks.f:32: warning: will never be executed > areas_masks.f:25: warning: will never be executed > areas_masks.f:17: warning: will never be executed > g95-O5 -c -o advave.o advave.f > advave.f: In function ‘advave_’: > advave.f:160: warning: will never be executed > advave.f:151: warning: will never be executed > ...etc > > I've noticed that some lines are in the start of a "do loop". Both > generate an executable, however. > > Are the warnings related to their architectures? Any hints on how to fix this? Warnings only -- not errors? The build completes? You may want to report this to the developers of the software. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
g95 netcdf / mac architectures
Dear users, I've installed g95 and netcdf in two macs. The first is a MacBook Pro (Intel 2.53 GHz) with Mac OS X 10.6.2. After installation I obtain: $port installed g95 @0.91_2+darwin_10+gcc42 (active) netcdf @4.1_1+g95 (active) The second mac is PowerPC G5, 2.5 GHz with Mac OS X 10.5.8. The installation results on: $port installed g95 @0.91_2 (active) netcdf @4.1_1+g95 (active) (differnt only for the variant on g95). These computers compile a code in different ways, see below. The PowerPC compilation is smooth. The Intel generates a long list of warnings during the compilation. Here's a piece of these warnings: g95 -O5 -c -o areas_masks.o areas_masks.f areas_masks.f: In function ‘areas_masks__’: areas_masks.f:44: warning: will never be executed areas_masks.f:37: warning: will never be executed areas_masks.f:32: warning: will never be executed areas_masks.f:25: warning: will never be executed areas_masks.f:17: warning: will never be executed g95 -O5 -c -o advave.o advave.f advave.f: In function ‘advave_’: advave.f:160: warning: will never be executed advave.f:151: warning: will never be executed ...etc I've noticed that some lines are in the start of a "do loop". Both generate an executable, however. Are the warnings related to their architectures? Any hints on how to fix this? Many thanks, Felipe -- == Felipe M. Pimenta R. Murta 147, Campeche, Florianópolis Santa Catarina, Brasil, 88066-125 Phone: (55) 48 3334-1636 == ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: enable to fetch g95
David Trem wrote: > Using fresh install of macport on leopard: > > ---> Fetching g95 > ---> Attempting to fetch g95_source.tgz from http://ftp.g95.org/v0.91/ > Error: Target org.macports.fetch returned: fetch failed > > Is this temporary server problem or something else? g95.org is a server we do not control. So you would have to speak to their admins to find out what the issue is. But you can use our new MacPorts distfiles mirror for now: $ sudo env MASTER_SITE_LOCAL=http://distfiles.macports.org/g95/:g95 \ port fetch g95 Or get the file from somewhere else and simply put it into /opt/local/var/macports/distfiles/g95. Rainer ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
enable to fetch g95
Using fresh install of macport on leopard: ---> Fetching g95 ---> Attempting to fetch g95_source.tgz from http://ftp.g95.org/v0.91/ Error: Target org.macports.fetch returned: fetch failed Is this temporary server problem or something else? David ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: py25-numpy keeps wanting to install g95 on upgrade
Hi, It reminds me that the dependency graph on py25-cairo (a fairly needed port for all things gtk2 IIRC) seems a bit awkward, due to the dependency on py25-numpy declared, which was added in Ticket #14652. I have been using a modified py25-cairo Portfile removing that dependency because it pulls lots of IMHO heavy stuff, like g95 or other compilers. So far I haven't been encountering bugs, but I'm just installing the cairo python bindings as dependencies, not as a cairo programmer. Could the dependency graph be simplified (if at all possible)? -- Pierre Daniel Horwood wrote: When I initially installed py25-numpy I used its +gcc43 variant (which removes py25-numpy's g95 dependency), and it installed just fine. Today, however, when I tried to upgrade gnome-menus, I had to Ctrl-C when I saw that macports had started downloading files for the g95 port. It took me a while to trace down, but it's definitely something to do with py25-numpy. The receipt in /opt/local/var/macports/receipts/py25-numpy/1.0.4_7+gcc43/ correctly lists the variant as +gcc43, so I'm not sure what's going wrong. Here are the bottom few lines of output from '$ sudo port -dv upgrade py25-numpy': === DEBUG: No need to upgrade! openssl 0.9.8g_0 >= openssl 0.9.8g_0 DEBUG: No need to upgrade! py25-hashlib 2.5.2_0 >= py25-hashlib 2.5.2_0 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/g95 DEBUG: g95 is *not* installed by MacPorts DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/g95 DEBUG: Requested variant darwin is not provided by port g95. DEBUG: Requested variant i386 is not provided by port g95. DEBUG: Requested variant macosx is not provided by port g95. DEBUG: Executing variant darwin_9 provides darwin_9 DEBUG: Searching for dependency: g95 DEBUG: Didn't find receipt, going to depspec regex for: g95 DEBUG: Executing org.macports.main (g95) ---> Fetching g95 DEBUG: Executing proc-pre-org.macports.fetch-fetch-0 DEBUG: Executing org.macports.fetch (g95) ---> gcc-core-4.0.3.tar.gz doesn't seem to exist in /opt/local/var/macports/distfiles/g95 ---> Attempting to fetch gcc-core-4.0.3.tar.gz from ftp://gcc.gnu.org/pub/gcc/releases/gcc-4.0.3/ === Steps to reproduce: 1. sudo port install py25-numpy +gcc43 2. sudo port upgrade py25-numpy My system: macports 1.6; OSX 10.5.2 (Intel) I'll file a bug once I confirm this isn't user error, but I have a feeling that it's the funky way that the py25-numpy sets +g95 as a default variant within a conditional block. Dan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: py25-numpy keeps wanting to install g95 on upgrade
On Apr 23, 2008, at 12:07 PM, Ryan Schmidt wrote: I'll file a bug once I confirm this isn't user error, but I have a feeling that it's the funky way that the py25-numpy sets +g95 as a default variant within a conditional block. I don't consider the way in which py25-numpy sets the default variant in a conditional to be funky. It's a strategy I employ in my ports too. I recommend it. I personally don't like that style. For the py25-numpy port, you can get equivalent functionality by including the g95 variant stuff in the main port body and having the gcc42/gcc43 variants do appropriate deletion/addition of depends_lib/ build.cmd However, Ryan is right in that there may be a bug here since it should probably work with things as they are set up. -- Daniel J. Luke ++ | * [EMAIL PROTECTED] * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ PGP.sig Description: This is a digitally signed message part ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: py25-numpy keeps wanting to install g95 on upgrade
On Apr 23, 2008, at 9:16 AM, Daniel Horwood wrote: When I initially installed py25-numpy I used its +gcc43 variant (which removes py25-numpy's g95 dependency), and it installed just fine. Today, however, when I tried to upgrade gnome-menus, I had to Ctrl-C when I saw that macports had started downloading files for the g95 port. It took me a while to trace down, but it's definitely something to do with py25-numpy. The receipt in /opt/local/var/macports/receipts/py25-numpy/1.0.4_7 +gcc43/ correctly lists the variant as +gcc43, so I'm not sure what's going wrong. Here are the bottom few lines of output from '$ sudo port -dv upgrade py25-numpy': === DEBUG: No need to upgrade! openssl 0.9.8g_0 >= openssl 0.9.8g_0 DEBUG: No need to upgrade! py25-hashlib 2.5.2_0 >= py25-hashlib 2.5.2_0 DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/lang/g95 DEBUG: g95 is *not* installed by MacPorts DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/lang/g95 DEBUG: Requested variant darwin is not provided by port g95. DEBUG: Requested variant i386 is not provided by port g95. DEBUG: Requested variant macosx is not provided by port g95. DEBUG: Executing variant darwin_9 provides darwin_9 DEBUG: Searching for dependency: g95 DEBUG: Didn't find receipt, going to depspec regex for: g95 DEBUG: Executing org.macports.main (g95) ---> Fetching g95 DEBUG: Executing proc-pre-org.macports.fetch-fetch-0 DEBUG: Executing org.macports.fetch (g95) ---> gcc-core-4.0.3.tar.gz doesn't seem to exist in /opt/local/var/ macports/distfiles/g95 ---> Attempting to fetch gcc-core-4.0.3.tar.gz from ftp:// gcc.gnu.org/pub/gcc/releases/gcc-4.0.3/ === Steps to reproduce: 1. sudo port install py25-numpy +gcc43 2. sudo port upgrade py25-numpy My system: macports 1.6; OSX 10.5.2 (Intel) I'll file a bug once I confirm this isn't user error, but I have a feeling that it's the funky way that the py25-numpy sets +g95 as a default variant within a conditional block. I don't consider the way in which py25-numpy sets the default variant in a conditional to be funky. It's a strategy I employ in my ports too. I recommend it. Th´re may be a MacPorts base bug here. What you describe sounds vaguely familiar. I can't test it out right now though as my CPU is busy with other things. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
py25-numpy keeps wanting to install g95 on upgrade
When I initially installed py25-numpy I used its +gcc43 variant (which removes py25-numpy's g95 dependency), and it installed just fine. Today, however, when I tried to upgrade gnome-menus, I had to Ctrl-C when I saw that macports had started downloading files for the g95 port. It took me a while to trace down, but it's definitely something to do with py25-numpy. The receipt in /opt/local/var/macports/receipts/py25-numpy/ 1.0.4_7+gcc43/ correctly lists the variant as +gcc43, so I'm not sure what's going wrong. Here are the bottom few lines of output from '$ sudo port -dv upgrade py25-numpy': === DEBUG: No need to upgrade! openssl 0.9.8g_0 >= openssl 0.9.8g_0 DEBUG: No need to upgrade! py25-hashlib 2.5.2_0 >= py25-hashlib 2.5.2_0 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/g95 DEBUG: g95 is *not* installed by MacPorts DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/lang/g95 DEBUG: Requested variant darwin is not provided by port g95. DEBUG: Requested variant i386 is not provided by port g95. DEBUG: Requested variant macosx is not provided by port g95. DEBUG: Executing variant darwin_9 provides darwin_9 DEBUG: Searching for dependency: g95 DEBUG: Didn't find receipt, going to depspec regex for: g95 DEBUG: Executing org.macports.main (g95) ---> Fetching g95 DEBUG: Executing proc-pre-org.macports.fetch-fetch-0 DEBUG: Executing org.macports.fetch (g95) ---> gcc-core-4.0.3.tar.gz doesn't seem to exist in /opt/local/var/ macports/distfiles/g95 ---> Attempting to fetch gcc-core-4.0.3.tar.gz from ftp://gcc.gnu.org/pub/gcc/releases/gcc-4.0.3/ === Steps to reproduce: 1. sudo port install py25-numpy +gcc43 2. sudo port upgrade py25-numpy My system: macports 1.6; OSX 10.5.2 (Intel) I'll file a bug once I confirm this isn't user error, but I have a feeling that it's the funky way that the py25-numpy sets +g95 as a default variant within a conditional block. Dan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
g95-0.90_2 Intel Leopard build error
Hi I'm having a problem building g95-0.90_2 on Intel Leopard, I get the following error: Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/g95-0.90" && make all " returned error 2 Command output: /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/gcc.h:45:1: warning: this is the location of the previous definition gawk -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opt-functions.awk \ -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opt-gather.awk \ /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/common.opt lang.opt > options.tmp gawk -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opt-functions.awk \ -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/optc-gen.awk options.tmp > options.c gawk -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opt-functions.awk \ -f /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opth-gen.awk options.tmp > options.h /usr/bin/gcc-4.0 -c -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp-precomp -I. -I- -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/config -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/libcpp/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/gcc -I/opt/local/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/intl -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/intl /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/opts.c cc1: note: obsolete option -I- used, please use -iquote instead /usr/bin/gcc-4.0 -c -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp-precomp -I. -I- -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/config -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/libcpp/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/gcc -I/opt/local/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/intl -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/intl options.c cc1: note: obsolete option -I- used, please use -iquote instead /usr/bin/gcc-4.0 -c -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp-precomp -DTARGET_NAME=\"i386-apple-darwin9.1.0\" -DSTANDARD_EXEC_PREFIX=\"/opt/local/lib/gcc-lib/i386-apple-darwin9.1.0/4.0.3\" -DTARGET_SYSTEM_ROOT=\"\" -DDEFAULT_TARGET_VERSION=\"\" -DDEFAULT_TARGET_MACHINE=\"\" -DTOOLDIR_BASE_PREFIX=\"\" -DSTANDARD_STARTFILE_PREFIX=\"\" -DSTANDARD_STARTFILE_PREFIX_2=\"/usr/lib/\" -DSTANDARD_EXEC_PREFIX=\"/opt/local/lib/gcc-lib/i386-apple-darwin9.1.0/4.0.3\" -DSTANDARD_BINDIR_PREFIX=\"/opt/local/bin\" -DSTANDARD_LIBEXEC_PREFIX=\"/opt/local/lib/gcc-lib/i386-apple-darwin9.1.0/4.0.3\" -DG95_SPEC=\"\" -I. -I- -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/config -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/libcpp/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/gcc -I/opt/local/include -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/g95/intl -I/opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/intl /opt/local/var/macports/build/_Users_ram_opt_macports_lang_g95/work/gcc-4.0.3/gcc/gcc.c cc1: note: obsolete option -I- used, please use -iquote instead echo "const char version_string[] = \"`cat gcc_version` (g95 0.90!) \" __DATE__;" > version.c echo 'const char bug_report_url[] = "http://www.g95.org or mail [EMAIL PROTECTED]";' >> version.c /usr/bin/gcc-4.0 -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp-precomp -c version.c /usr/bin/gcc-4.0 -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp-precomp -L/opt/local/lib -o g95 g95-g95spec.o /opt/local/var/m
Re: g95 Leopard
I tried renaming /usr/local but the build still failed with the same error. On 24 Dec 2007, at 19:33, Ryan Schmidt wrote: On Dec 24, 2007, at 13:27, Simon J. Bale wrote: On 24 Dec 2007, at 19:10, Ryan Schmidt wrote: On Dec 24, 2007, at 09:09, [EMAIL PROTECTED] wrote: I'm trying to install g95 on Leopard and is seems to fail with the following error: Undefined symbols: "_iconv", referenced from: __nl_find_msg in libintl.a(dcigettext.o) "_iconv_open", referenced from: __nl_init_domain_conv in libintl.a(loadmsgcat.o) __nl_init_domain_conv in libintl.a(loadmsgcat.o) "_iconv_close", referenced from: __nl_free_domain_conv in libintl.a(loadmsgcat.o) ld: symbol(s) not found collect2: ld returned 1 exit status make[1]: *** [g95] Error 1 make: *** [all] Error 2 I've had a look through the bug reports and this problem seems to have been reported but changeset 32219 was supposed to have fixed the build issues on Leopard. Is anyone else still having the same problem? That changeset was supposed to have resolved #13190... So you're having problems with iconv symbols referenced from the gettext library. What versions of libiconv and gettext do you have installed? $ port installed libiconv gettext And can you show me what the relevant libraries are linked with? $ otool -L /opt/local/lib/libiconv.dylib /opt/local/lib/ libintl.dylib Do you have anything in /usr/local? Anything in /sw? If so, these can conflict with MacPorts ports. Thanks for the reply. I have libiconv 1.12_0 and gettext 0.17_2 installed. The output of otool -L /opt/local/lib/libiconv.dylib /opt/local/ lib/libintl.dylib is: /opt/local/lib/libiconv.dylib: /opt/local/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.0.0) /opt/local/lib/libintl.dylib: /opt/local/lib/libintl.8.dylib (compatibility version 9.0.0, current version 9.2.0) /opt/local/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.0.0) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/ CoreFoundation (compatibility version 150.0.0, current version 476.0.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) Well, drat, that's pretty much what mine says too (modulo some different version numbers since you're on Leopard and I'm on Tiger). So that doesn't help us identify the problem. I have a MacTex installed in /usr/local. Any help is greatly appreciated. You could try renaming /usr/local (e.g. to /usr/local-off) and try installing g95 again (after cleaning it: sudo port clean --work g95) to see if anything in /usr/local was interfering. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: g95 Leopard
There seems to be libintl.dylib in /usr/local from the MacTex distribution. Is there any way to force g95 to use the libraries in / opt/local/lib ? On 24 Dec 2007, at 19:33, Ryan Schmidt wrote: On Dec 24, 2007, at 13:27, Simon J. Bale wrote: On 24 Dec 2007, at 19:10, Ryan Schmidt wrote: On Dec 24, 2007, at 09:09, [EMAIL PROTECTED] wrote: I'm trying to install g95 on Leopard and is seems to fail with the following error: Undefined symbols: "_iconv", referenced from: __nl_find_msg in libintl.a(dcigettext.o) "_iconv_open", referenced from: __nl_init_domain_conv in libintl.a(loadmsgcat.o) __nl_init_domain_conv in libintl.a(loadmsgcat.o) "_iconv_close", referenced from: __nl_free_domain_conv in libintl.a(loadmsgcat.o) ld: symbol(s) not found collect2: ld returned 1 exit status make[1]: *** [g95] Error 1 make: *** [all] Error 2 I've had a look through the bug reports and this problem seems to have been reported but changeset 32219 was supposed to have fixed the build issues on Leopard. Is anyone else still having the same problem? That changeset was supposed to have resolved #13190... So you're having problems with iconv symbols referenced from the gettext library. What versions of libiconv and gettext do you have installed? $ port installed libiconv gettext And can you show me what the relevant libraries are linked with? $ otool -L /opt/local/lib/libiconv.dylib /opt/local/lib/ libintl.dylib Do you have anything in /usr/local? Anything in /sw? If so, these can conflict with MacPorts ports. Thanks for the reply. I have libiconv 1.12_0 and gettext 0.17_2 installed. The output of otool -L /opt/local/lib/libiconv.dylib /opt/local/ lib/libintl.dylib is: /opt/local/lib/libiconv.dylib: /opt/local/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.0.0) /opt/local/lib/libintl.dylib: /opt/local/lib/libintl.8.dylib (compatibility version 9.0.0, current version 9.2.0) /opt/local/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.0.0) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/ CoreFoundation (compatibility version 150.0.0, current version 476.0.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) Well, drat, that's pretty much what mine says too (modulo some different version numbers since you're on Leopard and I'm on Tiger). So that doesn't help us identify the problem. I have a MacTex installed in /usr/local. Any help is greatly appreciated. You could try renaming /usr/local (e.g. to /usr/local-off) and try installing g95 again (after cleaning it: sudo port clean --work g95) to see if anything in /usr/local was interfering. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: g95 Leopard
On Dec 24, 2007, at 13:27, Simon J. Bale wrote: On 24 Dec 2007, at 19:10, Ryan Schmidt wrote: On Dec 24, 2007, at 09:09, [EMAIL PROTECTED] wrote: I'm trying to install g95 on Leopard and is seems to fail with the following error: Undefined symbols: "_iconv", referenced from: __nl_find_msg in libintl.a(dcigettext.o) "_iconv_open", referenced from: __nl_init_domain_conv in libintl.a(loadmsgcat.o) __nl_init_domain_conv in libintl.a(loadmsgcat.o) "_iconv_close", referenced from: __nl_free_domain_conv in libintl.a(loadmsgcat.o) ld: symbol(s) not found collect2: ld returned 1 exit status make[1]: *** [g95] Error 1 make: *** [all] Error 2 I've had a look through the bug reports and this problem seems to have been reported but changeset 32219 was supposed to have fixed the build issues on Leopard. Is anyone else still having the same problem? That changeset was supposed to have resolved #13190... So you're having problems with iconv symbols referenced from the gettext library. What versions of libiconv and gettext do you have installed? $ port installed libiconv gettext And can you show me what the relevant libraries are linked with? $ otool -L /opt/local/lib/libiconv.dylib /opt/local/lib/libintl.dylib Do you have anything in /usr/local? Anything in /sw? If so, these can conflict with MacPorts ports. Thanks for the reply. I have libiconv 1.12_0 and gettext 0.17_2 installed. The output of otool -L /opt/local/lib/libiconv.dylib /opt/local/ lib/libintl.dylib is: /opt/local/lib/libiconv.dylib: /opt/local/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.0.0) /opt/local/lib/libintl.dylib: /opt/local/lib/libintl.8.dylib (compatibility version 9.0.0, current version 9.2.0) /opt/local/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.0.0) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/ CoreFoundation (compatibility version 150.0.0, current version 476.0.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) Well, drat, that's pretty much what mine says too (modulo some different version numbers since you're on Leopard and I'm on Tiger). So that doesn't help us identify the problem. I have a MacTex installed in /usr/local. Any help is greatly appreciated. You could try renaming /usr/local (e.g. to /usr/local-off) and try installing g95 again (after cleaning it: sudo port clean --work g95) to see if anything in /usr/local was interfering. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: g95 Leopard
On Dec 24, 2007, at 09:09, [EMAIL PROTECTED] wrote: I'm trying to install g95 on Leopard and is seems to fail with the following error: Undefined symbols: "_iconv", referenced from: __nl_find_msg in libintl.a(dcigettext.o) "_iconv_open", referenced from: __nl_init_domain_conv in libintl.a(loadmsgcat.o) __nl_init_domain_conv in libintl.a(loadmsgcat.o) "_iconv_close", referenced from: __nl_free_domain_conv in libintl.a(loadmsgcat.o) ld: symbol(s) not found collect2: ld returned 1 exit status make[1]: *** [g95] Error 1 make: *** [all] Error 2 I've had a look through the bug reports and this problem seems to have been reported but changeset 32219 was supposed to have fixed the build issues on Leopard. Is anyone else still having the same problem? That changeset was supposed to have resolved #13190... So you're having problems with iconv symbols referenced from the gettext library. What versions of libiconv and gettext do you have installed? $ port installed libiconv gettext And can you show me what the relevant libraries are linked with? $ otool -L /opt/local/lib/libiconv.dylib /opt/local/lib/libintl.dylib Do you have anything in /usr/local? Anything in /sw? If so, these can conflict with MacPorts ports. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
g95 Leopard
Hi, I'm trying to install g95 on Leopard and is seems to fail with the following error: Undefined symbols: "_iconv", referenced from: __nl_find_msg in libintl.a(dcigettext.o) "_iconv_open", referenced from: __nl_init_domain_conv in libintl.a(loadmsgcat.o) __nl_init_domain_conv in libintl.a(loadmsgcat.o) "_iconv_close", referenced from: __nl_free_domain_conv in libintl.a(loadmsgcat.o) ld: symbol(s) not found collect2: ld returned 1 exit status make[1]: *** [g95] Error 1 make: *** [all] Error 2 I've had a look through the bug reports and this problem seems to have been reported but changeset 32219 was supposed to have fixed the build issues on Leopard. Is anyone else still having the same problem? Best Regards, Simon ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: g95
Please file a bug report and Cc the port's maintainer. Instructions for filing bugs are here: http://trac.macosforge.org/projects/macports/wiki/TracTicketing On Dec 20, 2007, at 20:42, William Davis wrote: attempting the new g95 portfile install gave: cc1: note: obsolete option -I- used, please use -iquote instead echo "const char version_string[] = \"`cat gcc_version` (g95 0.90!) \" __DATE__;" > version.c echo 'const char bug_report_url[] = "http://www.g95.org or mail [EMAIL PROTECTED]";' >> version.c /usr/bin/gcc-4.0 -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp- precomp -c version.c /usr/bin/gcc-4.0 -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp- precomp -L/opt/local/lib -o g95 g95-g95spec.o /opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ g95/work/gcc-4.0.3/g95/gcc/prefix.o gcc.o version.o /opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ g95/work/gcc-4.0.3/g95/gcc/intl.o /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ g95/work/gcc-4.0.3/g95/libiberty/libiberty.a /opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ g95/work/gcc-4.0.3/g95/intl/libintl.a -liconv Undefined symbols: "_iconv", referenced from: __nl_find_msg in libintl.a(dcigettext.o) "_iconv_open", referenced from: __nl_init_domain_conv in libintl.a(loadmsgcat.o) __nl_init_domain_conv in libintl.a(loadmsgcat.o) "_iconv_close", referenced from: __nl_free_domain_conv in libintl.a(loadmsgcat.o) ld: symbol(s) not found collect2: ld returned 1 exit status make[1]: *** [g95] Error 1 make: *** [all] Error 2 Warning: the following items did not execute (for g95): org.macports.destroot org.macports.build DEBUG: Error: Unable to upgrade port: 1 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
g95
attempting the new g95 portfile install gave: cc1: note: obsolete option -I- used, please use -iquote instead echo "const char version_string[] = \"`cat gcc_version` (g95 0.90!) \" __DATE__;" > version.c echo 'const char bug_report_url[] = "http://www.g95.org or mail [EMAIL PROTECTED] ";' >> version.c /usr/bin/gcc-4.0 -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp- precomp -c version.c /usr/bin/gcc-4.0 -O2 -DIN_GCC -Wall -Wmissing-prototypes -no-cpp- precomp -L/opt/local/lib -o g95 g95-g95spec.o /opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_lang_g95/work/gcc-4.0.3/g95/gcc/prefix.o gcc.o version.o /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_lang_g95/work/gcc-4.0.3/g95/gcc/intl.o / opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_lang_g95/work/gcc-4.0.3/g95/libiberty/ libiberty.a /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_lang_g95/work/gcc-4.0.3/g95/intl/libintl.a -liconv Undefined symbols: "_iconv", referenced from: __nl_find_msg in libintl.a(dcigettext.o) "_iconv_open", referenced from: __nl_init_domain_conv in libintl.a(loadmsgcat.o) __nl_init_domain_conv in libintl.a(loadmsgcat.o) "_iconv_close", referenced from: __nl_free_domain_conv in libintl.a(loadmsgcat.o) ld: symbol(s) not found collect2: ld returned 1 exit status make[1]: *** [g95] Error 1 make: *** [all] Error 2 Warning: the following items did not execute (for g95): org.macports.destroot org.macports.build DEBUG: Error: Unable to upgrade port: 1 William Davis frstanATbellsouthDOTnet Mac OS X.5.1 Darwin 9.1.0 X11.app 2.1.1 - (xorg-server 1.3.0-apple5) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: g95
On Nov 11, 2007, at 3:48 PM, Adam Mercer wrote:
On 11/11/2007, William Davis <[EMAIL PROTECTED]> wrote:
Help me understand: the Leopard version of gcc is 4.0.1 as supplied
by
apple. mac ports has a gcc 4.0 @ 4.0.4 (and a gcc 4.2 @ 4.2.2).
So where does gcc 4.0.3 come from?
g95 pulls down the gcc-core-4.0.3 source.
Cheers
Adam
thanks Adam, I see that now. Though I now have Leopard, my existing
(working) g95 was built and installed installed under OS 10.4.10.
g95 -dumpspecs does give *version: 4.0.3 and
*darwin_arch:
i686
*darwin_subarch:
%{march=pentium3:pentIIm3;:i686}
for what that is worth as information. Attempting rebuild failed as
indicated by Takeshi. I wonder if this warning had anything to do
with the case:
gcc -c -DHAVE_CONFIG_H -g -O2 -I. -I../../libiberty/../include -W -
Wall -Wtraditional -pedantic ../../libiberty/concat.c -o concat.o
../../libiberty/concat.c: In function 'concat_length':
../../libiberty/concat.c:112: warning: traditional C rejects ISO C
style function definitions
../../libiberty/concat.c: In function 'concat_copy':
../../libiberty/concat.c:127: warning: traditional C rejects ISO C
style function definitions
../../libiberty/concat.c: In function 'concat_copy2':
../../libiberty/concat.c:146: warning: traditional C rejects ISO C
style function definitions
../../libiberty/concat.c: In function 'concat':
../../libiberty/concat.c:157: warning: traditional C rejects ISO C
style function definitions
../../libiberty/concat.c: In function 'reconcat':
../../libiberty/concat.c:194: warning: traditional C rejects ISO C
style function definitions
and also:
(SHLIB_LINK='/opt/local/var/macports/build/
_opt_local_var_macports_sources_rsync
.macports.org_release_ports_lang_g95/work/gcc-4.0.3/g95/gcc/xgcc -B/
opt/local/var/macports/build/
_opt_local_var_macports_sources_rsync
.macports.org_release_ports_lang_g95/work/gcc-4.0.3/g95/gcc/ -B/opt/
local/lib/gcc-lib/i386-apple-darwin9.0.0/4.0.3/i386-apple-darwin9.0.0/
bin/ -B/opt/local/lib/gcc-lib/i386-apple-darwin9.0.0/4.0.3/i386-apple-
darwin9.0.0/lib/ -isystem /opt/local/lib/gcc-lib/i386-apple-
darwin9.0.0/4.0.3/i386-apple-darwin9.0.0/include -isystem /opt/local/
lib/gcc-lib/i386-apple-darwin9.0.0/4.0.3/i386-apple-darwin9.0.0/sys-
include -O2 -DIN_GCC-W -Wall -Wwrite-strings -Wstrict-prototypes -
Wmissing-prototypes -Wold-style-definition -Wno-error -isystem ./
include -fPIC -pipe -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -
D__GCC_FLOAT_NOT_NEEDED -dynamiclib -nodefaultlibs -Wl,-install_name,/
opt/local/lib/gcc-lib/i386-apple-darwin9.0.0/4.0.3/
[EMAIL PROTECTED]@/@[EMAIL PROTECTED] -Wl,-
flat_namespace -o @multilib_dir@/@[EMAIL PROTECTED] -Wl,-
exported_symbols_list,@shlib_map_file@ -compatibility_version 1 -
current_version 1.0 @multilib_flags@ @shlib_objs@ -lc && rm -f
@multilib_dir@/@[EMAIL PROTECTED] && if [ -f @multilib_dir@/
@[EMAIL PROTECTED] ]; then mv -f @multilib_dir@/
@[EMAIL PROTECTED] @multilib_dir@/@[EMAIL PROTECTED]
1.0.dylib.backup; else true; fi && mv @multilib_dir@/@[EMAIL PROTECTED]
1.0.dylib.tmp @multilib_dir@/@[EMAIL PROTECTED] && ln -s
@[EMAIL PROTECTED] @multilib_dir@/@[EMAIL PROTECTED]' \
SHLIB_MULTILIB=''; \
gcc -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -
Wold-style-definition -Wno-error -DHAVE_CONFIG_H -I. -I. -I../../gcc
-I../../gcc/. -I../../gcc/../include -I./../intl -I../../gcc/../libcpp/
include \
-DSTANDARD_STARTFILE_PREFIX=\"../../../\" -DSTANDARD_EXEC_PREFIX=\"/
opt/local/lib/gcc-lib/i386-apple-darwin9.0.0/4.0.3/lib/gcc/\" -
DSTANDARD_LIBEXEC_PREFIX=\"/opt/local/lib/gcc-lib/i386-apple-
darwin9.0.0/4.0.3/libexec/gcc/\" -DDEFAULT_TARGET_VERSION=\"4.0.3\" -
DDEFAULT_TARGET_MACHINE=\"i386-apple-darwin9.0.0\" -
DSTANDARD_BINDIR_PREFIX=\"/opt/local/lib/gcc-lib/i386-apple-
darwin9.0.0/4.0.3/bin/\" -DTOOLDIR_BASE_PREFIX=\"../../../../\" `test
"X${SHLIB_LINK}" = "X" || test "yes" != "yes" || echo "-
DENABLE_SHARED_LIBGCC"` `test "X${SHLIB_MULTILIB}" = "X" || echo "-
DNO_SHARED_LIBGCC_MULTILIB"` \
-c ../../gcc/gcc.c -o gcc.o)
../../gcc/gcc.c:732: warning: string length '2975' is greater than the
length '509' ISO C89 compilers are required to support
../../gcc/gcc.c:738: warning: string length '510' is greater than the
length '509' ISO C89 compilers are required to support
../../gcc/gcc.c:938: warning: string length '844' is greater than the
length '509' ISO C89 compilers are required to support
../../gcc/gcc.c:963: warning: string length '608' is greater than the
length '509
Re: g95
On 11/11/2007, William Davis <[EMAIL PROTECTED]> wrote: > Help me understand: the Leopard version of gcc is 4.0.1 as supplied by > apple. mac ports has a gcc 4.0 @ 4.0.4 (and a gcc 4.2 @ 4.2.2). > So where does gcc 4.0.3 come from? g95 pulls down the gcc-core-4.0.3 source. Cheers Adam ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: gdc & g95 error: indirect jmp without `*'
Ryan Schmidt: Both g95 and gdc ports do indeed build new versions of GCC, FSF GCC 4.0.3 for g95 port and FSF GCC 4.1.2 for gdc port. It looks to me as though g95 and gdc download parts of the GCC 4.0.3 and 4.1.2 source, respectively, but that they actually compile themselves using the Apple GCC 4.0 compiler. I meant which source code they use, not which compiler they use. If you do a "make bootstrap", it also rebuilds using itself... --anders ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: gdc & g95 error: indirect jmp without `*'
On Sep 18, 2007, at 02:57, Anders F Björklund wrote: Casey Rodarmor wrote: I can't seem to compile anything with g95 @0.90_1 and gdc 0.24. I get the same error message for both. I am running OS X 10.4.10 on a MacBook Pro. I haven't installed any gcc aside from Apple's. I guess that either the compiler is giving bad output, or the assembler is complaining unnecessarily. Any ideas? Would it be worth trying to install a new gcc through macports? It might just be a quirk with using the FSF GCC on Darwin, I don't see any such problems with GDC and the Apple GCC*... Both g95 and gdc ports do indeed build new versions of GCC, FSF GCC 4.0.3 for g95 port and FSF GCC 4.1.2 for gdc port. It looks to me as though g95 and gdc download parts of the GCC 4.0.3 and 4.1.2 source, respectively, but that they actually compile themselves using the Apple GCC 4.0 compiler. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: gdc & g95 error: indirect jmp without `*'
Casey Rodarmor wrote: I can't seem to compile anything with g95 @0.90_1 and gdc 0.24. I get the same error message for both. I am running OS X 10.4.10 on a MacBook Pro. I haven't installed any gcc aside from Apple's. I guess that either the compiler is giving bad output, or the assembler is complaining unnecessarily. Any ideas? Would it be worth trying to install a new gcc through macports? It might just be a quirk with using the FSF GCC on Darwin, I don't see any such problems with GDC and the Apple GCC*... Both g95 and gdc ports do indeed build new versions of GCC, FSF GCC 4.0.3 for g95 port and FSF GCC 4.1.2 for gdc port. --anders * from http://gdcmac.sourceforge.net/ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
gdc & g95 error: indirect jmp without `*'
Hi everybody, I can't seem to compile anything with g95 @0.90_1 and gdc 0.24. I get the same error message for both. I am running OS X 10.4.10 on a MacBook Pro. I haven't installed any gcc aside from Apple's. Here is the output when I try to compile a hello world with f95: [EMAIL PROTECTED] [~/Desktop] g95 hello.f95 /var/tmp//cc6OFGZh.s:59:indirect jmp without `*' /var/tmp//cc6OFGZh.s:78:indirect jmp without `*' /var/tmp//cc6OFGZh.s:97:indirect jmp without `*' /var/tmp//cc6OFGZh.s:112:indirect jmp without `*' I can then use g95 to compile but not assemble using the -S flag, and then change all the instances of 'jmp %eax' to 'jmp *%eax' in the .s file. When I run it on the modified .s, it produces a working program. I guess that either the compiler is giving bad output, or the assembler is complaining unnecessarily. Any ideas? Would it be worth trying to install a new gcc through macports? Thanks for reading! Best, Casey Rodarmor ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
py-scientific / g95 (was: (no subject))
I had the very same error on PPC: On 18.07.2007, at 01:16, LD wrote: MP 1.5.0, Mac OS 10.4.10 PPC # port upgrade -d py-scientific ---> Fetching py-scientific ---> Verifying checksum(s) for py-scientific ---> Extracting py-scientific ---> Configuring py-scientific ---> Building py-scientific with target build Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_pytho n_py-scientific/work/ScientificPython-2.6" && /opt/local/bin/ python2.4 setup.py build " returned error 1 Command output: Src/Scientific_netcdf.c:1949: error: 'i' undeclared (first use in this function) Src/Scientific_netcdf.c: At top level: Src/Scientific_netcdf.c:1959: error: parse error before 'Py_ssize_t' Originally I thought it was related to odcctools (which causes strange errors for me repeatedly). I could solve the issue for me, but, honestly, I have no clue what the problem was nor what the solution is... Anyway, I uninstalled all installed gcc (gcc41 and gcc42) plus g95, odcctools, and netcdf. I reinstalled netcdf and g95 (which in turn installs odcctools) and could then successfully install py-scientific. Just my 2 ct -- not a very "scientific" guide to solve your problem... Btw, why does g95 rely on odcctools per default, instead of having a odcctools variant? Greetings, Jochen -- Einigkeit und Recht und Freiheithttp://www.Jochen- Kuepper.de Liberté, Égalité, FraternitéGnuPG key: CC1B0B4D Sex, drugs and rock-n-roll PGP.sig Description: This is a digitally signed message part ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Failled to install g95
On May 29, 2007, at 06:00, David Tremouilles wrote: >> > grep: /opt/local/lib/libgssapi.la: No such file or directory >> > sed: /opt/local/lib/libgssapi.la: No such file or directory >> > libtool: link: `/opt/local/lib/libgssapi.la' is not a valid libtool >> > archive >> > make: *** [subversion/libsvn_ra_dav/libsvn_ra_dav-1.la] Error 1 >> > >> > Error: Status 1 encountered during processing. >> >> Subversion installs just fine for me, even though I also do not >> have /opt/local/lib/libgssapi.la. >> >> There is a gss port. Perhaps, for some reason I don't understand, you >> need to install that first. Let us know if that makes a difference. >> >> Looking through the OS, I see there is /usr/lib/ libgssapi_krb5.dylib, >> which suggests this relates to Kerberos. Have you installed the >> kerberos5 port? I have not. > > I have not installed kerberos5 port. And did not try... > I did try to install gss. But still the same problem for subversion... Hum... I see, yes, the gss port provides /opt/local/lib/libgss.la but not /opt/local/lib/libgssapi.la. The other result for "port search gss" shows p5-gssapi, which I forgot I already had installed. (It's one of the many dependencies of p5-svn-notify which I installed a little while ago.) Would you see if installing p5-gssapi helps? No p5-gssapi does not help Would you send the complete verbose output of your installation attempt, like "sudo port -v install subversion +no_bdb"? I'm hoping the configure output will give me a clue what it's choking on. The output will be large, so if you can put it on a web page and just send us a link to it that would be best. Otherwise... you could email it to me off-list. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Failled to install g95
On May 29, 2007, at 04:30, David Tremouilles wrote: 2007/5/29, Ryan Schmidt: > grep: /opt/local/lib/libgssapi.la: No such file or directory > sed: /opt/local/lib/libgssapi.la: No such file or directory > libtool: link: `/opt/local/lib/libgssapi.la' is not a valid libtool > archive > make: *** [subversion/libsvn_ra_dav/libsvn_ra_dav-1.la] Error 1 > > Error: Status 1 encountered during processing. Subversion installs just fine for me, even though I also do not have / opt/local/lib/libgssapi.la. There is a gss port. Perhaps, for some reason I don't understand, you need to install that first. Let us know if that makes a difference. Looking through the OS, I see there is /usr/lib/libgssapi_krb5.dylib, which suggests this relates to Kerberos. Have you installed the kerberos5 port? I have not. I have not installed kerberos5 port. And did not try... I did try to install gss. But still the same problem for subversion... Hum... I see, yes, the gss port provides /opt/local/lib/libgss.la but not / opt/local/lib/libgssapi.la. The other result for "port search gss" shows p5-gssapi, which I forgot I already had installed. (It's one of the many dependencies of p5-svn-notify which I installed a little while ago.) Would you see if installing p5-gssapi helps? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Failled to install g95
I have not installed kerberos5 port. And did not try... I did try to install gss. But still the same problem for subversion... David 2007/5/29, Ryan Schmidt <[EMAIL PROTECTED]>: On May 29, 2007, at 03:19, David Tremouilles wrote: > 2007/5/29, Ryan Schmidt: > > > It looks like it's db44, not g95, that's failing. g95 requires > > odcctools which requires subversion which by default requires db44, > > though it can be configured without db44. You could do that this > way: > > > > sudo port install apr-util +no_bdb > > sudo port install subversion +no_bdb > > > > Then continue to install g95. > > > > If you want to work out why db44 is not working, then please first > > ensure that your MacPorts, OS and Xcode are up to date. Current > > version of MacPorts is 1.4.4.2, OS is 10.4.9 (or 10.3.9), and Xcode > > is 2.4.1 (for 10.4.9) or 1.5 (for 10.3.9). When you write back, let > > us know what version of each you have, and also your processor > > architecture. > > Hello, thanks for your fast reply. > I have: > MacOsX 1.4.9 on an Intel Core 2 Duo MacBook > Xcode 2.4.1 > MacPorts 1.442 Ok, great. I have the same except on a Core 2 Duo MacBook Pro. > I do not need db44 but intalling the way you suggested raised a new > problem: > > sudo port install subversion +no_bdb > ---> Building subversion with target all mucc > Error: Target com.apple.build returned: shell command " cd > "/opt/local/var/db/dports/build/ > _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_ > dports_devel_subversion/work/subversion-1.4.3" > && make all mucc " returned error 2 > Command output: cd subversion/libsvn_ra_dav && /bin/sh > /opt/local/var/db/dports/build/ > _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_ > dports_devel_subversion/work/subversion-1.4.3/libtool > --tag=CC --silent --mode=link gcc -O2 -L/opt/local/lib > -L/opt/local/lib -rpath /opt/local/lib -o libsvn_ra_dav-1.la > commit.lo fetch.lo file_revs.lo log.lo merge.lo options.lo props.lo > replay.lo session.lo util.lo > ../../subversion/libsvn_delta/libsvn_delta-1.la > ../../subversion/libsvn_subr/libsvn_subr-1.la > /opt/local/lib/libaprutil-1.la -lsqlite3 -lexpat -liconv > /opt/local/lib/libapr-1.la -lpthread /opt/local/lib/libneon.la -lintl > -framework Security -framework CoreFoundation -framework CoreServices > -lz > grep: /opt/local/lib/libgssapi.la: No such file or directory > sed: /opt/local/lib/libgssapi.la: No such file or directory > libtool: link: `/opt/local/lib/libgssapi.la' is not a valid libtool > archive > make: *** [subversion/libsvn_ra_dav/libsvn_ra_dav-1.la] Error 1 > > Error: Status 1 encountered during processing. Subversion installs just fine for me, even though I also do not have / opt/local/lib/libgssapi.la. There is a gss port. Perhaps, for some reason I don't understand, you need to install that first. Let us know if that makes a difference. Looking through the OS, I see there is /usr/lib/libgssapi_krb5.dylib, which suggests this relates to Kerberos. Have you installed the kerberos5 port? I have not. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Failled to install g95
On May 29, 2007, at 03:19, David Tremouilles wrote: 2007/5/29, Ryan Schmidt: > It looks like it's db44, not g95, that's failing. g95 requires > odcctools which requires subversion which by default requires db44, > though it can be configured without db44. You could do that this way: > > sudo port install apr-util +no_bdb > sudo port install subversion +no_bdb > > Then continue to install g95. > > If you want to work out why db44 is not working, then please first > ensure that your MacPorts, OS and Xcode are up to date. Current > version of MacPorts is 1.4.4.2, OS is 10.4.9 (or 10.3.9), and Xcode > is 2.4.1 (for 10.4.9) or 1.5 (for 10.3.9). When you write back, let > us know what version of each you have, and also your processor > architecture. Hello, thanks for your fast reply. I have: MacOsX 1.4.9 on an Intel Core 2 Duo MacBook Xcode 2.4.1 MacPorts 1.442 Ok, great. I have the same except on a Core 2 Duo MacBook Pro. I do not need db44 but intalling the way you suggested raised a new problem: > sudo port install subversion +no_bdb ---> Building subversion with target all mucc Error: Target com.apple.build returned: shell command " cd "/opt/local/var/db/dports/build/ _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_ dports_devel_subversion/work/subversion-1.4.3" && make all mucc " returned error 2 Command output: cd subversion/libsvn_ra_dav && /bin/sh /opt/local/var/db/dports/build/ _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_ dports_devel_subversion/work/subversion-1.4.3/libtool --tag=CC --silent --mode=link gcc -O2 -L/opt/local/lib -L/opt/local/lib -rpath /opt/local/lib -o libsvn_ra_dav-1.la commit.lo fetch.lo file_revs.lo log.lo merge.lo options.lo props.lo replay.lo session.lo util.lo ../../subversion/libsvn_delta/libsvn_delta-1.la ../../subversion/libsvn_subr/libsvn_subr-1.la /opt/local/lib/libaprutil-1.la -lsqlite3 -lexpat -liconv /opt/local/lib/libapr-1.la -lpthread /opt/local/lib/libneon.la -lintl -framework Security -framework CoreFoundation -framework CoreServices -lz grep: /opt/local/lib/libgssapi.la: No such file or directory sed: /opt/local/lib/libgssapi.la: No such file or directory libtool: link: `/opt/local/lib/libgssapi.la' is not a valid libtool archive make: *** [subversion/libsvn_ra_dav/libsvn_ra_dav-1.la] Error 1 Error: Status 1 encountered during processing. Subversion installs just fine for me, even though I also do not have / opt/local/lib/libgssapi.la. There is a gss port. Perhaps, for some reason I don't understand, you need to install that first. Let us know if that makes a difference. Looking through the OS, I see there is /usr/lib/libgssapi_krb5.dylib, which suggests this relates to Kerberos. Have you installed the kerberos5 port? I have not. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Failled to install g95
2007/5/29, David Tremouilles <[EMAIL PROTECTED]>: Hello, thanks for your fast reply. I have: MacOsX 1.4.9 on an Intel Core 2 Duo MacBook Xcode 2.4.1 MacPorts 1.442 I do not need db44 but intalling the way you suggested raised a new problem: > sudo port install subversion +no_bdb ---> Building subversion with target all mucc Error: Target com.apple.build returned: shell command " cd "/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_devel_subversion/work/subversion-1.4.3" && make all mucc " returned error 2 Command output: cd subversion/libsvn_ra_dav && /bin/sh /opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_devel_subversion/work/subversion-1.4.3/libtool --tag=CC --silent --mode=link gcc -O2 -L/opt/local/lib -L/opt/local/lib -rpath /opt/local/lib -o libsvn_ra_dav-1.la commit.lo fetch.lo file_revs.lo log.lo merge.lo options.lo props.lo replay.lo session.lo util.lo ../../subversion/libsvn_delta/libsvn_delta-1.la ../../subversion/libsvn_subr/libsvn_subr-1.la /opt/local/lib/libaprutil-1.la -lsqlite3 -lexpat -liconv /opt/local/lib/libapr-1.la -lpthread /opt/local/lib/libneon.la -lintl -framework Security -framework CoreFoundation -framework CoreServices -lz grep: /opt/local/lib/libgssapi.la: No such file or directory sed: /opt/local/lib/libgssapi.la: No such file or directory libtool: link: `/opt/local/lib/libgssapi.la' is not a valid libtool archive make: *** [subversion/libsvn_ra_dav/libsvn_ra_dav-1.la] Error 1 Error: Status 1 encountered during processing. 2007/5/29, Ryan Schmidt <[EMAIL PROTECTED]>: > On May 29, 2007, at 01:59, David Tremouilles wrote: > > > Failled to install g95... > > Any suggestions ? > > (sorry previous mail was sent with an unrealated object...) > > David > > > >>> port install g95 > > ---> Building db44 with target all > [snip] > > It looks like it's db44, not g95, that's failing. g95 requires > odcctools which requires subversion which by default requires db44, > though it can be configured without db44. You could do that this way: > > sudo port install apr-util +no_bdb > sudo port install subversion +no_bdb > > Then continue to install g95. > > If you want to work out why db44 is not working, then please first > ensure that your MacPorts, OS and Xcode are up to date. Current > version of MacPorts is 1.4.4.2, OS is 10.4.9 (or 10.3.9), and Xcode > is 2.4.1 (for 10.4.9) or 1.5 (for 10.3.9). When you write back, let > us know what version of each you have, and also your processor > architecture. > > > ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Failled to install g95
On May 29, 2007, at 01:59, David Tremouilles wrote: Failled to install g95... Any suggestions ? (sorry previous mail was sent with an unrealated object...) David port install g95 ---> Building db44 with target all [snip] It looks like it's db44, not g95, that's failing. g95 requires odcctools which requires subversion which by default requires db44, though it can be configured without db44. You could do that this way: sudo port install apr-util +no_bdb sudo port install subversion +no_bdb Then continue to install g95. If you want to work out why db44 is not working, then please first ensure that your MacPorts, OS and Xcode are up to date. Current version of MacPorts is 1.4.4.2, OS is 10.4.9 (or 10.3.9), and Xcode is 2.4.1 (for 10.4.9) or 1.5 (for 10.3.9). When you write back, let us know what version of each you have, and also your processor architecture. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Failled to install g95
Failled to install g95... Any suggestions ? (sorry previous mail was sent with an unrealated object...) David port install g95 ---> Building db44 with target all Error: Target com.apple.build returned: shell command " cd "/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_databases_db44/work/db-4.4.20/build_unix" && make all " returned error 2 Command output: /bin/sh ./libtool --mode=compile /usr/bin/gcc-4.0 -c -O2 -I../dist/.. -I/opt/local/include ../dist/../db_dump185/db_dump185.c /usr/bin/gcc-4.0 -c -O2 -I../dist/.. -I/opt/local/include ../dist/../db_dump185/db_dump185.c -fno-common -DPIC -o .libs/db_dump185.o ../dist/../db_dump185/db_dump185.c: In function 'main': ../dist/../db_dump185/db_dump185.c:212: warning: assignment makes pointer from integer without a cast ../dist/../db_dump185/db_dump185.c:214: warning: assignment makes pointer from integer without a cast ../dist/../db_dump185/db_dump185.c:229: error: 'struct __db' has no member named 'seq' ../dist/../db_dump185/db_dump185.c:229: error: 'R_NEXT' undeclared (first use in this function) ../dist/../db_dump185/db_dump185.c:229: error: (Each undeclared identifier is reported only once ../dist/../db_dump185/db_dump185.c:229: error: for each function it appears in.) ../dist/../db_dump185/db_dump185.c:234: error: 'struct __db' has no member named 'seq' ../dist/../db_dump185/db_dump185.c: In function 'db_hash': ../dist/../db_dump185/db_dump185.c:262: error: 'struct __db' has no member named 'internal' ../dist/../db_dump185/db_dump185.c:264: error: 'struct __db' has no member named 'internal' ../dist/../db_dump185/db_dump185.c: In function 'db_btree': ../dist/../db_dump185/db_dump185.c:289: error: 'struct __db' has no member named 'internal' make: *** [db_dump185.lo] Error 1 Error: The following dependencies failed to build: odcctools subversion apr-util db44 sqlite3 Error: Status 1 encountered during processing. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
