Re: i686-linux GCC package on x86_64

2019-10-16 Thread Alex Kost
Mathieu Othacehe (2019-10-14 16:54 +0200) wrote: > Hey Pierre, > >> --8<---cut here---start->8--- >> (define-public cross-gcc >> (package >> (inherit ((@@ (gnu packages cross-base) cross-gcc) >> "i686-unknown-linux-gnu" >>

Re: i686-linux GCC package on x86_64

2019-10-14 Thread Mathieu Othacehe
Hey Pierre, > --8<---cut here---start->8--- > (define-public cross-gcc > (package > (inherit ((@@ (gnu packages cross-base) cross-gcc) > "i686-unknown-linux-gnu" > #:libc (cross-libc "i686-unknown-linux-gnu"))) > (name

Re: i686-linux GCC package on x86_64

2019-10-14 Thread Jelle Licht
Jelle Licht writes: > Would `guix build cross-gcc-i686-unknown-linux-gnu' work? > My mail reader did not expand your snippet fully, I overlooked the fact that you already overrode the name field. Sorry for the noise!

Re: i686-linux GCC package on x86_64

2019-10-14 Thread Jelle Licht
Pierre Neidhardt writes: >[snip] > --8<---cut here---start->8--- > (define-public cross-gcc > (package > (inherit ((@@ (gnu packages cross-base) cross-gcc) > "i686-unknown-linux-gnu" > #:libc (cross-libc

Re: i686-linux GCC package on x86_64

2019-10-11 Thread Mathieu Othacehe
> Now the only issue is that the libc is placed in a > "/gnu/store/...-gcc-cross-i686-unknown-linux-gnu-5.5.0/i686-unknown-linux-gnu" > subfolder. > I wonder why. How are dependencies supposed to find the libs in there? > > Is it possible to move the libs to the usual "lib" folder at the root?

Re: i686-linux GCC package on x86_64

2019-10-11 Thread Mathieu Othacehe
> This works but cross-gcc only delivers GCC and the libc. > The "lib" output of the regular GCC is missing. > > In particular, I'd need libstdc++.so. Then, that should be fine: --8<---cut here---start->8--- (native-inputs `(,@(if (not

Re: i686-linux GCC package on x86_64

2019-10-10 Thread Ludovic Courtès
Hi, Pierre Neidhardt skribis: > Yes, this is what I had tried. Sadly it works for all packages that I know of > except GCC. Maybe a bug? Oh, there may be confusion as to which GCC you’re targeting. That is, the #:system argument is presumably passed to the “leaf” GCC, but not to the ones

Re: i686-linux GCC package on x86_64

2019-10-10 Thread Pierre Neidhardt
Hi Ludo, Yes, this is what I had tried. Sadly it works for all packages that I know of except GCC. Maybe a bug? -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

Re: i686-linux GCC package on x86_64

2019-10-07 Thread Chris Marusich
Ricardo Wurmus writes: > Chris Marusich writes: > >> That said, I am curious about something. If I want to make a >> cross-compiler available for the purpose of hacking around on some code >> and cross-compiling it, is there an equivalent to "guix package -i >> gcc-toolchain" which will give

Re: i686-linux GCC package on x86_64

2019-10-07 Thread Ricardo Wurmus
Chris Marusich writes: > That said, I am curious about something. If I want to make a > cross-compiler available for the purpose of hacking around on some code > and cross-compiling it, is there an equivalent to "guix package -i > gcc-toolchain" which will give me a cross-compilation

Re: i686-linux GCC package on x86_64

2019-10-07 Thread Ludovic Courtès
Hi Pierre, Pierre Neidhardt skribis: > Pierre Neidhardt writes: > >> Hi! >> >> I'm trying to define an i686-linux package of gcc. >> Simply using the >> >> --8<---cut here---start->8--- >> #:system "i686-linux" >> --8<---cut

Re: i686-linux GCC package on x86_64

2019-10-04 Thread Chris Marusich
Danny Milosavljevic writes: > On Fri, 04 Oct 2019 17:46:43 +0200 > Jelle Licht wrote: > >> Mathieu Othacehe writes: >> >> > >> > --8<---cut here---start->8--- >> > (native-inputs >> > `(,@(if (not (string-prefix? "i686" (%current-system))) >> >

Re: i686-linux GCC package on x86_64

2019-10-04 Thread Danny Milosavljevic
Hi, On Fri, 04 Oct 2019 17:46:43 +0200 Jelle Licht wrote: > Mathieu Othacehe writes: > > > > > --8<---cut here---start->8--- > > (native-inputs > > `(,@(if (not (string-prefix? "i686" (%current-system))) > >`(("cross-gcc" ,(cross-gcc

Re: i686-linux GCC package on x86_64

2019-10-04 Thread Jelle Licht
Mathieu Othacehe writes: > > --8<---cut here---start->8--- > (native-inputs > `(,@(if (not (string-prefix? "i686" (%current-system))) >`(("cross-gcc" ,(cross-gcc "i686-unknown-linux-gnu")) > ("cross-binutils" ,(cross-binutils

Re: i686-linux GCC package on x86_64

2019-10-04 Thread Mathieu Othacehe
> Works for me to, but I'd like to write a package that depends on GCC > i686-linux. You mean a package that uses a compiler able to generate code for i686-linux? In that case you can have a look to (gnu packages firmware), where "cross-gcc" packages are used (ovmf-aarch64 package for

Re: i686-linux GCC package on x86_64

2019-10-04 Thread Mathieu Othacehe
Hello Pierre, >> guix build --system=i686-linux -e '(@@ (gnu packages gcc) gcc)' >> >> produces a hash error.) >> >> Any clue? > > Friendly ping! :) > > Mathieu, I think you've got experience with cross-compilation on Guix, > any clue about this? I think the gcc packages defined in (gnu

Re: i686-linux GCC package on x86_64

2019-10-03 Thread Pierre Neidhardt
Pierre Neidhardt writes: > Hi! > > I'm trying to define an i686-linux package of gcc. > Simply using the > > --8<---cut here---start->8--- > #:system "i686-linux" > --8<---cut here---end--->8--- > > results in a bunch of > >