From: Matthew Stock <stock@csgeeks.org>
To: binutils@sourceware.org
Subject: Issue with cross compile and --64
Date: Tue, 21 Mar 2023 10:55:59 -0400 [thread overview]
Message-ID: <CAJEih4_eK1LOH14NqW=aVi-3msywbMEUQ9ycuqXiuycgh43qoQ@mail.gmail.com> (raw)
Hi folks,
Looking for some guidance from folks on how to resolve a problem I'm
running into. Short version is that I have a custom 32-bit CPU core
with a target for binutils, gcc and newlib target (hobby stuff). I
haven't updated the toolchain in about 9 months or so, and this time
around it failed when building gcc, complaining that my cross-gas
didn't recognize --64:
make[2]: Entering directory '/home/mstock/projects/gnutools/build/gcc/gcc'
g++ -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE
-fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall
-Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute
-Wconditionally-supported -Woverloaded-virtual -pedantic
-Wno-long-long -Wno-variadic-macros -Wno-overlength-strings
-fno-common -DHAVE_CONFIG_H -DGENERATOR_FILE -I. -Ibuild
-I../../../gcc/gcc -I../../../gcc/gcc/build
-I../../../gcc/gcc/../include -I../../../gcc/gcc/../libcpp/include \
-o build/genmodes.o ../../../gcc/gcc/genmodes.cc
/home/mstock/cross/bexkat1-elf/bin/as: unrecognized option '--64'
Host and build are Linux, target is bexkat1-elf (custom).
For this group, my question: is this an issue with my gas port, or
should I be looking at gcc? The intersection of issues here are
unique enough where google hasn't really helped. Thanks for any
suggestions.
Matt
next reply other threads:[~2023-03-21 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 14:55 Matthew Stock [this message]
2023-03-21 15:06 ` Jan Beulich
2023-03-21 15:14 ` Andreas Schwab
2023-03-21 19:32 ` Matthew Stock
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='CAJEih4_eK1LOH14NqW=aVi-3msywbMEUQ9ycuqXiuycgh43qoQ@mail.gmail.com' \
--to=stock@csgeeks.org \
--cc=binutils@sourceware.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).