From: Juergen Beisert <jbe@pengutronix.de>
To: CARAYOL Sophie <s.carayol@lacroix-electronics.com>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Compilation of OSELAS Toolchain
Date: Thu, 20 Mar 2014 16:39:15 +0100 [thread overview]
Message-ID: <201403201639.15399.jbe@pengutronix.de> (raw)
In-Reply-To: <657f0f8acddf4b749858a644f0e0a6a7@AMSPR07MB470.eurprd07.prod.outlook.com>
Hi Sophie,
On Thursday 20 March 2014 15:35:40 CARAYOL Sophie wrote:
> 1- OK for the mailing list
\o/
> 2- Yes, the directory
> "/opt/OSELAS.Toolchain-2013.12.1/arm-v7a-linux-gnueabihf/" exists and
> contains a toolchain.
Hmm, but why you start again to build a toolchain, when it is already present?
> 3- I wrote a source and need to create all needed
> files to be used with Ptxdist. I usually use "how to become a Ptxdist Guru"
> but there is nothing explained to start from sources without makefile, etc.
To build binaries from sources you always need some kind of management.
And "make" is the tool here which does exactly this job. How do you build your
sources without "make"? Do you call your compiler manually for each source
file?
> 4- I have created another project for my sources and don't compile in the
> toolchain directory
But you sent us the logs from building your toolchain, not from your project.
> 5- It seems the problem appears when I launched the "$ pxtdist compile
> my_packet" command. Something was broken but where ? I have installed again
> the toolchain and ptxdist but the problem remains...
Then send us your project or the logs from your project and not the logfile
from your toolchain build.
Regards,
Juergen
--
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 15:39 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
2014-03-20 14:35 ` CARAYOL Sophie
2014-03-20 15:39 ` Juergen Beisert [this message]
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=201403201639.15399.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