[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Writing recipe for Crypto++, and getting build errors
From: |
Adonay Felipe Nogueira |
Subject: |
Re: Writing recipe for Crypto++, and getting build errors |
Date: |
Thu, 22 Sep 2016 11:49:12 -0300 |
I tried your suggestions, and the unpack phase doesn't seem to be
working as expected. Inspecting **all** the directories created with
--keep-failed shows that the "source" directory wasn't made.
In attachment are the new recipes that I'm using and also the `guix
build` log.
tahoe-lafs.scm
Description: Text Data
guix build.log
Description: Text Data
signature.asc
Description: This is a digitally signed message part
- Writing recipe for Crypto++, and getting build errors, Adonay Felipe Nogueira, 2016/09/21
- Re: Writing recipe for Crypto++, and getting build errors, Ben Woodcroft, 2016/09/21
- Re: Writing recipe for Crypto++, and getting build errors, Ben Woodcroft, 2016/09/21
- Re: Writing recipe for Crypto++, and getting build errors, Ludovic Courtès, 2016/09/26
- Re: Writing recipe for Crypto++, and getting build errors, Adonay Felipe Nogueira, 2016/09/30
- Re: Writing recipe for Crypto++, and getting build errors, Ludovic Courtès, 2016/09/30
- Re: Writing recipe for Crypto++, and getting build errors, Adonay Felipe Nogueira, 2016/09/30