Missing "standard" headers in FC37 arm (aarch64) C/C++ cross-compiler RPMs ??

[ron flory]

Hi- am hopefully missing something dumb/obvious here---

 Am trying to cross-compile for raspberry-pi, but some basic headers appear to be missing,
or not redirecting to 'generics'. 

-----
Install the cross-compiler(s):
    dnf install gcc-aarch64-linux-gnu  gcc-c++-aarch64-linux-gnu

-----
Compile hello_world sample:
    aarch64-linux-gnu-gcc  hello_world.cpp -o hello_world

Results:
hello_world.c:1:10: fatal error: stdio.h: No such file or directory
    1 | #include <stdio.h>
      |          ^~~~~~~~~
compilation terminated.

-----
Hello_world sample consists of:

#include <stdio.h>
#include <stdlib.h>

int main(int argc, char *argv[])
{
        printf("Hello World\n");
        return(0);
}

[stan]

On Thu, 01 Jun 2023 20:29:54 -0000
ron flory via users <users(a)lists.fedoraproject.org&gt; wrote:

>  Results:
>  hello_world.c:1:10: fatal error: stdio.h: No such file or directory
>      1 | #include <stdio.h>
>        |          ^~~~~~~~~
>  compilation terminated.
>  
>  -----
>  Hello_world sample consists of:
>  
>  #include <stdio.h>
>  #include <stdlib.h>
>  
>  int main(int argc, char *argv[])
>  {
>          printf("Hello World\n");
>          return(0);
>  } 
I find at this link 
https://stackoverflow.com/questions/19580758/gcc-fatal-error-stdio-h-no-s...
this comment,
You can see where gcc is looking for header files by doing echo
"#include <bogus.h>" | gcc -v -x c - and examining the search paths. –
Christian Ternus Oct 25, 2013 at 3:53

It is old, and when I tried it, it didn't work.  But it might give you
an idea for things to try.

This also seems relevant,
"it seems implausible that there would be a release which generated
errors upon importing stdio"

Is the file present in /usr/include?  If it is, you could use the -I
option to point there, -I /usr/include, and see if it works.  If it
does, that indicates that it is a problem in the configuration of gcc;
it isn't looking in the system include directory.

[Ron Flory]

On 6/3/23 08:55, stan via users wrote:
>  On Thu, 01 Jun 2023 20:29:54 -0000 ron flory via users 
>  <users(a)lists.fedoraproject.org&gt; wrote:
> > Results: hello_world.c:1:10: fatal error: stdio.h: No such file or 
> > directory 1 | #include <stdio.h> | ^~~~~~~~~ compilation terminated. 
> > ----- Hello_world sample consists of: #include <stdio.h> #include 
> > <stdlib.h> int main(int argc, char *argv[]) { printf("Hello 
> > World\n"); return(0); } 
>  I find at this link 
>
> https://stackoverflow.com/questions/19580758/gcc-fatal-error-stdio-h-no-s...
>
>  comment, You can see where gcc is looking for header files by doing 
>  echo "#include <bogus.h>" | gcc -v -x c - and examining the search 
>  paths. – Christian Ternus Oct 25, 2013 at 3:53 It is old, and when I 
>  tried it, it didn't work. But it might give you an idea for things to 
>  try. This also seems relevant, "it seems implausible that there would 
>  be a release which generated errors upon importing stdio" Is the file 
>  present in /usr/include? If it is, you could use the -I option to 
>  point there, -I /usr/include, and see if it works. If it does, that 
>  indicates that it is a problem in the configuration of gcc; it isn't 
>  looking in the system include directory.  
  it was sloppy of me to assume everybody understood the host is x86-64.

  There are only 3 relevant compiler/binutils RPMs for aarch64 in FC37: 
(excluding other langs/libs)

dnf list all | grep aarch | grep -v "^rust\|^qemu\|^edk2\|^ipxe"
   gcc-aarch64-linux-gnu
   gcc-c++-aarch64-linux-gnu
   binutils-aarch64-linux-gnu

  ...the binutils is automatically installed as a dependency (similar 
deal for the "gcc-arm-linux" sibling).


The (very few) related headers are installed in 
/usr/lib/gcc/aarch64-linux-gnu/12/include/ as confirmed by 1)
   dnf repoquery -l gcc-aarch64-linux-gnu gcc-c++-aarch64-linux-gnu | 
grep /st | grep "\.h$" | sort

and 2) which are not present when the cross-compiler is removed, but are 
present when the cross-compiler is re-installed.

   Having built many cross-compilers over the years, a look at this 
