From: ludo@gnu.org (Ludovic Courtès)
To: phorgan1@yahoo.com
Cc: guile-devel@gnu.org
Subject: Re: guile and visibility problems
Date: Thu, 03 Jul 2008 00:01:31 +0200 [thread overview]
Message-ID: <87r6acc5dw.fsf@gnu.org> (raw)
In-Reply-To: <485FE03F.4020609@yahoo.com> (Patrick Horgan's message of "Mon\, 23 Jun 2008 10\:41\:19 -0700")
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
Hi Patrick,
Sorry for the delay...
Patrick Horgan <phorgan1@gmail.com> writes:
> gcc (GCC) 4.3.1
> Linux dell 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686
> GNU/Linux
OK. I had been using 4.2.3 until now, and I was able to reproduce the
problem with 4.3.1 (with 4.3, symbols not declared as `extern' are
considered as "common" symbols).
Can you try out the attached patch? It seems to fix the problem for me.
To apply it:
$ cd /path/to/guile
$ patch -p1 < ,,no-common-symbols.diff
Thanks in advance,
Ludovic.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: The patch --]
[-- Type: text/x-patch, Size: 495 bytes --]
diff --git a/libguile/__scm.h b/libguile/__scm.h
index 76b4448..30077fd 100644
--- a/libguile/__scm.h
+++ b/libguile/__scm.h
@@ -101,9 +101,9 @@
* as having "internal" linkage. */
#if (defined __GNUC__) && \
((__GNUC__ >= 4) || (__GNUC__ == 3 && __GNUC_MINOR__ == 3))
-# define SCM_INTERNAL __attribute__ ((__visibility__ ("internal")))
+# define SCM_INTERNAL extern __attribute__ ((__visibility__ ("internal")))
#else
-# define SCM_INTERNAL
+# define SCM_INTERNAL extern
#endif
next parent reply other threads:[~2008-07-02 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <485ACACB.5040405@yahoo.com>
[not found] ` <878wwwa5mn.fsf@gnu.org>
[not found] ` <485FE03F.4020609@yahoo.com>
2008-07-02 22:01 ` Ludovic Courtès [this message]
2008-07-04 20:26 ` guile and visibility problems Ludovic Courtès
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=87r6acc5dw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=phorgan1@yahoo.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).