From: "Uwe Kindler" <ukindler@htwm.de>
To: <ecos-discuss@sources.redhat.com>
Cc: "Andrew Lunn" <andrew@lunn.ch>
Subject: Re: [ECOS] Free BSD ioctl problem (Renesas EDOSK2674)
Date: Thu, 10 Jun 2004 06:04:00 -0000 [thread overview]
Message-ID: <002501c44eb0$f4260700$7e84378d@uwepc> (raw)
Hello Andrew,
just for your information. I have mailed the H8S IOCTL call problem we have
talked about to www.kpitgnutools.com and received the following answer.
------------------------------------------------------
Hi,
Thank you for using the GNUH8 tool chain.
We accept that gcc does not behave as per the documentation in
http://www.gnu.org/software/libc/manual/html_node/Why-Variadic.html#Why%20Va
riadic
We will file a bug report on this to the GCC mailing list.
Regards,
GNU Support.
----------------------------------------------------------
So there is another issue you should keep in mind when offering H8S support
:o(.
As a workaround for my H8S port of eCos I think about making the ioctl
function definition in io.cxx variadic so that it matches the declaration.
Regards, Uwe
eCos port for Renesas H8S family
http://www.htwm.de/ukindler/ecos
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2004-06-10 6:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 6:04 Uwe Kindler [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-04 17:49 Uwe Kindler
2004-06-04 21:09 ` Andrew Lunn
2004-06-05 8:47 ` Uwe Kindler
2004-06-05 12:50 ` Andrew Lunn
2004-06-23 17:18 ` Uwe Kindler
2004-06-23 20:07 ` Andrew Lunn
2004-06-29 20:44 ` Andrew Lunn
2004-06-30 21:21 ` Uwe Kindler
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='002501c44eb0$f4260700$7e84378d@uwepc' \
--to=ukindler@htwm.de \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).