On 11/15/06, David Reiser <[EMAIL PROTECTED]> wrote:
>
> On Nov 15, 2006, at 9:28 PM, Lars Rosengreen wrote:
>
> > On 11/15/06, Alexander Hansen <[EMAIL PROTECTED]> wrote:
> >>
> >> Linking to the system's openssl allows us to redistribute the
> >> packages
> >> in binary form if there aren't any o
On Nov 15, 2006, at 9:28 PM, Lars Rosengreen wrote:
> On 11/15/06, Alexander Hansen <[EMAIL PROTECTED]> wrote:
>>
>> Linking to the system's openssl allows us to redistribute the
>> packages
>> in binary form if there aren't any other cryptographic issues that
>> require the packages to be unde
On 11/15/06, Lars Rosengreen <[EMAIL PROTECTED]> wrote:
> On 11/15/06, Alexander Hansen <[EMAIL PROTECTED]> wrote:
> >
> > Linking to the system's openssl allows us to redistribute the packages
> > in binary form if there aren't any other cryptographic issues that
> > require the packages to be und
On Nov 15, 2006, at 9:12 PM, Alexander Hansen wrote:
> On 11/15/06, David Reiser <[EMAIL PROTECTED]> wrote:
>>
>> On Nov 15, 2006, at 8:32 AM, Peter O'Gorman wrote:
>>
>>>
>>> On Nov 15, 2006, at 2:44 PM, David Reiser wrote:
>>>
I've been wrangling with gnucash dependencies for a while. Earl
On 11/15/06, Alexander Hansen <[EMAIL PROTECTED]> wrote:
>
> Linking to the system's openssl allows us to redistribute the packages
> in binary form if there aren't any other cryptographic issues that
> require the packages to be under a Restrictive license.
I think it is probably still possible t
On 11/15/06, David Reiser <[EMAIL PROTECTED]> wrote:
>
> On Nov 15, 2006, at 8:32 AM, Peter O'Gorman wrote:
>
> >
> > On Nov 15, 2006, at 2:44 PM, David Reiser wrote:
> >
> >> I've been wrangling with gnucash dependencies for a while. Early on
> >> it was possible to avoid the crypto tree by gettin
On Nov 15, 2006, at 8:32 AM, Peter O'Gorman wrote:
>
> On Nov 15, 2006, at 2:44 PM, David Reiser wrote:
>
>> I've been wrangling with gnucash dependencies for a while. Early on
>> it was possible to avoid the crypto tree by getting unified versions
>> of libofx and crypt-ssleay-pm packaged.
>>
>>
It is important that anyone who maintains a gfortran-dependent
package tests this before it goes into fink unstable. With the ccp4
package I've been maintaining, I've found it breaks about 25% of the
programs. Jack is kindly helping me find workarounds, but it is
fairly safe to say it be
The attached packaging has been placed on the
fink package tracking system for gcc4. The new
packaging builds the latest gcc 4.2 branch
snapshot as multilib for the c, c++, objc and
fortran languages on both PPC and Intel Darwin.
The multilib build is suppressed for the java
language for both archi
On Nov 15, 2006, at 2:44 PM, David Reiser wrote:
> I've been wrangling with gnucash dependencies for a while. Early on
> it was possible to avoid the crypto tree by getting unified versions
> of libofx and crypt-ssleay-pm packaged.
>
> Gwenhywfar and aqbanking will be crypto for the foreseeable f
Michèle Garoche wrote:
> Fink cvs from yesterday
> XCode 2.4.
> freetype219-2.2.1-2
> Tree 10.4 unstable
>
> While compiling freetype219, I've got a number of deprecated calls on 10.4:
>
> In file included from
> /sw/src/fink.build/freetype219-2.2.1-2/freetype-2.2.1/src/base/ftbase.c:36:
> /sw/s
Fink cvs from yesterdayXCode 2.4.freetype219-2.2.1-2Tree 10.4 unstableWhile compiling freetype219, I've got a number of deprecated calls on 10.4:In file included from /sw/src/fink.build/freetype219-2.2.1-2/freetype-2.2.1/src/base/ftbase.c:36:/sw/src/fink.build/freetype219-2.2.1-2/freetype-2.2.1/src
12 matches
Mail list logo
