From: Stephanie Nile <stephie@connect.org.uk>
Cc: "M. Lavasani" <lavasani@connect.org.uk>
Subject: Guile Builds but Core dumps on 11.20
Date: Mon, 1 Jul 2002 09:55:59 +0100 (BST) [thread overview]
Message-ID: <1020701095559.9420000.adc19449@shin.connect.liv.ac.uk> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
Hi,
We have been given the job (by HP) of porting our top 100 packages from
HPUX11.00 to HPUX 11.20 - the new IA64 archeteture. Unfortuantly the 11.20
version
of guile coredumps. We are using gcc 3.0. Can you help? What info should I
send about the build? We are using the same compile flags on both (11.00 and
11.20) systems.
Any suggestions would be very welcome,
Thanks.
http://hpux.connect.org.uk/
© HPUX Porting and Archive Centre, Connect, Liverpool University.
__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/__/
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next reply other threads:[~2002-07-01 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 8:55 Stephanie Nile [this message]
2002-07-01 16:02 ` Guile Builds but Core dumps on 11.20 Thien-Thi Nguyen
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=1020701095559.9420000.adc19449@shin.connect.liv.ac.uk \
--to=stephie@connect.org.uk \
--cc=lavasani@connect.org.uk \
/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).