[gentoo-embedded] Trying to get toolchain

[gentoo-embedded] Trying to get toolchain

[Jean-Marc Beaune]

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

Hi,

I'm trying to install the toolchain and regardless of the tuple I use
crossdev fails to compile gcc.

Any idea?
Please tell me if you need more info.

Thank you,
-- 
Jean-Marc

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

Re: [gentoo-embedded] Trying to get toolchain

[Peter Stuge]

Jean-Marc Beaune wrote:
> I'm trying to install the toolchain and regardless of the tuple I
> use crossdev fails to compile gcc.
> 
> Any idea?
> Please tell me if you need more info.

Versions of all packages involved and the build log would be helpful.


//Peter

Re: [gentoo-embedded] Trying to get toolchain

[Ned Ludd]

On Fri, 2008-10-10 at 15:07 +0200, Jean-Marc Beaune wrote:
> Hi,
>  
> I'm trying to install the toolchain and regardless of the tuple I use
> crossdev fails to compile gcc.
>  
> Any idea?
> 


Chances are you are hitting the bug with crossdev and headers.

If so.

crossdev $CTARGET
#wait for failure.
USE="-*" emerge -O cross-$CTARGET/gcc
crossdev $CTARGET


Good luck.

-- 
Ned Ludd <solar@gentoo.org>
Gentoo Linux

Re: [gentoo-embedded] Trying to get toolchain

[Jean-Marc Beaune]

[-- Attachment #1.1: Type: text/plain, Size: 1955 bytes --]

Hi,

Before doing anything I try to give you more info (I attached log files when
I try to build toolchain for an Etrax100).

I tried USE="-*" emerge -O cross-$CTARGET/gcc but it ends with the following
error :

* Applying gcc-4.0.2-softfloat.patch ...

 * Failed Patch: gcc-4.0.2-softfloat.patch !
 *  (
/usr/local/portage/cross-cris-softfloat-uclinux-uclibc/gcc/files/4.0.2/gcc-4.0.2-softfloat.patch
)
 *
 * Include in your bugreport the contents of:
 *
 *
/var/tmp/portage/cross-cris-softfloat-uclinux-uclibc/gcc-4.3.1-r1/temp/gcc-4.0.2-softfloat.patch-18633.out

 *
 * ERROR: cross-cris-softfloat-uclinux-uclibc/gcc-4.3.1-r1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_unpack
 *             environment, line 4589:  Called epatch 'src_unpack'
 *             environment, line 2097:  Called die
 * The specific snippet of code:
 *                   die "Failed Patch: ${patchname}!";
 *  The die message:
 *   Failed Patch: gcc-4.0.2-softfloat.patch!
 *
 * If you need support, post the topmost build error, and the call stack if
relevant.
 * A complete build log is located at
'/var/tmp/portage/cross-cris-softfloat-uclinux-uclibc/gcc-4.3.1-r1/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/cross-cris-softfloat-uclinux-uclibc/gcc-4.3.1-r1/temp/environment'.
 * This ebuild is from an overlay: '/usr/local/portage/'

Thank you,
Jean-Marc

On Fri, Oct 10, 2008 at 4:44 PM, Ned Ludd <solar@gentoo.org> wrote:

>
> On Fri, 2008-10-10 at 15:07 +0200, Jean-Marc Beaune wrote:
> > Hi,
> >
> > I'm trying to install the toolchain and regardless of the tuple I use
> > crossdev fails to compile gcc.
> >
> > Any idea?
> >
>
>
> Chances are you are hitting the bug with crossdev and headers.
>
> If so.
>
> crossdev $CTARGET
> #wait for failure.
> USE="-*" emerge -O cross-$CTARGET/gcc
> crossdev $CTARGET
>
>
> Good luck.
>
> --
> Ned Ludd <solar@gentoo.org>
> Gentoo Linux
>
>
>


-- 
Jean-Marc

[-- Attachment #1.2: Type: text/html, Size: 3049 bytes --]

[-- Attachment #2: cross-cris-softfloat-uclinux-uclibc-info.log --]
[-- Type: application/octet-stream, Size: 11479 bytes --]

[-- Attachment #3: cross-cris-softfloat-uclinux-uclibc-uclibc-headers.log --]
[-- Type: application/octet-stream, Size: 4033 bytes --]

>>> Verifying ebuild Manifests...

>>> Emerging (1 of 1) cross-cris-softfloat-uclinux-uclibc/uclibc-0.9.30_rc1 to /
 * uClibc-0.9.30-rc1.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...              [ ok ]
 * uClibc-0.9.30-rc1-patches-0.1.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...  [ ok ]
 * checking ebuild checksums ;-) ...                                      [ ok ]
 * checking auxfile checksums ;-) ...                                     [ ok ]
 * checking miscfile checksums ;-) ...                                    [ ok ]
 * checking uClibc-0.9.30-rc1.tar.bz2 ;-) ...                             [ ok ]
 * checking uClibc-0.9.30-rc1-patches-0.1.tar.bz2 ;-) ...                 [ ok ]
