public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Brown <david.brown@hesbynett.no>
To: T Rex <sixpalax@gmail.com>, gcc-help@gcc.gnu.org
Subject: Re: Fwd: Problems building gcc
Date: Wed, 7 Feb 2024 09:56:29 +0100	[thread overview]
Message-ID: <1092a0b0-b328-2e33-1265-78c8b0c6309a@hesbynett.no> (raw)
In-Reply-To: <CAGmGLoibkDriSdzmr9OK=pGRcx5WBzCeTtytU5UHob=7jZZ73A@mail.gmail.com>


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



  parent reply	other threads:[~2024-02-07  8:56 UTC|newest]

Thread overview: 6+ 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
2024-02-07  8:56       ` David Brown [this message]
2024-02-07 13:25         ` Fwd: " T Rex

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=1092a0b0-b328-2e33-1265-78c8b0c6309a@hesbynett.no \
    --to=david.brown@hesbynett.no \
    --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).