Hi Roger,

2012/1/4 Carlos Eduardo G. Carvalho (Cartola) <[email protected]>

> Hi Roger, I have compiled it ok with the "-O" option. It is running fine
> on FreeBSD 8.2-RELEASE with tiff-4.0.0.
>
> My gcc version is:
> > g++ -v
> Using built-in specs.
> Target: amd64-undermydesk-freebsd
> Configured with: FreeBSD/amd64 system compiler
> Thread model: posix
> gcc version 4.2.1 20070719  [FreeBSD]
>
>
> Thanks!
>
> Carlos E G Carvalho (Cartola)
> http://cartola.org/360
>
>
>
I don't think it has to do with the compiler but with the data declarations
in the program.

For what it's worth.
When doing a straight compilation on MacOSX (snow leopard 10.6.8): g++ 4.2
is used and -O2 works fine. So, this will ceate a x86_64 64bit binary which
works fine.
When crosscompiling, using a massive set of all kind of  settings, the
x86_64 version is compiled with g++ 4.2 as well. However, as it needs to
run on Leopard, Snow Leopard and Lion I use that set of extra settings. For
this version when using -O2 it segfaults. -O works.
The i386 binary is compiled with g++ 4.0 otherwise it wouldn't run on on
Tiger. These segfault also with -O2 and work fine with -O.
(note: other binaries which I cross-compile for triple universal
x86_64/i386/ppc, the ppc part is also compiled with gcc/g++ 4.0 for the
same reason).

Next to that: Versions of enblend before version 4.0 were "unstable"  when
cross-compiling with -O3 but worked fine with -O2. Version 4.0 and some
development versions before that, worked fine with -O3. Somewhere during
the development I tried switching to -O3 and it "suddenly" worked. I don't
have a clue which changeset(s) made this possible.

Harry

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Reply via email to