>>> Unpacking source...
>>> Unpacking uClibc-0.9.30-rc1.tar.bz2 to /var/tmp/cross/cris-softfloat-uclinux-uclibc/portage/cross-cris-softfloat-uclinux-uclibc/uclibc-0.9.30_rc1/work
>>> Unpacking uClibc-0.9.30-rc1-patches-0.1.tar.bz2 to /var/tmp/cross/cris-softfloat-uclinux-uclibc/portage/cross-cris-softfloat-uclinux-uclibc/uclibc-0.9.30_rc1/work

 * Runtime Prefix: /
 * Devel Prefix:   /usr
 * Kernel Prefix:  /usr/cris-softfloat-uclinux-uclibc/usr/include
 * CBUILD:         i686-pc-linux-gnu
 * CHOST:          i686-pc-linux-gnu
 * CTARGET:        cris-softfloat-uclinux-uclibc
 * CPU:            default
 * ENDIAN:         little

>>> Unpacking uClibc-0.9.30-rc1-patches-0.1.tar.bz2 to /var/tmp/cross/cris-softfloat-uclinux-uclibc/portage/cross-cris-softfloat-uclinux-uclibc/uclibc-0.9.30_rc1/work/uClibc-0.9.30-rc1
 * Applying various patches (bugfixes/updates) ...
 *   66_all_uClibc-0.9.29-conditional-sched_affinity.patch ...
  [ ok ]
 *   69_all_uClibc-0.9.29-fix-gethostent_r-failure-retval.patch ...
  [ ok ]
 *   71_all_uClibc-arm_fix_alignment.patch ...
  [ ok ]
 *   72_all_uClibc-0.9.29-linuxthreads.patch ...
  [ ok ]
 *   74_all_uClibc-0.9.29-rm-whitespace.patch ...
  [ ok ]
 *   75_all_uClibc-arm-ftruncate64.patch ...
  [ ok ]
 *   77_all_uClibc-unistd_arm.patch ...
  [ ok ]
 *   80_all_uClibc-no-locale-in-configure.patch ...
  [ ok ]
 *   81_all_uClibc-gnu89-inline.patch ...
  [ ok ]
 * Done with patching
 * Applying various patches (bugfixes/updates) ...
 *   10_all_uClibc-0.9.29-susv3-2.patch ...
  [ ok ]
 *   15_all_uClibc-0.9.29-susv3-ldouble-3.patch ...
  [ ok ]
 * Done with patching
 * 
 * ERROR: cross-cris-softfloat-uclinux-uclibc/uclibc-0.9.30_rc1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_unpack
 *             environment, line 2716:  Called die
 * The specific snippet of code:
 *               die "$(tc-arch) lists no defaults :/"
 *  The die message:
 *   cris lists no defaults :/
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/cross/cris-softfloat-uclinux-uclibc/portage/cross-cris-softfloat-uclinux-uclibc/uclibc-0.9.30_rc1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/cross/cris-softfloat-uclinux-uclibc/portage/cross-cris-softfloat-uclinux-uclibc/uclibc-0.9.30_rc1/temp/environment'.
 * This ebuild is from an overlay: '/usr/local/portage/'
 * 

 * Messages for package cross-cris-softfloat-uclinux-uclibc/uclibc-0.9.30_rc1:

 * 
 * ERROR: cross-cris-softfloat-uclinux-uclibc/uclibc-0.9.30_rc1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_unpack
 *             environment, line 2716:  Called die
 * The specific snippet of code:
 *               die "$(tc-arch) lists no defaults :/"
 *  The die message:
 *   cris lists no defaults :/
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/cross/cris-softfloat-uclinux-uclibc/portage/cross-cris-softfloat-uclinux-uclibc/uclibc-0.9.30_rc1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/cross/cris-softfloat-uclinux-uclibc/portage/cross-cris-softfloat-uclinux-uclibc/uclibc-0.9.30_rc1/temp/environment'.
 * This ebuild is from an overlay: '/usr/local/portage/'
 * 

