Loading ...
Sorry, an error occurred while loading the content.

Re: Cross-compile toolchain

Expand Messages
  • clerew5
    ... It is not clear to me whether you need the cross-compiler in order to compile slugos itself (or maybe additional kernel modules), or whether you just want
    Message 1 of 10 , Nov 1, 2010
    • 0 Attachment
      --- In nslu2-linux@yahoogroups.com, Harsh <harshbaste@...> wrote:
      >
      > Thanks a bunch for the direction! Probably saved me a lot of pain in the process.
      >
      > I'll try and give it a go with the latest snapshot and tweak the OE build to see how it goes.
      >

      It is not clear to me whether you need the cross-compiler in order to compile slugos itself (or maybe additional kernel modules), or whether you just want to compile applications to run on Slugos 5.3. If it's the former, then Mike is the expert and you do what he says. But if it is the latter, then you really do not need to get involved with all the OE stuff at all.

      Even the machinery for cross compiling Optware is more complex than it needs to be IMHO.

      I have constructed a cross-compiler which will compile for both slugos 4.8 and slugos 5.3, including both big and little endian versions of each, depending on just how you call it, and making use of the library and include files already available with the respective distributions, without making any versions of its own. It is still a bit hairy (I had to cheat the gcc Makefiles in a few places, which is why it is not ready for publication yet).
    • Harsh
      For the moment, I d just be happy to get a cross compile environment for regular C++ binaries. I probably would need to port/build a few drivers onto the slug
      Message 2 of 10 , Nov 1, 2010
      • 0 Attachment
        For the moment, I'd just be happy to get a cross compile environment for regular C++ binaries. I probably would need to port/build a few drivers onto the slug later on though so having kernel module build capability would be rather handy.

        Thanks for everyone's response on this. Really great to see this group still has a lot of life in it even though the device is long EOL'd.

        -H

        --- On Mon, 1/11/10, clerew5 <clerew5@...> wrote:

        From: clerew5 <clerew5@...>
        Subject: [nslu2-linux] Re: Cross-compile toolchain
        To: nslu2-linux@yahoogroups.com
        Date: Monday, 1 November, 2010, 4:22 PM

         



        --- In nslu2-linux@yahoogroups.com, Harsh <harshbaste@...> wrote:
        >
        > Thanks a bunch for the direction! Probably saved me a lot of pain in the process.
        >
        > I'll try and give it a go with the latest snapshot and tweak the OE build to see how it goes.
        >

        It is not clear to me whether you need the cross-compiler in order to compile slugos itself (or maybe additional kernel modules), or whether you just want to compile applications to run on Slugos 5.3. If it's the former, then Mike is the expert and you do what he says. But if it is the latter, then you really do not need to get involved with all the OE stuff at all.

        Even the machinery for cross compiling Optware is more complex than it needs to be IMHO.

        I have constructed a cross-compiler which will compile for both slugos 4.8 and slugos 5.3, including both big and little endian versions of each, depending on just how you call it, and making use of the library and include files already available with the respective distributions, without making any versions of its own. It is still a bit hairy (I had to cheat the gcc Makefiles in a few places, which is why it is not ready for publication yet).


      Your message has been successfully submitted and would be delivered to recipients shortly.