From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Kai Ruottu <kai.ruottu@wippies.com>
Cc: Jouk Jansen <joukj@hrem.nano.tudelft.nl>,
gcc-help <GCC-HELP@gcc.gnu.org>
Subject: Re: Problem creating cross-compiler
Date: Thu, 18 Jun 2020 12:46:06 +0100 [thread overview]
Message-ID: <CAH6eHdTHsqDjJvURaO6GbYfn8vnQSHEmsTrqrFP4ZNu2kJbuoA@mail.gmail.com> (raw)
In-Reply-To: <7d23ba40-85d9-497c-6d54-abeed4e62937@wippies.com>
On Thu, 18 Jun 2020 at 12:26, Kai Ruottu <kai.ruottu@wippies.com> wrote:
>
> Jonathan Wakely via Gcc-help kirjoitti 18.6.2020 klo 13.52:
> > On Thu, 18 Jun 2020 at 09:59, Jouk Jansen via Gcc-help
> > <gcc-help@gcc.gnu.org> wrote:
> >> Hi,
> >>
> >> I'm trying to build a cross-compiler which should be running on a Fedora 32
> >> system building objects for a IA64-OpenVMS system. I'm running the
> >> compilation on a "up-to-date" Fedora 32 system.
> >>
> >> What do I do wrong?
> >>
> >> ./configure --prefix=/home/joukj/openvms --exec-prefix=/home/joukj/openvms --build=x86_64-unknown-linux-gnu --host=x86_64-unknown-linux-gnu --target=ia64-hp-openvms
> > Don't run configure in the source tree, see
> > https://gcc.gnu.org/wiki/InstallingGCC
> >
> >
> >> make
> >>
> >>
> >> ...
> >> g++ -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtt
> >> i -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qu
> >> al -Wno-error=format-diag -Wmissing-format-attribute -Woverloaded-virtual -pedan
> >> tic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_
> >> H -DGENERATOR_FILE -fno-PIE -I. -Ibuild -I../.././gcc -I../.././gcc/build -I../
> >> .././gcc/../include -I../.././gcc/../libcpp/include \
> >> -o build/genmodes.o ../.././gcc/genmodes.c
> >> ./as: line 106: exec: -I: invalid option
> > This means you don't have an assembler for the cross target.
>
> I would guess this coming somehow from configuring in the source
> directory. The 'genmodes'
> executable is produced for the BUILD system so the 'as' required here
> would be the native one.
> The './as' script is somehow broken.
And the way it's broken is that one of the variables like
ORIGINAL_AS_FOR_TARGET is empty, meaning that trying to exec it fails.
And the usual way that happens is that the assembler (or linker, or
nm) is not found during configure.
Look in the gcc/as script in the build tree, and see if
ORIGINAL_AS_FOR_TARGET is set correctly. If not, look at the logs
generated by the configure step (probably the gcc/config.log one) and
look for the results related to the assembler.
next prev parent reply other threads:[~2020-06-18 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 8:48 Jouk Jansen
2020-06-18 10:52 ` Jonathan Wakely
2020-06-18 11:26 ` Kai Ruottu
2020-06-18 11:46 ` Jonathan Wakely [this message]
2020-06-18 11:52 ` Kai Ruottu
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=CAH6eHdTHsqDjJvURaO6GbYfn8vnQSHEmsTrqrFP4ZNu2kJbuoA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=GCC-HELP@gcc.gnu.org \
--cc=joukj@hrem.nano.tudelft.nl \
--cc=kai.ruottu@wippies.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).