Re: [gentoo-embedded] Trying to get toolchain

[Ryan Tandy]

On Sat, Oct 11, 2008 at 09:32:22AM +0200, Jean-Marc Beaune wrote:
> * Applying gcc-4.0.2-softfloat.patch ...
> 
>  * Failed Patch: gcc-4.0.2-softfloat.patch !
>  *  (
> /usr/local/portage/cross-cris-softfloat-uclinux-uclibc/gcc/files/4.0.2/gcc-4.0.2-softfloat.patch
> )

This happens with any *-softfloat-* toolchain and gcc-4.3.  Try
compiling a gcc-4.1 or -4.2 toolchain.

Thanks,
Ryan

Re: [gentoo-embedded] Trying to get toolchain

[Martin Gysel]

Ryan Tandy schrieb:
> On Sat, Oct 11, 2008 at 09:32:22AM +0200, Jean-Marc Beaune wrote:
>> * Applying gcc-4.0.2-softfloat.patch ...
>>
>>  * Failed Patch: gcc-4.0.2-softfloat.patch !
>>  *  (
>> /usr/local/portage/cross-cris-softfloat-uclinux-uclibc/gcc/files/4.0.2/gcc-4.0.2-softfloat.patch
>> )
> 
> This happens with any *-softfloat-* toolchain and gcc-4.3.  Try
> compiling a gcc-4.1 or -4.2 toolchain.

of have a look at bug #228119, there's a new patch (AFAIK just converted
the 4.0.2 to compile with 4.3) but as it's not verified to work so
vapier hasn't committed it yet... - maybe you can verify it

Martin

Re: [gentoo-embedded] Trying to get toolchain

[Ryan Tandy]

On Sat, Oct 11, 2008 at 09:08:13PM +0200, Martin Gysel wrote:
> of have a look at bug #228119, there's a new patch (AFAIK just converted
> the 4.0.2 to compile with 4.3) but as it's not verified to work so
> vapier hasn't committed it yet... - maybe you can verify it

Thanks for the pointer.  I hadn't noticed that bug.  I'm setting up for
a toolchain build with that patch right now.  When it's done I'll build
up a userland and see how it goes.

Thanks,
Ryan

Re: [gentoo-embedded] Trying to get toolchain

[Enrico Weigelt]

* Jean-Marc Beaune <jm.beaune@gmail.com> schrieb:
> Hi,
> 
> I'm trying to install the toolchain and regardless of the tuple I use
> crossdev fails to compile gcc.

Did you try crosstool instead ?

http://ymorin.is-a-geek.org/dokuwiki/projects/crosstool


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------

[gentoo-embedded] Configuration of an embedded system

[Gareth McClean]

I figure this group is best placed to answer my questions, if not please
feel free to point me in the right direction: 

a) Do any open source projects target the initial setup of an embedded
system i.e. basics like manually configuring an Ethernet port, configuration
of wireless networking or possibly other essentials like hostname, timezone,
etc?

b) If not, do you perform your 'out-of-the-box setup' i.e. did you create
your own set of tools using packages like awk, sed, perl etc?

c) How are you communicating with the user during the installation process?

