Re: To compile glib on MinGW is not easy

[LRN <lrn1986 gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 30.05.2014 15:51, Florian HEGRON wrote:
> Hello,
>
> I compiled glib on my MinGW installation ! It's unbelievable.
>
> I plaisant but this is because I try since many days (weeks).
>
>
> My different problems (with glib 2.41.0) :
>
> - There is a bug into mingw-libintl package I opened a ticket in the bug 
> tracker system of the MinGW project [1].

.la files must not be installed. Removing .la files is THE right solution.

> - There is a problem with rand_s in grand.c in Glib and Windows API 
> provided with MinGW32. I saw that there are several patchs on several 
> forums/bugtrackers but I can't make it to work. If anybody know more
> about this, thank you. My solution : I read the commit on git repo [2] and
> I unpatched glib.

Seems like MinGW.org-only problem.
It might be possible to rewrite this to use W32 CryptoAPI instead
(XP-or-later, but i doubt that glib maintains pre-XP compatibility anymore).

> - There is a last problem with Python when I "make install". The error : 
> python can't read /usr/bin/sh. My solution : I install Python (2.7.6), I 
> add the path into $PATH, and I modified the 
> glib-2.41.0/bld/gio/gdbus-2.0/codegen/Makefile file. On line 538, I
> delete "PYTHON = /usb/bin/env python25" and wrote "PYTHON = ". And at the
> line 199, I change "am__py_compile = $(PYTHON) $(SHELL) $(py_compile)" by 
> "am__py_compile = $(SHELL) $(py_compile)". I didn't test but I think that 
> the error is juste the "/usr/bin/env". I think that there is a bug with 
> the ./configure script because in the Makefile files, the value of the 
> PYTHON variable was "/usr/bin/env python25" but, at the beginning, I 
> didn't have Python installed on my computer.

This is kind of complicated. Personally, i have W32 CPython integrated into
my MinGW-w64 installation, and i also have MSYS2-Python installed. Other
people use MinGW-CPython instead of W32 CPython. Either way, things seem to
work out just fine for me.
Your description of the problem (not the solution) is kind of short, so i
have no idea why would Python try to read /usr/bin/sh.

> I really want to help to make glib more easy to compile and install. So 
> say me what can I do to help the project. Do you want that I make a 
> specific test and show to you the result ?

I don't know. Not many people care about MinGW.org these days. It's hard
enough to make glib devs accept patches that are MinGW-w64-compatible, with
MinGW.org it's going to be even harder.


- -- 
O< ascii ribbon - stop html email! - www.asciiribbon.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)

iQEcBAEBAgAGBQJTiHwjAAoJEOs4Jb6SI2CwYoYIANFP7iZODN5HKe47aCjE9Kzw
mT4TAgrJczADnRPjWg63FQhionEmdwtgjvMLa+P6T2HRlhSUQKhqE2JoiGARyd2z
fzCnobrLP59djSFFTokuIGyHA3ggdG/Bzp+gVw5baUpgZ050p6qzUr1ifJrUPEwo
ffwGddTwI++vJX11kVySJZ3oG9E4G6vOere/QrnVki/19eQ9Hq1wyEdy7Hji9NsH
k2xSCj0dKLGB2c/IOfzTVM69vxvqPYG0UjKBGhMdYJMYCdMeH8F0oNK/iX4Qum8N
90OT50us7PO1WTQpEl1BchF3gsaF9gZmGWTisNBRLDEheQ5pHGclPsCzocTnDOk=
=whFB
-----END PGP SIGNATURE-----