Hi,

Maciej (Matchek) BliziƄski wrote:
2015-03-08 11:31 GMT+00:00 Laurent Blume <[email protected]>:
I've not looked much into it, Just noticed that the .so of that libffi
is in a different subdir. I see no .so for the GCC one, nor dependency
on it, so it looks basically useless.
Yes, it is useless now. This quirk comes from the times when we
couldn't, or didn't want to remove gcc3 from the catalog. Riccardo,
I'd suggest moving the .so file back to /opt/csw/lib.
The odyssey is not done! we have a clash:

INFO 2015-03-16 21:54:56,221 package_stats.py:132 Juicing the svr4 package stream files... 100% Time: 0:00:23 |#############################################################################|
INFO 2015-03-16 21:55:22,464 checkpkg_lib.py:263 Unwrapping candies...
100% |###########################################################################################| INFO 2015-03-16 21:55:22,521 checkpkg_lib.py:878 Tasting candies one by one... 100% |###########################################################################################|
INFO 2015-03-16 21:55:23,206 checkpkg_lib.py:914 Tasting them all at once...
INFO 2015-03-16 21:55:31,725 checkpkg_lib.py:305 Stuffing the candies under the pillow... WARNING 2015-03-16 21:55:31,825 checkpkg_lib.py:311 Not saving an error for CSWgcc3javart. | WARNING 2015-03-16 21:55:31,826 checkpkg_lib.py:311 Not saving an error for CSWgcc3javart. WARNING 2015-03-16 21:55:31,827 checkpkg_lib.py:311 Not saving an error for CSWgcc4core. | WARNING 2015-03-16 21:55:31,828 checkpkg_lib.py:311 Not saving an error for CSWgcc4core. 100% |###########################################################################################|
CSWlibffi-dev:
CSWgcc3javart:
CSWgcc4core:
If any of the reported errors were false positives, you can override them
pasting the lines below to the GAR recipe.
CHECKPKG_OVERRIDES_CSWlibffi-dev += file-collision|/opt/csw/lib/libffi.so|CSWgcc3javart|CSWgcc4core|CSWlibffi-dev CHECKPKG_OVERRIDES_CSWlibffi-dev += file-collision|/opt/csw/lib/sparcv9/libffi.so|CSWgcc3javart|CSWgcc4core|CSWlibffi-dev

is this CSWgcc3javart package still actual? Why does it want a private libffi version? I think that was probabl the package that was the reason for this "hiding" of libffi.so

What now, should I revert my changes in libffi or can we clean up this stubborn package or at least update it to use a system libffi?

Riccardo

Reply via email to