-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 1/11/10 9:27 PM, Kevin Horton wrote:
> On 2010-01-11, at 10:24 , Hanspeter Niederstrasser wrote:
> 
>> To all package-maintainers (and interested parties):
>>
>> I've just completed a build-all of the stable tree (pulled on 
>> 2009-12-30) on 10.5 Intel/32-bit.  Out of almost 4000 debs that were 
>> built, only 121 packages had build errors, so that's not too bad.  Many 
>> were missing dependencies, a few were pkg-config unable to find stuff 
>> (gnutls was a common package that couldn't be found), and others were 
>> actual code problems (for some examples).  I have not done any real 
>> analysis of the errors, so I can't specifically say how to fix stuff, etc.
>>
>> The error logs can be found here: 
>> <http://www.snaggledworks.com/fink/fink-build-forever/>
>>
>> There have been multiple updates to the stable tree in the meantime, so 
>> I'll try to pull a new tree on Friday, Jan 15 and redo the buildall that 
>> weekend.
>>
>> List of packages that failed:
>> ****
> 
>> sylpheed-beta-gpgme
>> sylpheed-beta
>> sylpheed-gpgme
>> sylpheed
> 
> I maintain the various sylpheed packages.  All four failed like:
> 
> grep: /sw/lib/libenchant.la: No such file or directory
> sed: /sw/lib/libenchant.la: No such file or directory
> libtool: link: `/sw/lib/libenchant.la' is not a valid libtool archive
> make[2]: *** [libsylph.la] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all-recursive-am] Error 2
> ### execution of make failed, exit code 2
> 
> I'm baffled.  I don't think there is anything wrong with the packages, but 
> without access to the build machine when the failure occurred I don't know 
> how to discern the source of the problem.  I'd greatly appreciate any 
> comments or hints.
> 
> --
> Kevin Horton
> Ottawa, Canada
> 
> 
> 
> 

You don't have an explicit dependency on enchant1, and this is
presumably coming through via one of sylpheed's dependencies.  Since
build dependencies aren't inherited, this is not necessarily unexpected.

By the way, you might want to change the pilot-link dependency from
pilot-link10 to pilot-link09, which is a newer version (bad nomenclature
is due to me changing the numbering to the soname rather than the
compatibility version).
- -- 
Alexander Hansen
Fink User Liaison
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktL7DMACgkQB8UpO3rKjQ8OxgCgm2B+3up4oLurFnayF8Vk3X1r
CbEAniGgc8WzBqQlhT35a+AffR5sDwy/
=DaSa
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to