Re: More record.c build failures

[Hui Zhu <teawater@gmail.com>]

Hi Michael,

We forget some hosts don't support core dump.

I have 2 ideas to handle this issue:
1.  Make the record log don't together with core file.  Then the
record.c will not need gcore.o.
2.  Divide the "record save" cmd out of record.c.  Make gcore.o and
this .o file togther.

What do you think about them?

Thanks,
Hui

On Fri, Oct 23, 2009 at 21:37, Tristan Gingold <gingold@adacore.com> wrote:
>
> On Oct 23, 2009, at 11:46 AM, Pierre Muller wrote:
>
>> record.c is bound to give problems
>> on all targets that do not compile gcore.c
>> source.
>>
>>  gcore.o  is a optional object that
>> is only added to the list of compiled
>> object in the config directory.
>>
>>  Thus it is not possible to
>> use this without some configure test...
>
> For the record (:-), record.c doesn't compile on Darwin because <byteswap.h>
> doesn't exists (nor
> bswap_xx).
>
> For these, maybe you could use bfd_getb64, bfd_getb32 and bfd_getb16 ?
>
> Tristan.
>
>