* Error using gcc with trivial-build-system
@ 2022-11-08 10:23 Emmanuel Medernach
2022-11-08 10:45 ` Sergiu Ivanov
2022-11-08 14:10 ` Tobias Geerinckx-Rice
0 siblings, 2 replies; 9+ messages in thread
From: Emmanuel Medernach @ 2022-11-08 10:23 UTC (permalink / raw)
To: help-guix
Hello Guix,
I have a local package with a compile script that
I need to add to our local GUIX packages.
I tried to use trivial-build-system with
gcc-toolchain input, all works well when I compile
it manually in a 'guix shell' but when I try to
define a package I ran into this error:
ld: cannot find crt1.o: No such file or directory
ld: cannot find crti.o: No such file or directory
collect2: error: ld returned 1 exit status
I cannot produce correct binaries with
gcc-toolchain, here is a minimal package
definition with the above problem. Could you
please tell me how to solve this problem ?
(define-public SimpleTest
(package
(name "SimpleTest")
(version "0.0.0")
(source
(origin
(method url-fetch)
(uri ".../simpletest.tgz")
(sha256
(base32 "0nx8dgs5n4s1alp8lnp7a96czdll8bb7ljbg152yk7m0mr07728d"))))
(inputs `(("gcc-toolchain" ,gcc-toolchain-9)
("gzip" ,gzip)
("tar" ,tar)))
(build-system trivial-build-system)
(arguments
`(#:modules
((guix build utils))
#:builder
(begin
(use-modules (guix build utils))
(let* ((source (assoc-ref %build-inputs "source"))
(out (assoc-ref %outputs "out"))
(gzip (assoc-ref %build-inputs "gzip"))
(gunzip-bin (string-append gzip "/bin/gunzip"))
(tar (assoc-ref %build-inputs "tar"))
(tar-bin (string-append tar "/bin/tar"))
(gcc-dir (assoc-ref %build-inputs "gcc-toolchain"))
(gcc-bin (string-append gcc-dir "/bin/gcc")))
(let* ((packages (alist-delete "source" %build-inputs))
(packages-path (map cdr packages)))
(setenv
"PATH"
(apply
string-append
(getenv "PATH") ":"
(map (lambda (p) (string-append p "/bin:"))
packages-path))))
;; (setenv "GCC_EXEC_PREFIX" gcc-dir)
;; gcc: fatal error: cannot execute 'cc1': execvp: No such
file or directory
(display (list "gcc-bin" gcc-bin)) (newline)
(mkdir-p out) (chdir out)
(copy-file source "simpletest.tar.gz")
(invoke gunzip-bin "simpletest.tar.gz")
(invoke tar-bin "xvf" "simpletest.tar")
(delete-file "simpletest.tar")
(chdir "simpletest")
(invoke gcc-bin "simpletest.c" "-o" "simpletest")
#t))))
(synopsis "Simple Test")
(description "Simple Test")
(home-page "None")
(license license:gpl3+)))
Best regards,
Emmanuel Medernach
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Error using gcc with trivial-build-system
2022-11-08 10:23 Error using gcc with trivial-build-system Emmanuel Medernach
@ 2022-11-08 10:45 ` Sergiu Ivanov
2022-11-08 10:58 ` Emmanuel Medernach
2022-11-08 14:10 ` Tobias Geerinckx-Rice
1 sibling, 1 reply; 9+ messages in thread
From: Sergiu Ivanov @ 2022-11-08 10:45 UTC (permalink / raw)
To: Emmanuel Medernach; +Cc: help-guix
Hi,
I have little experience with Guix packages, but I ran into a similar
issue using guix shell --pure recently, and I believe that you need to
add glibc to your dependencies.
I suppose that guix shell works for you because you already have glibc
available in the active profile. I'd expect guix shell --pure to fail
with the same error.
-
HTH,
Sergiu
Emmanuel Medernach <Emmanuel.Medernach@iphc.cnrs.fr> [2022-11-08T11:23:16+0100]:
> Hello Guix,
>
> I have a local package with a compile script that
> I need to add to our local GUIX packages.
>
> I tried to use trivial-build-system with
> gcc-toolchain input, all works well when I compile
> it manually in a 'guix shell' but when I try to
> define a package I ran into this error:
>
> ld: cannot find crt1.o: No such file or directory
> ld: cannot find crti.o: No such file or directory
> collect2: error: ld returned 1 exit status
>
> I cannot produce correct binaries with
> gcc-toolchain, here is a minimal package
> definition with the above problem. Could you
> please tell me how to solve this problem ?
>
> (define-public SimpleTest
> (package
> (name "SimpleTest")
> (version "0.0.0")
> (source
> (origin
> (method url-fetch)
> (uri ".../simpletest.tgz")
> (sha256
> (base32 "0nx8dgs5n4s1alp8lnp7a96czdll8bb7ljbg152yk7m0mr07728d"))))
> (inputs `(("gcc-toolchain" ,gcc-toolchain-9)
> ("gzip" ,gzip)
> ("tar" ,tar)))
> (build-system trivial-build-system)
> (arguments
> `(#:modules
> ((guix build utils))
> #:builder
> (begin
> (use-modules (guix build utils))
>
> (let* ((source (assoc-ref %build-inputs "source"))
> (out (assoc-ref %outputs "out"))
> (gzip (assoc-ref %build-inputs "gzip"))
> (gunzip-bin (string-append gzip "/bin/gunzip"))
> (tar (assoc-ref %build-inputs "tar"))
> (tar-bin (string-append tar "/bin/tar"))
> (gcc-dir (assoc-ref %build-inputs "gcc-toolchain"))
> (gcc-bin (string-append gcc-dir "/bin/gcc")))
>
> (let* ((packages (alist-delete "source" %build-inputs))
> (packages-path (map cdr packages)))
> (setenv
> "PATH"
> (apply
> string-append
> (getenv "PATH") ":"
> (map (lambda (p) (string-append p "/bin:"))
> packages-path))))
>
> ;; (setenv "GCC_EXEC_PREFIX" gcc-dir)
> ;; gcc: fatal error: cannot execute 'cc1': execvp: No such
> file or directory
>
> (display (list "gcc-bin" gcc-bin)) (newline)
>
> (mkdir-p out) (chdir out)
> (copy-file source "simpletest.tar.gz")
> (invoke gunzip-bin "simpletest.tar.gz")
> (invoke tar-bin "xvf" "simpletest.tar")
> (delete-file "simpletest.tar")
> (chdir "simpletest")
> (invoke gcc-bin "simpletest.c" "-o" "simpletest")
>
> #t))))
>
> (synopsis "Simple Test")
> (description "Simple Test")
> (home-page "None")
> (license license:gpl3+)))
>
> Best regards,
>
> Emmanuel Medernach
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Error using gcc with trivial-build-system
2022-11-08 10:45 ` Sergiu Ivanov
@ 2022-11-08 10:58 ` Emmanuel Medernach
2022-11-08 11:39 ` Wojtek Kosior via
0 siblings, 1 reply; 9+ messages in thread
From: Emmanuel Medernach @ 2022-11-08 10:58 UTC (permalink / raw)
To: Sergiu Ivanov; +Cc: help-guix
Le 08/11/2022 à 11:45, Sergiu Ivanov a écrit :
> Hi,
>
> I have little experience with Guix packages, but I ran into a similar
> issue using guix shell --pure recently, and I believe that you need to
> add glibc to your dependencies.
>
> I suppose that guix shell works for you because you already have glibc
> available in the active profile. I'd expect guix shell --pure to fail
> with the same error.
Thanks for your idea but no luck, still the same error with glibc added :-/
Emmanuel
> -
> HTH,
> Sergiu
>
>
> Emmanuel Medernach <Emmanuel.Medernach@iphc.cnrs.fr> [2022-11-08T11:23:16+0100]:
>> Hello Guix,
>>
>> I have a local package with a compile script that
>> I need to add to our local GUIX packages.
>>
>> I tried to use trivial-build-system with
>> gcc-toolchain input, all works well when I compile
>> it manually in a 'guix shell' but when I try to
>> define a package I ran into this error:
>>
>> ld: cannot find crt1.o: No such file or directory
>> ld: cannot find crti.o: No such file or directory
>> collect2: error: ld returned 1 exit status
>>
>> I cannot produce correct binaries with
>> gcc-toolchain, here is a minimal package
>> definition with the above problem. Could you
>> please tell me how to solve this problem ?
>>
>> (define-public SimpleTest
>> (package
>> (name "SimpleTest")
>> (version "0.0.0")
>> (source
>> (origin
>> (method url-fetch)
>> (uri ".../simpletest.tgz")
>> (sha256
>> (base32 "0nx8dgs5n4s1alp8lnp7a96czdll8bb7ljbg152yk7m0mr07728d"))))
>> (inputs `(("gcc-toolchain" ,gcc-toolchain-9)
>> ("gzip" ,gzip)
>> ("tar" ,tar)))
>> (build-system trivial-build-system)
>> (arguments
>> `(#:modules
>> ((guix build utils))
>> #:builder
>> (begin
>> (use-modules (guix build utils))
>>
>> (let* ((source (assoc-ref %build-inputs "source"))
>> (out (assoc-ref %outputs "out"))
>> (gzip (assoc-ref %build-inputs "gzip"))
>> (gunzip-bin (string-append gzip "/bin/gunzip"))
>> (tar (assoc-ref %build-inputs "tar"))
>> (tar-bin (string-append tar "/bin/tar"))
>> (gcc-dir (assoc-ref %build-inputs "gcc-toolchain"))
>> (gcc-bin (string-append gcc-dir "/bin/gcc")))
>>
>> (let* ((packages (alist-delete "source" %build-inputs))
>> (packages-path (map cdr packages)))
>> (setenv
>> "PATH"
>> (apply
>> string-append
>> (getenv "PATH") ":"
>> (map (lambda (p) (string-append p "/bin:"))
>> packages-path))))
>>
>> ;; (setenv "GCC_EXEC_PREFIX" gcc-dir)
>> ;; gcc: fatal error: cannot execute 'cc1': execvp: No such
>> file or directory
>>
>> (display (list "gcc-bin" gcc-bin)) (newline)
>>
>> (mkdir-p out) (chdir out)
>> (copy-file source "simpletest.tar.gz")
>> (invoke gunzip-bin "simpletest.tar.gz")
>> (invoke tar-bin "xvf" "simpletest.tar")
>> (delete-file "simpletest.tar")
>> (chdir "simpletest")
>> (invoke gcc-bin "simpletest.c" "-o" "simpletest")
>>
>> #t))))
>>
>> (synopsis "Simple Test")
>> (description "Simple Test")
>> (home-page "None")
>> (license license:gpl3+)))
>>
>> Best regards,
>>
>> Emmanuel Medernach
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Error using gcc with trivial-build-system
2022-11-08 10:58 ` Emmanuel Medernach
@ 2022-11-08 11:39 ` Wojtek Kosior via
2022-11-08 13:01 ` Emmanuel Medernach
0 siblings, 1 reply; 9+ messages in thread
From: Wojtek Kosior via @ 2022-11-08 11:39 UTC (permalink / raw)
To: Emmanuel Medernach; +Cc: Sergiu Ivanov, help-guix
[-- Attachment #1: Type: text/plain, Size: 5262 bytes --]
> > Hi,
> >
> > I have little experience with Guix packages, but I ran into a similar
> > issue using guix shell --pure recently, and I believe that you need to
> > add glibc to your dependencies.
> >
> > I suppose that guix shell works for you because you already have glibc
> > available in the active profile. I'd expect guix shell --pure to fail
> > with the same error.
>
> Thanks for your idea but no luck, still the same error with glibc added :-/
>
> Emmanuel
Perhaps `find /gnu/store/ -name "crt1.o"` will give further hints?
Good luck!
Wojtek
-- (sig_start)
website: https://koszko.org/koszko.html
PGP: https://koszko.org/key.gpg
fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79 FD1A
Meet Kraków saints! #10: blessed Hilary Januszewski
Poznaj świętych krakowskich! #10: błogosławiony Hilary Januszewski
https://pl.wikipedia.org/wiki/Hilary_Januszewski
-- (sig_end)
On Tue, 8 Nov 2022 11:58:41 +0100
Emmanuel Medernach <Emmanuel.Medernach@iphc.cnrs.fr> wrote:
> Le 08/11/2022 à 11:45, Sergiu Ivanov a écrit :
> > Hi,
> >
> > I have little experience with Guix packages, but I ran into a similar
> > issue using guix shell --pure recently, and I believe that you need to
> > add glibc to your dependencies.
> >
> > I suppose that guix shell works for you because you already have glibc
> > available in the active profile. I'd expect guix shell --pure to fail
> > with the same error.
>
> Thanks for your idea but no luck, still the same error with glibc added :-/
>
> Emmanuel
>
>
> > -
> > HTH,
> > Sergiu
> >
> >
> > Emmanuel Medernach <Emmanuel.Medernach@iphc.cnrs.fr> [2022-11-08T11:23:16+0100]:
> >> Hello Guix,
> >>
> >> I have a local package with a compile script that
> >> I need to add to our local GUIX packages.
> >>
> >> I tried to use trivial-build-system with
> >> gcc-toolchain input, all works well when I compile
> >> it manually in a 'guix shell' but when I try to
> >> define a package I ran into this error:
> >>
> >> ld: cannot find crt1.o: No such file or directory
> >> ld: cannot find crti.o: No such file or directory
> >> collect2: error: ld returned 1 exit status
> >>
> >> I cannot produce correct binaries with
> >> gcc-toolchain, here is a minimal package
> >> definition with the above problem. Could you
> >> please tell me how to solve this problem ?
> >>
> >> (define-public SimpleTest
> >> (package
> >> (name "SimpleTest")
> >> (version "0.0.0")
> >> (source
> >> (origin
> >> (method url-fetch)
> >> (uri ".../simpletest.tgz")
> >> (sha256
> >> (base32 "0nx8dgs5n4s1alp8lnp7a96czdll8bb7ljbg152yk7m0mr07728d"))))
> >> (inputs `(("gcc-toolchain" ,gcc-toolchain-9)
> >> ("gzip" ,gzip)
> >> ("tar" ,tar)))
> >> (build-system trivial-build-system)
> >> (arguments
> >> `(#:modules
> >> ((guix build utils))
> >> #:builder
> >> (begin
> >> (use-modules (guix build utils))
> >>
> >> (let* ((source (assoc-ref %build-inputs "source"))
> >> (out (assoc-ref %outputs "out"))
> >> (gzip (assoc-ref %build-inputs "gzip"))
> >> (gunzip-bin (string-append gzip "/bin/gunzip"))
> >> (tar (assoc-ref %build-inputs "tar"))
> >> (tar-bin (string-append tar "/bin/tar"))
> >> (gcc-dir (assoc-ref %build-inputs "gcc-toolchain"))
> >> (gcc-bin (string-append gcc-dir "/bin/gcc")))
> >>
> >> (let* ((packages (alist-delete "source" %build-inputs))
> >> (packages-path (map cdr packages)))
> >> (setenv
> >> "PATH"
> >> (apply
> >> string-append
> >> (getenv "PATH") ":"
> >> (map (lambda (p) (string-append p "/bin:"))
> >> packages-path))))
> >>
> >> ;; (setenv "GCC_EXEC_PREFIX" gcc-dir)
> >> ;; gcc: fatal error: cannot execute 'cc1': execvp: No such
> >> file or directory
> >>
> >> (display (list "gcc-bin" gcc-bin)) (newline)
> >>
> >> (mkdir-p out) (chdir out)
> >> (copy-file source "simpletest.tar.gz")
> >> (invoke gunzip-bin "simpletest.tar.gz")
> >> (invoke tar-bin "xvf" "simpletest.tar")
> >> (delete-file "simpletest.tar")
> >> (chdir "simpletest")
> >> (invoke gcc-bin "simpletest.c" "-o" "simpletest")
> >>
> >> #t))))
> >>
> >> (synopsis "Simple Test")
> >> (description "Simple Test")
> >> (home-page "None")
> >> (license license:gpl3+)))
> >>
> >> Best regards,
> >>
> >> Emmanuel Medernach
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Error using gcc with trivial-build-system
2022-11-08 11:39 ` Wojtek Kosior via
@ 2022-11-08 13:01 ` Emmanuel Medernach
0 siblings, 0 replies; 9+ messages in thread
From: Emmanuel Medernach @ 2022-11-08 13:01 UTC (permalink / raw)
To: Wojtek Kosior; +Cc: Sergiu Ivanov, help-guix
Le 08/11/2022 à 12:39, Wojtek Kosior a écrit :
>>> Hi,
>>>
>>> I have little experience with Guix packages, but I ran into a similar
>>> issue using guix shell --pure recently, and I believe that you need to
>>> add glibc to your dependencies.
>>>
>>> I suppose that guix shell works for you because you already have glibc
>>> available in the active profile. I'd expect guix shell --pure to fail
>>> with the same error.
>> Thanks for your idea but no luck, still the same error with glibc added :-/
>>
>> Emmanuel
> Perhaps `find /gnu/store/ -name "crt1.o"` will give further hints?
Yes, it is already part of gcc-toolchain (gcc-toolchain-9.4.0/lib/crt1.o)
Adding "-L" flags to gcc does not help
Emmanuel
> Good luck!
>
> Wojtek
>
> -- (sig_start)
> website: https://koszko.org/koszko.html
> PGP: https://koszko.org/key.gpg
> fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79 FD1A
>
> Meet Kraków saints! #10: blessed Hilary Januszewski
> Poznaj świętych krakowskich! #10: błogosławiony Hilary Januszewski
> https://pl.wikipedia.org/wiki/Hilary_Januszewski
> -- (sig_end)
>
>
> On Tue, 8 Nov 2022 11:58:41 +0100
> Emmanuel Medernach <Emmanuel.Medernach@iphc.cnrs.fr> wrote:
>
>> Le 08/11/2022 à 11:45, Sergiu Ivanov a écrit :
>>> Hi,
>>>
>>> I have little experience with Guix packages, but I ran into a similar
>>> issue using guix shell --pure recently, and I believe that you need to
>>> add glibc to your dependencies.
>>>
>>> I suppose that guix shell works for you because you already have glibc
>>> available in the active profile. I'd expect guix shell --pure to fail
>>> with the same error.
>> Thanks for your idea but no luck, still the same error with glibc added :-/
>>
>> Emmanuel
>>
>>
>>> -
>>> HTH,
>>> Sergiu
>>>
>>>
>>> Emmanuel Medernach <Emmanuel.Medernach@iphc.cnrs.fr> [2022-11-08T11:23:16+0100]:
>>>> Hello Guix,
>>>>
>>>> I have a local package with a compile script that
>>>> I need to add to our local GUIX packages.
>>>>
>>>> I tried to use trivial-build-system with
>>>> gcc-toolchain input, all works well when I compile
>>>> it manually in a 'guix shell' but when I try to
>>>> define a package I ran into this error:
>>>>
>>>> ld: cannot find crt1.o: No such file or directory
>>>> ld: cannot find crti.o: No such file or directory
>>>> collect2: error: ld returned 1 exit status
>>>>
>>>> I cannot produce correct binaries with
>>>> gcc-toolchain, here is a minimal package
>>>> definition with the above problem. Could you
>>>> please tell me how to solve this problem ?
>>>>
>>>> (define-public SimpleTest
>>>> (package
>>>> (name "SimpleTest")
>>>> (version "0.0.0")
>>>> (source
>>>> (origin
>>>> (method url-fetch)
>>>> (uri ".../simpletest.tgz")
>>>> (sha256
>>>> (base32 "0nx8dgs5n4s1alp8lnp7a96czdll8bb7ljbg152yk7m0mr07728d"))))
>>>> (inputs `(("gcc-toolchain" ,gcc-toolchain-9)
>>>> ("gzip" ,gzip)
>>>> ("tar" ,tar)))
>>>> (build-system trivial-build-system)
>>>> (arguments
>>>> `(#:modules
>>>> ((guix build utils))
>>>> #:builder
>>>> (begin
>>>> (use-modules (guix build utils))
>>>>
>>>> (let* ((source (assoc-ref %build-inputs "source"))
>>>> (out (assoc-ref %outputs "out"))
>>>> (gzip (assoc-ref %build-inputs "gzip"))
>>>> (gunzip-bin (string-append gzip "/bin/gunzip"))
>>>> (tar (assoc-ref %build-inputs "tar"))
>>>> (tar-bin (string-append tar "/bin/tar"))
>>>> (gcc-dir (assoc-ref %build-inputs "gcc-toolchain"))
>>>> (gcc-bin (string-append gcc-dir "/bin/gcc")))
>>>>
>>>> (let* ((packages (alist-delete "source" %build-inputs))
>>>> (packages-path (map cdr packages)))
>>>> (setenv
>>>> "PATH"
>>>> (apply
>>>> string-append
>>>> (getenv "PATH") ":"
>>>> (map (lambda (p) (string-append p "/bin:"))
>>>> packages-path))))
>>>>
>>>> ;; (setenv "GCC_EXEC_PREFIX" gcc-dir)
>>>> ;; gcc: fatal error: cannot execute 'cc1': execvp: No such
>>>> file or directory
>>>>
>>>> (display (list "gcc-bin" gcc-bin)) (newline)
>>>>
>>>> (mkdir-p out) (chdir out)
>>>> (copy-file source "simpletest.tar.gz")
>>>> (invoke gunzip-bin "simpletest.tar.gz")
>>>> (invoke tar-bin "xvf" "simpletest.tar")
>>>> (delete-file "simpletest.tar")
>>>> (chdir "simpletest")
>>>> (invoke gcc-bin "simpletest.c" "-o" "simpletest")
>>>>
>>>> #t))))
>>>>
>>>> (synopsis "Simple Test")
>>>> (description "Simple Test")
>>>> (home-page "None")
>>>> (license license:gpl3+)))
>>>>
>>>> Best regards,
>>>>
>>>> Emmanuel Medernach
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Error using gcc with trivial-build-system
2022-11-08 10:23 Error using gcc with trivial-build-system Emmanuel Medernach
2022-11-08 10:45 ` Sergiu Ivanov
@ 2022-11-08 14:10 ` Tobias Geerinckx-Rice
2022-11-08 14:48 ` Emmanuel Medernach
1 sibling, 1 reply; 9+ messages in thread
From: Tobias Geerinckx-Rice @ 2022-11-08 14:10 UTC (permalink / raw)
To: Emmanuel Medernach; +Cc: help-guix
Hi Emmanuel!
On 2022-11-08 11:23, Emmanuel Medernach wrote:
> I have a local package with a compile script that
> I need to add to our local GUIX packages.
(Nitpick: Guix isn't a acronym. Never has been.)
> I tried to use trivial-build-system with
> gcc-toolchain input, all works well when I compile
> it manually in a 'guix shell'
Because ‘guix shell’ sets up a proper profile; quite unlike the
trivial-build-system.
Using trivial-build-system here *is* the bug. It's not a starter kit
for building better things; it's for trivial packages that don't need
building.
Rather than waste your time fighting that fact, use the
gnu-build-system. It is that starter kit.
If your tarball doesn't provide some standard GNU things like
./configure or ‘make check’, that's quite common. You can simply
(delete 'configure), set #:tests? #f, etc.
Happy building,
T G-R
Sent from a Web browser. Excuse or enjoy my brevity.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Error using gcc with trivial-build-system
2022-11-08 14:10 ` Tobias Geerinckx-Rice
@ 2022-11-08 14:48 ` Emmanuel Medernach
2022-11-08 21:16 ` zimoun
0 siblings, 1 reply; 9+ messages in thread
From: Emmanuel Medernach @ 2022-11-08 14:48 UTC (permalink / raw)
To: Tobias Geerinckx-Rice; +Cc: help-guix
Le 08/11/2022 à 15:10, Tobias Geerinckx-Rice a écrit :
> Hi Emmanuel!
>
> On 2022-11-08 11:23, Emmanuel Medernach wrote:
>> I have a local package with a compile script that
>> I need to add to our local GUIX packages.
>
> (Nitpick: Guix isn't a acronym. Never has been.)
>
>> I tried to use trivial-build-system with
>> gcc-toolchain input, all works well when I compile
>> it manually in a 'guix shell'
>
> Because ‘guix shell’ sets up a proper profile; quite unlike the
> trivial-build-system.
>
> Using trivial-build-system here *is* the bug. It's not a starter kit
> for building better things; it's for trivial packages that don't need
> building.
>
> Rather than waste your time fighting that fact, use the
> gnu-build-system. It is that starter kit.
>
> If your tarball doesn't provide some standard GNU things like
> ./configure or ‘make check’, that's quite common. You can simply
> (delete 'configure), set #:tests? #f, etc.
>
Thanks for your help, I will use the gnu-build-system and customize it
as you suggest.
About customizing I have another question, at the end of the build I
have messages like:
warning: collision encountered: ...
I would prefer to manage myself what is copied to the profile or what is
not and where, is it possible ?
Emmanuel
> Happy building,
>
> T G-R
>
> Sent from a Web browser. Excuse or enjoy my brevity.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Error using gcc with trivial-build-system
2022-11-08 14:48 ` Emmanuel Medernach
@ 2022-11-08 21:16 ` zimoun
2022-11-09 7:18 ` Emmanuel Medernach
0 siblings, 1 reply; 9+ messages in thread
From: zimoun @ 2022-11-08 21:16 UTC (permalink / raw)
To: Emmanuel Medernach, Tobias Geerinckx-Rice; +Cc: help-guix
Hi,
On Tue, 08 Nov 2022 at 15:48, Emmanuel Medernach <Emmanuel.Medernach@iphc.cnrs.fr> wrote:
> About customizing I have another question, at the end of the build I
> have messages like:
>
> warning: collision encountered: ...
This collision is about? What do you as inputs for your package
definition?
> I would prefer to manage myself what is copied to the profile or what is
> not and where, is it possible ?
You mean skip the automatic references, right?
Cheers,
simon
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Error using gcc with trivial-build-system
2022-11-08 21:16 ` zimoun
@ 2022-11-09 7:18 ` Emmanuel Medernach
0 siblings, 0 replies; 9+ messages in thread
From: Emmanuel Medernach @ 2022-11-09 7:18 UTC (permalink / raw)
To: zimoun, Tobias Geerinckx-Rice; +Cc: help-guix
Le 08/11/2022 à 22:16, zimoun a écrit :
> Hi,
>
> On Tue, 08 Nov 2022 at 15:48, Emmanuel Medernach <Emmanuel.Medernach@iphc.cnrs.fr> wrote:
>
>> About customizing I have another question, at the end of the build I
>> have messages like:
>>
>> warning: collision encountered: ...
> This collision is about? What do you as inputs for your package
> definition?
It is about header files or binaries with the same name coming from my
local package sources, I want to be sure either to only copy the one
needed to the profile or not to copy it if it is only helper binaries.
>
>> I would prefer to manage myself what is copied to the profile or what is
>> not and where, is it possible ?
> You mean skip the automatic references, right?
>
I would like to copy only what has been compiled/installed in some
directories and not other for instance.
Cheers,
Emmanuel
> Cheers,
> simon
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2022-11-09 7:19 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-11-08 10:23 Error using gcc with trivial-build-system Emmanuel Medernach
2022-11-08 10:45 ` Sergiu Ivanov
2022-11-08 10:58 ` Emmanuel Medernach
2022-11-08 11:39 ` Wojtek Kosior via
2022-11-08 13:01 ` Emmanuel Medernach
2022-11-08 14:10 ` Tobias Geerinckx-Rice
2022-11-08 14:48 ` Emmanuel Medernach
2022-11-08 21:16 ` zimoun
2022-11-09 7:18 ` Emmanuel Medernach
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.