Re: [Boost-build] Linker error with filesystem2 on windows

Subject: Re: [Boost-build] Linker error with filesystem2 on windows
From: Bo Jensen (jensen.bo_at_[hidden])
Date: 2011-04-12 17:13:56

On Tue, Apr 12, 2011 at 8:31 PM, Gevorg Voskanyan <v_gevorg_at_[hidden]> wrote:
> Bo Jensen wrote:
>
>> I get the following error on windows with msvc 10 :
>>
>> sulumcmd.obj : error  LNK2019: unresolved external symbol "void __cdecl
>>boost::as
>> sertion_failed(char const *,char const *,char const *,long)"
> [snip]
>> bin\msvc-10.0\debug\address-model-64\threading-multi\sulum.exe  : fatal error
>>LNK
>> 1120: 1 unresolved externals
>> ...failed msvc.link
>>bin\msvc-10.0\debug\address-model-64\threading-multi\sulum.e
>> xe  bin\msvc-10.0\debug\address-model-64\threading-multi\sulum.pdb...
>> ...removing  bin\msvc-10.0\debug\address-model-64\threading-multi\sulum.pdb
>> ...failed  updating 1 target...
>> ...updated 1 target...
>>
>> Maybe it's just me I don't  get how I can get a unresolved symbol on a
>> only header based function  ?
>>
>> I am linking with both the filesystem and system lib.
>>
>> Any help  appreciated.
>>
>> /Bo
>
> Is BOOST_ENABLE_ASSERT_HANDLER #defined by any chance?
>
> HTH,
> Gevorg
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
>

Doooohhh my mistake, I had set the macro myself long time ago in a far
out corner of a large code base... Thanks Gevorg!