unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Cc: hrvoje.niksic@avl.com, guile-devel@gnu.org
Subject: Re: Building Guile on IA64 HPUX
Date: Thu, 02 Nov 2006 21:15:23 +0000	[thread overview]
Message-ID: <873b91czys.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <200611012157.NAA20914@hpsje.cup.hp.com> (Steve Ellcey's message of "Wed, 1 Nov 2006 13:57:57 -0800 (PST)")

Steve Ellcey <sje@hpsje.cup.hp.com> writes:

> I have downloaded the latest guile sources
> (guile-core.unstable-20060828.tar.gz) and am trying to build them on an
> HP-UX 11.23 system with GCC and the HP C compiler.  So far neither has
> built.

As Hrvoje has said, there have been some significant changes since
that date, so you might have more luck with latest CVS.

> HP C compiler:
> -------------
>
> The compiler is being passed the '-mthreads' which is not an HP C option
> but a GCC option, it should use -mt for multi-threaded compiles with HP
> C.

That's frustrating.  Surely this is a libtool-determined detail, so is
the problem that we're not using the right libtool, or do libtool
builds fail for all free software tarballs when building with the HP C
compiler?


>  The compile of libguile/environments.c has several warnings and an
> error:

I think we should just remove environments.c from the build, as it
isn't even used yet, and only causes us problems.  I've just done this
in CVS HEAD, and will do so in the branches also if no one objects.

> The error seems to be complaining about different return types for the
> macro expressions SCM_SET_CORE_ENVIRONMENT_WEAK_OBSERVERS and
> SCM_SET_CORE_ENVIRONMENT_OBSERVERS.
> SCM_SET_CORE_ENVIRONMENT_WEAK_OBSERVERS expands to scm_c_vector_set_x
> which is a void routine and SCM_SET_CORE_ENVIRONMENT_OBSERVERS expands
> to an assignment expression with an SCM type.
>
> I am not sure which type should be changed.

I just don't think this is worth worrying about, until we decide
_really_ to plumb environments.[ch] into the rest of libguile.

>
> GCC Compiler (prerelease 4.2)
> -----------------------------
>
> With GCC I died in continuations.c:
>
> /tmp/guile/guile-core.unstable-20060828/libguile/continuations.c: In function 'scm_make_continuation':
> /tmp/guile/guile-core.unstable-20060828/libguile/continuations.c:151: error: 'mcontext_t' has no member named 'sc_ar_bsp'
>
> I assume this is because the code is still checking for __ia64__ instead
> of __ia64.  HP C defines __ia64 but not __ia64__.  GCC defines both.
> Some files use __ia64 (gs_os_dep.c, __scm.h) but most still use
> __ia64__, i.e.  continuations.c, gc.c, gc-malloc.c, threads.c.
>
> I will change the __ia64__ uses and see if I can then compile with GCC.

This is the problem that has since been fixed in CVS.

Regards,
     Neil



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2006-11-02 21:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200611012157.NAA20914@hpsje.cup.hp.com>
2006-11-02  8:29 ` Building Guile on IA64 HPUX Hrvoje Nikšić
2006-11-02 21:15 ` Neil Jerram [this message]
2006-10-25 15:31 Hrvoje Nikšić
2006-10-25 22:36 ` Neil Jerram
2006-10-26  7:13   ` Hrvoje Nikšić
2006-10-27  0:06     ` Neil Jerram
2006-10-27  7:16       ` Hrvoje Nikšić

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=873b91czys.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    --cc=hrvoje.niksic@avl.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).