all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: gtk-doc build failure
Date: Fri, 2 Dec 2016 14:11:04 +0100	[thread overview]
Message-ID: <584172E8.8010708@crazy-compilers.com> (raw)
In-Reply-To: <87twans1pm.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>

Am 01.12.2016 um 23:51 schrieb Marius Bakke:
> I've committed a workaround in 3cc0342b45406f97d675266cc9ac7877be855122.
> […]
> -package_base = r"gnu/store/k6211w9hlqyxvzhrsmh2a113rnzdqlkc-dblatex-0.3.5/share/dblatex"
> +package_base = r"/gnu/store/qx7wx5vhpjs5kgy876xdh2dqr1v5zd39-dblatex-0.3.5/share/dblatex"

Thanks for spotting this. I did not see it when looking there.

The core reasons is that the code for creating the "dblatex" script
strips the root path, which in our case is "/". (dblatex's setup.py
still uses distutils and thus has to create the script by itself. The
feature for creating scripts os one of  setuptools' features.)

So possible solutions are disable setuptools (like you did) of hacking
setup.py. Since dblatex is a program and not a package to be imported,
disabling setuptools is absolutely okay and I would not call it a
workaround but a solution :-)

Are you going to update the comment?

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

      reply	other threads:[~2016-12-02 13:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01 21:01 gtk-doc build failure Marius Bakke
2016-12-01 22:51 ` Marius Bakke
2016-12-02 13:11   ` Hartmut Goebel [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=584172E8.8010708@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.