cross-compiler support?

[Igor Gnatenko]

Hi,

I found only one cross-compiler in repos -- arm-none-eabi-gcc-cs

But it doesn't work:
This package is compiled in bootstrap mode and used only to solve circular
build dependency. You don't want to use this package. It's not expected to
work.

In normal circumstances, you should not see bootstrap package in any
released Fedora.

Do I miss something?
-- 
-Igor Gnatenko

[Laura Abbott]

On 12/19/2016 02:59 PM, Igor Gnatenko wrote:
>  Hi,
>  
>  I found only one cross-compiler in repos -- arm-none-eabi-gcc-cs
>  
>  But it doesn't work:
>  This package is compiled in bootstrap mode and used only to solve circular
>  build dependency. You don't want to use this package. It's not expected to
>  work.
>  
>  In normal circumstances, you should not see bootstrap package in any
>  released Fedora.
>  
>  Do I miss something?
>   
Well there is gcc-arm-linux-gnu for example but that's for kernels per
description

$ dnf info gcc-arm-linux-gnu
Installed Packages
Name        : gcc-arm-linux-gnu
Arch        : x86_64
Epoch       : 0
Version     : 6.1.1
Release     : 2.fc24
Size        : 59 M
Repo        : @System
From repo   : updates
Summary     : Cross-build binary utilities for arm-linux-gnu
URL         : http://gcc.gnu.org
License     : GPLv3+ and GPLv3+ with exceptions and GPLv2+ with exceptions and
            : LGPLv2+ and BSD
Description : Cross-build GNU C compiler.
            : 
            : Only building kernels is currently supported.  Support for
            : cross-building user space programs is not currently provided as
            : that would massively multiply the number of packages

[Igor Gnatenko]

On Tue, Dec 20, 2016 at 12:59 AM, Laura Abbott <labbott(a)redhat.com&gt; wrote:
>  On 12/19/2016 02:59 PM, Igor Gnatenko wrote:
> > Hi,
> >
> > I found only one cross-compiler in repos -- arm-none-eabi-gcc-cs
> >
> > But it doesn't work:
> > This package is compiled in bootstrap mode and used only to solve circular
> > build dependency. You don't want to use this package. It's not expected to
> > work.
> >
> > In normal circumstances, you should not see bootstrap package in any
> > released Fedora.
> >
> > Do I miss something?
> >
>
>  Well there is gcc-arm-linux-gnu for example but that's for kernels per
>  description 
Didn't see it before... But looks like it doesn't work either:
/usr/bin/arm-linux-gnu-ld: cannot find crt1.o: No such file or directory
/usr/bin/arm-linux-gnu-ld: cannot find crti.o: No such file or directory
/usr/bin/arm-linux-gnu-ld: cannot find -lc
/usr/bin/arm-linux-gnu-ld: cannot find crtn.o: No such file or directory
>  $ dnf info gcc-arm-linux-gnu
>  Installed Packages
>  Name        : gcc-arm-linux-gnu
>  Arch        : x86_64
>  Epoch       : 0
>  Version     : 6.1.1
>  Release     : 2.fc24
>  Size        : 59 M
>  Repo        : @System
>  From repo   : updates
>  Summary     : Cross-build binary utilities for arm-linux-gnu
>  URL         : http://gcc.gnu.org
>  License     : GPLv3+ and GPLv3+ with exceptions and GPLv2+ with exceptions and
>              : LGPLv2+ and BSD
>  Description : Cross-build GNU C compiler.
>              :
>              : Only building kernels is currently supported.  Support for
>              : cross-building user space programs is not currently provided as
>              : that would massively multiply the number of packages
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org 


-- 
-Igor Gnatenko

[Josh Boyer]

On Mon, Dec 19, 2016 at 7:27 PM, Igor Gnatenko <ignatenko(a)redhat.com&gt; wrote:
>  On Tue, Dec 20, 2016 at 12:59 AM, Laura Abbott
> <labbott(a)redhat.com&gt; wrote:
> > On 12/19/2016 02:59 PM, Igor Gnatenko wrote:
> >> Hi,
> >>
> >> I found only one cross-compiler in repos -- arm-none-eabi-gcc-cs
> >>
> >> But it doesn't work:
> >> This package is compiled in bootstrap mode and used only to solve circular
> >> build dependency. You don't want to use this package. It's not expected
> to
> >> work.
> >>
> >> In normal circumstances, you should not see bootstrap package in any
> >> released Fedora.
> >>
> >> Do I miss something?
> >>
> >
> > Well there is gcc-arm-linux-gnu for example but that's for kernels per
> > description
>  Didn't see it before... But looks like it doesn't work either:
>  /usr/bin/arm-linux-gnu-ld: cannot find crt1.o: No such file or directory
>  /usr/bin/arm-linux-gnu-ld: cannot find crti.o: No such file or directory
>  /usr/bin/arm-linux-gnu-ld: cannot find -lc
>  /usr/bin/arm-linux-gnu-ld: cannot find crtn.o: No such file or directory 
Laura said it only works for kernels.  None of the userspace bits are
built.  Fedora does not allow cross compilation for package builds in
koji, so nobody has bothered to flesh out the rest of the cross
environment.

josh

[Sérgio Basto]

