From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: linux-omap-open-source@linux.omap.com
Subject: Re: Missing "bin" file when files extracted from gcc-3.4.0.tar.bz2
Date: Fri, 20 Oct 2006 08:45:27 +0200 [thread overview]
Message-ID: <200610200845.28619.openembedded@hrw.one.pl> (raw)
In-Reply-To: <20061019213008.53834.qmail@web50102.mail.yahoo.com>
Dnia czwartek, 19 października 2006 23:30, Rene Holder napisał:
> The project I am currently undertaking is "Building Linux for the
> OMAP5912 OSK Development Platform".
> One of the first steps required me to unzip the gcc-3.4.0.tar.bz2 file
> using the command: tar -xjvf /root/gcc-3.4.0.tar.bz2
>
> One of the following instructions asked me to add the tool chain path
> to the current path via the following command: export
> PATH=/opt/gcc-3.4.0/bin:$PATH
>
> Unfortunately, I am unable to locate the "bin" folder and this is
> leading to errors later on in the process. I also tried a later version
> of the gnu toolchain: gcc-3.4.3.tar.bz2 but I was still unable to
> locate the "bin" folder.
>
> Could you please help me with this problem?
I suggest taking a look at OpenEmbedded [1] project which can build
working images for omap5912osk with gcc 3.4.4 or 4.1.1.
With simple configuration you can get everything needed (glibc- or uclibc-
based toolchain, 2.6.18-omap-git kernel, userspace apps) built with just
one command.
I can provide rootfs + kernel for test if someone want to take a look.
1. http://www.openembedded.org/
--
JID: hrw-jabber.org
OpenEmbedded developer/consultant
prev parent reply other threads:[~2006-10-20 6:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 21:30 Missing "bin" file when files extracted from gcc-3.4.0.tar.bz2 Rene Holder
2006-10-20 6:45 ` Marcin Juszkiewicz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200610200845.28619.openembedded@hrw.one.pl \
--to=openembedded@hrw.one.pl \
--cc=linux-omap-open-source@linux.omap.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox