Well.. I tweaked a .pl file to use the xcc version of one tool, but now I'm hitting another issue
cd ~/Win32/inkscape/ make -f Makefile.mingw make -C po -f Makefile.mingw make[1]: Entering directory `/home/joncruz/Win32/inkscape/po' make[1]: `all' is up to date. make[1]: Leaving directory `/home/joncruz/Win32/inkscape/po' make -C src -f Makefile.mingw make[1]: Entering directory `/home/joncruz/Win32/inkscape/src' i686-pc-mingw32-dllwrap --output-lib=inkscape.la \ --def=inkscape.def --driver-name=g++ \ -o inkscape.dll libinkscape.a -L/target/lib -lgtkmm-2.4 -lgdkmm-2.4 -lglibmm-2.4 -latkmm-1.6 -lpangomm-1.4 -lsigc-2.0 -lgtk-win32-2.0 -lgdk-win32-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangoft2-1.0 -lpangowin32-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 -lxml2 /target/lib/iconv.lib -lfreetype6.dll -lfontconfig-1.dll -lpng -lpopt /target/lib/zdll.lib -lgc -mwindows -lws2_32 -lintl /usr/bin/ld: unrecognized option '--base-file' /usr/bin/ld: use the --help option for usage information collect2: ld returned 1 exit status i686-pc-mingw32-dllwrap: g++ exited with status 1 make[1]: *** [inkscape.dll] Error 1 make[1]: Leaving directory `/home/joncruz/Win32/inkscape/src' make: *** [all] Error 2
So... anyone have ideas on making it hit the proper version of ld?
On Sat, Nov 13, 2004 at 12:35:38PM -0800, Jon A. Cruz wrote:
/usr/bin/ld: unrecognized option '--base-file'
The problem is that the mingw tools all use the "regular" names, so you have to set up symlink and adjust your path:
lrwxrwxrwx 1 root root 18 2004-10-27 20:30 ld -> i686-pc-mingw32-ld* lrwxrwxrwx 1 root root 18 2004-10-27 20:31 ar -> i686-pc-mingw32-ar* lrwxrwxrwx 1 root root 18 2004-10-27 20:31 nm -> i686-pc-mingw32-nm* lrwxrwxrwx 1 root root 19 2004-10-27 20:31 g++ -> i686-pc-mingw32-g++* lrwxrwxrwx 1 root root 19 2004-10-27 20:31 gcc -> i686-pc-mingw32-gcc* drwxr-xr-x 2 nobody 99 4096 2004-10-27 20:31 ./ /usr/local/xmingw/bin$
So... anyone have ideas on making it hit the proper version of ld?
And I use this script to compile:
#!/bin/bash
export PKG_CONFIG_PATH=/target/lib/pkgconfig export PATH=/usr/local/xmingw/bin:$PATH
make -j3 -f Makefile.mingw || exit 1
Jon A. Cruz wrote:
Well.. I tweaked a .pl file to use the xcc version of one tool, but now I'm hitting another issue
cd ~/Win32/inkscape/ make -f Makefile.mingw make -C po -f Makefile.mingw make[1]: Entering directory `/home/joncruz/Win32/inkscape/po' make[1]: `all' is up to date. make[1]: Leaving directory `/home/joncruz/Win32/inkscape/po' make -C src -f Makefile.mingw make[1]: Entering directory `/home/joncruz/Win32/inkscape/src' i686-pc-mingw32-dllwrap --output-lib=inkscape.la \ --def=inkscape.def --driver-name=g++ \ -o inkscape.dll libinkscape.a -L/target/lib -lgtkmm-2.4 -lgdkmm-2.4 -lglibmm-2.4 -latkmm-1.6 -lpangomm-1.4 -lsigc-2.0 -lgtk-win32-2.0 -lgdk-win32-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangoft2-1.0 -lpangowin32-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 -lxml2 /target/lib/iconv.lib -lfreetype6.dll -lfontconfig-1.dll -lpng -lpopt /target/lib/zdll.lib -lgc -mwindows -lws2_32 -lintl /usr/bin/ld: unrecognized option '--base-file' /usr/bin/ld: use the --help option for usage information collect2: ld returned 1 exit status i686-pc-mingw32-dllwrap: g++ exited with status 1 make[1]: *** [inkscape.dll] Error 1 make[1]: Leaving directory `/home/joncruz/Win32/inkscape/src' make: *** [all] Error 2
So... anyone have ideas on making it hit the proper version of ld?
Jon,
The cross-compiler is built to be located at /usr/local/xmingw, so this is what I always set to use it (I use tcsh, but bash works fine):
setenv PATH /usr/local/xmingw/bin:/usr/local/xmingw/i686-pc-mingw32/bin:$PATH
Then maybe a 'rehash' afterward, to cache the right paths for gcc, ld, ar, etc.
Bob
Bob Jamison wrote:
The cross-compiler is built to be located at /usr/local/xmingw, so this is what I always set to use it (I use tcsh, but bash works fine):
setenv PATH /usr/local/xmingw/bin:/usr/local/xmingw/i686-pc-mingw32/bin:$PATH
Well, I had mainly done all that, but to no avail.
Then I went ahead and did Kees' kludge of symlinks for all the executable names. That ended up making things work for me finally.
I'm sure, though, that there's some way to get it to do things the "right" way, as half my build used the proper prefixed binary names. However, 'till we have time to track subtle things down, the work-around should be sufficient. Just add that step of symlinking to your instructions page and we should be good for now.
:-)
participants (3)
-
Bob Jamison
-
Jon A. Cruz
-
Kees Cook