From: "Matwey V. Kornilov" <matwey.kornilov@gmail.com>
To: libffi-discuss@sourceware.org
Subject: Re: git libffi and gcc
Date: Wed, 21 Sep 2016 09:23:00 -0000 [thread overview]
Message-ID: <CAJs94EYXM8q932_r-o08LjsMMTO-UVw=EgAktui52KEu8SwSnA@mail.gmail.com> (raw)
In-Reply-To: <CAJs94EYtVLyRdUntxpci=fwctMh7bL_UrMDGfkOtHbCXb5UwYQ@mail.gmail.com>
2016-09-19 15:29 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>:
> Hello,
>
> I've found that some gcc/libjava issue was fixed in gcc at libffi merge commit.
> I would like to bisect exact commit it libffi which fixes this issue.
> I am trying to use libffi git with gcc as the following:
>
> cd gcc
> rm -rf libffi
> git clone https://github.com/libffi/libffi
> cd libffi
> git checkout needed_commit
> sh autogen.sh
>
> But then something is broken inside the build framework after it:
>
> make[2]: Entering directory
> '/home/abuild/gcc/obj/armv7hl-suse-linux-gnueabi/libffi'
> depbase=`echo src/prep_cif.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\
> /bin/sh ./libtool --tag=CC --mode=compile
> /home/abuild/gcc/obj/./gcc/xgcc -B/home/abuild/gcc/obj/./gcc/
> -B/usr/armv7hl-suse-linux-gnueabi/bin/
> -B/usr/armv7hl-suse-linux-gnueabi/lib/ -isystem
> /usr/armv7hl-suse-linux-gnueabi/include -isystem
> /usr/armv7hl-suse-linux-gnueabi/sys-include -DHAVE_CONFIG_H -I.
> -I../../../libffi -I. -I../../../libffi/include -Iinclude
> -I../../../libffi/src -O3 -fomit-frame-pointer -fstrict-aliasing
> -ffast-math -Wall -fexceptions -MT src/prep_cif.lo -MD -MP -MF
> $depbase.Tpo -c -o src/prep_cif.lo ../../../libffi/src/prep_cif.c &&\
> mv -f $depbase.Tpo $depbase.Plo
> mv: cannot stat 'src/.deps/prep_cif.Tpo': No such file or directory
> Makefile:1343: recipe for target 'src/prep_cif.lo' failed
> make[2]: *** [src/prep_cif.lo] Error 1
>
> So, what is the correct way to regenerate libffi autoconf/automake
> stuff for using inside gcc build tree?
./configure generates something incomplete for ./libtool
Probably it has to use ltmain.sh from gcc root?
>
> --
> With best regards,
> Matwey V. Kornilov
> http://blog.matwey.name
> xmpp://0x2207@jabber.ru
--
With best regards,
Matwey V. Kornilov
http://blog.matwey.name
xmpp://0x2207@jabber.ru
prev parent reply other threads:[~2016-09-21 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 12:30 Matwey V. Kornilov
2016-09-21 9:23 ` Matwey V. Kornilov [this message]
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='CAJs94EYXM8q932_r-o08LjsMMTO-UVw=EgAktui52KEu8SwSnA@mail.gmail.com' \
--to=matwey.kornilov@gmail.com \
--cc=libffi-discuss@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).