From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Mahmoud, Abdulrahman (DI SW ICS MNA)" <Abdulrahman_Mahmoud@mentor.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Usability of --with-specs option
Date: Sun, 11 Dec 2022 12:04:52 +0000 [thread overview]
Message-ID: <CAH6eHdSDZFBEPWdo+AoYd54ZQfnatJyM-6-9ehTmf+=-GKcx=w@mail.gmail.com> (raw)
In-Reply-To: <8923dbfa73a844ec9356821014f642d7@mentor.com>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
On Sun, 11 Dec 2022, 09:54 Mahmoud, Abdulrahman (DI SW ICS MNA), <
Abdulrahman_Mahmoud@mentor.com> wrote:
> Hi,
>
> I am facing an issue in the GCC on ubuntu 20 as it can't find the crti.o
> and crtn.o during linking.
> The GCC I am using is being built on Redhat6.5 so it searches for the
> missing files in /lib instead of /lib/x86_64-linux-gnu.
>
> I was searching for a way to configure the GCC to include the
> /lib/x86_64-linux-gnu directory in the search dirs while building on
> Redhat6.5.
>
Maybe you're looking for the --enable-multiarch option, but why are you
doing this?
If you want a compiler that works with Ubuntu conventions, build it on
Ubuntu.
I found a configuration option called --with-specs so I was thinking I may
> add this line "%:if-exists-else(crti.o /lib/x86_64-linux-gnu/crti.o)" to
> the --with-specs to be added to Startfile spec name.
>
> Is this possible with some sort of syntax and if it's not, is there any
> other way that I can add the /lib/x86_64-linux-gnu directory to the search
> dirs during the configuration?
>
--enable-multiarch
But I think you're trying to solve the wrong problem.
> I would really appreciate your help.
>
> Thanks,
> Abdulrahman
>
prev parent reply other threads:[~2022-12-11 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 9:52 Mahmoud, Abdulrahman (DI SW ICS MNA)
2022-12-11 12:04 ` Jonathan Wakely [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='CAH6eHdSDZFBEPWdo+AoYd54ZQfnatJyM-6-9ehTmf+=-GKcx=w@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=Abdulrahman_Mahmoud@mentor.com \
--cc=gcc-help@gcc.gnu.org \
/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).