public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Jouk Jansen" <joukj@hrem.nano.tudelft.nl>
To: GCC-HELP@gcc.gnu.org
Subject: Problem creating cross-compiler
Date: Thu, 18 Jun 2020 10:48:57 +0200 (CEST)	[thread overview]
Message-ID: <20061810485711_32800155@hrem.nano.tudelft.nl> (raw)

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.

It does not matter which version of gcc I try, I always get the same error
message (see below). For gcc-10.1.0 II used the configure command showed
below. immediately after that I did run "make" and after some time I got the
error liste below.

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
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
exec: usage: exec [-cl] [-a name] [command [arguments ...]] [redirection ...]
make[2]: *** [Makefile:2722: build/genmodes.o] Error 1
make[2]: Leaving directory '/home2/joukj/public/gcc/gcc-10.1.0/host-x86_64-unkno
wn-linux-gnu/gcc'
make[1]: *** [Makefile:4390: all-gcc] Error 2
make[1]: Leaving directory '/home2/joukj/public/gcc/gcc-10.1.0'
make: *** [Makefile:955: all] Error 2



    regards
       Jouk


Pax, vel iniusta, utilior est quam iustissimum bellum.
    (free after Marcus Tullius Cicero (106 b.Chr.-46 b.Chr.)
     Epistularum ad Atticum 7.1.4.3)


               Touch not the cat bot a glove

>------------------------------------------------------------------------------<

  Jouk Jansen
		 
  joukj@hrem.nano.tudelft.nl

  Technische Universiteit Delft        tttttttttt  uu     uu  ddddddd
  Kavli Institute of Nanoscience       tttttttttt  uu     uu  dd    dd
  Nationaal centrum voor HREM              tt      uu     uu  dd     dd
  Lorentzweg 1                             tt      uu     uu  dd     dd
  2628 CJ Delft                            tt      uu     uu  dd     dd
  Nederland                                tt      uu     uu  dd    dd
  tel. 31-15-2782272                       tt       uuuuuuu   ddddddd

>------------------------------------------------------------------------------<


             reply	other threads:[~2020-06-18  8:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18  8:48 Jouk Jansen [this message]
2020-06-18 10:52 ` Jonathan Wakely
2020-06-18 11:26   ` Kai Ruottu
2020-06-18 11:46     ` Jonathan Wakely
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=20061810485711_32800155@hrem.nano.tudelft.nl \
    --to=joukj@hrem.nano.tudelft.nl \
    --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).