c) Are there any intentions to migrate the Linux 'system configuration' into
a machine readable format like XML. Ignore that that might sound like a call
to implement the equivalent of the windows registry and focus on the fact I
am concerned about the potential issues of processing unstructured, human
readable text files and want an easy/reliable way to programmatically change
the system configuration and manage future system updates.  


Thanks in advance, Gareth

Re: [gentoo-embedded] Configuration of an embedded system

[Daniel Stonier]

2008/11/20 Ryan Tandy <tarpman@gmail.com>:
> On Wed, Nov 19, 2008 at 11:13:46AM -0000, Gareth McClean wrote:
>> a) Do any open source projects target the initial setup of an embedded
>> system i.e. basics like manually configuring an Ethernet port, configuration
>> of wireless networking or possibly other essentials like hostname, timezone,
>> etc?
>
> ...
>> b) If not, do you perform your 'out-of-the-box setup' i.e. did you create
>> your own set of tools using packages like awk, sed, perl etc?
>
> Again, depending on the scale of the project, I use either a stripped
> down Gentoo system or a simple Busybox-based system.
>
I just set up a control board and was also wondering about the best way to
create a runtime root. Since a control board only requires a few packages,
busybox ended up being really simple. I put the kernel and rootfs in ram
and let the user manually extend it by mounting a drive
on /usr/local where they can dump any extra binaries and libs they want.
But I wouldn't recommend it for a system where you wanted to pile on
packages up to the point of needing an x server.

I also tried gentoo's crossdev to create a root fs, thinking that would be
really easy just to xmerge in the right packages. But you end up with alot
of cruft that way, and the other problem is most ebuilds aren't set up to
work with cross-compiling out of the box (lots of bugs), so xmerge falls
over alot.

The other option I tried is openembedded. Which for me, was using a sledge
hammer on a tiny nail. Probably really good as your embedded project scales
up though - it gives you a way of defining your filesystem/package
configuration.

>> c) How are you communicating with the user during the installation process?
>
> Most of the systems I'm used to aren't designed to be installed by a
> user - at least the software side of things.
>
>> c) Are there any intentions to migrate the Linux 'system configuration' into
>> a machine readable format like XML.
>
> No.  Do you have any idea how long it takes to read and write XML?
>
>> Ignore that that might sound like a call to implement the equivalent
>> of the windows registry
>
> It doesn't, although it does sound like unnecessary overhead.
>
>> and focus on the fact I am concerned about the potential issues of
>> processing unstructured, human readable text files
>
> Which issues?  All of the base system configuration files seem fairly
> structured to me.  At any rate I'd much rather be parsing simple text
> files than XML.  Which files are you having trouble with?
>
>> and want an easy/reliable way to programmatically change the system
>> configuration and manage future system updates.
>
> Most people that I know of solve these problems with shell or
> perl/python/language-of-the-moment scripts.
>
> Bear in mind that these are just my opinions; other people on the list
> will doubtless disagree with them. :)
>
> Thanks,
> Ryan
>
>

Re: [gentoo-embedded] Configuration of an embedded system

[Natanael Copa]

On Thu, 2008-11-20 at 02:50 -0800, Ryan Tandy wrote:
> On Wed, Nov 19, 2008 at 11:13:46AM -0000, Gareth McClean wrote:
> > a) Do any open source projects target the initial setup of an embedded
> > system i.e. basics like manually configuring an Ethernet port, configuration
> > of wireless networking or possibly other essentials like hostname, timezone,
> > etc?
> 
> I either use Gentoo's baselayout or openrc, or write my own simple init
> script, depending on what I'm doing.  I don't know of any init system
> projects that are targeted specifically at embedded.

I have an alpine-baselayout that is a simplified gentoo basealyout
(without openrc)  targetted gentoo-embedded.

It uses busybox's ifup -a (debian style /etc/network/interface)

http://dev.alpinelinux.org/cgit/cgit.cgi/alpine-baselayout/

-nc

Re: [gentoo-embedded] Configuration of an embedded system

[Ryan Tandy]

