Opened 15 years ago

Closed 14 years ago

#1074 closed Patches (duplicate)

FreeBSD specific patches to boost 1.34.0

Reported by: barner@… Owned by: René Rivera
Milestone: Boost 1.36.0 Component: build
Version: Boost 1.34.0 Severity: Showstopper
Keywords: patch freebsd Cc:

Description

Porting boost 1.34.0 to FreeBSD (I am the FBSD maintainer of the boost port), resulted in the following patches that should be included into the boost distribution:

patch-libs_random_random_device.cpp: Fixes the random device code on FreeBSD

patch-libs_regex_build_Jamfile.v2: /usr/local/include is not a standard include path on FreeBSD and thus must be explicitly passed to the compiler in order to detect and use the ICU library

patch-tools_build_v2_tools_python.jam: -ldl is not necessary on the BSD (dlopen is built into libc) See also: http://svn.boost.org/trac/boost/ticket/1010

Attachments (3)

patch-libs_random_random_device.cpp (523 bytes ) - added by barner@… 15 years ago.
Fix random device on FreeBSD
patch-libs_regex_build_Jamfile.v2 (392 bytes ) - added by barner@… 15 years ago.
Detect ICU on FreeBSD (don't remove -I/usr/local/include from include path)
patch-tools_build_v2_tools_python.jam (397 bytes ) - added by barner@… 15 years ago.
Fix build of Boost.Python on *BSD: don't link against libdl

Download all attachments as: .zip

Change History (5)

by barner@…, 15 years ago

Fix random device on FreeBSD

by barner@…, 15 years ago

Detect ICU on FreeBSD (don't remove -I/usr/local/include from include path)

by barner@…, 15 years ago

Fix build of Boost.Python on *BSD: don't link against libdl

comment:1 by René Rivera, 15 years ago

Component: Building Boostbuild
Milestone: To Be DeterminedBoost 1.35.0
Owner: set to René Rivera

comment:2 by René Rivera, 14 years ago

Resolution: duplicate
Status: newclosed

Split into individual tickets appropriate for each maintainer to handle. Please refrain from submitting composite tickets in the future as it just delays getting them resolved as the person who gets them may not be in a position to know what to do with them in a responsive manner.

See tickets #2027, #2028, and #2029.

Note: See TracTickets for help on using tickets.