From: Zopolis0 <creatorsmithmdt@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Xi Ruoyao <xry111@xry111.site>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Segfault in libjava/prims.cc while compiling gcj
Date: Wed, 18 May 2022 21:16:49 +1000 [thread overview]
Message-ID: <CAEYL+X8XNRGdpy3T-LBsP+W4xcT+GB8Ar8mk83D977TVBBxakg@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdSXqzyskB0UHrLCGzkU2nt1dP9VPQ43V-vg+ACK95H8wQ@mail.gmail.com>
I'm running gcc -shared-libgcc -nostdinc++
-L/home/zopolis4/gcjbuild/x86_64-pc-linux-gnu/32/libstdc++-v3/src
-L/home/zopolis4/gcjbuild/x86_64-pc-linux-gnu/32/libstdc++-v3/src/.libs
-L/home/zopolis4/gcjbuild/x86_64-pc-linux-gnu/32/libstdc++-v3/libsupc++/.libs
-isystem /usr/local/x86_64-pc-linux-gnu/include -isystem
/usr/local/x86_64-pc-linux-gnu/sys-include -fno-checking -m32 -fno-rtti
-fnon-call-exceptions -fdollars-in-identifiers -Wswitch-enum -ffloat-store
-fomit-frame-pointer -Usun -Wextra -Wall -fno-omit-frame-pointer -g -O2
-m32 -MD -MP -fPIC -DPIC -c .libs/prims.ii to compile the .ii file, which I
created with /home/zopolis4/gcjbuild/./gcc/xgcc -shared-libgcc
-B/home/zopolis4/gcjbuild/./gcc -nostdinc++
-L/home/zopolis4/gcjbuild/x86_64-pc-linux-gnu/32/libstdc++-v3/src
-L/home/zopolis4/gcjbuild/x86_64-pc-linux-gnu/32/libstdc++-v3/src/.libs
-L/home/zopolis4/gcjbuild/x86_64-pc-linux-gnu/32/libstdc++-v3/libsupc++/.libs
-B/usr/local/x86_64-pc-linux-gnu/bin/ -B/usr/local/x86_64-pc-linux-gnu/lib/
-isystem /usr/local/x86_64-pc-linux-gnu/include -isystem
/usr/local/x86_64-pc-linux-gnu/sys-include -fno-checking -m32
-DHAVE_CONFIG_H -I. -I../../../../gcj/libjava -I./include -I./gcj
-I../../../../gcj/libjava -Iinclude -I../../../../gcj/libjava/include
-I../../../../gcj/libjava/classpath/include -Iclasspath/include
-I../../../../gcj/libjava/classpath/native/fdlibm
-I../../../../gcj/libjava/../boehm-gc/include -I../boehm-gc/include
-I../../../../gcj/libjava/libltdl
-I../../../../gcj/libjava/.././libjava/../libgcc
-I../../../../gcj/libjava/../zlib
-I../../../../gcj/libjava/../libffi/include -I../libffi/include -fno-rtti
-fnon-call-exceptions -fdollars-in-identifiers -Wswitch-enum
-D_FILE_OFFSET_BITS=64 -ffloat-store -fomit-frame-pointer -Usun -Wextra
-Wall -D_GNU_SOURCE -DPREFIX=\"/usr/local\"
-DTOOLEXECLIBDIR=\"/usr/local/lib/../lib32\" -DJAVA_HOME=\"/usr/local\"
-DBOOT_CLASS_PATH=\"/usr/local/share/java/libgcj-13.0.0.jar\"
-DJAVA_EXT_DIRS=\"/usr/local/share/java/ext\"
-DGCJ_ENDORSED_DIRS=\"/usr/local/share/java/gcj-endorsed\"
-DGCJ_VERSIONED_LIBDIR=\"/usr/local/lib/../lib32/gcj-13.0.0-18\"
-DPATH_SEPARATOR=\":\" -DECJ_JAR_FILE=\"\"
-DLIBGCJ_DEFAULT_DATABASE=\"/usr/local/lib/../lib32/gcj-13.0.0-18/classmap.db\"
-DLIBGCJ_DEFAULT_DATABASE_PATH_TAIL=\"gcj-13.0.0-18/classmap.db\"
-fno-omit-frame-pointer -g -O2 -D_GNU_SOURCE -m32 -MT prims.lo -MD -MP -MF
.deps/prims.Tpo -E ../../../../gcj/libjava/prims.cc -fPIC -DPIC -o
.libs/prims.ii
Attempting to compile that file breaks horribly, mainly on the lack of
declarations for jsize, jint, jboolean and so on.
On Wed, May 18, 2022 at 8:58 PM Jonathan Wakely <jwakely.gcc@gmail.com>
wrote:
> On Wed, 18 May 2022 at 11:45, Zopolis0 wrote:
> >
> > I thought " But "-D...", "-I...", and "-B..." shall be
> > removed." was asking me to remove them.
> >
> > I used -E, I said I produced the file.
>
> Ah I missed that, sorry. I thought you were still trying to produce a .ii
> file.
>
> So then you should be able to compile the .ii file as described. A .ii
> file needs no headers, so removing -I... options shouldn't matter, and
> has already expanded macros, so removing -D... options shouldn't
> matter. And the system g++ knows how to find its own sub-programs, so
> the -B... options would just confuse it.
>
> What command are you actually running to try and compile the .ii file?
>
next prev parent reply other threads:[~2022-05-18 11:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 9:23 Zopolis0
2022-05-18 9:59 ` Xi Ruoyao
2022-05-18 10:38 ` Zopolis0
2022-05-18 10:43 ` Jonathan Wakely
2022-05-18 10:45 ` Zopolis0
2022-05-18 10:57 ` Jonathan Wakely
2022-05-18 11:01 ` Xi Ruoyao
2022-05-18 23:20 ` Zopolis0
2022-05-19 4:32 ` Zopolis0
2022-05-19 8:06 ` Xi Ruoyao
2022-05-20 10:50 ` Zopolis0
2022-05-18 11:16 ` Zopolis0 [this message]
2022-05-19 10:47 ` Florian Weimer
2022-05-19 12:22 ` Zopolis0
2022-05-21 7:12 ` Zopolis0
2022-06-15 7:51 ` Zopolis0
2022-06-17 9:20 ` Zopolis0
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=CAEYL+X8XNRGdpy3T-LBsP+W4xcT+GB8Ar8mk83D977TVBBxakg@mail.gmail.com \
--to=creatorsmithmdt@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=xry111@xry111.site \
/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).