Alexey Pavlov <[email protected]> writes: >>>> So what's the right method to force the build to use -static-libgcc when >>>> it links a dll? (LDFLAGS doesn't work) >>>> >>> In PKGBUILD before configure: >>> LDFLAGS+=« -static-libgcc» >>> doesn’t work? >> >> No. Apparently LDFLAGS is ignored when creating a dll: >> >> LDFLAGS+=" -static-libgcc " >> "${srcdir}"/${_pkgnameactual}${pkgver}/configure \ >> --prefix=${MINGW_PREFIX} \ >> $enable64bit >> make >> >> The command that creates the dll: >> >> gcc -shared -o Tktable210.dll tkTable.o tkTableWin.o tkTableTag.o >> tkTableEdit.o tkTableCell.o tkTableCellSort.o tkTableCmds.o tkTableUtil.o >> -lgdi32 -luser32 "C:\apps\msys32\mingw32\lib\libtclstub86.a" >> "C:\apps\msys32\mingw32\lib\libtkstub86.a" >> >> > Seems configure override all system wide LDFLAGS or not use them at > all. You need patch configure then to pass «-static-libgcc»
It is very likely that the same problem will arise for other Tcl binary extensions I intend to package. Patching the configure script for each of those (and discriminating by architecture, as 64 bit arch is not affected by the problem) can be a bit tiresome. Is it ok to use the CC="gcc -static-libgcc" configure ... trick until the problem with libgcc_s_dw2-1 is fixed? I guess that eventually SEH will be implemented on 32 bits MinGW-w64. ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
