From: Joel Brobecker <brobecker@adacore.com>
To: Peter O'Gorman <gdb-patches@mlists.thewrittenword.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: minor portability patches
Date: Tue, 21 Sep 2010 21:56:00 -0000 [thread overview]
Message-ID: <20100921195922.GB3063@adacore.com> (raw)
In-Reply-To: <20100921194322.GD32745@tw.local>
> Oh sorry. I should have checked. We built python on this platform with
> CC set to "gcc -pthread", so no -lpthread in LIBS etc. and we build gdb
> with MIPSpro C.
Perhaps you should just do the same when building GDB?
--
Joel
next prev parent reply other threads:[~2010-09-21 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 19:59 Peter O'Gorman
2010-09-21 20:06 ` Tom Tromey
2010-09-21 20:40 ` Joel Brobecker
2010-09-21 20:50 ` Peter O'Gorman
2010-09-21 21:56 ` Joel Brobecker [this message]
2010-09-21 21:09 ` Peter O'Gorman
2010-09-22 16:15 ` Doug Evans
2010-09-23 22:03 ` 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=20100921195922.GB3063@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@mlists.thewrittenword.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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