This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Gcc on Blue Gene / Q
- From: Kai Ruottu <kai dot ruottu at wippies dot com>
- To: Fatih Ertinaz <fertinaz at gmail dot com>, gcc-help at gcc dot gnu dot org
- Date: Fri, 23 Feb 2018 11:59:58 +0200
- Subject: Re: Gcc on Blue Gene / Q
- Authentication-results: sourceware.org; auth=none
- References: <CAJk3+YVyi_a0sfdg0NCuoaHsG6KfCTmLmZ6T0asVdozc3wo8nA@mail.gmail.com>
Let's try to put some sanity into this case...
Fatih Ertinaz wrote 22.2.2018 klo 0:33:
Configuration flags:
configure --prefix $INSTALLDIR --disable-bootstrap
The required "=" seems to be missing :( From the
'https://gcc.gnu.org/install/configure.html' :
|--prefix=dirname|
Specify the toplevel installation directory. This is the recommended
way to install the tools into a directory other than the default.
The toplevel installation directory defaults to /usr/local.
--with-headers=${SYSROOT}/sys-include \
What on earth is this "native place" for the headers in the native
'powerpc64-bgq-linux' system?
--with-libs=${SYSROOT}/lib \
--with-bin=${SYSROOT}/bin \
--with-sbin=${SYSROOT}/sbin \
And these too?
A normal Linux system has its standard headers natively in
'/usr/include' and its standard libraries
in '/lib' (shared runtime, 32-bit), '/lib64' (shared runtime, 64-bit),
'/usr/lib' and '/usr/lib64' (development
and static libraries). Using a ${SYSROOT} usually means crosscompiling
for some other system than
the native one. One puts the "alien" libraries there and points with
'--with-sysroot=${SYSROOT}' to
them so the crosstools (linker and GCC) will find them there...