david

thanx very much for that explanation. so i guess i'll just try again the 
packages that failed with install_name error before

> There are two versions of libtool that packages might be using.  If a
> package uses libtool 1.3.5, then most likely there is a line
> "UpdateLibtool: True: in the fink .info file, and these packages should
> be fixed by the change I made.  If a package uses libtool 1.4, then
> fixing the install_name problem will have to be done by hand, by the
> package maintainer.
>

unfortunately i have run into trouble: doing my first fink update-all 
after the update to the cvs version of the package manager gives me the 
foolowing (with both gcc2 and gcc3)

[...]
glib-1.2.10/tests/type-test.c
glib-1.2.10/tests/makefile.msc
glib-1.2.10/tests/makefile.msc.in
glib-1.2.10/glib.spec
cp -f /Volumes/sw/lib/fink/update/config.guess .
cp -f /Volumes/sw/lib/fink/update/config.sub .
cp -f /Volumes/sw/lib/fink/update/ltconfig .
cp -f /Volumes/sw/lib/fink/update/ltmain.sh .
patch -p1 
</Volumes/sw/fink/dists/unstable/main/finkinfo/gnome/glib-1.2.10-6.patch
patching file ltconfig
Hunk #1 FAILED at 1381.
1 out of 1 hunk FAILED -- saving rejects to file ltconfig.rej
patching file ltmain.sh
### execution of patch failed, exit code 1
Failed: patching glib-1.2.10-6 failed

my first thought of course was the updated package manager as you said 
you changed ltconfig. is this somehow related? thanx in advance for any 
help

mathias


_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas - 
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink

_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to