On Thu, Nov 20, 2008 at 04:31:38PM +0900, Daniel Stonier wrote:
> But you end up with alot of cruft that way

Look into INSTALL_MASK.  It is true, though, that one of the things
Gentoo people tend to spend quite a bit of time at is stripping down
their images. :)

> and the other problem is most ebuilds aren't set up to work with
> cross-compiling out of the box (lots of bugs), so xmerge falls over
> alot.

I wouldn't say 'most'.  Unfortunately a non-trivial chunk of the ones
that don't cross compile cleanly are ones that lots of people like to
have (notable examples include perl and python).  On the other hand,
once you have a sane base system up, most packages should cross compile
with minimal trickery.

If you're struggling to get a package to compile, you can always check
http://tinderbox.dev.gentoo.org/ and see if anyone has left a package
for your target there.

> The other option I tried is openembedded.

I haven't looked into openembedded much myself, but I understand it's
pretty good at what it does.

Thanks,
Ryan

Re: [gentoo-embedded] Configuration of an embedded system

[Ryan Tandy]

On Wed, Nov 19, 2008 at 11:13:46AM -0000, Gareth McClean wrote:
> a) Do any open source projects target the initial setup of an embedded
> system i.e. basics like manually configuring an Ethernet port, configuration
> of wireless networking or possibly other essentials like hostname, timezone,
> etc?

I either use Gentoo's baselayout or openrc, or write my own simple init
script, depending on what I'm doing.  I don't know of any init system
projects that are targeted specifically at embedded.

> b) If not, do you perform your 'out-of-the-box setup' i.e. did you create
> your own set of tools using packages like awk, sed, perl etc?

Again, depending on the scale of the project, I use either a stripped
down Gentoo system or a simple Busybox-based system.

> c) How are you communicating with the user during the installation process?

Most of the systems I'm used to aren't designed to be installed by a
user - at least the software side of things.

> c) Are there any intentions to migrate the Linux 'system configuration' into
> a machine readable format like XML.

No.  Do you have any idea how long it takes to read and write XML?

> Ignore that that might sound like a call to implement the equivalent
> of the windows registry

It doesn't, although it does sound like unnecessary overhead.

> and focus on the fact I am concerned about the potential issues of
> processing unstructured, human readable text files

Which issues?  All of the base system configuration files seem fairly
structured to me.  At any rate I'd much rather be parsing simple text
files than XML.  Which files are you having trouble with?

> and want an easy/reliable way to programmatically change the system
> configuration and manage future system updates.  

Most people that I know of solve these problems with shell or
perl/python/language-of-the-moment scripts.

Bear in mind that these are just my opinions; other people on the list
will doubtless disagree with them. :)

Thanks,
Ryan

Re: [gentoo-embedded] Configuration of an embedded system

[Daniel Stonier]

2008/11/20 Ryan Tandy <tarpman@gmail.com>:
> On Thu, Nov 20, 2008 at 04:31:38PM +0900, Daniel Stonier wrote:
>> But you end up with alot of cruft that way
>
> Look into INSTALL_MASK.  It is true, though, that one of the things
> Gentoo people tend to spend quite a bit of time at is stripping down
> their images. :)

>> and the other problem is most ebuilds aren't set up to work with
>> cross-compiling out of the box (lots of bugs), so xmerge falls over
>> alot.
>
> I wouldn't say 'most'.  Unfortunately a non-trivial chunk of the ones
> that don't cross compile cleanly are ones that lots of people like to
> have (notable examples include perl and python).  On the other hand,
> once you have a sane base system up, most packages should cross compile
> with minimal trickery.
>
> If you're struggling to get a package to compile, you can always check
> http://tinderbox.dev.gentoo.org/ and see if anyone has left a package
> for your target there.

Oh, cheers!...Thanks for the information.

Regards,
Daniel Stonier.

Re: [gentoo-embedded] Configuration of an embedded system

[Peter Stuge]

Daniel Stonier wrote:
> The other option I tried is openembedded. Which for me, was using a
> sledge hammer on a tiny nail.

Also worth looking into may be T2; http://www.t2-project.org/


//Peter