svn commit: r351936 - in head: . Mk Mk/Uses archivers/libcomprex archivers/libdynamite archivers/liborange archivers/librtfcomp archivers/lzo2 archivers/ucl archivers/unshield audio/gstreamer1-plug...

[Tijl Coosemans]

On Wed, 9 Jul 2014 01:52:56 +0200 (CEST) Gerald Pfeifer wrote:
> On Wed, 2 Jul 2014, Tijl Coosemans wrote:
>>> -	${RM} -f ${STAGEDIR}${TARGLIB}/*.la
>>>  	${RM} -f ${STAGEDIR}${PREFIX}/man/man7/*
>>>  	${RM} -f ${STAGEDIR}${PREFIX}/bin/rebuild-gcj-db${SUFFIX} \
>>>  	         ${STAGEDIR}${PREFIX}/man/man1/rebuild-gcj-db${SUFFIX}.1
>> The problem is that you create plist in post-install while USES=libtool
>> only removes .la files after staging.  I'm thinking of moving the
>> patch-lafiles target right before post-stage so you can create plist in
>> post-stage, but for now you'll have to keep the RM (together with
>> USES=libtool).
> 
> I looked into this further and tested various patches.  It turns out
> the lang/gcc* had some *.la left over which I now removed as well (for
> lang/gcc410 today, others in the coming days).
> 
> The primary difference I can see if I add USES=libtool on top is that
> I get a couple of libraries like the following ones:
> 
>   prefix/gcc410/lib/gcc410/libstdc++.so.6.0.21
>   prefix/gcc410/lib/gcc410/libstdc++.so.6.0.21-gdb.py
>   prefix/gcc410/lib/gcc410/libcilkrts.so.5.0.0
>   prefix/gcc410/lib/gcc410/libssp.so.0.0.0
>   prefix/gcc410/lib/gcc410/libquadmath.so.0.0.0
>   prefix/gcc410/lib/gcc410/libgfortran.so.3.0.0
>   prefix/gcc410/lib/gcc410/libobjc.so.4.0.0
>   prefix/gcc410/lib/gcc410/libgcj.so.15.0.0
>   prefix/gcc410/lib/gcc410/libgij.so.15.0.0
>   prefix/gcc410/lib/gcc410/libgcj-tools.so.15.0.0
>   prefix/gcc410/lib/gcc410/libgomp.so.1.0.0
>   prefix/gcc410/lib/gcc410/libitm.so.1.0.0
>   prefix/gcc410/lib/gcc410/libatomic.so.1.1.0
>   prefix/gcc410/libexec/gcc410/gcc/i386-portbld-freebsd10.0/4.10.0/liblto_plugin.so.0.0.0
> 
> So, should I still add USES=libtool to these ports?

Yes.  This new version scheme reduces future library version bumps.