Re: Two build problems

[Noah Lavine <noah.b.lavine@gmail.com>]

Guile seems to build fine after "make distclean", so I guess the
problem was left-over files. I may also have installed another package
in an attempt to work around this, though. I'd rather not try
reverting package installs to see if I can break it again.

It's an unusual problem - in order to reproduce it, you have to have a
system with two distinct library directories, one of which has
uniconv.h but not unistr.h, and they have to have different
definitions of unitypes.h. I don't know of a good solution, but I
don't think it's worth worrying about right now. It should never occur
for distro builds of Guile, because they will be packaging all of
their libraries together, so they'll only have one version of
uniconv.h.

Noah

On Wed, Sep 26, 2012 at 5:41 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> Hi Noah,
>
> This vaguely rings a bell...
>
> Noah Lavine <noah.b.lavine@gmail.com> skribis:
>
>> libguile/bytevectors.c includes <uniconv.h>.
>>
>> uniconv.h lives in my system include directory
>
> [...]
>
>> But then on the next line, libguile/bytevectors.c includes <unistr.h>.
>> That refers to lib/unistr.h, not the system unistr.h.
>
> Could it be that lib/unitstr.h is a left-over from a previous build?
>
> Can you check whether the problem exists when building from a fresh
> checkout?  (Hydra is happy, FWIW...)
>
> Thanks,
> Ludo’.
>
>