On 01/10/2010 12:24 PM, DRC wrote: > Antoine Martin wrote: > >> On 10/08/2009 04:59 PM, DRC wrote: >> >>> The problem has been isolated and worked around. The issue is that the >>> OS X linker doesn't seem to honor the request to align code segments to >>> 16-byte boundaries. This has been a problem all along, but for some >>> reason, when using the OS X 10.4 linker, the problem somehow escaped >>> detection. The workaround, which I found by reading this page: >>> >>> >>> http://www.nabble.com/--nasm-Bugs-1871199---Mac-OS-X-%28Mach-O%29-misaligned-data-td22143305.html >>> >>> was to add an explicit "align 16" directive at the end of every code >>> segment. >>> >> Have you got a patch that does this? Is this still needed? >> >> You may want to merge this rather simple fix: I had to rename the "fls" >> function: >> >> libtool: compile: gcc -DHAVE_CONFIG_H -I. -O3 -m32 -MT jcdctmgr.lo -MD >> -MP -MF .deps/jcdctmgr.Tpo -c jcdctmgr.c -fno-common -DPIC -o >> .libs/jcdctmgr.o >> jcdctmgr.c:77: error: conflicting types for 'fls' >> /usr/include/string.h:123: error: previous declaration of 'fls' was here >> make[5]: *** [jcdctmgr.lo] Error 1 >> > How is this related? The bug my E-Mail was referring to was in the OS X > linker, and the patch that worked around it in the TigerVNC build has > been checked in to trunk for quite some time. Was this before or after 1.0 was released? I was building from the tigervnc-1.0.0.tar and I still get this alignment issue:
ld: in ./.libs/libjpeg.a(jiss2int.o), malformed .o file, symbol _jconst_idct_islow_sse2 with address 0x969 is not with section 2 (__DATA,__const) address range of 0x970 to 0xA20 > I have not seen the > problem with fls() that you describe above. Under what circumstances do > you see that? Judging by the message I saw ealier, this fix will be included in 1.0.1 Not sure how to build from svn as there is no "./configure" script in there and automake barfs at me with all sorts of errors on osx. How do you create a full release tigervnc-X.X.X.tar from an svn tree? > i.e. what build platform? > 10.5.6 + macports >> FYI: macports now includes 2.07 by default. >> > I've tried 'port upgrade nasm' and also doing a clean > uninstall/reinstall of nasm, but it still gives me 2.05.01. > I'm new to macports, I'll assume you've run "port sync" recently and that your $PATH is correct. port info nasm nasm @2.07 (lang) [...] which nasm /opt/local/bin/nasm port contents nasm | grep bin/nasm /opt/local/bin/nasm Or maybe you have a different version of macos/ports? Cheers Antoine ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
