Someone came into #sword with build problems. I now have the same thing
happening; I hadn't done "svn up" since 3358, but a fresh tree has all
manner of trouble with autotools build, during ./autogen.sh.
Makefile.am: installing './depcomp'
lib/Makefile.am:17: warning: source file '$(keysdir)/swke
On Wed, Oct 20, 2010 at 6:29 AM, Troy A. Griffitts wrote:
> Do you have a mods.d/ folder or mods.conf file in your current working
> directory when you run the utilities?
>
> CWD takes precedence over most other settings.
I just tried running the commands from within my ~/.sword folder.
Here is t
Do you have a mods.d/ folder or mods.conf file in your current working
directory when you run the utilities?
CWD takes precedence over most other settings.
Troy
On 10/20/2010 01:38 AM, Greg Hellings wrote:
> On Tue, Oct 19, 2010 at 5:14 PM, Matthew Talbert wrote:
>>> I made those adjustments a
On Tue, Oct 19, 2010 at 5:14 PM, Matthew Talbert wrote:
>> I made those adjustments after the default settings failed to locate the
>> modules in my user home directory. After clearing the environment variable
>> and setting /etc/sword.conf back to /usr/local/sword, the command line tools
>> still
> I made those adjustments after the default settings failed to locate the
> modules in my user home directory. After clearing the environment variable
> and setting /etc/sword.conf back to /usr/local/sword, the command line tools
> still fail to locate my modules.
>
There is a test utility, tests
I made those adjustments after the default settings failed to locate the
modules in my user home directory. After clearing the environment variable
and setting /etc/sword.conf back to /usr/local/sword, the command line tools
still fail to locate my modules.
--Greg
On Oct 19, 2010 4:54 PM, "Matthew
On Tue, Oct 19, 2010 at 5:46 PM, Greg Hellings wrote:
> [Install]
> DataPath=/home/greg/.sword
Why this instead of /usr/share/sword? What you're basically making
sword do is repetitively look in the same directories which may cause
problems. The default SWMgr constructor (which is presumably used
[Install]
DataPath=/home/greg/.sword
SWORD_HOME is set to the same value.
On Oct 19, 2010 4:42 PM, "Matthew Talbert" wrote:
>> And I'm not installing the library to .sword, rather I'm installing
modules
>> there both by hand and with installmgr. Sorry for the confusion.
>
> Do you have /etc/sword
> And I'm not installing the library to .sword, rather I'm installing modules
> there both by hand and with installmgr. Sorry for the confusion.
Do you have /etc/sword.conf? If so, what are its contents?
___
sword-devel mailing list: sword-devel@crosswi
Fixing that problem with the autotools shouldn't be overly difficult, but I
don't know if it is desired.
And I'm not installing the library to .sword, rather I'm installing modules
there both by hand and with installmgr. Sorry for the confusion.
--Greg
On Oct 19, 2010 3:49 PM, "Matthew Talbert"
On Tue, Oct 19, 2010 at 4:03 PM, Greg Hellings wrote:
>
> Sword keeps stressing me out whenever I try to build with autotools on a new
> system.
>
> I did not have ICU installed, because I don't care about its functionality.
> Rather than default to not build with ICU or error and tell me I need
Sword keeps stressing me out whenever I try to build with autotools on a new
system.
I did not have ICU installed, because I don't care about its functionality.
Rather than default to not build with ICU or error and tell me I need to
expressly specify --without-icu, configure quietly said it was a
12 matches
Mail list logo
