okay so this error is different, but I've had about 10 other ppl that is was because of fink cvs, I assume this is all surfacing because of gimp2. I'll add the new builddep
---
TS
http://southofheaven.org
Chaos is the beginning and end, try dealing with the rest.

On 10-Apr-04, at 1:42 AM, Martin Costabel wrote:

TheSin wrote:
the problem was with the order of splitoffs, dmacks added the ability to have none consecutive SplitOffN fields in info files, when he did this he accidentally reversed to order in which they built the deb files, so if SplitOff had lib/lib%N.*.dylib in the Files: field and SplitOff2: had lib in the Files: field, splitoof two would get processed first and would take all of lib so when SplitOff got processed lib/lib%N.*.dylib no longer existed. But he was very quick to fix this. It was only in HEAD for like a week or so.

I see what you mean. But I don't think this explains the error that has been reported, for two reasons:

1. The people that are seeing the error say that they see it with the released 0.20.0

2. They have a weird command line where the dylib suffix has disappeared:

gcc -dynamiclib  -flat_namespace -undefined suppress -o .libs/libmng.1
.libs/libmng_callback_xs.o .libs/libmng_chunk_io.o
.libs/libmng_chunk_prc.o .libs/libmng_chunk_xs.o .libs/libmng_cms.o
.libs/libmng_display.o .libs/libmng_dither.o .libs/libmng_error.o
.libs/libmng_filter.o .libs/libmng_hlapi.o .libs/libmng_jpeg.o
.libs/libmng_object_prc.o .libs/libmng_pixels.o .libs/libmng_prop_xs.o
.libs/libmng_read.o .libs/libmng_trace.o .libs/libmng_write.o
.libs/libmng_zlib.o  -L/sw/lib -lz /sw/lib/libjpeg.dylib
/sw/lib/liblcms.dylib -install_name  /sw/lib/libmng.1
-compatibility_version 2 -current_version 2.0
ld: warning -dylib_install_name /sw/lib/libmng.1 not found in segment

To me this looks like a problem between automake, autoconf and libtool.

--
Martin

Attachment: PGP.sig
Description: This is a digitally signed message part



Reply via email to