Andreas Rottmann writes:
> Hi!
>
> Attached is a patch that fixes a linker error in the test suite when
> using the default toolchain on Debian sid. It should be applied to both
> master and stable-2.0, I think.
>
Thanks for the patch!
I really should have checked the mailinglist first before
I was trying to build Guile 2.0, but I stubbed my toe on
"Oh, you haven't installed libunistring". So, I found one
and installed it:
checking for LIBFFI... configure: error: Package requirements (libffi) were not
met:
No package 'libffi' found
Consider adjusting the PKG_CONFIG_PATH environmen
> From:Bruce Korb
>
> I was trying to build Guile 2.0, but I stubbed my toe on
> "Oh, you haven't installed libunistring". So, I found one
> and installed it:
>
> checking for LIBFFI... configure: error: Package requirements (libffi) were
> not
> met:
Really these checks should be at the t
Thanks, Mike, but:
On Mon, Feb 28, 2011 at 10:43 AM, Mike Gran wrote:
>> No package 'libffi' found
>
> On Fedora at least, libffi's been packaged for a long time. I think
> it is widely available generally as a pre-built package.
Saying that if you use Linux, then it must be Red Hat wouldn't f
Hello,
I think the list you want is in Guile's README file, which says that
Guile depends on these libraries:
- libgmp
- libiconv
- libintl
- libltdl
- libunistring
- libgc
- libffi
Unless of course I misunderstood your question.
Noah
On Mon, Feb 28, 2011 at 2:13 PM, Bruce Korb wrote:
> Thank
Hi,
On Mon, Feb 28, 2011 at 11:25 AM, Noah Lavine wrote:
> Hello,
>
> I think the list you want is in Guile's README file, which says that
> Guile depends on these libraries:
More or less.
> - libgmp
OK
> - libiconv
Not available for openSuSE
> - libintl
A perl library?
> - libltdl
> - libun
Bruce Korb writes:
> Hi,
>
> On Mon, Feb 28, 2011 at 11:25 AM, Noah Lavine wrote:
>> Hello,
>>
>> I think the list you want is in Guile's README file, which says that
>> Guile depends on these libraries:
>
>> - libiconv
> Not available for openSuSE
>
>> - libintl
> A perl library?
>
I think both
On Mon 28 Feb 2011 01:15, Andreas Rottmann writes:
> Andy Wingo writes:
>
>> (define-accessor get-x set-x! 0)
>>
> This example serves to illustrate the issue, but I want to make clear
> that there are situations where one cannot work around "cleanly" around
> this issue
Sure, a better exampl
Hello all,
I believe what I'm saying is equivalent to what Andreas said, but let
me put it in this way: I think the Right Thing to do is to change what
we think of as a name - instead of a name being a symbol, a name would
be a symbol plus the environment it was defined in (which is what a
syntax
Hi,
Mike Gran writes:
> Also, is the libunistring dependency still necessary,
Yes, e.g., in scm_from_stringn. Besides we may eventually provide
bindings for other parts of libunistring, like ‘unicode_character_name’,
etc.
Thanks,
Ludo’.
Hi,
Andy Wingo writes:
> But you have to, I think. If that module that contained the above
> define-syntactic-accessor expansion exports "foo", then in another
> module you have:
>
> (define bar (lambda () (foo)))
>
> which expands to
>
> (define bar (lambda () val-234123))
>
> Val needs to
Hi,
I'm running into a compile-time problem passing a C function
pointer to scm_c_define_gsubr, compiling in C++. And yes, I know I'm
using -Werror.
e.g.:
cc1plus: warnings being treated as errors
../../../src/guile/hackt-config.cc: In function 'void
HAC::guile_wrap::wrap_package_string_ini
12 matches
Mail list logo
