A question on the GCC toolchain compiled for ARM

| Hello,
| 
| We are security researchers at Vrije Universiteit Amsterdam. We have a
| scenario where we need to be able to compile a C source on the Android
| device itself. Hence, I came upon the R project's Android port:
| 
| http://rwiki.sciviews.org/doku.php?id=getting-started:installation:android
| 
| I could not find who created the "android gcc", so I guess R porting for
| Debian is the closest mailing list I could find that is related.
| 
| Good news is that I've tried the gcc on the device and it works like a
| charm.
| question is, the size is really large. We have simple C files with no
| threading and the like.
| Just bionic + linux system headers + lib math. Nothing else.
| 
| I was wondering whether I could strip the toolchain down to a bare minimum?
| Or what were your steps while building it in the first place, so that I can
| exclude things not needed up front?
| 
| If this is not the right place, please direct me to the right forum or the
| team who did the work on the android gcc port.

I'd talk to the Debian Arm porters starting with the info here: 

    http://www.debian.org/ports/arm/

The different ports go through different ebbs and flows depending on hardware
availability and viability; I think the arm / armel folks are reasonably
active.

The mailing which you contacted here is mostly concerned with using R on
Debian / Ubuntu which almost invariably limits the userbase to x86 and amd64
architectures. 

Hth, Dirk

| Cheers,
| Earlence
| 
| 	[[alternative HTML version deleted]]
| 
| _______________________________________________
| R-SIG-Debian mailing list
| R-SIG-Debian at r-project.org
| https://stat.ethz.ch/mailman/listinfo/r-sig-debian

A question on the GCC toolchain compiled for ARM

Thread (2 messages)