From: Greg White <Gregory.W<hite@ps...> - 2012-03-23 13:50:40
[ccing the distribution list.]
Hi Dirk, sorry, I meant to send this to you yesterday, but got overtaken by some 24hr flu.
Here's the mail archive:
I't linked off the the home page.
We started a thread on your issue yesterday , but your email adds a lot of specifics - thanks. It
seems the team is largely aware if issues, but we need to be specific about what modules of EPICS V4
we actually want to be cross-compilable, and then list the system requirements for that. I'm hoping
Marty and James can do that.
On 23 Mar 2012, at 14:13, Dirk Zimoch wrote:
> Hi all,
> I am writing to you because I could not find any mailing list on the EPICS 4 web site. You are those of the "EPICS v4 Working group" list whose e-mail address I know.
> I have tried to compile EPICS 4 for several cross architectures and failed. Now I would like to talk to some developer. Unfortunately the code is anonymous. It would be great if the main authors of some code could put their mail addresses into each file.
> I tried the following cross architectures:
> * vxWorks 5.5 -- a disaster
> * vxWorks 6.3 -- some problems I don't understand
> * vxWorks 6.7 -- promising after some modifications
> * Linux (several embedded distributions) -- fails to link test apps
> Has anyone tried to cross compile EPICS 4 before?
> I found that the major problem with vxWorks is the tr1 C++ extension. It is not included in the vxWorks tool chain. So I downloaded it from boost but found that the vxWorks 5.5 g++ cannot not compile it. This how boost reacted on my report:
>> #6725: exception.hpp does not compile with vxWorks 5.5
>> Replying to [ticket:6725 dirk.zimoch@…]:
>> > Compiler is:
>> > gcc version gcc-2.96 (2.96+) 19990621 AltiVec
>> This is ancient. I suspect that very little in
>> Boost is going to work with this compiler.
> I must admit that the smart pointers in tr1 are interesting, but on the other hand vxWorks 5.5 is still one of the major EPICS platforms. Probably it is possible to extract from boost/tr1 what is needed by EPICS 4 and include it in the package (-> check license). It would be nice if someone could take care of it.
> To make EPICS 4 run on vxWorks 6.7, some modifications were necessary. Whom can I send the changes for a review?
> There are compiler problems on vxWorks 6.3 which need some discussion with the authors of the EPICS 4 code. Whom can I talk to?
> There is a strange linker problem for cross Linux architectures. For some reason, the path to EPICS base is not given to the linker so that the Com library cannot be found when building the test applications. Who can have a look at this problem? (I have set up the Linux cross builds as "Host" builds, so that I get all the executables.)
> Best regards,