[ports/glib] You must have either have gettext support

[michaK]

Hi,

I'm trying to build the glib from the ports on MacOSX 10.6 over a
pepper_16 but I get this error:

*** You must have either have gettext support in your C library, or
use the
*** GNU gettext library. (http://www.gnu.org/software/gettext/
gettext.html

Anyone bumped into this ?

M

[Brad Chen]

I remember seeing this once, although I don't think I was don't anything for Native Client, it was building a Mac binary. In that case I believe I had to download the gettext source and build it for MacOS. So in this case you would have to do the same thing, but for Native Client. You may need to learn something about config scripts and Native Client to get gettext to build properly.

I'm not sure exactly what you are referring to below when you say "glib" and "ports". Is that glib as in developer.gnome.org/glib? Porting Gnome to Native Client is a non-trivial task. I don't know of anybody having worked on that yet.

Brad

M

--
You received this message because you are subscribed to the Google Groups "Native-Client-Discuss" group.
To post to this group, send email to native-cli...@googlegroups.com.
To unsubscribe from this group, send email to native-client-di...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/native-client-discuss?hl=en.

[Evgeniy Stepanov]

You are probably building with the newlib toolchain. GLib in nacl-ports only works with the glibc toolchain. 

[michaK]

Thanks for the info. Brad, I was refering to the naclport of glib. http://code.google.com/p/naclports/ if you haven't looked at the ports, you should definitely try to check it out.

I worked around my issue with gettext by not using nacl-mounts. but Is nacl-mounts going to be supported in the futture?

Cheers,

M

Michel Courtine | CEO | iVoltage
+33 6 189 354 89 | mic...@ivoltage.me

http://ivoltage.me

[Brad Chen]

Oops; fortunately Evgeniy was watching.

What were you trying to do with nacl-mounts? Last time I tried I was able to use it. Things build best on Linux and Mac. There are definitely naclports build problems on Windows.

We do intend to improve support for nacl-mounts. For 3rd party stuff in naclports, such as glib, we are hopeful that over time more and more patches will move upstream, such that the patches in naclports would no longer be needed. In the mean time things are pretty much 'as-is/no-warranty' unfortunately. Please file a bug (code.google.com/p/naclports/issues) of send a patch if you see a problem or how to fix it.

Thanks,

Brad

[michaK]

Well I was just looking for a replacement for memory.h for our physics engine (bullet) as suggested here:

http://code.google.com/p/nativeclient/issues/detail?id=1210

 but the game that I'm porting doesn't use this physics engine at all so I just disabled it :p

 

Yeah I love the ports, self deploying into the sdk make them really comfortable and easy to use.

There's just one thing that bugs me. It's the conflict between the paths pointed to by NACL_SDK_ROOT

for scons to find g++ on my system the variable must be set to:

export NACL_SDK_ROOT=/Users/michaK/nacl/nacl_sdk/

or for the port builder shell script to find the right branch to target, as I have to set my variable to:

export NACL_SDK_ROOT=/Users/michaK/nacl/nacl_sdk/pepper_16

for the build to install the lib & header into the right branch, maybe you need a second optional environment variable NACL_SDK_BRANCH ?

Or any other directory trick to your taste.

Best,

M

Also, I'm building on MacOS now, much better than Windows for now.