On 5/1/10 3:25 PM, sebastien masson wrote:
> Hello,
> Would it be possible to update cdo package to the latest version:
> 1.4.4 ?
> thank you,
cdo is currently not maintained by anyone. However, it is possible for
you to try to update your local version and you can then report back if
it worked
David R. Morrison wrote:
[]
> However, I can't think of a case other than the openssl nonsense
> where this would apply. And many openssl packages have been
> converted to use the openssl which ships with os x (rather than
> fink's) which makes it ok to distribute. So I'm thinking that it
Alexander,
No, FSF gcc locks onto a specific version of autoconf
and the process of getting them to bump to a newer version
can take quite awhile. Read...
http://www.pubbs.net/200812/gcc/2456-re-gcc-and-autoconf-261.html
I guess autoconf itself doesn't have to be 2.64 but we need
an alternate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/1/10 3:11 PM, Jack Howarth wrote:
>FYI, Steven Bosscher has made amazing progress towards
> implementing Mach-O link time optimization for FSF gcc
> working on my machine under fink...
>
> http://gcc.gnu.org/ml/gcc-bugs/2010-05/msg00035.html
Hello,
Would it be possible to update cdo package to the latest version:
1.4.4 ?
thank you,
Sebastien
--
___
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://ne
David,
Any chance I can get back my cvs commit access
for checking in the gcc4x and llvm related packages?
I think Peter is getting tried of having to do all
of my checkins.
Jack
ps I'll see if I can get clean backports of the
new Mach-O Link Time Optimization patches for
gcc-4_5-bra
FYI, Steven Bosscher has made amazing progress towards
implementing Mach-O link time optimization for FSF gcc
working on my machine under fink...
http://gcc.gnu.org/ml/gcc-bugs/2010-05/msg00035.html
One issue I have run into though is how to reliably produce
the necessary fink autoconf-2.64 pa
On May 1, 2010, at 6:13 AM, Alexander Hansen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 5/1/10 7:07 AM, Hanspeter Niederstrasser wrote:
>> libnessus3-ssl is marked as Restrictive (links to OpenSSL) and the
>> source is now unavailable upstream (license change for newer versio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/1/10 7:07 AM, Hanspeter Niederstrasser wrote:
> libnessus3-ssl is marked as Restrictive (links to OpenSSL) and the
> source is now unavailable upstream (license change for newer versions
> and dead FTP server). fink fetch libnessus3-ssl then fa
libnessus3-ssl is marked as Restrictive (links to OpenSSL) and the
source is now unavailable upstream (license change for newer versions
and dead FTP server). fink fetch libnessus3-ssl then fails to build,
only checking Source: defined in the .info file.
However, the tarball _is_ available fro
10 matches
Mail list logo
