mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Schenk, Gavin" <G.Schenk@eckelmann.de>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] ptxdist-2016-06-0 fails in install step if sphinx-build is missing on host
Date: Thu, 23 Jun 2016 08:39:55 +0000	[thread overview]
Message-ID: <D415CD2EC4182C4EAB90A76B7D9F16DC019E5E5FCF@EX-DAG01.eckelmann.group> (raw)

Hi,

thank you for the new release ptxdist and toolchain \o/!

The make install step of ptxdist-2016-06-0 failed on my system, sphinx-build was missing on my host. 
I worked around this by installing the package python-sphinx. 
Now ptxdist builds successfullly on my machine!
 
[schenk:~/projects/ptxdist/ptxdist-2016.06.0] $ sudo make install
building conf and mconf ...
make[1]: Verzeichnis >/var/projects/ptxdist/ptxdist-2016.06.0/scripts/kconfig< wird betreten
make[1]: >conf< ist bereits aktualisiert.
make[1]: >mconf< ist bereits aktualisiert.
make[1]: >nconf< ist bereits aktualisiert.
make[1]: Verzeichnis >/var/projects/ptxdist/ptxdist-2016.06.0/scripts/kconfig< wird verlassen
done.
preparing PTXdist environment ...ln: auf >/home/schenk/projects/ptxdist/ptxdist-2016.06.0/bin/sphinx-build" konnte nicht zugegriffen werden: Zu viele Ebenen aus symbolischen Links
make: *** [environment] Fehler 1

I have no idea how to fix this in ptxdist and cannot contribute a patch, sorry :-(
I would support you with testing if you want.

Best Regards
Gavin

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2016-06-23  8:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23  8:39 Schenk, Gavin [this message]
2016-06-23 20:20 ` 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=D415CD2EC4182C4EAB90A76B7D9F16DC019E5E5FCF@EX-DAG01.eckelmann.group \
    --to=g.schenk@eckelmann.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