public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: T Rex <sixpalax@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Problems building gcc
Date: Wed, 7 Feb 2024 07:33:32 +0000	[thread overview]
Message-ID: <CAH6eHdRHrLcPkKRy=L+6O3sJqA_c-y3bo92d-r0b-91t+3UrpQ@mail.gmail.com> (raw)
In-Reply-To: <CAGmGLoibkDriSdzmr9OK=pGRcx5WBzCeTtytU5UHob=7jZZ73A@mail.gmail.com>

[-- 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
> >
>

  reply	other threads:[~2024-02-07  7:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 17:36 T Rex
2024-02-06 19:22 ` Jonathan Wakely
     [not found]   ` <CAGmGLoh+Pbo9G9=1sDRXyHTV7-_CkPDOw+JWppn1TuVRXnszcA@mail.gmail.com>
2024-02-06 22:35     ` Fwd: " T Rex
2024-02-07  7:33       ` Jonathan Wakely [this message]
2024-02-07  8:56       ` David Brown
2024-02-07 13:25         ` T Rex
  -- strict thread matches above, loose matches on Subject: below --
2016-07-27  8:17 Douglas Houston
2016-07-27  8:22 ` Jonathan Wakely
2016-07-27  8:33   ` Jonathan Wakely
2016-07-27 21:59 ` Brian Drummond
2000-10-20 18:44 Problems building GCC jeisen
2000-07-19  2:17 problems building gcc Helfried Tschemmernegg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH6eHdRHrLcPkKRy=L+6O3sJqA_c-y3bo92d-r0b-91t+3UrpQ@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=sixpalax@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).