On Sat, Feb 7, 2015 at 9:40 AM, Alon Zakai <[email protected]> wrote:
> This is a limitation of how we "fake" configure results. We invoke the
> native compiler but with our libraries and defines, so this can fail if
> types are different. The reason we do this is that configure can do
> anything natively - read/write to a file, open a process, etc., stuff we
> can't do in compiled JS.
>
> There is an EMCONFIGURE_JS env var you can set, to force use of JS, which
> might help here.
>
> Perhaps we should default to EMCONFIGURE_JS, and force people to modify
> configure scripts the other way - but either way, there will be manual work.
>
In this case, you could use the right flags with clang to request a 32 bit
build.
On Linux and FreeBSD, pass -m32, on OS X, pass -arch i386.
Seems like you could do that in this chunk:
env['HOST_CC'] = CLANG_CC
env['HOST_CXX'] = CLANG_CPP
env['HOST_CFLAGS'] = "-W" #if set to nothing, CFLAGS is used, which we
don't want
env['HOST_CXXFLAGS'] = "-W" #if set to nothing, CXXFLAGS is used, which
we don't want
env['PKG_CONFIG_LIBDIR'] = path_from_root('system', 'local', 'lib',
'pkgconfig') + os.path.pathsep + path_from_root('system', 'lib',
'pkgconfig')
env['PKG_CONFIG_PATH'] = os.environ.get ('EM_PKG_CONFIG_PATH') or ''
env['EMSCRIPTEN'] = path_from_root()
- Bruce
--
You received this message because you are subscribed to the Google Groups
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
