Experimental Physics and
Industrial Control System

Henrique Almeida <[email protected]> · Wed, 7 Jan 2015 13:35:22 -0200

 It's necessary to include the definition of the classes you're using
on any system, you probably got away with not including them before
because the header could have been implicitly included by other
headers. It looks like the new C++ library has become stricter.

2015-01-07 11:18 GMT-02:00 Mark Rivers <[email protected]>:
> Why is it necessary to include string only on OSX Yosemite, and not on Linux, Windows, vxWorks, or earlier versions of OSX?
> ________________________________________
> From: Henrique Almeida [[email protected]]
> Sent: Wednesday, January 07, 2015 4:56 AM
> To: Mark Rivers
> Cc: Henrique Almeida; [email protected] Talk
> Subject: Re: Problem building asyn R4-25 on Mac OSX Yosemite
>
>  It looks like a bug in the asyn include file, which was not including
> string in the first place.
>
> 2015-01-06 21:39 GMT-02:00 Mark Rivers <[email protected]>:
>> Yes, that fixes the problem, thanks.
>>
>> I think it is a bug in the OSX C++ include files, but the workaround is simple and harmless.
>>
>> Mark
>>
>>
>> -----Original Message-----
>> From: Henrique Almeida [mailto:[email protected]]
>> Sent: Tuesday, January 06, 2015 2:08 PM
>> To: Mark Rivers
>> Cc: [email protected] Talk
>> Subject: Re: Problem building asyn R4-25 on Mac OSX Yosemite
>>
>>  Include <string> ?
>>
>> 2015-01-06 17:37 GMT-02:00 Mark Rivers <[email protected]>:
>>> Folks,
>>>
>>>
>>>
>>> Diego Omitto from BNL has reported the following errors when building asyn
>>> R4-25 on Max OSX Yosemite.
>>>
>>>
>>>
>>> It builds fine on Linux, Windows, vxWorks, and earlier versions of OSX.
>>>
>>>
>>>
>>> c++ -c              -DUNIX  -Ddarwin     -O3 -g   -Wall      -arch x86_64
>>> -fno-common -fPIC -MMD -I. -I../O.Common -I. -I.. -I../../asyn/asynDriver
>>> -I../../asyn/asynGpib -I../../asyn/drvAsynSerial -I../../asyn/interfaces
>>> -I../../asyn/miscellaneous -I../../asyn/asynPortDriver/exceptions
>>> -I../../asyn/asynPortDriver -I../../asyn/asynPortClient
>>> -I../../asyn/devEpics -I../../asyn/asynRecord -I../../asyn/vxi11
>>> -I../../asyn/gsIP488 -I../../asyn/ni1014 -I../../asyn/devGpib
>>> -I../../include/os/Darwin -I../../include
>>> -I/Users/diego/epics/synApps_5_7/support/ipac-2-12/include
>>> -I/Users/diego/epics/synApps_5_7/support/seq-2-1-13/include
>>> -I/Users/diego/epics/base/include/os/Darwin
>>> -I/Users/diego/epics/base/include
>>> ../../asyn/asynPortClient/asynPortClient.cpp
>>>
>>> In file included from ../../asyn/asynPortClient/asynPortClient.cpp:18:
>>>
>>> ../../asyn/asynPortClient/asynPortClient.h:75:38: error: implicit
>>> instantiation of undefined template 'std::__1::basic_string<char,
>>> std::__1::char_traits<char>,
>>>
>>>       std::__1::allocator<char> >'
>>>
>>>             throw std::runtime_error(std::string("pasynInt32SyncIO->connect
>>> failed"));
>>>
>>>                                      ^
>>>
>>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/iosfwd:188:33:
>>> note: template is declared here
>>>
>>>     class _LIBCPP_TYPE_VIS_ONLY basic_string;
>>>
>>>                                 ^
>>>
>>>
>>>
>>> Can anyone suggest what needs to be changed to eliminate this error?
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Mark
>>>
>>>

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System