From: Juergen Beisert <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: CARAYOL Sophie <s.carayol@lacroix-electronics.com>
Subject: Re: [ptxdist] Compilation of OSELAS Toolchain
Date: Thu, 20 Mar 2014 09:30:06 +0100 [thread overview]
Message-ID: <201403200930.06997.jbe@pengutronix.de> (raw)
In-Reply-To: <70f834c065aa4f0cad795958e2577040@AMSPR07MB470.eurprd07.prod.outlook.com>
Hi Sophie,
On Thursday 20 March 2014 08:58:46 CARAYOL Sophie wrote:
> scar@scar-Linux-T3500:~$ uname -a
> Linux scar-Linux-T3500 3.8.0-35-generic #50~precise1-Ubuntu SMP Wed Dec 4
> 17:28:45 UTC 2013 i686 i686 i386 GNU/Linux scar@scar-Linux-T3500:~$ make --version
> GNU Make 3.81
> Copyright (C) 2006 Free Software Foundation, Inc.
> Ceci est un logiciel libre ; voir le source pour les conditions de copie.
> Il n'y a PAS de garantie ; tant pour une utilisation COMMERCIALE que pour
> RÉPONDRE À UN BESOIN PARTICULIER.
>
> Ce logiciel est construit pour i686-pc-linux-gnu
My french from school is a little bit rusty... :)
Hmm, I'm using the same 'make' than you do. My system is a 64 bit type, but
we also run our PTXdist on 32 bit system types. We run out of ideas what
is going wrong on your machine.
Ahhhhh, I see the difference by typing the exact same command than you did:
/usr/local/lib/ptxdist-2013.12.0/bin/ptxdist select arm-v7a-linux-gnueabihf_gcc-4.8.3_glibc-2.18_binutils-2.24_kernel-3.13.6-sanitized.ptxconfig
error: cannot select
'arm-v7a-linux-gnueabihf_gcc-4.8.3_glibc-2.18_binutils-2.24_kernel-3.13.6-sanitized.ptxconfig'
does not exist, or is not a file.
It seems you have a separate file called "arm-v7a-linux-gnueabihf_gcc-4.8.3_glibc-2.18_binutils-2.24_kernel-3.13.6-sanitized.ptxconfig".
Where does it comes from? Our toolchain package only comes with a
"arm-v7a-linux-gnueabihf_gcc-4.8.3_glibc-2.18_binutils-2.24_kernel-3.12-sanitized.ptxconfig".
So, when I change your command to our predefined toolchain config it works:
/usr/local/lib/ptxdist-2013.12.0/bin/ptxdist select ptxconfigs/arm-v7a-linux-gnueabihf_gcc-4.8.3_glibc-2.18_binutils-2.24_kernel-3.12-sanitized.ptxconfig
info: selected ptxconfig:
'ptxconfigs/arm-v7a-linux-gnueabihf_gcc-4.8.3_glibc-2.18_binutils-2.24_kernel-3.12-sanitized.ptxconfig'
Can you send me the "arm-v7a-linux-gnueabihf_gcc-4.8.3_glibc-2.18_binutils-2.24_kernel-3.13.6-sanitized.ptxconfig"
file? Maybe then we are able to find the cause of your trouble.
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 8: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 [this message]
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
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=201403200930.06997.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