• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.
Sign in to follow this  
Followers 0

The horror of cross-compiling!

3 posts in this topic

Posted

Hello!

I've been trying to bake my own rom now for a while, and a part from failing with the signing of the update.zip and actually upload it to my hero it goes alright..

However when i try to add some more stuff like binaries i run into problems (here is where it gets a little less focused on actually baking the rom and more on software dev).

For example when i try to cross-compile helloworld.c everything goes just fine whether i statically link it or dynamically using a codesourcery's toolchain or the one from google with the agcc script (people who know about cross-compiling should know what i am talking about right :D)

So simple programs i write myself are all oke.

However when i try to cc more complicated programs such as PAND (Personal area network daemon) or even nano it just always fails. Whether it's missing a file/header or just missing a structtype... what am i doing wrong?

I type this into a terminal:

- export PATH=$PATH:<path-to-android-kernel-source>/prebuild/linux-x86/toolchain/arm-eabi-4.2.1/bin

export CC=agcc
./configure --host arm-linux
make[/codebox]

and any variation on that (statically or not different cross compilers whatever..

Shouldn' t this be working? or is it quite normal that you run into alot of problems while cc'ing and you just have to hack your way around until it gives you the green light?

Any help would be greatly appreciated!

Richard

0

Share this post


Link to post
Share on other sites

Posted

i am everything else than an expert on this, as a matter of fact i have no idea what agcc is, but have you tried it the regular way? meaning without agcc?

0

Share this post


Link to post
Share on other sites

Posted

i am everything else than an expert on this, as a matter of fact i have no idea what agcc is, but have you tried it the regular way? meaning without agcc?

agcc is a script which helps with the linking to bionic's libs.

And yeah I've tried static builds as well but it gives me the same error's...

Or what did you mean by "the regular way" ?

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.