Enrico Forestieri wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
>> -LangString FinishPageMessage "${LYX_LANG}" "Congratulations! LyX has
>> been installed successfully."
>> +LangString FinishPageMessage "${LYX_LANG}" "LyX should now be
>> installed. However, some of our users report that the configure script
>> fails to run and, as a result, LyX fails to start, reporting a missing
>> textclass.lst file. To fix, run the command: 'sh configure' from the
>> LyX/Resources/lyx directory."
>
> Here is an "artistic" translation in italian:
>
> LangString FinishPageMessage "${LYX_LANG}" "LyX è stato installato.
> Però, se l'installer non è riuscito a lanciare lo script di
> configurazione, non sarete in grado di usare LyX a causa della mancata
> generazione del file textclass.lst. In tal caso, il rimedio consiste
> nell'eseguire il comando 'sh configure' nella directory
> LyX/Resources/lyx."
Thanks Enrico.
> However, I endorse the use of a configure.bat script such as this:
>
> $ cat configure.bat
> @echo off
> <path_to_sh>\sh.exe configure
>
> where <path_to_sh> should be filled in by the installer. Indeed, it is
> not sure that everyone has sh.exe in his path. In this way, 'sh
> configure' in the LangString becomes 'configure'.
>
> Another point is that when the configure script does not get started,
> I observe that path_prefix in the configure file is also mangled (I don't
> remeber exactly in which way... perhaps it has repeated entries and thus
> turns out to be a very long string), so I am not sure that 'sh configure'
> succeeds when launched from the command line...
>
> I observed that configure is not launched for me (Win2000) but there is
> no problem with WinXP.
And for these observations. I'm not going to do anything with them
though ;-) I think that the message is enough to allow people to
"investigate" without getting too despondent and throwing this "bloody,
broken software" away.
--
Angus
