[gentoo-embedded] Building packages

[gentoo-embedded] Building packages

[Tim Erwin]

[-- Attachment #1: Type: text/plain, Size: 336 bytes --]

Hi I am new to embedded linux and am trying to get gentoo on my phone
(openmoko). I have used a stage3 build on the phone and have tried distcc
but this is still painfully slow as all the configuration is still done on
the phone. So using just the cross-compiler how can I build packages and
then get them onto the phone?

Thanks,

Tim

[-- Attachment #2: Type: text/html, Size: 419 bytes --]

Re: [gentoo-embedded] Building packages

[Sven 'sleipnir' Rebhan]

Hello Tim,

a few people (including me) started a cross-compile overlay for the
openmoko phone.
The overlay can be found here:  http://projects.openmoko.org/projects/gentoo

The goal of our project is to fix cross-compile problems of ebuilds
and feed back those fixes to the portage tree... Feel free to report
bugs, problems, documentation ;-), fixes or new ebuilds there!

Best regards,

    Sven

Re: [gentoo-embedded] Building packages

[Christopher Friedt]

Hi Tim,

You may have already gotten past this point, but in order to start
building packages for the OpenMoko, the right place to start off with
is a cross-compiler.

I have a cross-compiler pre-built for i686, which you can install with:

PORTAGE_BINHOST=http://vaiprime.visibleassets.com/~cfriedt/toolchains/i686-pc-linux-gnu/arm-softfloat-linux-gnueabi/All
\
emerge -avG1 cross-arm-softfloat-linux-gnueabi/{binutils,linux-headers,gcc,glibc}

You should then

emerge sys-devel/crossdev-wrapper

Remember to set FEATURES="buildpkg" in
/usr/arm-softfloat-linux-gnueabi/etc/make.conf so that whenever you
build something, the binary tbz2 package is created as well.

Also, if you are going to cross-compile glibc, then use the -B
argument to emerge, otherwise it will overwrite your cross-toolchain
libc in /usr/arm-softfloat-linux-gnueabi.

Cheers,

Chris

On Wed, Dec 10, 2008 at 8:49 AM, Sven 'sleipnir' Rebhan
<odinshorse@googlemail.com> wrote:
> Hello Tim,
>
> a few people (including me) started a cross-compile overlay for the
> openmoko phone.
> The overlay can be found here:  http://projects.openmoko.org/projects/gentoo
>
> The goal of our project is to fix cross-compile problems of ebuilds
> and feed back those fixes to the portage tree... Feel free to report
> bugs, problems, documentation ;-), fixes or new ebuilds there!
>
> Best regards,
>
>    Sven
>
>

Re: [gentoo-embedded] Building packages

[Tim Erwin]

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

Thanks for your comments Chris, just a few other questions:


> Also, if you are going to cross-compile glibc, then use the -B
> argument to emerge, otherwise it will overwrite your cross-toolchain
> libc in /usr/arm-softfloat-linux-gnueabi.
>

If I emerge-armv4tl-softfloat-linux-gnueabi -uvDN system this pulls in glibc
will this cause problems?

Regards,

Tim





>
> On Wed, Dec 10, 2008 at 8:49 AM, Sven 'sleipnir' Rebhan
> <odinshorse@googlemail.com> wrote:
> > Hello Tim,
> >
> > a few people (including me) started a cross-compile overlay for the
> > openmoko phone.
> > The overlay can be found here:
> http://projects.openmoko.org/projects/gentoo
> >
> > The goal of our project is to fix cross-compile problems of ebuilds
> > and feed back those fixes to the portage tree... Feel free to report
> > bugs, problems, documentation ;-), fixes or new ebuilds there!
> >
> > Best regards,
> >
> >    Sven
> >
> >
>
>

[-- Attachment #2: Type: text/html, Size: 1625 bytes --]

Re: [gentoo-embedded] Building packages

[Christopher Friedt]

Hi Tim,

On Sun, Mar 8, 2009 at 10:47 PM, Tim Erwin <taerwin@gmail.com> wrote:
> If I emerge-armv4tl-softfloat-linux-gnueabi -uvDN system this pulls in glibc
> will this cause problems?

Yes, you should avoid cross-emerging glibc to your 'sysroot', or
/usr/arm-softfloat-linux-gnueabi, if at all possible.

On a related note, if you're using that toolchain for the FR, then you
can squeeze out a few bytes of space, and squeeze in a few cycles  of
performance if you set CFLAGS="-O2 -mcpu=arm920t -fomit-frame-pointer
-pipe" ... you'll loose the frame pointer for debugging purposes, but
compiling specifically for the arm920t core will certainly improve
overall performance and decrease binary size.

C