Problems building gcc

Problems building gcc

[T Rex]

[-- Attachment #1: Type: text/plain, Size: 760 bytes --]

Good morning everyone,

I am compiling gcc-13.2 with the following configuration,

./configure --disable-multilib --enable-languages=c,c++ --enable-multiarch
--host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
--enable-deterministic-archives --disable-bootstrap --enable-default-pie
--enable-default-ssp --disable-libssp --enable-linker-build-id
--disable-libstdcxx-filesystem-ts --enable-shared
--prefix=/home/runner/work/gcc/gcc/builds

and the process is successful. But when reviewing the include directory, it
is empty, with only the g++ directory and its contents, I would like all
the files necessary for the compiler to be in the folder. I don't know if
it's a configuration error or something additional needs to be done.

(this is a translation)

Re: Problems building gcc

[Jonathan Wakely]

On Tue, 6 Feb 2024 at 17:38, T Rex via Gcc-help <gcc-help@gcc.gnu.org> wrote:
>
> Good morning everyone,
>
> I am compiling gcc-13.2 with the following configuration,
>
> ./configure

Don't run configure in the source directory. See
https://gcc.gnu.org/wiki/InstallingGCC

> --disable-multilib --enable-languages=c,c++ --enable-multiarch
> --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
> --enable-deterministic-archives --disable-bootstrap --enable-default-pie
> --enable-default-ssp --disable-libssp --enable-linker-build-id
> --disable-libstdcxx-filesystem-ts --enable-shared
> --prefix=/home/runner/work/gcc/gcc/builds
>
> and the process is successful. But when reviewing the include directory, it

Which include directory?

> is empty, with only the g++ directory and its contents, I would like all

Do you mean c++ directory?

> the files necessary for the compiler to be in the folder. I don't know if
> it's a configuration error or something additional needs to be done.

Which files are you expecting to be there?

The C library headers are not part of GCC, they are already installed
elsewhere, like /usr/include

And many of GCC's headers will be under
$prefix/lib/gcc/x86_64-pc-linux-gnu/13.2.0/include

Fwd: Problems building gcc

[T Rex]

[-- Attachment #1: Type: text/plain, Size: 1830 bytes --]

Thanks for the reply.

What I need are all the files that are in /usr/include, at the
$prefix/include location. I'm building a package for flatpak and I need
everything that gcc uses and makes it work to be contained in the directory
specified by $prefix. I was thinking about simply copying it from the
system but it seems to me that it's not the right thing to do and maybe it
won't work.

El mar, 6 feb 2024 a la(s) 2:22 p.m., Jonathan Wakely (jwakely.gcc@gmail.com)
escribió:

> On Tue, 6 Feb 2024 at 17:38, T Rex via Gcc-help <gcc-help@gcc.gnu.org>
> wrote:
> >
> > Good morning everyone,
> >
> > I am compiling gcc-13.2 with the following configuration,
> >
> > ./configure
>
> Don't run configure in the source directory. See
> https://gcc.gnu.org/wiki/InstallingGCC
>
> > --disable-multilib --enable-languages=c,c++ --enable-multiarch
> > --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
> > --enable-deterministic-archives --disable-bootstrap --enable-default-pie
> > --enable-default-ssp --disable-libssp --enable-linker-build-id
> > --disable-libstdcxx-filesystem-ts --enable-shared
> > --prefix=/home/runner/work/gcc/gcc/builds
> >
> > and the process is successful. But when reviewing the include directory,
> it
>
> Which include directory?
>
> > is empty, with only the g++ directory and its contents, I would like all
>
> Do you mean c++ directory?
>
> > the files necessary for the compiler to be in the folder. I don't know if
> > it's a configuration error or something additional needs to be done.
>
> Which files are you expecting to be there?
>
> The C library headers are not part of GCC, they are already installed
> elsewhere, like /usr/include
>
> And many of GCC's headers will be under
> $prefix/lib/gcc/x86_64-pc-linux-gnu/13.2.0/include
>

Re: Problems building gcc

[Jonathan Wakely]

[-- Attachment #1: Type: text/plain, Size: 2291 bytes --]

On Tue, 6 Feb 2024, 22:36 T Rex via Gcc-help, <gcc-help@gcc.gnu.org> wrote:

> Thanks for the reply.
>
> What I need are all the files that are in /usr/include, at the
> $prefix/include location. I'm building a package for flatpak and I need
> everything that gcc uses and makes it work to be contained in the directory
> specified by $prefix.


GCC doesn't own or install those headers though. It also uses libc.so.6 and
it doesn't own that either.

A flatpak GCC would need to depend on a runtime that provides those files.
This will be complicated to build.

I was thinking about simply copying it from the
> system but it seems to me that it's not the right thing to do and maybe it
> won't work.
>

Correct, it probably won't.



> El mar, 6 feb 2024 a la(s) 2:22 p.m., Jonathan Wakely (
> jwakely.gcc@gmail.com)
> escribió:
>
> > On Tue, 6 Feb 2024 at 17:38, T Rex via Gcc-help <gcc-help@gcc.gnu.org>
> > wrote:
> > >
> > > Good morning everyone,
> > >
> > > I am compiling gcc-13.2 with the following configuration,
> > >
> > > ./configure
> >
> > Don't run configure in the source directory. See
> > https://gcc.gnu.org/wiki/InstallingGCC
> >
> > > --disable-multilib --enable-languages=c,c++ --enable-multiarch
> > > --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
> > > --enable-deterministic-archives --disable-bootstrap
> --enable-default-pie
> > > --enable-default-ssp --disable-libssp --enable-linker-build-id
> > > --disable-libstdcxx-filesystem-ts --enable-shared
> > > --prefix=/home/runner/work/gcc/gcc/builds
> > >
> > > and the process is successful. But when reviewing the include
> directory,
> > it
> >
> > Which include directory?
> >
> > > is empty, with only the g++ directory and its contents, I would like
> all
> >
> > Do you mean c++ directory?
> >
> > > the files necessary for the compiler to be in the folder. I don't know
> if
> > > it's a configuration error or something additional needs to be done.
> >
> > Which files are you expecting to be there?
> >
> > The C library headers are not part of GCC, they are already installed
> > elsewhere, like /usr/include
> >
> > And many of GCC's headers will be under
> > $prefix/lib/gcc/x86_64-pc-linux-gnu/13.2.0/include
> >
>

Re: Fwd: Problems building gcc

[David Brown]

On 06/02/2024 23:35, T Rex via Gcc-help wrote:
> Thanks for the reply.
> 
> What I need are all the files that are in /usr/include, at the
> $prefix/include location. I'm building a package for flatpak and I need
> everything that gcc uses and makes it work to be contained in the directory
> specified by $prefix. I was thinking about simply copying it from the
> system but it seems to me that it's not the right thing to do and maybe it
> won't work.
> 


Some resources you might find helpful here are :

<https://crosstool-ng.github.io/>
<https://github.com/crazychenz/x-tools>

Although the "crosstools" project was primarily created for building 
cross-compiler toolchains, it works perfectly well when the target 
system is the same as the host system.  The aim is a complete toolchain, 
including include files, library, assembler, linker, compiler, and so 
on.  I've found it useful for making updated static gcc toolchains for 
old Linux systems where the distro toolchains are older, and you don't 
want to face the complications of having a system glibc newer than the 
distro version supports.

David

Re: Fwd: Problems building gcc

[T Rex]

[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]

Thank you very much for the answers, I will continue searching to see what
I can find and what I can do.

El mié, 7 feb 2024 a la(s) 3:56 a.m., David Brown (david.brown@hesbynett.no)
escribió:

>
> On 06/02/2024 23:35, T Rex via Gcc-help wrote:
> > Thanks for the reply.
> >
> > What I need are all the files that are in /usr/include, at the
> > $prefix/include location. I'm building a package for flatpak and I need
> > everything that gcc uses and makes it work to be contained in the
> directory
> > specified by $prefix. I was thinking about simply copying it from the
> > system but it seems to me that it's not the right thing to do and maybe
> it
> > won't work.
> >
>
>
> Some resources you might find helpful here are :
>
> <https://crosstool-ng.github.io/>
> <https://github.com/crazychenz/x-tools>
>
> Although the "crosstools" project was primarily created for building
> cross-compiler toolchains, it works perfectly well when the target
> system is the same as the host system.  The aim is a complete toolchain,
> including include files, library, assembler, linker, compiler, and so
> on.  I've found it useful for making updated static gcc toolchains for
> old Linux systems where the distro toolchains are older, and you don't
> want to face the complications of having a system glibc newer than the
> distro version supports.
>
> David
>
>
>

Problems building gcc

[Douglas Houston]

Hi all,

I'm having some trouble installing the latest gcc (which I need to  
build another program called Gromacs).

I am on Scientific Linux release 6.8 (Carbon) (kernel  
2.6.32-573.3.1.el6.x86_64), trying to install gcc-5.4.0.

After installing the latest gmp, mpfr and mpc, I create a separate  
objdir build/install directory as recommended. In there, as root, I run:


../gcc-5.4.0/configure


Which fails with:


/usr/bin/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status
configure: error: I suspect your system does not have 32-bit  
developement librar
ies (libc and headers). If you have them, rerun configure with  
--enable-multilib
. If you do not have them, and want to build a 64-bit-only compiler,  
rerun confi
gure with --disable-multilib.


So as directed by the output, I try:


../gcc-5.4.0/configure  --disable-multilib


Now it fails with:


checking for x86_64-unknown-linux-gnu-gcc...  
/root/gcc-5.4.0-install/./gcc/xgcc
-B/root/gcc-5.4.0-install/./gcc/  
-B/usr/local/x86_64-unknown-linux-gnu/bin/ -B/u
sr/local/x86_64-unknown-linux-gnu/lib/ -isystem  
/usr/local/x86_64-unknown-linux-
gnu/include -isystem /usr/local/x86_64-unknown-linux-gnu/sys-include
checking for suffix of object files... configure: error: in  
`/root/gcc-5.4.0-ins
tall/x86_64-unknown-linux-gnu/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.


Can anyone suggest what the fix might be? I've looked in config.log as  
the output suggests but can't find any reference to  
x86_64-unknown-linux-gnu-gcc.

cheers,
Doug






-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Re: Problems building gcc

[Jonathan Wakely]

On 27 July 2016 at 08:47, Douglas Houston <dhouston@staffmail.ed.ac.uk> wrote:
> Hi all,
>
> I'm having some trouble installing the latest gcc (which I need to build
> another program called Gromacs).
>
> I am on Scientific Linux release 6.8 (Carbon) (kernel
> 2.6.32-573.3.1.el6.x86_64), trying to install gcc-5.4.0.
>
> After installing the latest gmp, mpfr and mpc, I create a separate objdir
> build/install directory as recommended. In there, as root, I run:
>
>
> ../gcc-5.4.0/configure
>
>
> Which fails with:
>
>
> /usr/bin/ld: crt1.o: No such file: No such file or directory
> collect2: ld returned 1 exit status
> configure: error: I suspect your system does not have 32-bit developement
> librar
> ies (libc and headers). If you have them, rerun configure with
> --enable-multilib
> . If you do not have them, and want to build a 64-bit-only compiler, rerun
> confi
> gure with --disable-multilib.

https://gcc.gnu.org/wiki/FAQ#gnu_stubs-32.h


> So as directed by the output, I try:
>
>
> ../gcc-5.4.0/configure  --disable-multilib
>
>
> Now it fails with:
>
>
> checking for x86_64-unknown-linux-gnu-gcc...
> /root/gcc-5.4.0-install/./gcc/xgcc
> -B/root/gcc-5.4.0-install/./gcc/ -B/usr/local/x86_64-unknown-linux-gnu/bin/
> -B/u
> sr/local/x86_64-unknown-linux-gnu/lib/ -isystem
> /usr/local/x86_64-unknown-linux-
> gnu/include -isystem /usr/local/x86_64-unknown-linux-gnu/sys-include
> checking for suffix of object files... configure: error: in
> `/root/gcc-5.4.0-ins
> tall/x86_64-unknown-linux-gnu/libgcc':
> configure: error: cannot compute suffix of object files: cannot compile
> See `config.log' for more details.

https://gcc.gnu.org/wiki/FAQ#configure_suffix

> Can anyone suggest what the fix might be? I've looked in config.log as the
> output suggests but can't find any reference to
> x86_64-unknown-linux-gnu-gcc.

As it says at https://gcc.gnu.org/wiki/FAQ#configure_suffix, you're
probably looking at the wrong config.log file.

https://gcc.gnu.org/wiki/InstallingGCC might be useful. You've
probably installed gmp, mpfr and mpc awkwardly.

Re: Problems building gcc

[Jonathan Wakely]

On 27 July 2016 at 09:20, Jonathan Wakely wrote:
> On 27 July 2016 at 08:47, Douglas Houston <dhouston@staffmail.ed.ac.uk> wrote:
>> /usr/bin/ld: crt1.o: No such file: No such file or directory
>> collect2: ld returned 1 exit status
>> configure: error: I suspect your system does not have 32-bit developement
>> librar
>> ies (libc and headers). If you have them, rerun configure with
>> --enable-multilib
>> . If you do not have them, and want to build a 64-bit-only compiler, rerun
>> confi
>> gure with --disable-multilib.
>
> https://gcc.gnu.org/wiki/FAQ#gnu_stubs-32.h

P.S. for Scientific Linux the missing package that provides the 32-bit
dev environment is glibc-devel.i686

Re: Problems building gcc

[Brian Drummond]

On Wed, 2016-07-27 at 08:47 +0100, Douglas Houston wrote:
> 
> configure: error: in  
> `/root/gcc-5.4.0-ins
> tall/x86_64-unknown-linux-gnu/libgcc':
> configure: error: cannot compute suffix of object files: cannot
> compile
> See `config.log' for more details.

Note - there are config.log files all over the place ... the way to
read this message is that it is the config.log in the named directory
(path ending in libgcc) which indicates the problem. 

The message could be a little clearer about that.

-- Brian

Problems building GCC

[jeisen]

I've been trying to compile GCC for the past few days without success.
My first attempts were with the 2.95.2 distribution, unmodified. I would
run the set of commands given by instructions (provided below) and the
compilation would proceed smoothly until reaching a certain point in the
build2 section, where it would fail abruptly, stating that "indstream.o"
was not found. After searching for a solution to the problem, I found a
patch on the GCC archives for something that seemed similar to my
problem, a fix to let the compilation work with glibc installed. I
applied the patch, and tried again, but it failed at the same place...
with a different error. Does anyone see if there's anything I can do?

****************************************
The command I've been running to compile
****************************************

mkdir /lfs/usr/src/gcc-build &&
     cd /lfs/usr/src/gcc-build &&
     ../gcc-2.95.2/configure --prefix=/usr \
        --with-gxx-include-dir=/usr/include/g++ \
        --enable-languages=c,c++ --disable-nls &&
     make -e LDFLAGS=-static bootstrap &&
     make prefix=/lfs/usr local_prefix=/lfs/usr/local \
        gxx_include_dir=/lfs/usr/include/g++ install

**************************
The new patch I downloaded
**************************

***************
*** 1,2 ****
--- 1,7 ----
+ 2000-08-22  Rodrigo Barbosa <rodrigob@conectiva.com.br>
+
+  * libio/indstream.cc (indirectbuf::seekoff): Change int ret_val to
+  streampos ret_val for compatibility with glibc 2.1.9X
+
  2000-08-22  Alexandre Oliva  <aoliva@redhat.com>

diff -c2pr gcc/libio/indstream.cc gcc-conectiva/libio/indstream.cc
*** gcc/libio/indstream.cc Tue Aug 22 17:38:46 2000
--- gcc-conectiva/libio/indstream.cc Tue Aug 22 18:05:49 2000
*************** int indirectbuf::uflow()
*** 75,79 ****
  streampos indirectbuf::seekoff(streamoff off, _seek_dir dir, int mode)

  {
!     int ret_val = 0;
      int select = mode == 0 ? (ios::in|ios::out) : mode;
      streambuf *gbuf = (select & ios::in) ? get_stream() :
(streambuf*)NULL;
--- 75,79 ----
  streampos indirectbuf::seekoff(streamoff off, _seek_dir dir, int mode)

  {
!     streampos ret_val = 0;
      int select = mode == 0 ? (ios::in|ios::out) : mode;
      streambuf *gbuf = (select & ios::in) ? get_stream() :
(streambuf*)NULL;
*************** streampos indirectbuf::seekoff(streamoff
*** 92,96 ****
  streampos indirectbuf::seekpos(streampos pos, int mode)
  {
!     int ret_val = EOF;
      int select = mode == 0 ? (ios::in|ios::out) : mode;
      streambuf *gbuf = (select & ios::in) ? get_stream() :
(streambuf*)NULL;
--- 92,96 ----
  streampos indirectbuf::seekpos(streampos pos, int mode)
  {
!     streampos ret_val = EOF;
      int select = mode == 0 ? (ios::in|ios::out) : mode;
      streambuf *gbuf = (select & ios::in) ? get_stream() :
(streambuf*)NULL;

*************************
End of compilation output
*************************
pc-linux-gnu/bin/ -c -g -O2 -I. -I../../../gcc-2.95.2/libio
-D_IO_MTSAFE_IO  ../../../gcc-2.95.2/libio/iogetline.c -o
pic/iogetline.o
/lfs/usr/src/gcc-build/gcc/xgcc -B/lfs/usr/src/gcc-build/gcc/
-B/usr/i586-pc-linux-gnu/bin/ -c -g -O2 -I. -I../../../gcc-2.95.2/libio
-D_IO_MTSAFE_IO ../../../gcc-2.95.2/libio/iogetline.c
rm -rf libio.a
ar rc libio.a iogetline.o
ranlib libio.a
test x"no" != xyes || \
  /lfs/usr/src/gcc-build/gcc/xgcc -B/lfs/usr/src/gcc-build/gcc/
-B/usr/i586-pc-linux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE
-fno-implicit-templates -I. -I../../../gcc-2.95.2/libio -nostdinc++
-D_IO_MTSAFE_IO  ../../../gcc-2.95.2/libio/builtinbuf.cc -o
pic/builtinbuf.o
/lfs/usr/src/gcc-build/gcc/xgcc -B/lfs/usr/src/gcc-build/gcc/
-B/usr/i586-pc-linux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE
-fno-implicit-templates -I. -I../../../gcc-2.95.2/libio -nostdinc++
-D_IO_MTSAFE_IO ../../../gcc-2.95.2/libio/builtinbuf.cc
test x"no" != xyes || \
  /lfs/usr/src/gcc-build/gcc/xgcc -B/lfs/usr/src/gcc-build/gcc/
-B/usr/i586-pc-linux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE
-fno-implicit-templates -I. -I../../../gcc-2.95.2/libio -nostdinc++
-D_IO_MTSAFE_IO  ../../../gcc-2.95.2/libio/filebuf.cc -o pic/filebuf.o
/lfs/usr/src/gcc-build/gcc/xgcc -B/lfs/usr/src/gcc-build/gcc/
-B/usr/i586-pc-linux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE
-fno-implicit-templates -I. -I../../../gcc-2.95.2/libio -nostdinc++
-D_IO_MTSAFE_IO ../../../gcc-2.95.2/libio/filebuf.cc
test x"no" != xyes || \
  /lfs/usr/src/gcc-build/gcc/xgcc -B/lfs/usr/src/gcc-build/gcc/
-B/usr/i586-pc-linux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE
-fno-implicit-templates -I. -I../../../gcc-2.95.2/libio -nostdinc++
-D_IO_MTSAFE_IO  ../../../gcc-2.95.2/libio/fstream.cc -o pic/fstream.o
/lfs/usr/src/gcc-build/gcc/xgcc -B/lfs/usr/src/gcc-build/gcc/
-B/usr/i586-pc-linux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE
-fno-implicit-templates -I. -I../../../gcc-2.95.2/libio -nostdinc++
-D_IO_MTSAFE_IO ../../../gcc-2.95.2/libio/fstream.cc
test x"no" != xyes || \
  /lfs/usr/src/gcc-build/gcc/xgcc -B/lfs/usr/src/gcc-build/gcc/
-B/usr/i586-pinux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE
-fno-implicit-templates. -I../../../gcc-2.95.2/libio -nostdinc++
-D_IO_MTSAFE_IO  ../../../gcc-2.95.ibio/indstream.cc -o pic/indstream.o
/lfs/usr/src/gcc-build/gcc/xgcc -B/lfs/usr/src/gcc-build/gcc/
-B/usr/i586-pc-ux-gnu/bin/ -c -g -O2 -fvtable-thunks -D_GNU_SOURCE
-fno-implicit-templates --I../../../gcc-2.95.2/libio -nostdinc++
-D_IO_MTSAFE_IO ../../../gcc-2.95.2/lo/indstream.cc
../../../gcc-2.95.2/libio/indstream.cc: In method `struct streampos
indirectb:seekoff(long long int, ios::seek_dir, int = 3)':
../../../gcc-2.95.2/libio/indstream.cc:77: conversion from `int' to
non-scalaype `_G_fpos64_t' requested
../../../gcc-2.95.2/libio/indstream.cc:86: no match for `streampos & !=
int'
../../../gcc-2.95.2/libio/indstream.cc: In method `struct streampos
indirectb:seekpos(_G_fpos64_t, int = 3)':
../../../gcc-2.95.2/libio/indstream.cc:94: conversion from `int' to
non-scalaype `_G_fpos64_t' requested
../../../gcc-2.95.2/libio/indstream.cc:103: no match for `streampos & !=
int'make[2]: *** [indstream.o] Error 1
make[2]: Leaving directory
`/lfs/usr/src/gcc-build/i586-pc-linux-gnu/libio'
make[1]: *** [all-target-libio] Error 2
make[1]: Leaving directory `/lfs/usr/src/gcc-build'
make: *** [bootstrap] Error 2

problems building gcc

[Helfried Tschemmernegg]

Hi!
I've been trying to build gcc-2.95.2 with cygwin for more than a week with
many different parameters calling configure. But I get the following error,
when I call make:

toplev.o: In function `main':
/cygdrive/c/xmingw/build/gcc/../../src/gcc-2.95.2/gcc/toplev.c:5462:
undefined reference to `_environ'
collect2: ld returned 1 exit status
make[1]: *** [cc1.exe] Error 1
make[1]: Leaving directory `/cygdrive/c/xmingw/build/gcc'
make: *** [all-gcc] Error 2

What do I do wrong? Please help me.

Thanks in advance
   Helfried

-- 
Sent through GMX FreeMail - http://www.gmx.net