From: Glynn Clements <glynn@gclements.plus.com>
To: Shriramana Sharma <samjnaa@gmail.com>
Cc: Linux C Programming List <linux-c-programming@vger.kernel.org>
Subject: Re: Debugging ephemeris code
Date: Wed, 22 Mar 2006 15:39:32 +0000 [thread overview]
Message-ID: <17441.28596.565556.430774@cerise.gclements.plus.com> (raw)
In-Reply-To: <200603220530.21282.samjnaa@gmail.com>
Shriramana Sharma wrote:
> In the LGPL ephcom library (53 KB) available from:
> http://ephemeris.com/software.html do I get an error when using make or
> trying to compile ephcom.c directly:
>
> gcc -g -O2 -c -o ephcom.o ephcom.c
> ephcom.c: In function ^[-F¡ephcom_writebinary_block¢:^[-A
> ephcom.c:1418: error: conflicting types for ^[-F¡ephcom_outdouble¢^[-A
> ephcom.c:1266: error: previous declaration of ^[-F¡ephcom_outdouble¢ was here^[-A
> ephcom.c: At top level:
> ephcom.c:1767: warning: ^[-F¡ephcom_cheby¢ declared inline after being called^[-A
> ephcom.c:1767: warning: previous implicit declaration of ^[-F¡ephcom_cheby¢ was ^[-A
> here
> make: *** [ephcom.o] Error 1
>
> So what shall I do to safely avert this error? (I don't want to mess up things
> so I ask the experts here.)
Change line 1266 from:
double ephcom_outdouble(FILE *, double);
to:
int ephcom_outdouble(FILE *, double);
And report this issue to bugs@ephemeris.com.
The return value is never used anyhow.
--
Glynn Clements <glynn@gclements.plus.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2006-03-22 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 0:00 Debugging ephemeris code Shriramana Sharma
2006-03-22 15:39 ` Glynn Clements [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=17441.28596.565556.430774@cerise.gclements.plus.com \
--to=glynn@gclements.plus.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=samjnaa@gmail.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 NNTP newsgroup(s).