Patches item #312018, was changed at 18/10/2009 10:20 by Pino Toscano You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=312018&group_id=30628
>Status: Closed Priority: 3 Submitted By: Pino Toscano (pino-guest) Assigned to: Nobody (None) Summary: #552383: boost 1.40.0 Category: None Group: None >Resolution: Fixed Initial Comment: A couple of changes needed to build boost 1.40 on GNU/Hurd: - boost/math/special_functions/ellint_rd.hpp: the local 'ED' variable conflicts with the enum/define in bits/errno.h, so replaced with 'ED_' - boost/test/impl/execution_monitor.ipp: properly use simple int or singinfo_t* signal handling & reporting based on the SA_SIGINFO definition Also boost depends on an MPI implementation, but there were no issues in any MPI-related boost code. ---------------------------------------------------------------------- >Comment By: Pino Toscano (pino-guest) Date: 20/11/2009 19:31 Message: boost1.40 1.40.0-3 contains the patches, and boost1.40 1.40.0-4 currently installed correctly. Thus, closing. ---------------------------------------------------------------------- Comment By: Pino Toscano (pino-guest) Date: 25/10/2009 22:40 Message: Thanks for the review! Sent as bug #552383. ---------------------------------------------------------------------- Comment By: Samuel Thibault (sthibault) Date: 25/10/2009 19:30 Message: ED: I'd say yes. ---------------------------------------------------------------------- Comment By: Pino Toscano (pino-guest) Date: 24/10/2009 21:42 Message: Ok, thanks! What should I tell the boost guys about the 'ED' patch? To keep it Debian-specific for now? ---------------------------------------------------------------------- Comment By: Samuel Thibault (sthibault) Date: 24/10/2009 01:04 Message: Looks great, please submit! ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=312018&group_id=30628 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
