From: Juergen Beisert <jbe@pengutronix.de>
To: CARAYOL Sophie <s.carayol@lacroix-electronics.com>,
ptxdist@pengutronix.de
Subject: Re: [ptxdist] Compilation of OSELAS Toolchain
Date: Thu, 20 Mar 2014 14:30:03 +0100 [thread overview]
Message-ID: <201403201430.03312.jbe@pengutronix.de> (raw)
In-Reply-To: <43cf16db313b442f9d840ea634ae2e79@AMSPR07MB470.eurprd07.prod.outlook.com>
Hi Sophie,
please, please, keep the mailing list at least on CC.
On Thursday 20 March 2014 10:33:03 CARAYOL Sophie wrote:
> it's not the problem of this file. It's the same with the original file. I
> joined the file i used (there was light changes).
--- arm-v7a-linux-gnueabihf_gcc-4.8.3_glibc-2.18_binutils-2.24_kernel-3.12-sanitized.ptxconfig
+++ arm-v7a-linux-gnueabihf_gcc-4.8.3_glibc-2.18_binutils-2.24_kernel-3.13.6-sanitized.ptxconfig
@@ -57,13 +57,13 @@
PTXCONF_CROSS_BINUTILS_MD5="e0f71a7b2ddab0f8612336ac81d9636b"
# PTXCONF_CROSS_ELF2FLT is not set
PTXCONF_KERNEL_HEADERS=y
-PTXCONF_KERNEL_HEADERS_VERSION="3.12"
-PTXCONF_KERNEL_HEADERS_MD5="cc6ee608854e0da4b64f6c1ff8b6398c"
+PTXCONF_KERNEL_HEADERS_VERSION="3.13.6"
+PTXCONF_KERNEL_HEADERS_MD5="445aa27da818617409982f42902a6e41"
PTXCONF_KERNEL_HEADERS_SANITIZED=y
PTXCONF_CROSS_GCC=y
PTXCONF_CROSS_GCC_VERSION="4.8.3"
-PTXCONF_CROSS_GCC_MD5="729f4ac34ad404892ecafb991bea2da5"
-PTXCONF_CROSS_GCC_DL_VERSION="linaro-4.8-2013.11"
+PTXCONF_CROSS_GCC_MD5="2b3bbea7806931e2048e0fc5983021c8"
+PTXCONF_CROSS_GCC_DL_VERSION="linaro-4.8-2014.02"
PTXCONF_CROSS_GCC_PKGVERSION="${PTXCONF_PROJECT} ${PTXCONF_CROSS_GCC_DL_VERSION}"
PTXCONF_CROSS_GCC_43=y
PTXCONF_CROSS_GCC_45=y
Not that much changes. But when I use your config file and start the build, I
get:
---------------------------------------------------------------------
[jbe@thebe]> ptxdist go
error: '/opt/OSELAS.Toolchain-2013.12.1/arm-v7a-linux-gnueabihf/gcc-4.8.3-glibc-2.18-binutils-2.24-kernel-3.13.6-sanitized'
does not exist and cannot be created!
Please create that dir with write permissions for you.
press enter to let sudo do that job!
---------------------------------------------------------------------
Where is this step on your machine? Does the "/opt/OSELAS.Toolchain-2013.12.1/arm-v7a-linux-gnueabihf/"
directory already exist and already contains a toolchain?
> The problem occurred the first time when I tried to use the joined document
> "Application Note : work with sources".
How do "Application Note : work with sources" correlates with building a
toolchain? What do you intend to do?
> Maybe, I made something wrong... but there are bugs also in the document :-)
First of all: this document is veeeery old. Please try the current "How to
become a PTXdist guru" [1] instead.
> so I gave up and the problem remains. Maybe the problem is linked to
> rules files...
Please keep the toolchain building a separate step. Start with the
"arm-v7a-linux-gnueabihf" toolchain.
If you want to build your own application with the help of PTXdist, create
a new PTXdist project, do not re-use the toolchain project for this purpose.
Regards,
Juergen
[1] http://www.pengutronix.de/software/ptxdist/appnotes/OSELAS.BSP-Pengutronix-Generic-arm-Quickstart.pdf
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-03-20 13:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 11:04 Sophie
2014-03-17 13:14 ` Juergen Beisert
2014-03-17 20:09 ` Alexander Aring
2014-03-18 8:06 ` CARAYOL Sophie
2014-03-19 8:04 ` Juergen Beisert
2014-03-19 10:37 ` CARAYOL Sophie
2014-03-19 10:58 ` Juergen Beisert
2014-03-20 7:58 ` CARAYOL Sophie
2014-03-20 8:30 ` Juergen Beisert
2014-03-20 9:33 ` CARAYOL Sophie
2014-03-20 13:30 ` Juergen Beisert [this message]
2014-03-20 14:35 ` CARAYOL Sophie
2014-03-20 15:39 ` Juergen Beisert
2014-03-21 13:50 ` CARAYOL Sophie
2014-03-19 13:44 ` Uwe Kleine-König
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=201403201430.03312.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=s.carayol@lacroix-electronics.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