RE: Renesas __trap34() system calls broken - possibly on other platforms, too

["Dave Korn" <dave dot korn at artimi dot com>]

On 09 January 2007 16:24, Andrew STUBBS wrote:

> Dave Korn wrote:
>> On 09 January 2007 15:10, Jonas Mark (ST-FIR/ENG1) wrote:
>> 
>>> Sadly, I am locked on a Windows machine so compiling newlib is extremely
>>> painful.
>> 
>>   Huh?  It's usually trivial with cygwin.
> 
> Only with a gcc that understands cygwin pathnames. 

  Yep, that's basically what I meant when I said "with cygwin".  With
/cygwin/.  Not with /something else/.  I imagine MSVC won't find it easy
either ....   ;-)

> The KPIT toolset is mingw based (IFAIK).

  Ah.  Still, that shouldn't necessarily imply a problem; mingw is not djgpp,
and it happily handles posix-style paths.  However, it's not nearly as
complete a posix emulation as cygwin, so there may be some other omission that
causes problems; without more information from Mark, I can't say.
 
> However, unless the problem is that the whole library was not built with
> the -mrenesas option, he only really needs to rebuild the syscalls.c file.

  Agreed, this is totally a mixing-binaries-with-different-ABIs problem.
 
> Either way, he really should be asking KPIT for support for KPIT
> toolset. As I understand it, they will provide a limited amount support
> free of charge.

  Yes, we often get the KPIT guys turning up here and on the crossgcc list,
they're very approachable.  Mark, if you don't hear from them on this list, it
wouldn't be off-topic for you to raise the problem at the crossgcc list as
well.

  

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....