hugin-devs team mailing list archive

[Yuv <816240@xxxxxxxxxxxxxxxxxx>]

On July 28, 2011 01:13:12 AM Greg 'groggy' Lehey wrote:
> OK, tried revision 5428.  I didn't get the message.  Then I tried
> revision 5435 again, and I didn't get the message either.  It was
> easily repeatable when I reported it, but something seems to have
> changed since then.  Presumably this is some kind of benign race
> condition.

Thanks for testing.  Can there be such a thing as a benign race
condition?

 
> I've updated http://wiki.panotools.org/Hugin_Compiling_FreeBSD .
> Comments welcome.

Very much appreciated, thank you!  It would be useful to expand the document 
with regard to libpano13 and enblend.

It happens often (out of my head I would say about 50% of the times) that the 
development version of Hugin depends of a development version of 
graphics/libpano13 at build- and run-time.

There are currently two issues with that port.
1) the build of libpano13 has moved to CMake but the port still uses the 
autotool build.
2) by default, it requires Java.  Makes it very heavy.  However, for the 
majority of users of the library, Java is unnecessary.  It would be better to 
use .if defined(WITH_JAVA) rather than .if !defined(WITHOUT_JAVA).

Changes with enblend are less frequent, but it is safe to assume that users 
venturing beyond the standard port install will also want to test a bleeding 
edge version of enblend.

Last but not least:  I know that in Gentoo Linux Portage (conceptually copied 
from the ports collection) it is possible to define an SCM as the source for 
the code.  Any such thing with the FreeBSD ports?  I am asking because it 
would be handy to have a /graphics/hugin-nightly (and related libpano13-
nightly and enblend-nightly) to enable easy bleeding edge testing and improve 
FreeBSD support.

Thanks again
Yuv (Kubuntu desktop, but all of my servers are FreeBSD).

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/816240

Title:
  Fatal error message after stitching

Status in Hugin - Panorama Tools GUI:
  Incomplete

Bug description:
  After stitching a 25 image two-row panorama with the currently latest
  development version of Hugin (changeset 5435), I get the message:

    Fatal error 'Thread 0x882f6780 has called pthread_exit() from a
  destructor. POSIX 1003.1 1996 s16.2.5.2 does not allow this!' at line
  79 in file /src/FreeBSD/svn/stable/8/lib/libthr/thread/thr_exit.c
  (errno = 0)

  The final image was produced, and as far as I can tell, it was
  stitched correctly.  Hugin did not crash.

  System:    FreeBSD 8.2-STABLE, i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/816240/+subscriptions