From: Hans Aberg <haberg-1@telia.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org
Subject: Re: Guile 1.9.14 & GIT version linking errror
Date: Sun, 16 Jan 2011 13:04:49 +0100 [thread overview]
Message-ID: <988A307C-F4BD-46A2-BD33-C6E4EE5D040F@telia.com> (raw)
In-Reply-To: <87k4i51790.fsf@ossau.uklinux.net>
On 16 Jan 2011, at 11:18, Neil Jerram wrote:
>>> ... when I try to install guile-1.9.14, I get the error below (Mac
>>> OS X 10.5.8 PPC G4).
>>>
>>> ld: duplicate symbol ___gmpz_abs in .libs/libguile_2.0_la-arbiters.o
>>> and .libs/libguile_2.0_la-alist.o
>>
>> And I get the same error when using GIT.
> - understand why it is being _defined_ twice, as opposed to just
> declared
There might be a problem with GMP inlining. A lot of binary files
match by 'grep -r mpz_abs *', but no source files. The header /usr/
local/include/gmp.h has a section inlining (below). The macro
__GMP_EXTERN_INLINE is turned on by another section:
/* gcc has __inline__ in all modes, including strict ansi. Give a
prototype
for an inline too, so as to correctly specify "dllimport" on
windows, in
case the function is called rather than inlined.
GCC 4.3 and above with -std=c99 or -std=gnu99 implements ISO C99
inline semantics, unless -fgnu89-inline is used. */
#ifdef __GNUC__
#if (defined __GNUC_STDC_INLINE__) || (__GNUC__ == 4 && __GNUC_MINOR__
== 2)
#define __GMP_EXTERN_INLINE extern __inline__ __attribute__
((__gnu_inline__))
#else
#define __GMP_EXTERN_INLINE extern __inline__
#endif
#define __GMP_INLINE_PROTOTYPES 1
#endif
...
/* The following are provided as inlines where possible, but always
exist as
library functions too, for binary compatibility.
Within gmp itself this inlining generally isn't relied on, since it
doesn't get done for all compilers, whereas if something is worth
inlining then it's worth arranging always.
There are two styles of inlining here. When the same bit of code is
wanted for the inline as for the library version, then
__GMP_FORCE_foo
arranges for that code to be emitted and the __GMP_EXTERN_INLINE
directive suppressed, eg. mpz_fits_uint_p. When a different bit
of code
is wanted for the inline than for the library version, then
__GMP_FORCE_foo arranges the inline to be suppressed, eg.
mpz_abs. */
#if defined (__GMP_EXTERN_INLINE) && ! defined (__GMP_FORCE_mpz_abs)
__GMP_EXTERN_INLINE void
mpz_abs (mpz_ptr __gmp_w, mpz_srcptr __gmp_u)
{
if (__gmp_w != __gmp_u)
mpz_set (__gmp_w, __gmp_u);
__gmp_w->_mp_size = __GMP_ABS (__gmp_w->_mp_size);
}
#endif
next prev parent reply other threads:[~2011-01-16 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <13B7D376-7BFD-4236-B6EF-5BF70FE248B7@telia.com>
[not found] ` <87lj2lgavf.fsf@ossau.uklinux.net>
2011-01-15 23:11 ` Macro expansion Hans Aberg
2011-01-16 10:00 ` Guile 1.9.14 & GIT version linking errror Hans Aberg
2011-01-16 10:18 ` Neil Jerram
2011-01-16 10:27 ` Neil Jerram
2011-01-16 10:38 ` Hans Aberg
2011-01-16 12:04 ` Hans Aberg [this message]
2011-01-16 14:32 ` Hans Aberg
2011-01-17 22:31 ` Ludovic Courtès
2011-01-26 19:30 ` Andy Wingo
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=988A307C-F4BD-46A2-BD33-C6E4EE5D040F@telia.com \
--to=haberg-1@telia.com \
--cc=bug-guile@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).