Re: Writing recipe for Crypto++, and getting build errors

Indeed, you're right: I no longer need it. But I decided to test it so that people can make use of the patch you suggested. signature.asc Description: This is a digitally signed message part

Re: Writing recipe for Crypto++, and getting build errors

Adonay Felipe Nogueira skribis: > I have good news: The patch suggested by Ludovic does work. :) > > I did a test with a simple recipe (because I no longer need to deal with > zipbomb itself, since I found the tar.gz generated by their repository, > which luckly isn't a

Re: Writing recipe for Crypto++, and getting build errors

Thank you very much! :) I have good news: The patch suggested by Ludovic does work. :) I did a test with a simple recipe (because I no longer need to deal with zipbomb itself, since I found the tar.gz generated by their repository, which luckly isn't a tarbomb). Now, reverting the patch with

Re: Writing recipe for Crypto++, and getting build errors

On Sat, Oct 15, 2016 at 05:47:01PM -0300, Adonay Felipe Nogueira wrote: > Note: I'm using Guix with other distribution, not GuixSD. > > I was trying to find out what is the "working tree" in my case, and I > decided to investigate "/gnu/store", and I found three possible places > that are

Re: Writing recipe for Crypto++, and getting build errors

Note: I'm using Guix with other distribution, not GuixSD. I was trying to find out what is the "working tree" in my case, and I decided to investigate "/gnu/store", and I found three possible places that are directories: /gnu/store/...-guix-0.11.0-1.4420 /gnu/store/...-guix-latest

Re: Writing recipe for Crypto++, and getting build errors

Hi, Adonay Felipe Nogueira skribis: > Sorry for taking so long to answer. > > How do I use the patch in the source file? > > It seems to refer to some Guix internal, not a package definition. Right, what I posted is a patch for Guix. You can store it in a file and

Re: Writing recipe for Crypto++, and getting build errors

Also, I forgot to tell: I found their Git repository, and that offers the source files in a directory inside a compressed file. signature.asc Description: This is a digitally signed message part

Re: Writing recipe for Crypto++, and getting build errors

I removed the snippet and tried replacing the unpack phase, and that did worked around the problem. Also, I found their Git repository, and that offers the source files in a directory inside a compressed file. signature.asc Description: This is a digitally signed message part

Re: Writing recipe for Crypto++, and getting build errors

Sorry for taking so long to answer. How do I use the patch in the source file? It seems to refer to some Guix internal, not a package definition. Meanwhile, I'll try to take the patch's content and apply it directly to the recipe (although my knowledge is very limited). signature.asc

Re: Writing recipe for Crypto++, and getting build errors

Hello! Adonay Felipe Nogueira skribis: > Archive: /gnu/store/52v106n4y88myk2c8nykymfidq6080ws-cryptopp-5.6.4.zip > inflating: 3way.cpp > inflating: 3way.h [...] >?: 0 [chdir "3way.cpp"] > > ERROR: In procedure chdir: > ERROR:

Re: Writing recipe for Crypto++, and getting build errors

Hi, On 09/23/2016 12:49 AM, Adonay Felipe Nogueira wrote: 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. I believe the problem now is the snippet,

Re: Writing recipe for Crypto++, and getting build errors

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. ;;; GNU Guix ---

Re: Writing recipe for Crypto++, and getting build errors

On 09/22/2016 11:18 AM, Ben Woodcroft wrote: Welcome Adoney, Also, I forgot to say, make sure to remove the "-mtune=native" flag from the gcc calls, and there is no need to set 'gcc' as an input if you are using the gnu-build-system. ben

Re: Writing recipe for Crypto++, and getting build errors

Welcome Adoney, On 09/22/2016 01:24 AM, Adonay Felipe Nogueira wrote: [..] Doing: $ guix build --fallback "cryptopp" ... outputs: # Begin of output starting phase `build' make: *** No rule to make target 'dynamic'. Stop. phase `build' failed after 0.2 seconds builder for

Writing recipe for Crypto++, and getting build errors

Note: I'm not a programmer, the only thing I can understand is basic Guile Scheme and basic Bash scripting. So, I'm not really fit to make changes in the Crypto++'s source files by myself. I'm writing a recipe for Crypto++ and other packages. I'm not a programmer, but I decided to try to