Ticket #30 (closed defect: invalid)

Opened 1 year ago

Last modified 3 months ago

(260) Current framework does not build with Boost version 1.34.0

Reported by: cdietric Assigned to: shereef
Priority: critical Milestone: Release 0.8.0
Component: ossiecf Version:
Keywords: Cc:

Change History

08/07/07 21:45:59 changed by balister

Apparently boost 1.34 dropped the path checking routines. Need to investigate and work out alternate method for verifying valid file names.

11/13/07 17:42:45 changed by balister

  • owner changed from cdietric to balister.
  • priority changed from major to critical.
  • status changed from new to assigned.

I have confirmed this problem exists in Fedora 8. Time to fix this problem.

g++ -DPACKAGE_NAME=\"ossie\" -DPACKAGE_TARNAME=\"ossie\" -DPACKAGE_VERSION=\"0.6.2\" "-DPACKAGE_STRING=\"ossie 0.6.2\"" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"ossie\" -DVERSION=\"0.6.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_LIBOMNIORB4=1 -DHAVE_OMNIORB4_CORBA_H=1 -DHAVE_BOOST_FILESYSTEM_OPERATIONS_HPP=1 -DHAVE_LIBBOOST_FILESYSTEM=1 -DHAVE_SYS_WAIT_H=1 -DHAVE_TIME_H=1 -DHAVE_DIRENT_H=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 -DHAVE_WORKING_VFORK=1 -DHAVE_WORKING_FORK=1 -I../include -I../parser -Wall -g -g -O2 -MT FileManager?_impl.lo -MD -MP -MF .deps/FileManager_impl.Tpo -c FileManager?_impl.cpp -fPIC -DPIC -o .libs/FileManager_impl.o

FileManager?_impl.cpp: In member function 'virtual CF::FileSystem::FileInformationSequence?* FileManager?_impl::list(const char*)': FileManager?_impl.cpp:242: error: 'const class boost::filesystem::filesystem_error' has no member named 'error' FileManager?_impl.cpp:244: error: 'const class boost::filesystem::filesystem_error' has no member named 'error' FileManager?_impl.cpp:244: error: 'other_error' is not a member of 'fs'

11/14/07 09:22:40 changed by jgaeddert

The interfaces for boost 1.34.0 have changed as well, if I remember correctly. Look at the difference in the header files from 1.33.0 to 1.34.0.

On a side note, is there an easy way to install just the boost filesystem from source and not the whole flippin' boost package?

11/14/07 09:47:13 changed by balister

yum install boost-devel solves the problem for me. Dunno about installing from source.

11/14/07 17:02:11 changed by balister

r5740 compiles against boost 1.34, but not 1.33.

Bother. Looks like I need to probe for the library version and #ifdef code.

11/16/07 08:04:52 changed by balister

r5788 adds code so you can compile for boost pre and post 1.34. To build with 1.34 use ./configure CFLAGS=BOOST_1_34. Close the bug when we autodetect the boost library version, or no one can find a 1.33 system we care about ....

04/11/08 13:08:08 changed by shereef

  • owner changed from balister to shereef.
  • status changed from assigned to new.

05/07/08 13:15:12 changed by bhilburn

  • status changed from new to closed.
  • resolution set to invalid.

This isn't really a valid ticket anymore since 'trunk' no longer has boost capabilities. When Shereef ports the boost code into the new 'trunk', he will need to keep this in mind, however.