FS#11016 - freetype2 should also be built statically

Attached to Project: Arch Linux
Opened by Heiko Baums (cyberpatrol) - Sunday, 27 July 2008, 10:23 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 14 April 2009, 21:50 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Medium
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

freetype2 is currently compiled with
./configure --prefix=/usr --disable-static

It would be nice, if --disable-static would be removed from the PKGBUILD and freetype2 would be rebuilt, so that the statically linked version of libfreetype is also built.

I'm just trying to build an updated package for fbsplash (http://aur.archlinux.org/packages.php?ID=13541). As spock, the upstream developer of fbsplash, told me, splashutils needs the dynamically linked (.so) version as well as the statically linked (.a) version of libfreetype in /usr/lib. Otherwise splashutils fails to compile.

And building a new package freetype-static in AUR just to get --disable-static removed and to get possibly only one additional file, would be a bit over-the-top and not quite KISS like in my opinion.

Additional info:
* package version(s)
freetype-2.3.7-1
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Tuesday, 14 April 2009, 21:50 GMT
Reason for closing:  Implemented
Comment by Glenn Matthys (RedShift) - Sunday, 27 July 2008, 11:27 GMT
The AUR is not an officially supported repository. If you want to use fbsplash, pull in the freetype PKGBUILD and adjust the configure arguments as you wish.
Comment by Jan de Groot (JGC) - Sunday, 27 July 2008, 11:27 GMT
Static libraries aren't needed to build static binaries. The makefiles contain hardcoded references to the .a files, which is wrong. Other major distributions like Redhat don't build static versions of freetype2 either.
Comment by Vesa Kaihlavirta (vegai) - Monday, 26 January 2009, 07:06 GMT
Re-opened due to confusion. How can one build a static binary out of dynamic libraries?
Comment by Gerardo Exequiel Pozzi (djgera) - Wednesday, 25 March 2009, 00:19 GMT
@vegal, not possible, when you try to link a shared lib with a static binary a linker will report an error: "attempted static link of dynamic object"
Comment by Vesa Kaihlavirta (vegai) - Wednesday, 25 March 2009, 12:48 GMT
Doing a static x86_64 build of freetype increases the size of the tarball by 333KB (72% increase) and installed size by 824KB (47%).

IMHO not too much, but I'll ask for opinions.

Loading...