Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andreas Tobler <andreast-list@fgznet.ch>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sourceware.org
Subject: Re: powerpc port question
Date: Wed, 09 Sep 2009 19:55:00 -0000	[thread overview]
Message-ID: <4AA8082D.805@fgznet.ch> (raw)
In-Reply-To: <200909091930.n89JUVe9019544@brahms.sibelius.xs4all.nl>

Mark Kettenis wrote:
>> Date: Wed, 09 Sep 2009 21:14:43 +0200
>> From: Andreas Tobler <andreast-list@fgznet.ch>
>>
>> But now I hunt for this:
>> with my built gdb 'show endian' shows this:
>>
>> (gdb) show endian
>> The target is assumed to be big endian
>>
>> On my linuxppc machine I see this:
>>
>> (gdb) show endian
>> The target endianness is set automatically (currently big endian)
>>
>> The reason I'm not satisfied is, that inside the testsuite it looks 
>> exactly for the automatically set endianness string. (altivec tests).
>>
>> I still wonder what my port lacks to spit out the same message as 
>> powerpc linux does?
> 
> I get the same message on OpenBSD that you're seeing on Linux.  And I
> don't think I do something special on OpenBSD to get that behaviour.
> The problem may very well lie in how you've configured BFD.

Hm, I did nothing special there:

[wolfram:~/gdb-6.6-build] andreast% ./config.status --recheck
/home/andreast/gdb-6.6/configure  --prefix=/home/andreast/gdb/testbin 
--disable-nls --with-libiconv-prefix=/usr/local

May I miss some stuff for fbsd in bfd?

The build itself is done outside the source-tree.

Thanks!
Andreas



      reply	other threads:[~2009-09-09 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 18:26 Andreas Tobler
2009-09-09 18:50 ` Mark Kettenis
2009-09-09 19:14   ` Andreas Tobler
2009-09-09 19:30     ` Mark Kettenis
2009-09-09 19:55       ` Andreas Tobler [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=4AA8082D.805@fgznet.ch \
    --to=andreast-list@fgznet.ch \
    --cc=gdb@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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