Date: Fri, 18 Sep 1998 18:07:25 -0500 (CDT) From: Scott Mace <smace@intt.org> To: smace@FreeBSD.ORG (Scott Mace) Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: ports/graphics/tiff34 Makefile ports/graphics/tiff34/patches patch-aa patch-ab ports/graphics/tiff34/pkg PLI Message-ID: <199809182307.SAA02426@metal.intt.org> In-Reply-To: <199809182205.PAA02870@freefall.freebsd.org> from Scott Mace at "Sep 18, 1998 3: 5:56 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> smace 1998/09/18 15:05:56 PDT > > Modified files: > graphics/tiff34 Makefile > Log: > Convert to Elf > > Revision Changes Path > 1.10 +2 -2 ports/graphics/tiff34/Makefile > > Modified files: > graphics/tiff34/patches patch-aa patch-ab > Log: > COnvert to Elf. > Two DSO types for tiff34 are now supported: FREEBSD_AOUTdso and FREEBSD_ELFdso > > Revision Changes Path > 1.8 +12 -13 ports/graphics/tiff34/patches/patch-aa > 1.4 +12 -6 ports/graphics/tiff34/patches/patch-ab > > Modified files: > graphics/tiff34/pkg PLIST > Log: > Convert to Elf. > > Revision Changes Path > 1.7 +4 -3 ports/graphics/tiff34/pkg/PLIST > Only side effect of this is that anything that links with -ltiff34 needs -Wl,-rpath,/usr/local/lib This is because libtiff34.so.1 is linked with -ljpeg and -lz. Is this inheritanly evil? Should a port that links with -ltiff34 just be required to link with -ljpeg and -lz or is adding the rpath the right way to go? Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809182307.SAA02426>