From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: Guile 1.6.6 build comments ... alpha ncurses
Date: Thu, 02 Dec 2004 11:14:26 +1100 [thread overview]
Message-ID: <877jo1a74t.fsf@zip.com.au> (raw)
In-Reply-To: <CMM.0.92.0.1101943637.beebe@psi.math.utah.edu> (Nelson H. F. Beebe's message of "Wed, 1 Dec 2004 16:27:17 -0700 (MST)")
"Nelson H. F. Beebe" <beebe@math.utah.edu> writes:
>
> It may well be that is what is happening here: extracting
> lib_termcap.o from libncurses.a is producing mixed data-access
> conventions, causing the linker error.
Yep. (I'm pretty sure OSF alpha is always PIC, even in .a, but I
don't know the conventions on a gnu system.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-12-02 0:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 23:27 Guile 1.6.6 build comments ... alpha ncurses Nelson H. F. Beebe
2004-12-02 0:14 ` Kevin Ryde [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-01 17:24 Guile 1.6.6 build comments Nelson H. F. Beebe
2004-12-01 23:18 ` Guile 1.6.6 build comments ... alpha ncurses Kevin Ryde
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=877jo1a74t.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@gnu.org \
/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).