header include directory is very, very sparse, missing the majority of 
our usual .h friends.

   It --may-- be the RPMs were just built 'for successful compilation' 
without running a minimal test suite to confirm the output artifacts are 
functional-  ...maybe.   ( at least a 'hello-world' should be 
cross-compiled to confirm output-artifacts are produced, and for the 
correct target arch )

  If another noarch or arm header-only RPM happens to contain the 
missing headers (which I have not stumbled upon yet), it would be 
helpful for this to be marked a co-dependency so dnf can install it too.

- - -

  As a side note, for reference only, please no flames intended; the 
corresponding two aarch64 gcc/c++ packages for the popular debian-based 
distro beginning with "U" (which shall not be spoken here) does compile 
and link C/C++ programs correctly, which is why I suspect it could be an 
RPM packaging issue.

ron

[Barry]

>  On 4 Jun 2023, at 21:48, Ron Flory via users
> <users(a)lists.fedoraproject.org&gt; wrote:
>  
>   If another noarch or arm header-only RPM happens to contain the missing headers (which I
> have not stumbled upon yet), it would be helpful for this to be marked a co-dependency so
> dnf can install it too. 
I use dnf search to look for the stdio.h and there are no rpms that contain that header.

Try raising a bug against the cross compiler package. Or ask on fedora devel list.
This needs the maintainer to comment.

Barry

[Barry]

>  On 1 Jun 2023, at 21:30, ron flory via users
> <users(a)lists.fedoraproject.org&gt; wrote:
>  
>  Install the cross-compiler(s):
>     dnf install gcc-aarch64-linux-gnu  gcc-c++-aarch64-linux-gnu 
I am not near my fedora to check, but are there more packages with the CRTL devel stuff?
Maybe the output pf this will help?

dnf  search aarch64

Barry

[Jeffrey Walton]

On Thu, Jun 1, 2023 at 4:30 PM ron flory via users
<users(a)lists.fedoraproject.org&gt; wrote:
>  Hi- am hopefully missing something dumb/obvious here---
>
>   Am trying to cross-compile for raspberry-pi, but some basic headers appear to be
> missing, or not redirecting to 'generics'.
>
>  -----
>  Install the cross-compiler(s):
>      dnf install gcc-aarch64-linux-gnu  gcc-c++-aarch64-linux-gnu
>
>  -----
>  Compile hello_world sample:
>      aarch64-linux-gnu-gcc  hello_world.cpp -o hello_world
>
>  Results:
>  hello_world.c:1:10: fatal error: stdio.h: No such file or directory
>      1 | #include <stdio.h>
>        |          ^~~~~~~~~
>  compilation terminated.
>
>  -----
>  Hello_world sample consists of:
>
>  #include <stdio.h>
>  #include <stdlib.h>
>
>  int main(int argc, char *argv[])
>  {
>          printf("Hello World\n");
>          return(0);
>  } 
When cross-compiling, you typically need to setup the tools (for the
cross-compile) and the include and library path (for the
cross-compile). Assuming aarch64-linux-gnu-gcc is the only tool you
need, you are still missing include and library paths.

You can add include and library paths via --isysroot and --sysroot. So
something like:

    AARCH64_INCL="..."
    AARCH64_LIB="..."
    aarch64-linux-gnu-gcc -o hello_world \
        --isysroot="${AARCH64_INCL}" hello_world.cpp \
        --sysroot="${AARCH64_LIB}"

When you are building for the host, like x86_64, stuff is found in
/usr by default, and you don't need to specify --isysroot and
--sysroot.

When building for aarch64, your cross-compile headers will be
somewhere like /usr/aarch64/include, and libraries will be in
/usr/aarch64/lib. So you would use AARCH64_INCL=/usr/aarch64 and
AARCH64_LIB=/usr/aarch64. --isysroot should add the trailing include/
for you, and --sysroot should add the trailing lib/ for you.

In reality, it is usually a little more complex, like when building a
library for Android or iOS. In this case you usually want to set your
tools, too. (Tools like CC, CXX, AR and LD). For an example of scripts
that setup those environments, see
https://github.com/weidai11/cryptopp/blob/master/TestScripts/setenv-andro...
and https://github.com/weidai11/cryptopp/blob/master/TestScripts/setenv-ios.sh
.

Jeff