On Ter, 2016-12-20 at 01:27 +0100, Igor Gnatenko wrote:
>  On Tue, Dec 20, 2016 at 12:59 AM, Laura Abbott
> <labbott(a)redhat.com&gt;
>  wrote:
>  > 
>  > On 12/19/2016 02:59 PM, Igor Gnatenko wrote:
>  > > 
>  > > Hi,
>  > > 
>  > > I found only one cross-compiler in repos -- arm-none-eabi-gcc-cs
>  > > 
>  > > But it doesn't work:
>  > > This package is compiled in bootstrap mode and used only to solve
>  > > circular
>  > > build dependency. You don't want to use this package. It's not
>  > > expected to
>  > > work.
>  > > 
>  > > In normal circumstances, you should not see bootstrap package in
>  > > any
>  > > released Fedora.
>  > > 
>  > > Do I miss something?
>  > > 
>  > Well there is gcc-arm-linux-gnu for example but that's for kernels
>  > per
>  > description
>  Didn't see it before... But looks like it doesn't work either:
>  /usr/bin/arm-linux-gnu-ld: cannot find crt1.o: No such file or
>  directory
>  /usr/bin/arm-linux-gnu-ld: cannot find crti.o: No such file or
>  directory
>  /usr/bin/arm-linux-gnu-ld: cannot find -lc
>  /usr/bin/arm-linux-gnu-ld: cannot find crtn.o: No such file or
>  directory 

I don't know if it helps, in copr I used packages from lantw44 to cross
compile to arm and worked. 

https://copr.fedorainfracloud.org/coprs/lantw44/arm-linux-gnueabi-toolcha...

>  > 
>  > $ dnf info gcc-arm-linux-gnu
>  > Installed Packages
>  > Name        : gcc-arm-linux-gnu
>  > Arch        : x86_64
>  > Epoch       : 0
>  > Version     : 6.1.1
>  > Release     : 2.fc24
>  > Size        : 59 M
>  > Repo        : @System
>  > From repo   : updates
>  > Summary     : Cross-build binary utilities for arm-linux-gnu
>  > URL         : http://gcc.gnu.org
>  > License     : GPLv3+ and GPLv3+ with exceptions and GPLv2+ with
>  > exceptions and
>  >             : LGPLv2+ and BSD
>  > Description : Cross-build GNU C compiler.
>  >             :
>  >             : Only building kernels is currently
>  > supported.  Support for
>  >             : cross-building user space programs is not currently
>  > provided as
>  >             : that would massively multiply the number of packages
>  > _______________________________________________
>  > devel mailing list -- devel(a)lists.fedoraproject.org
>  > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  
>   
-- 
Sérgio M. B.

[David Howells]

Igor Gnatenko <ignatenko(a)redhat.com&gt; wrote:

>  > Well there is gcc-arm-linux-gnu for example but that's for
> kernels per
>  > description
>  Didn't see it before... But looks like it doesn't work either:
>  /usr/bin/arm-linux-gnu-ld: cannot find crt1.o: No such file or directory
>  /usr/bin/arm-linux-gnu-ld: cannot find crti.o: No such file or directory
>  /usr/bin/arm-linux-gnu-ld: cannot find -lc
>  /usr/bin/arm-linux-gnu-ld: cannot find crtn.o: No such file or directory 
Yeah - it's intended for building kernels (though it can build anything that
provides its own userspace).

There are a number of reasons I *don't* provide userspaces:

 (0) I build cross-compilers for 20-ish arches (note that not all kernel
     arches are actually supported by upstream gcc and binutils).

 (1) No single upstream C library supports all the arches I can build a
     cross-compiler for, so I would have to include multiple C libraries in
     the SRPM and build some arches differently to others.  Some I won't be
     able to bootstrap at all without an old or hacked version of a C library.

 (2) Do I bootstrap-build a single config for each arch or several configs?
     What one or ones do I pick?  Note that not all configs of a single arch
     are necessarily supported by the same C library (consider MMU vs NOMMU).
     Further note that each bootstrap increases the build footprint and
     installation footprint - and at some point the package will become
     unbuildable.

IMHO, it shouldn't be necessary for the compiler to know anything about the C
library...

David

[Gerd Hoffmann]

On Di, 2016-12-20 at 09:28 +0000, David Howells wrote:
>  Igor Gnatenko <ignatenko(a)redhat.com&gt; wrote:
>  
>  > > Well there is gcc-arm-linux-gnu for example but that's for kernels per
>  > > description
>  > Didn't see it before... But looks like it doesn't work either:
>  > /usr/bin/arm-linux-gnu-ld: cannot find crt1.o: No such file or directory
>  > /usr/bin/arm-linux-gnu-ld: cannot find crti.o: No such file or directory
>  > /usr/bin/arm-linux-gnu-ld: cannot find -lc
>  > /usr/bin/arm-linux-gnu-ld: cannot find crtn.o: No such file or directory
>  
>  Yeah - it's intended for building kernels (though it can build anything that
>  provides its own userspace). 
FYI: they also work great for building qemu firmware.

cheers,
  Gerd

[Eric Smith]

On Mon, Dec 19, 2016 at 3:59 PM, Igor Gnatenko <ignatenko(a)redhat.com&gt; wrote:

>  I found only one cross-compiler in repos -- arm-none-eabi-gcc-cs
>
>  But it doesn't work: 
This package is compiled in bootstrap mode and used only to solve circular
>  build dependency. You don't want to use this package. It's
> not expected to
>  work.
>  
I've used that package a lot for cross-development for ARM targets,
especially Cortex-M3 microcontrollers. It's intended for bare-metal
targets, not targets running Linux. I've never had any problem with it that
has anything to do with "bootstrap mode".  In fact, for a cross-compiler,
"bootstrap mode" is the only mode there is, because the normal
bootstrapping process for a native compiler (build new compiler using old
compiler, then build new compiler using new compiler) is completely
inapplicable.

[Kalev Lember]

On 12/19/2016 11:59 PM, Igor Gnatenko wrote:
>  Hi,
>  
>  I found only one cross-compiler in repos -- arm-none-eabi-gcc-cs 
There's also two mingw cross compilers: mingw32-gcc and mingw64-gcc. Not
sure if that's what you were looking for :)

-- 
Kalev