On Thu, 2009-04-23 at 14:13 +0200, Erik van Pienbroek wrote: > The way you've overriden the MINGW32_CFLAGS might cause issues in the > future when the MINGW32_CFLAGS in /etc/rpm/macros.mingw32 might get > changed.
I was worried about this too > You can try to change the line: > export MINGW32_CFLAGS="-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 > -fexceptions --param=ssp-buffer-size=4 -mms-bitfields > -DSQLITE_ENABLE_COLUMN_METADATA=1 -DSQLITE_DISABLE_DIRSYNC=1 > -DSQLITE_ENABLE_FTS3=3 -DSQLITE_ENABLE_RTREE=1 -fno-strict-aliasing" > > to this: > export MINGW32_CFLAGS="$MINGW32_CFLAGS -DSQLITE_ENABLE_COLUMN_METADATA=1 > -DSQLITE_DISABLE_DIRSYNC=1 -DSQLITE_ENABLE_FTS3=3 > -DSQLITE_ENABLE_RTREE=1 -fno-strict-aliasing" Good idea - except it does not work, as MINGW32_CFLAGS are only set when configure runs, they are unset when I do the export. See http://koji.fedoraproject.org/koji/taskinfo?taskID=1317231 So a working solution might look something like: export MINGW32_CFLAGS="`rpm --eval %{_mingw32_cflags}` -DSQLITE_ENABLE_COLUMN_METADATA=1 -DSQLITE_DISABLE_DIRSYNC=1 -DSQLITE_ENABLE_FTS3=3 -DSQLITE_ENABLE_RTREE=1 -fno-strict-aliasing" Tom _______________________________________________ fedora-mingw mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/fedora-mingw
