From: Eli Zaretskii <eliz@gnu.org>
To: Freddie Chopin <freddie_chopin@op.pl>
Cc: gdb@sourceware.org
Subject: Re: Problem with continue/halt
Date: Thu, 26 Jun 2014 16:23:00 -0000 [thread overview]
Message-ID: <837g43prmu.fsf@gnu.org> (raw)
In-Reply-To: <53AC3E90.5090500@op.pl>
> Date: Thu, 26 Jun 2014 17:38:56 +0200
> From: Freddie Chopin <freddie_chopin@op.pl>
>
> W dniu 2014-06-26 17:24, Eli Zaretskii pisze:
> > Are you per chance compiling with LTO? If so, don't.
>
> I'm using the same command as the one which worked fine previously:
>
> > $SRCDIR/$BINUTILS_GDB/configure --build=$BUILD \
> > --host=$HOST_MINGW \
> > --target=$TARGET \
> > --prefix=$INSTALLDIR_MINGW \
> > --infodir=$INSTALLDIR_MINGW_DOC/info \
> > --mandir=$INSTALLDIR_MINGW_DOC/man \
> > --htmldir=$INSTALLDIR_MINGW_DOC/html \
> > --pdfdir=$INSTALLDIR_MINGW_DOC/pdf \
> > --disable-nls \
> > --enable-plugins \
> > --with-sysroot=$INSTALLDIR_MINGW/arm-none-eabi \
> > --disable-sim \
> > --with-python=no \
> > --with-lzma=no \
> > --with-libexpat=$BUILDDIR_MINGW/host-libs/usr \
> > --with-libiconv-prefix=$BUILDDIR_MINGW/host-libs/usr \
> > --with-system-gdbinit=$INSTALLDIR_MINGW/$HOST_MINGW/arm-none-eabi/lib/gdbinit \
> > '--with-gdb-datadir='\''${prefix}'\''/arm-none-eabi/share/gdb' \
> > "--with-pkgversion=$PKGVERSION"
> >
> > make -j$JOBS
>
> So I'm not enabling LTO explicitly, maybe that's enabled by default somehow?
If you add -v to the GCC command line, it will show you what it is
doing.
> BTW - do you mean LTO is the cause for the continue/halt problem or the
> issue of building older versions?
The former, I think.
next prev parent reply other threads:[~2014-06-26 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-21 6:52 Freddie Chopin
2014-06-26 8:44 ` Freddie Chopin
2014-06-26 15:24 ` Eli Zaretskii
2014-06-26 15:39 ` Freddie Chopin
2014-06-26 16:23 ` Eli Zaretskii [this message]
2014-06-27 7:23 ` Freddie Chopin
2014-06-27 8:26 ` Problem with continue/halt - async support Freddie Chopin
2014-06-27 8:35 ` Eli Zaretskii
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=837g43prmu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=freddie_chopin@op.pl \
--cc=gdb@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