Ticket #6375 (closed Bugs: fixed)

Opened 5 years ago

Last modified 4 years ago

statically linking isn't possible

Reported by: peterlohse@… Owned by: bemandawes
Milestone: To Be Determined Component: filesystem
Version: Boost 1.46.0 Severity: Problem
Keywords: Cc:



I have a problem. If a compiler with -lboost-filesystem, then is no problem, but if I compile with -lboost-filesystem and -static, there is this error: /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lboost_filesystem

I have test it with -L/usr/lib64/boost-1_46, but the same error.

OS: Gentoo

Please help.


Change History

comment:1 Changed 5 years ago by grafik

  • Component changed from None to Building Boost

Could you specify how you built Boost, and the exact command line invocation for both the working and failing compiles.

comment:2 Changed 4 years ago by viboes

  • Owner set to bemandawes
  • Component changed from Building Boost to filesystem

comment:3 Changed 4 years ago by bemandawes

  • Status changed from new to closed
  • Resolution set to fixed

Boost.Filesystem's implementation of path locale and codecvt handling has been rewritten with much simpler, more portable, and hopefully more robust code. The interface has not changed. The rewrite has been applied to svn trunk as of revision 83062. An added reference documentation section (boost-root/libs/filesystem/doc/reference.html#path-Usage) describes class path usage concerns, such as thread data races.

These changes should resolve this issue. If you believe it has not been resolved satisfactorily, please open a new issue rather than reopening this issue. But before you do that, please read boost-root/libs/filesystem/doc/reference.html#path-Usage to be sure that the problem you are seeing is not a manifestation of one of the those concerns. If you do open a new issue, please be specific and supply a test case and lots of details. Just saying something "doesn't work" or "crashes" is not enough!




Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.