[ft-devel] Freetype, -no-undefined and BeOS

[Christian Biesinger]

Hi,

in 
http://lists.gnu.org/archive/html/freetype-devel/2005-09/msg00105.html I 
sent a patch to fix building a shared library on BeOS by adding 
-no-undefined, which was also committed.

Unfortunately, it looks like -no-undefined was since commented out:
http://cvs.savannah.gnu.org/viewcvs/freetype/freetype2/builds/unix/unix-cc.in?r1=1.12&r2=1.13

With a checkin comment of:
    * builds/unix/unix-cc.in: don't filter-out exported functions
    anymore, this is used to ensure that all FT_BASE internal
    functions are available for dynamic linking


Was it intentional that -no-undefined was commented out as well? As it 
is, compiling Freetype 2.2.1 on BeOS only creates a static library, and 
libtool says during the build:
libtool: link: warning: undefined symbols not allowed in i586-pc-beos 
shared libraries

The easy fix is to move -no-undefined in builds/unix/unix-cc.in to the 
previous line.

thanks,
-christian biesinger

smime.p7s
Description: S/MIME Cryptographic Signature