Hi everyone,
I can't compile my project using fedora mingw, but can compile using native mingw on Windows.
I've attached 2 log files: - make.log: make when using native compiler on Fedora. - make-mingw32.log: make when using mingw32 compiler on Fedora.
Thank you.
On Thu, May 28, 2009 at 10:00:33PM -0300, Fabrício Godoy wrote:
Hi everyone,
I can't compile my project using fedora mingw, but can compile using native mingw on Windows.
I've attached 2 log files:
- make.log: make when using native compiler on Fedora.
- make-mingw32.log: make when using mingw32 compiler on Fedora.
The major problem you have is this:
i686-pc-mingw32-g++ -DHAVE_CONFIG_H -I. -I.. \ -DNETWORK_LOGGER_GLADEDIR=""/usr/local/share/network-logger/glade/"" \ -I/usr/include/gtkmm-2.4 -I/usr/lib64/gtkmm-2.4/include \ -I/usr/include/glibmm-2.4 -I/usr/lib64/glibmm-2.4/include \ [...]
There's no way it's going to work if you use native header files for the cross build.
See also:
http://camltastic.blogspot.com/2008/11/common-mistakes-cross-compiling-mingw...
Rich.
Hi, thanks for the link.
When I call "./configure --host=i686-pc-mingw32", the mingw pkg-config is not found. Maybe "i686-pc-mingw32-pkg-config" is missing.
Thanks.
2009/5/29 Richard W.M. Jones rjones@redhat.com
On Thu, May 28, 2009 at 10:00:33PM -0300, Fabrício Godoy wrote:
Hi everyone,
I can't compile my project using fedora mingw, but can compile using
native
mingw on Windows.
I've attached 2 log files:
- make.log: make when using native compiler on Fedora.
- make-mingw32.log: make when using mingw32 compiler on Fedora.
The major problem you have is this:
i686-pc-mingw32-g++ -DHAVE_CONFIG_H -I. -I.. \ -DNETWORK_LOGGER_GLADEDIR=""/usr/local/share/network-logger/glade/"" \ -I/usr/include/gtkmm-2.4 -I/usr/lib64/gtkmm-2.4/include \ -I/usr/include/glibmm-2.4 -I/usr/lib64/glibmm-2.4/include \ [...]
There's no way it's going to work if you use native header files for the cross build.
See also:
http://camltastic.blogspot.com/2008/11/common-mistakes-cross-compiling-mingw...
Rich. _______________________________________________ fedora-mingw mailing list fedora-mingw@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fedora-mingw
On Fri, May 29, 2009 at 11:47:38AM -0300, Fabrício Godoy wrote:
Hi, thanks for the link.
When I call "./configure --host=i686-pc-mingw32", the mingw pkg-config is not found. Maybe "i686-pc-mingw32-pkg-config" is missing.
Nope, you need pkg-config.
However pkg-config needs an extra environment variable to be set, and therefore you should use:
mingw32-configure
instead of the above configure command. That will cause several extra environment variables to be set, and hopefully should mean that pkg-config will find the correct paths.
Rich.
Thanks, using mingw32-configure I could compile without errors.
But mingw pkg-config still not found, it's ok?
. . . checking for i686-pc-mingw32-pkg-config... no checking for pkg-config... /usr/bin/pkg-config . . .
2009/5/29 Richard W.M. Jones rjones@redhat.com
On Fri, May 29, 2009 at 11:47:38AM -0300, Fabrício Godoy wrote:
Hi, thanks for the link.
When I call "./configure --host=i686-pc-mingw32", the mingw pkg-config is not found. Maybe "i686-pc-mingw32-pkg-config" is missing.
Nope, you need pkg-config.
However pkg-config needs an extra environment variable to be set, and therefore you should use:
mingw32-configure
instead of the above configure command. That will cause several extra environment variables to be set, and hopefully should mean that pkg-config will find the correct paths.
Rich.
fedora-mingw mailing list fedora-mingw@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fedora-mingw
On Fri, May 29, 2009 at 10:05:28PM -0300, Fabrício Godoy wrote:
Thanks, using mingw32-configure I could compile without errors.
But mingw pkg-config still not found, it's ok?
. . . checking for i686-pc-mingw32-pkg-config... no checking for pkg-config... /usr/bin/pkg-config
Yeah that's fine. It's using the AC_CHECK_TOOLS macro, so it tries to look for a host-specific tool first before using the native tool. In this case that's OK - it should fall back to using the native tool.
Rich.