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] Building manually fails with unknown libraries
Date: Thu, 26 May 2016 12:02:33 +0200	[thread overview]
Message-ID: <20160526100233.GK30393@pengutronix.de> (raw)
In-Reply-To: <573F6510.9070006@ruediger.engineering>

On Fri, May 20, 2016 at 09:27:12PM +0200, Christoph Rüdiger wrote:
> 
> 
> Am 20.05.16 um 15:44 schrieb Christoph Rüdiger:
> > 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.
> 
> Too quick between two meetings. Forget about it. At the end of the
> chain, make and cmake are calling the wrapper, as they are supposed to do.
> 
> After putting my headphones on and investigating a bit more, I found out
> by accident, that you can just call the build command from the logfile's
> compile stage in an arbitrary shell, except for the ptxdist bash itself.
> 
> That was something I never expected, so I wasted some hours with
> thinking too complicated :-(
> 
> However, I don't know why it is not working when calling from the
> ptxdist bash. Maybe someone here can explain that.

This is strange. I think this should work. What does $PATH look like when
it fails?

Michael


> Hopefully, this post helps someone in the future.
> 
> Enjoy your weekend,
> 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

-- 
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:[~2016-05-26 10:02 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
2016-05-20 19:27     ` Christoph Rüdiger
2016-05-26 10:02       ` Michael Olbrich [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=20160526100233.GK30393@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