mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ryan Barnett <ryanbarnett3@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Using Crosstool-ng Toolchain with PTXDIST
Date: Mon, 19 Sep 2011 08:45:50 -0500	[thread overview]
Message-ID: <CALq67GBSoYDvbCQP82HwhSTtdO7+RD6KJ=YBFaO+covwz8Ug6w@mail.gmail.com> (raw)
In-Reply-To: <4E74DF73.7000008@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 2483 bytes --]

Updated GLIBC on the host machine to a version greater than 2.7 fixed that
error with the toolchain. However, the issue still exists
where ptxdist can't find the sysroot for the toolchain unless I manually
modify the ptxd_make_00-init.sh. What is the reason for searching for the
collect2 folder in order to determine the sysroot folder and isn't there a
better way to look for the sysroot folder?

On Sat, Sep 17, 2011 at 12:57 PM, Marc Kleine-Budde <mkl@pengutronix.de>wrote:

> On 09/16/2011 03:53 PM, Ryan Barnett wrote:
> > Hi,
> >
> > I'm currently trying to use a toolchain that I have compiled with
> > crosstool-ng with ptxdist-2011-07-0 however I have been having some
> problems
> > with ptxdist trying to recognize and use this toolchain.
> >
> > The first problem that I have had is with the following ptxdist script:
> > script/lib/ptxd_make_00-init.sh. It gives me the following error:
> >
> > "ptxdist: error: failed to source lib:
> > /opt/lib/ptxdist-2011.07.0/scripts//lib/ptxd_make_00-init.sh."
> >
> > I have tracked down where this error is coming from and it is on 65 of
> the
> > ptxd_make_00-init.sh because of the sed call that looks for the collect2
> > folder. There isn't a collect2 folder in the toolchain that was compiled.
> So
> > to overcome that error I have made a temporary work around by just
> setting
> > the sysroot folder manually.
> >
> > However, this has led to another problem, when trying to compile I get
> the
> > following error:
> >
> > arm-cortex_a8_linaro4.5-linux-gnueabi-ld: /lib/libc.so.6: version
> > `GLIBC_2.7' not found (required by
> arm-cortex_a8_linaro4.5-linux-gnueabi-ld)
>
> Update your distribution, you need atleast GLIBC_2.7 to run the
> toolchain. Is that toolchain compiled on that host?
>
> > It seems that ptxdist or something is trying to use the host machine's
> GLIBC
> > instead of the cross compiler's sysroot even though I have manually
> > specified it.
>
> Nope - It's about executing the toolchain's linker.
>
> > Could somebody please point me to how I can compile a toolchain with
> > crosstool-ng that can be used with ptxdist? Or point me in the right
> > direction in how I can fix these errors?
>
> cheers, Marc
>
> --
> Pengutronix e.K.                  | Marc Kleine-Budde           |
> Industrial Linux Solutions        | Phone: +49-231-2826-924     |
> Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
> Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |
>
>

[-- Attachment #1.2: Type: text/html, Size: 3138 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2011-09-19 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16 13:53 Ryan Barnett
2011-09-17 17:57 ` Marc Kleine-Budde
2011-09-19 13:45   ` Ryan Barnett [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='CALq67GBSoYDvbCQP82HwhSTtdO7+RD6KJ=YBFaO+covwz8Ug6w@mail.gmail.com' \
    --to=ryanbarnett3@gmail.com \
    --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