public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: T Rex <sixpalax@gmail.com>
To: David Brown <david.brown@hesbynett.no>
Cc: gcc-help@gcc.gnu.org, Jonathan Wakely <jwakely.gcc@gmail.com>
Subject: Re: Fwd: Problems building gcc
Date: Wed, 7 Feb 2024 08:25:39 -0500	[thread overview]
Message-ID: <CAGmGLoidanBqkipDgxvYg0mTSAuOWwLrc5QWoOOvHb0KzJrLTw@mail.gmail.com> (raw)
In-Reply-To: <1092a0b0-b328-2e33-1265-78c8b0c6309a@hesbynett.no>

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

      reply	other threads:[~2024-02-07 13:26 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       ` Fwd: " David Brown
2024-02-07 13:25         ` T Rex [this message]

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=CAGmGLoidanBqkipDgxvYg0mTSAuOWwLrc5QWoOOvHb0KzJrLTw@mail.gmail.com \
    --to=sixpalax@gmail.com \
    --cc=david.brown@hesbynett.no \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@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).