unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Hans Aberg <haberg-1@telia.com>
Cc: bug-guile@gnu.org
Subject: Re: GIT version: missing linking flag
Date: Fri, 21 Jan 2011 17:02:45 +0100	[thread overview]
Message-ID: <87aaiu8ct6.fsf@gnu.org> (raw)
In-Reply-To: <92164B15-45D1-4D76-9AF6-8E1E098C04BD@telia.com> (Hans Aberg's message of "Thu, 20 Jan 2011 22:13:12 +0100")

Hi,

Hans Aberg <haberg-1@telia.com> writes:

> On 20 Jan 2011, at 22:01, Ludovic Courtès wrote:
>
>> Can you post the exact link command line and error message?
>
>
> $ make
> gcc parser.o lexer.o driver.o guile++.o guile.o exception.o tuple.o
> guile-config link` -lstdc++ -o guile++

This line was mangled by your mailer, I think (missing backquote,
newline inserted).

Furthermore, if you’re linking C++ code, then you should link with g++,
not gcc, and omit -lstdc++.

> Undefined symbols:
>   "_GC_register_finalizer_no_order", referenced from:
>       _make_c_exception in exception.o
>       _make_exception in exception.o
>       _make_tuple in tuple.o
> ld: symbol(s) not found

Oooh, I finally got your point about SCM_NEWSMOB.  It introduces a
direct dependency from your app on libgc, which can require -lgc,
depending on the linker.

I’ll look into it.  I think the GC_REGISTER_FINALIZER_NO_ORDER call
should be buried in a function akin to scm_i_new_smob_with_mark_proc.

Thanks,
Ludo’.



  reply	other threads:[~2011-01-21 16:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18  9:57 GIT version: values writing Hans Aberg
2011-01-19 14:44 ` GIT version: values Hans Åberg
2011-01-26 20:51   ` Andy Wingo
2011-01-26 23:34     ` Hans Aberg
2011-01-27  9:00       ` Andy Wingo
2011-01-27 13:20         ` Hans Aberg
2011-01-19 17:05 ` Hans Aberg
2011-01-20 15:17   ` Ludovic Courtès
2011-01-20 17:10     ` Hans Aberg
2011-01-19 19:40 ` GIT version: segmentation fault Hans Aberg
2011-01-26 20:46   ` Andy Wingo
2011-01-26 23:37     ` Hans Aberg
2011-01-19 22:22 ` GIT version: missing linking flag Hans Aberg
2011-01-20 15:20   ` Ludovic Courtès
2011-01-20 17:03     ` Hans Aberg
2011-01-20 21:01       ` Ludovic Courtès
2011-01-20 21:13         ` Hans Aberg
2011-01-21 16:02           ` Ludovic Courtès [this message]
2011-01-21 17:59             ` Hans Aberg
2011-01-26 20:52               ` Andy Wingo
2011-01-26 23:44                 ` Hans Aberg
2011-01-29 21:47             ` Ludovic Courtès
2011-01-29 22:51               ` Hans Aberg
2011-01-26 20:55       ` Andy Wingo
2011-01-26 23:47         ` Hans Aberg
2011-01-20 15:16 ` GIT version: values writing Ludovic Courtès
2011-01-20 16:51   ` Hans Aberg
2011-01-20 21:18     ` Ludovic Courtès
2011-01-20 21:55       ` Hans Aberg
2011-01-21 17:13       ` Values extension Hans Aberg
2011-01-26 20:57     ` GIT version: values writing Andy Wingo
2011-01-26 23:50       ` Hans Aberg

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=87aaiu8ct6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guile@gnu.org \
    --cc=haberg-1@telia.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).