mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Christoph Rüdiger" <christoph@ruediger.engineering>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Building manually fails with unknown libraries
Date: Fri, 20 May 2016 15:44:19 +0200	[thread overview]
Message-ID: <573F14B3.1040603@ruediger.engineering> (raw)
In-Reply-To: <201605201350.14258.jbe@pengutronix.de>

Hi Juergen,

Am 20.05.16 um 13:50 schrieb Juergen Borleis:
> Hi Christoph,
> 
> On Friday 20 May 2016 12:28:46 Christoph Rüdiger wrote:
>> I am trying to build my project manually in the ptxdist environment to
>> start playing around with some diagnostics tools.
>>
>> First of all, the project compiles and links properly when building with
>> ptxdist compile <target>.
>>
>> However, when I enter ptxdist bash and execute the make command from the
>> logfile, including all the explicit environment variables, the linker
>> fails to find libraries. strace shows, that it is only looking in the
>> toolchain's sysroot, but not in the explicitly given sysroot-target (via
>> SYSROOT env variable).
> 
> Does it start the linker from the wrapper directory (e.g. 
> <platform>/sysroot-host/lib/wrapper/) or from the OSELAS.Toolchain directory 
> directly?

How can I check this? The logfile does not show any cd, pushd, or
similar commands. Ptxdist just starts make and sets the working dir with
make's -C command line argument.

I don't know if it makes a difference, but the application is configured
in the rule file as a cmake project without any further settings.


Regards
Christoph

-- 
rüdiger.engineering
Christoph Rüdiger
Düsseldorfer Str. 12
45145 Essen
Germany

phone: +49 201 458 478 58
PGP key: 0xE513B105

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2016-05-20 13:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20 10:28 Christoph Rüdiger
2016-05-20 11:50 ` Juergen Borleis
2016-05-20 13:44   ` Christoph Rüdiger [this message]
2016-05-20 19:27     ` Christoph Rüdiger
2016-05-26 10:02       ` Michael Olbrich

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=573F14B3.1040603@ruediger.engineering \
    --to=christoph@ruediger.engineering \
    --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