unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: guix-devel@gnu.org
Subject: libffi cannot be installed in user profile in core-updates
Date: Mon, 24 Mar 2014 02:07:10 -0400	[thread overview]
Message-ID: <87ior4ku41.fsf@yeeloong.lan> (raw)

On the Loongson 3A machine, I finished building all the packages from
core-updates that I use in my profile, and then tried installing them.
I got this:

--8<---------------cut here---------------start------------->8---
In /gnu/store/9sqx55rgygyrcyg350cfqwy8wqb4fr69-module-import/guix/build/union.scm:
 226: 1 [loop # #]
In unknown file:
   ?: 0 [mkdir "/gnu/store/c30bsax58scw5qwcnbma16k6z88s1lh3-profile/./include" ...]

ERROR: In procedure mkdir:
ERROR: In procedure mkdir: File exists
builder for `/gnu/store/17w6kggffh79drmmrdnxy1yhgr6p2in5-profile.drv' failed with exit code 1
--8<---------------cut here---------------end--------------->8---

The problem turns out to be that 'libffi' makes 'include' a symlink to
'lib/libffi-3.0.13/include', and union.scm cannot cope with conflicts
between a directory and a symlink.  Therefore, 'libffi' cannot be
installed in any user profile in core-updates (assuming that there's
some other installed package where 'include' is a directory).

This problem was introduced in d43547f12d4eae19845f3bf13a53a050af965063
"gnu: libffi: Leave a copy of headers where libffi.pc expects them."

     Mark

             reply	other threads:[~2014-03-24  6:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24  6:07 Mark H Weaver [this message]
2014-03-24  9:52 ` libffi cannot be installed in user profile in core-updates Sree Harsha Totakura
2014-03-24 13:15   ` Mark H Weaver
2014-03-24 14:15 ` bug#17083: ‘union-build’ does not handle collisions between a leaf and a sub-tree Ludovic Courtès
2014-04-02 21:43   ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ior4ku41.fsf@yeeloong.lan \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).