Re: [Fink-devel] fort77/f2c BuildDepends problem
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 remain "swappable"? dan Dan: I'm pretty sure the BDO flag in f2c is wrong. -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 NOAA/OAR/CDC R/CDC1FAX : (303)497-6449 325 BroadwayWeb : http://www.cdc.noaa.gov/~jsw Boulder, CO, USA 80305-3328 Office: Skaggs Research Cntr 1D-124 --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] fort77
-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 anyone object to me committing it? > Please go ahead and commit it. Thank you. - -d - -- nee anata wo mitsukete soshite nidoto wasurezu donna ni munega itakutemo soba ni iru no zutto...zutto...zutto Key fingerprint = FD77 F0B7 5C65 F546 EB08 A4EC 3CCA 1A32 7E24 291E -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFCtomGPMoaMn4kKR4RAzBkAJwPuufwrtTQXOWWK5h9whNe4utSxwCfbr7S HvVIGX1SczKRhUXk54t2M0M= =aGa/ -END PGP SIGNATURE- --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] fort77
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 --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] fort77
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 Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] fort77
-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 anyone object to me committing it?
|
| It's quite non-invasive, the change is to add
| $cc = "cc" if $cc =~ /fort77$;
| up near the top, after $cc is set? Some things (gcc4, for one) set
| $ENV{CC} = "fort77" when invoking fort77 in ./configure.
Yes, please apply this patch to fort77 (and up the revision), the fork bomb
happens if fort77 is installed and the package uses gnu libtool-1.5 or
later, and CC is an exported environment variable.
Peter
- --
Peter O'Gorman - http://www.pogma.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (Darwin)
iQCVAwUBQra7kriDAg3OZTLPAQIQeQQArbAl/Gfk9Z6jRYQBdD/K3A6Ed8BIpuaw
Fmj+LUj5jc4c5/W8G2ekzF3y2ruFyfXg4+rd4n0b49Io8GC71rRglU1v/SV7Ep9S
LX7UqM3CQoAv7Psu/h0ZB0SnP7UBHmFFYkoctYJ00hZYXkoorVy0g754bIzJ0Yhg
Ob9+mA6JXnw=
=kYaU
-END PGP SIGNATURE-
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] fort77
-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 anyone object to me committing it?
|
| It's quite non-invasive, the change is to add
| $cc = "cc" if $cc =~ /fort77$;
| up near the top, after $cc is set? Some things (gcc4, for one) set
| $ENV{CC} = "fort77" when invoking fort77 in ./configure.
Yes, please apply this patch to fort77 (and up the revision), the fork bomb
happens if fort77 is installed and the package uses gnu libtool-1.5 or
later, and CC is an exported environment variable.
Peter
- --
Peter O'Gorman - http://www.pogma.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (Darwin)
iQCVAwUBQra7kriDAg3OZTLPAQIQeQQArbAl/Gfk9Z6jRYQBdD/K3A6Ed8BIpuaw
Fmj+LUj5jc4c5/W8G2ekzF3y2ruFyfXg4+rd4n0b49Io8GC71rRglU1v/SV7Ep9S
LX7UqM3CQoAv7Psu/h0ZB0SnP7UBHmFFYkoctYJ00hZYXkoorVy0g754bIzJ0Yhg
Ob9+mA6JXnw=
=kYaU
-END PGP SIGNATURE-
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] fort77 can't be compiled.
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 ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] fort77 can't be compiled.
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 idea what's wrong. Ok, so some fink packages need 3.3, other need 3.1 (or is it 2.95.2?). Perhaps it would be possible for fink to select the right compiler for each package? 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 clisp package works with 3.1. Definitely not. That's the only reason why I upgraded to 3.3, to be able to compile clisp 2.29 from fink. I had no problems building clisp-2.29 with gcc 3.1. -- Alexander K. Hansen Levitated Dipole Experiment http://www.psfc.mit.edu/LDX --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] fort77 can't be compiled.
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 need 3.1 (or is it 2.95.2?). > > Perhaps it would be possible for fink to select the right compiler for > > each package? > > 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 clisp package works with 3.1. Definitely not. That's the only reason why I upgraded to 3.3, to be able to compile clisp 2.29 from fink. -- __Pascal_Bourguignon__ http://www.informatimago.com/ Do not adjust your mind, there is a fault in reality. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] fort77 can't be compiled.
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 clisp package works with 3.1. > > Definitely not. That's the only reason why I upgraded to 3.3, to be > able to compile clisp 2.29 from fink. > > clisp 2.29 compiles just fine (and even runs) with gcc 3.1. -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 NOAA/OAR/CDC R/CDC1FAX : (303)497-6449 325 BroadwayWeb : http://www.cdc.noaa.gov/~jsw Boulder, CO, USA 80305-3328 Office: Skaggs Research Cntr 1D-124 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] fort77 can't be compiled.
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 need 3.1 (or is it 2.95.2?). > Perhaps it would be possible for fink to select the right compiler for > each package? > > 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 clisp package works with 3.1. -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 NOAA/OAR/CDC R/CDC1FAX : (303)497-6449 325 BroadwayWeb : http://www.cdc.noaa.gov/~jsw Boulder, CO, USA 80305-3328 Office: Skaggs Research Cntr 1D-124 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] fort77 can't be compiled.
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 compile packages. > > The problem with fort77 might actually lie in f2c, so you may need to go > back and recompile various things to get fort77 to work. Yes, I did update my developer tools because there was no way to compile clisp with gcc 3.1. So my currently selected gcc compiler indeed is 3.3. Jeffrey S Whitaker writes: > > 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 need 3.1 (or is it 2.95.2?). Perhaps it would be possible for fink to select the right compiler for each package? > On Mon, 29 Sep 2003, Pascal Bourguignon wrote: > > > fort77 can't be compiled. > > > > Is there a way to know what package needs it? > > netcdf needs it. I don't think there are any others. I think it is the > f2c package that is broken by the gcc 3.3 update however, not fort77. -- __Pascal_Bourguignon__ http://www.informatimago.com/ Do not adjust your mind, there is a fault in reality. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] fort77 can't be compiled.
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? > netcdf needs it. I don't think there are any others. I think it is the f2c package that is broken by the gcc 3.3 update however, not fort77. -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 NOAA/OAR/CDC R/CDC1FAX : (303)497-6449 325 BroadwayWeb : http://www.cdc.noaa.gov/~jsw Boulder, CO, USA 80305-3328 Office: Skaggs Research Cntr 1D-124 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] fort77 can't be compiled.
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 with fort77 might actually lie in f2c, so you may need to go back and recompile various things to get fort77 to work. -- Dave --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] fort77 can't be compiled.
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 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 that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. The following 2 additional packages will be installed: fort77 g77 Do you want to continue? [Y/n] y dpkg -i /sw/fink/dists/stable/main/binary-darwin-powerpc/libs/db3_3.3.11- 13_darwin-powerpc.deb Selecting previously deselected package db3. dpkg: considering removing db41-ssl in favour of db3 ... dpkg: yes, will remove db41-ssl in favour of db3. (Reading database ... 14953 files and directories currently installed.) Unpacking db3 (from .../db3_3.3.11-13_darwin-powerpc.deb) ... Setting up db3 (3.3.11-13) ... rm -rf fort77-1.18-4 mkdir -p /sw/src/fort77-1.18-4 gzip -dc /sw/src/fort77-1.18.tar.gz | /sw/bin/tar -xf - sed 's||/sw|g' < /sw/fink/dists/stable/main/finkinfo/languages/fort77-1.18-4.patch | patch -p1 patching file fort77 echo "no compile script" no compile script rm -rf /sw/src/root-fort77-1.18-4 mkdir -p /sw/src/root-fort77-1.18-4/sw mkdir -p /sw/src/root-fort77-1.18-4/DEBIAN mkdir -p /sw/src/root-fort77-1.18-4/sw/bin mkdir -p /sw/src/root-fort77-1.18-4/sw/share/man/man1 make install BINDIR=/sw/src/root-fort77-1.18-4/sw/bin MANDIR=/sw/src/root-fort77-1.18-4/sw/share/man/man1 (cd tests; ./test.pl -v) ./fort77 -c foo.f ... test successful. ./fort77 -c bar.F ..."bar.o" not generated by "( ./fort77 -c bar.F ) >/dev/null 2>&1" ./fort77 -c -o gargle.o foo.f /fort77 foo.f /fort77 baz/bazfoo.f /fort77 -c baz/bazfoo.f /fort77 -o bar.o -c baz/ba\ zfoo.f /fort77 -o tscht foo.f /fort77 -k foo.f /fort77 -g -k foo.f /fort77 -c -f long.f /fort77 mainmiss.f \ /fort77 -c foo.f && ./fort77 -c mainmiss.f && ./fort77 -o foo foo.o mainmiss.o /fort77 -c foo.f && ./fort77 -o foo foo.o mainmi\ ss.f /fort77 synerr.f && touch gargle ...Total 1 error(s) encountered. make: *** [test] Error 1 ### execution of failed, exit code 2 Failed: installing fort77-1.18-4 failed -- __Pascal Bourguignon__ http://www.informatimago.com/ --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
