From: ludovic.courtes@laas.fr (Ludovic Courtès)
Subject: Re: guile-1.8.0 on HP-UX 11.23/IA-64
Date: Thu, 06 Jul 2006 10:44:24 +0200 [thread overview]
Message-ID: <87psgjunpz.fsf@laas.fr> (raw)
In-Reply-To: <20060705214036.GD93949@mail1.thewrittenword.com> (Albert Chin's message of "Wed, 5 Jul 2006 16:40:37 -0500")
Hi,
Albert Chin <guile-devel@mlists.thewrittenword.com> writes:
> I tried compiling guile-1.8.0 on HP-UX 11.23/IA-64 with the HP-UX C
> compiler. It compiles fine on HP-UX 11.23/PA-RISC. On IA-64, it fails:
> cc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I.. -I/opt/TWWfsw/libtool15/include -I/opt/TWWfsw/libgmp42/include -D_REENTRANT -mthreads -g -c environments.c -DPIC -o .libs/libguile_la-environments.o
> cc: warning 901: unknown option: `-hreads': use +help for online documentation.
> "environments.c", line 146: warning #2940-D: missing return statement at end
> of non-void function "scm_environment_ref"
> }
Actually, you don't need `environments.c' (it's currently unused and
undocumented). So one easy way to work around this is to remove
`environments.c' from `Makefile.am', and then re-generate the makefile
(`make Makefile' should do the trick).
When using GCC, these missing return statements are not caught because
`scm_error_environment_unbound ()' and friends are declared with
attribute `noreturn'. As for this:
> "environments.c", line 692: error #2042: operand types are incompatible ("void"
> and "SCM")
> : SCM_SET_CORE_ENVIRONMENT_OBSERVERS (env, rest);
> ^
This could be rewritten with an `if' to avoid this problem, if need be.
Thanks,
Ludovic.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-07-06 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 21:40 guile-1.8.0 on HP-UX 11.23/IA-64 Albert Chin
2006-07-06 8:44 ` Ludovic Courtès [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-07 16:06 Albert Chin
2006-06-12 17:11 ` Steve Ellcey
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87psgjunpz.fsf@laas.fr \
--to=ludovic.courtes@laas.fr \
/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).