public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: libgccjit
Date: Sun, 14 Mar 2021 07:52:39 +0100	[thread overview]
Message-ID: <87y2eqmdl4.fsf@Rainer.invalid> (raw)
In-Reply-To: <8735wyol2k.fsf@Rainer.invalid> (Achim Gratz's message of "Sat, 13 Mar 2021 21:28:03 +0100")

Achim Gratz writes:
> That also needs --enable-host-shared and then it dies shortly after
> configure because it can't find libiberty.a in $build_subdir which does
> not exist.  The library itself is already made in the libiberty
> directory, so some sort of install step went missing.  If I drop the
> file there, it then proceeds to want the same thing in yet another
> subdir.  Repeating the exercise gets me one step further after which it
> looks for the same file in a third place…  dropping it there also seems
> to get the compile rolling along, but there is clearly something
> missing, either in configure or with the general handling of the target
> triple.

It removes one of those places and later expects to find libiberty.a
again there (plus for whatever reason can't run "make -j" from that
point on).  Monkey-fixing that and letting it move on finally gets me
to:

/mnt/share/cygpkgs/gcc/gcc.x86_64/build/./prev-gcc/xg++ -B/mnt/share/cygpkgs/gcc/gcc.x86_64/build/./prev-gcc/ -B/usr/x86_64-pc-cygwin/bin/ -nostdinc++ -B/mnt/share/cygpkgs/gcc/gcc.x86_64/build/prev-x86_64-pc-cygwin/libstdc++-v3/src/.libs -B/mnt/share/cygpkgs/gcc/gcc.x86_64/build/prev-x86_64-pc-cygwin/libstdc++-v3/libsupc++/.libs  -I/mnt/share/cygpkgs/gcc/gcc.x86_64/build/prev-x86_64-pc-cygwin/libstdc++-v3/include/x86_64-pc-cygwin  -I/mnt/share/cygpkgs/gcc/gcc.x86_64/build/prev-x86_64-pc-cygwin/libstdc++-v3/include  -I/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/libstdc++-v3/libsupc++ -L/mnt/share/cygpkgs/gcc/gcc.x86_64/build/prev-x86_64-pc-cygwin/libstdc++-v3/src/.libs -L/mnt/share/cygpkgs/gcc/gcc.x86_64/build/prev-x86_64-pc-cygwin/libstdc++-v3/libsupc++/.libs -fno-PIE -c  -DIN_GCC_FRONTEND -g -O2 -fno-checking -gtoggle -DIN_GCC -fPIC    -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-error=format-diag -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings   -DHAVE_CONFIG_H -I. -Ijit -I/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/gcc -I/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/gcc/jit -I/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/gcc/../include -I/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/gcc/../libcpp/include  -I/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/gcc/../libdecnumber -I/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/gcc/../libdecnumber/bid -I../libdecnumber -I/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/gcc/../libbacktrace   -o jit/jit-playback.o -MT jit/jit-playback.o -MMD -MP -MF jit/.deps/jit-playback.TPo /mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/gcc/jit/jit-playback.c
/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/gcc/jit/jit-playback.c: In member function ‘gcc::jit::result* gcc::jit::playback::context::dlopen_built_dso()’:
/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/gcc/jit/jit-playback.c:2652:3: error: ‘dlerror’ was not declared in this scope; did you mean ‘error’?
 2652 |   dlerror ();
      |   ^~~~~~~
      |   error
/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/gcc/jit/jit-playback.c:2655:6: error: ‘RTLD_NOW’ was not declared in this scope
 2655 |      RTLD_NOW | RTLD_LOCAL);
      |      ^~~~~~~~
/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/gcc/jit/jit-playback.c:2655:17: error: ‘RTLD_LOCAL’ was not declared in this scope
 2655 |      RTLD_NOW | RTLD_LOCAL);
      |                 ^~~~~~~~~~
/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/gcc/jit/jit-playback.c:2654:12: error: ‘dlopen’ was not declared in this scope; did you mean ‘open’?
 2654 |   handle = dlopen (m_tempdir->get_path_so_file (),
      |            ^~~~~~
      |            open

I can pile on another kludge to make that compile and eventully it'll
end up linking libgccjit, but the build then stops with an error that is
not so easily skipped.

So no, Cygwin is not one of the targets that libgccjit is intended to
work on yet and needs work.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

  reply	other threads:[~2021-03-14  6:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 17:00 libgccjit Ken Brown
2021-03-11 10:16 ` libgccjit Corinna Vinschen
2021-03-11 16:00   ` libgccjit Jonathan Yong
2021-03-13 20:28     ` libgccjit Achim Gratz
2021-03-14  6:52       ` Achim Gratz [this message]
2021-03-14 14:54         ` libgccjit Jonathan Yong
2021-03-14 16:24           ` libgccjit Achim Gratz
2021-03-14 19:06             ` libgccjit Andy Moreton
2021-03-14 20:22               ` libgccjit Achim Gratz
2021-03-14 21:19                 ` libgccjit Andy Moreton
2021-03-14 20:42             ` libgccjit Achim Gratz
2021-03-11 17:19   ` libgccjit Achim Gratz
2021-04-04 19:45 ` libgccjit Achim Gratz
2021-04-04 20:39   ` libgccjit Ken Brown
2021-04-05 19:01   ` libgccjit Achim Gratz

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=87y2eqmdl4.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin@cygwin.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).