From: Tom Tromey <tromey@redhat.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [no-commit-intention] Naive unnamed fields for main_type [Re: [patch] Fix gdb-gdb.py for flds_bnds copy-pastes]
Date: Fri, 10 Feb 2012 18:07:00 -0000 [thread overview]
Message-ID: <87zkcqd0k3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4F341D1E.3090206@earthlink.net> (Stan Shebs's message of "Thu, 09 Feb 2012 11:23:10 -0800")
>>>>> "Stan" == Stan Shebs <stanshebs@earthlink.net> writes:
Stan> We should at least build with the standard native compiler on our
Stan> supported systems, but should feel free to use whatever flags.
Stan> Did any of the proprietary workstation compilers totally miss the
Stan> C99 boat?
Perhaps people with access to these machines could try it and report
back.
Stan> 3) Libraries/headers. This is probably the most common way that
Stan> people get hosed - their GCC is modern, but library and headers are
Stan> several generations older, and possibly lacking C99-required bits.
I'm not so concerned about this. We already have configure and we can
also import things from gnulib.
Tom
next prev parent reply other threads:[~2012-02-10 18:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 9:28 [patch] Fix gdb-gdb.py for flds_bnds copy-pastes Jan Kratochvil
2012-02-09 9:32 ` [no-commit-intention] Naive unnamed fields for main_type [Re: [patch] Fix gdb-gdb.py for flds_bnds copy-pastes] Jan Kratochvil
2012-02-09 15:16 ` Joel Brobecker
2012-02-09 15:37 ` Jan Kratochvil
2012-02-09 18:56 ` Eli Zaretskii
2012-02-10 18:05 ` Tom Tromey
2012-02-10 19:01 ` Jan Kratochvil
2012-02-10 19:22 ` Tom Tromey
2012-02-10 19:29 ` Jan Kratochvil
2012-02-12 10:20 ` Mark Kettenis
2012-02-12 19:23 ` Jan Kratochvil
2012-02-09 19:07 ` Alfred M. Szmidt
2012-02-09 19:23 ` Stan Shebs
2012-02-10 18:07 ` Tom Tromey [this message]
2012-02-09 15:12 ` [patch] Fix gdb-gdb.py for flds_bnds copy-pastes Joel Brobecker
2012-02-09 15:15 ` [commit] " Jan Kratochvil
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=87zkcqd0k3.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
/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