Re: Cross-compilation, static build, etc

[Bruno Seiva Martins <brunoseivam@gmail.com>]

Hi,

Just to let you all know, the idea of compiling from inside a VM was bugging me a lot, so I went to the trouble of building a toolchain to be able to cross compile my IOC to my target system.

It was painful and bloody, but I succeeded.

The general steps I took:

Download and configure crosstool-NG with the version numbers of my target's kernel, binutils, glibc and gcc

Generate the toolchain

Compile both 'readline' and 'ncurses' using that brand new toolchain

Configure EPICS to use my toolchain and compile it

Compile the IOC and copy it to my target

If there's enough interest in this process, I can write a detailed guide of what I did.

Regards,

Bruno Seiva Martins

On Thu, Aug 2, 2012 at 8:57 PM, Bruno Seiva Martins <brunoseivam@gmail.com> wrote:

Hi Andrew,

I came across that StackOverflow question too and tried the steps showed in the answer, but unluckly the offending symbol didn't have a correspondent in an older version... I'll try the VM approach, and in the meantime will think of other possible solutions. If I find one, I'll post it here.

Bruno Seiva Martins

On Thu, Aug 2, 2012 at 3:21 PM, Andrew Johnson <anj@aps.anl.gov> wrote:

Hi Bruno,

On 2012-08-02 Bruno Seiva Martins wrote:
> Looking closely, indeed using 'STATIC_BUILD=YES' compiled EPICS code
> statically to my executable, leaving only the shared system libraries out.
> I guess I will build a virtual machine with my target's Linux distribution
> and compile from it, although a cross compiler would be neater =)

Google does find some ways to get around this (including a Stack Overflow
question that goes into details about defining appropriately-versioned
symbols) so in theory it should be possible to do, but I suspect a VM will be
much easier in the end.

- Andrew
--
Never interrupt your enemy when he is making a mistake.
-- Napoleon Bonaparte