Re: [Fink-devel] fort77/f2c BuildDepends problem

2005-10-03 Thread Jeff Whitaker
Daniel Macks wrote: fort77-1.18-17 lists Depends:f2c, but f2c (20030428-2) is BuildDependsOnly:true. The bin/fort77 script contains an explicit call to the f2c binary, so the Depends makes sense. Is the BDO flag wrong? Or are there other alternate packages of f2c's files, requiring that f2c

[Fink-devel] fort77/f2c BuildDepends problem

2005-10-02 Thread Daniel Macks
fort77-1.18-17 lists Depends:f2c, but f2c (20030428-2) is BuildDependsOnly:true. The bin/fort77 script contains an explicit call to the f2c binary, so the Depends makes sense. Is the BDO flag wrong? Or are there other alternate packages of f2c's files, requiring that f2c remain swappable? dan --

Re: [Fink-devel] fort77

2005-06-21 Thread David Höhn
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Matthew Sachs wrote: On Sat, 18 Jun 2005, Daniel Macks wrote: There's a bug in ./configure or libtool that causes a fork-bomb with fort77. I sent a patch to the fort77 maintainer on June 3rd. I haven't received a reply yet, does

[Fink-devel] fort77

2005-06-20 Thread Matthew Sachs
On Sat, 18 Jun 2005, Daniel Macks wrote: There's a bug in ./configure or libtool that causes a fork-bomb with fort77. I sent a patch to the fort77 maintainer on June 3rd. I haven't received a reply yet, does anyone object to me committing it? It's quite non-invasive, the change is to add

Re: [Fink-devel] fort77

2005-06-20 Thread Peter O'Gorman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthew Sachs wrote: | On Sat, 18 Jun 2005, Daniel Macks wrote: | | | There's a bug in ./configure or libtool that causes a fork-bomb with | fort77. | | | I sent a patch to the fort77 maintainer on June 3rd. I haven't | received a reply yet, does

Re: [Fink-devel] fort77

2005-06-20 Thread Peter O'Gorman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthew Sachs wrote: | On Sat, 18 Jun 2005, Daniel Macks wrote: | | | There's a bug in ./configure or libtool that causes a fork-bomb with | fort77. | | | I sent a patch to the fort77 maintainer on June 3rd. I haven't | received a reply yet, does

Re: [Fink-devel] fort77

2005-06-20 Thread Matthew Sachs
On Jun 20, 2005, at 05:52, Peter O'Gorman wrote: Yes, please apply this patch to fort77 (and up the revision), the fork bomb Done. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow

Re: [Fink-devel] fort77

2005-06-20 Thread Daniel Macks
On Mon, Jun 20, 2005 at 10:22:38AM -0700, Matthew Sachs wrote: On Jun 20, 2005, at 05:52, Peter O'Gorman wrote: Yes, please apply this patch to fort77 (and up the revision), the fork bomb Done. Excellent! dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks

Re: [Fink-devel] fort77 can't be compiled.

2003-10-02 Thread Pascal J . Bourguignon
Jeff Whitaker writes: On Tue, 30 Sep 2003, Pascal J.Bourguignon wrote: Pascal: If you installed the gcc3.3 update, sudo /usr/sbin/gcc_select 3.1 and rebuild f2c and fort77. If you haven't installed gcc 3.3, I have no idea what's wrong. Ok, so some fink packages need 3.3, other

Re: [Fink-devel] fort77 can't be compiled.

2003-10-02 Thread Alexander K. Hansen
On Tuesday, September 30, 2003, at 11:37 AM, Pascal J.Bourguignon wrote: Jeff Whitaker writes: On Tue, 30 Sep 2003, Pascal J.Bourguignon wrote: Pascal: If you installed the gcc3.3 update, sudo /usr/sbin/gcc_select 3.1 and rebuild f2c and fort77. If you haven't installed gcc 3.3, I have no

Re: [Fink-devel] fort77 can't be compiled.

2003-10-02 Thread David R. Morrison
clisp-2.29 is also available from fink in binary form. The binary was compiled with gcc 3.1. -- Dave --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf

Re: [Fink-devel] fort77 can't be compiled.

2003-10-01 Thread Jeff Whitaker
On Tue, 30 Sep 2003, Pascal J.Bourguignon wrote: 3.3 is not officially supported in fink yet, there will be a 10.2-gcc3.3 distribution shortly however. Some packages need 2.95, but that is handled automatically by the package. There are no packages in fink now that need 3.3. The

Re: [Fink-devel] fort77 can't be compiled.

2003-09-30 Thread Pascal J . Bourguignon
David R. Morrison writes: I suppose you are using the updated Developer Tools? There is a problem with fort77 and the new tools. As it says on Fink's homepage, users are advised not to update their developer tools, or if they do, to be sure and run sudo gcc_select 3 before using fink to

Re: [Fink-devel] fort77 can't be compiled.

2003-09-30 Thread Jeffrey S Whitaker
Pascal: If you installed the gcc3.3 update, sudo /usr/sbin/gcc_select 3.1 and rebuild f2c and fort77. If you haven't installed gcc 3.3, I have no idea what's wrong. On Mon, 29 Sep 2003, Pascal Bourguignon wrote: fort77 can't be compiled. Is there a way to know what package needs it?

[Fink-devel] fort77 can't be compiled.

2003-09-29 Thread Pascal Bourguignon
fort77 can't be compiled. Is there a way to know what package needs it? bash-2.05a$ fink --version Package manager version: 0.13.7 Distribution version: 0.5.3.cvs Copyright (c) 2001 Christoph Pfisterer Copyright (c) 2001-2003 The Fink Package Manager Team This program is distributed in the hope

Re: [Fink-devel] fort77 can't be compiled.

2003-09-29 Thread Alexander K. Hansen
Did you install the gcc3.3 update to the Developer Tools? That causes a lot of havoc with Fortran. On Monday, September 29, 2003, at 02:05 AM, Pascal Bourguignon wrote: fort77 can't be compiled. Is there a way to know what package needs it? bash-2.05a$ fink --version Package manager

Re: [Fink-devel] fort77 can't be compiled.

2003-09-29 Thread David R. Morrison
I suppose you are using the updated Developer Tools? There is a problem with fort77 and the new tools. As it says on Fink's homepage, users are advised not to update their developer tools, or if they do, to be sure and run sudo gcc_select 3 before using fink to compile packages. The problem