mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Using external toolchain with penguitronix BSP distribution
Date: Tue, 1 Nov 2011 11:13:27 +0100	[thread overview]
Message-ID: <20111101101327.GA32220@pengutronix.de> (raw)
In-Reply-To: <loom.20111031T002642-163@post.gmane.org>

On Sun, Oct 30, 2011 at 11:57:30PM +0000, muntaqa wrote:
> Hello,
> 
> I am trying to use OSELAS BSP with CodeSourcery toolchain.  
> It seems there is a
> problem in ptxdist and unable to understand the path setup for external
> toolchain using "ptxdist toolchain pathToToolchainBinDir".
> 
> I have performed the following:
> 
> - ptxdist select configs/ptxconfig
> - ptxdist toolchain /home/muntaqa/SourceryARMLinux/bin/
>   this creates the softlink properly in the current directory.  But when I run
> the next command, it won't find toolchain and finds Penguintronix's toolchain
> which is also installed right now in /opt folder.  I had the same issue prior to
> installing the penguitronix toolchain that it would not recognize my
> CodeSourcery toolchain path.  See text below that shows what I have in
> /home/muntaqa/SourceryARMLinux/bin folder.
> -ptxdist platform configs/platform-friendlyarm-mini2440/platformconfig-NAND-128M
>   this command won't find my sourcery toolchain and default to penguitronix's
> toolchain.  Then, I know I need to clear the strings in "ptxdist platformconfig"
> dialogs.  But still, it keeps wanting to find something in /opt.  I have
> modified and cleared gcc version, libc version, binaries prefix such as
> gnuarm-none-linux-eabi. 
> 
> Nothing works, it won't recognize the external toolchain and if I have
> penguitronix's toolchain installed, it would find it otherwise it makes a path
> from the platformconfig items and complains that toolchain does not exist and
> tells me to use ptxdist toolchain command to specify a toolchain path ( but I
> have already done that.)
> 
> I have tried this many times with a clean installation of BSP package in
> different locations.  
> 
> Can someone send me proper instructions on how to get an external toolchain
> configured properly.  I have followed all of the steps in the QuickStart guide
> and they don't work.  I need different instructions that will work.
[...]
> #
> # toolchain                     
> #
> PTXCONF_CROSSCHAIN_VENDOR=""

empty is correct.

> PTXCONF_CROSSCHAIN_CHECK="4.5.2"

this must be the output of "gnuarm-none-linux-eabi-gcc -dumpversion".

This is compared with "${PTXCONF_COMPILER_PREFIX}-gcc -dumpversion".

> PTXCONF_LIBC_GLIBC=y
> # PTXCONF_LIBC_UCLIBC is not set
> PTXCONF_GLIBC_VERSION="2.13"

this is only used for toolchain guessing

> PTXCONF_GNU_TARGET="arm-v4t-linux-gnueabi"

PTXCONF_GNU_TARGET="gnuarm-none-linux-eabi"

> PTXCONF_COMPILER_PREFIX="${PTXCONF_GNU_TARGET}-"
> PTXCONF_COMPILER_PREFIX_KERNEL="${PTXCONF_COMPILER_PREFIX}"
> PTXCONF_COMPILER_PREFIX_BOOTLOADER="${PTXCONF_COMPILER_PREFIX}"



Regards,
Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2011-11-01 10:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-30 23:57 muntaqa
2011-11-01 10:13 ` Michael Olbrich [this message]
2011-11-02  1:39   ` muntaqa
2011-11-02  8:35     ` Juergen Beisert
2011-11-05 13:31       ` muntaqa
2011-11-05 14:54         ` Juergen Beisert
2011-11-15 14:32           ` muntaqa
2011-11-15 14:57             ` Juergen Beisert

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=20111101101327.GA32220@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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