Re: 2 questions about MXE

[Michael Goffioul]

On Mon, Jun 24, 2013 at 2:46 PM, PhilipNienhuis <address@hidden> wrote:

Michael Goffioul wrote

> 1) Is there a reason not to enable SSE2 support when compiling FFTW,
> except
> to support old CPU's?

Does this also apply to other packages? (blas, ....)

For FFTW, there's specific source files that make use of CPU features like SSE, SSE2, AVX... If can be enabled with e.g. --enable-sse2. Using CPU-optimized compilation makes sense for the underlying math libraries, I'm not sure you'd gain much for non-math libraries.

 

> 2) When compiling curl with MSVC, I noticed that SSL support got disabled
> at configure time, although --with-gnutls is specified. I think it's due

> to ...

How can I check that on a ready-built Octave (built using mxe-built
dependencies)? Does octave_config_info have that info?

Just try: ./usr/i686-pc-mingw32/bin/curl https://www.google.com

But I suppose it'll work for you, see below.

 

> ... curl configure script using pkg-config to detect gnutls, but it's

> using the
> one from ./usr/bin, which is looking into ./usr/lib/pkgconfig, while
> gnutls.pc has been installed in ./usr/i686-pc-mingw32/lib/pkgconfig. Does
> the problem occurs with native MinGW and how is it dealt with? Shouldn't
> we
> have a natively compiled pkg-config instead?

AFAICS pkg-config gets built in mxe-octave, also on native MinGW.
To be able to build other Octave versions (see my build instruction just
uploaded to your other -GSOC- thread) PKG_CONFIG_PATH has to be set
explicitly - John D made a shell script for that.

As I wrote in another mail, I'd expect these to be taken care of by the top-level Makefile. TBH I don't really get the separation between ./usr and ./usr/i686-pc-mingw32 for native builds. Obviously the solution is to force PKG_CONFIG_PATH, though I wouldn't expect to have to do it manually.

Michael.