[sword-devel] Compiling sword
Daniel Glassey
danglassey at ntlworld.com
Sat Apr 16 15:21:28 MST 2005
Troy A. Griffitts wrote:
> Will,
> It might be the version of automake/autoconf that you have on your
> system. But since you mention a link error, does that mean that you are
> able to run ./configure and make even thought the autogen.sh script
> thows these warnings? If so, could you post the link error? I don't
> know much about the build system (dglasseys is the resident expert in
> that area) but I only get 1 warning when I run ./autogen.sh Below is
> my version information. It you're able to update your automake/autoconf
> packages on your mac, maybe that might help. Hope we can get ya working
> again.
updating isn't a solution - it should work with whatever comes with the
system.
I've replicated the problem and it exists in revision 1770 (before the
changes I made recently so reverting that won't help). It doesn't exist
in 1674 and I haven't pinned it down more than that yet.
or at least this bit appears
>> lib/Makefile.am:18: libsword_la_SOURCES was already defined in
>> condition TRUE, which implies condition WITHCURL_TRUE
>>
>> ...
Regards,
Daniel
>
> Will Thimbleby wrote:
>
>> With that link I get similar errors:
>>
>> *** Sword build system generation
>> *** Recreating libtool
>> libtoolize
>> *** Recreating aclocal.m4
>> aclocal
>> *** Recreating configure
>> Can't locate object method "path" via package "Autom4te::Request" at
>> /usr/bin/autom4te line 81.
>> autoheader: /usr/bin/autom4te failed with exit status: 1
>> Can't locate object method "path" via package "Autom4te::Request" at
>> /usr/bin/autom4te line 81.
>> *** Recreating the Makefile.in files
>> configure.ac: installing `./mkinstalldirs'
>> lib/Makefile.am:18: libsword_la_SOURCES was already defined in
>> condition TRUE, which implies condition WITHCURL_TRUE
>>
>> ...
>>
>> The latest svn version is what I was using before. thanks --Will
>>
>> On 15 Apr 2005, at 7:44 pm, Troy A. Griffitts wrote:
>>
>>> Will,
>>> Could you confirm for me that you DON'T have the same issue in
>>> the latest 1.5.8 release candidate, and I'll try to hunt down what
>>> changed since then:
>>>
>>> http://crosswire.org/sword/ALPHAcckswwlkrfre22034820285912/alpha/
>>> sword-1.5.7.100.tar.gz
>>>
>>> -Troy.
>>>
>>>
>>>
>>> Will Thimbleby wrote:
>>>
>>>> Hi, I have problems when I make sword and also problems with
>>>> autogen,sh. Here is the trimmed output from autogen. Are these
>>>> warnings a problem, and is there an easy way to fix them? thanks
>>>> --Will
>>>> *** Sword build system generation
>>>> *** Recreating libtool
>>>> libtoolize
>>>> *** Recreating aclocal.m4
>>>> aclocal
>>>> *** Recreating configure
>>>> *** Recreating the Makefile.in files
>>>> lib/Makefile.am:18: libsword_la_SOURCES was already defined in
>>>> condition TRUE, which implies condition WITHCURL_TRUE
>>>> ...
>>>> lib/Makefile.am:18: libsword_la_SOURCES was already defined in
>>>> condition TRUE, which implies condition WITHCURL_FALSE
>>>> ...
>>>> lib/Makefile.am:18: warning: automake does not support conditional
>>>> definition of libsword_la_SOURCES in libsword_la_SOURCES
>>>> lib/Makefile.am:18: warning: automake does not support conditional
>>>> definition of libsword_la_SOURCES in libsword_la_SOURCES
>>>> Use of uninitialized value in concatenation (.) or string at
>>>> /usr/bin/automake line 8449.
>>>> : am_libsword_la_OBJECTS was already defined in condition
>>>> WITHCURL_TRUE, which is implied by condition TRUE
>>>> ...
>>>> Use of uninitialized value in concatenation (.) or string at
>>>> /usr/bin/automake line 8449.
>>>> : am_libsword_la_OBJECTS was already defined in condition TRUE,
>>>> which implies condition WITHCURL_FALSE
>>>> am_libsword_la_OBJECTS (Automake, where = undefined) =
>>>> ...
>>>> tests/cppunit/Makefile.am:4: HAVE_CPPUNIT does not appear in
>>>> AM_CONDITIONAL
More information about the sword-devel
mailing list