>>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Achh. That's a bit of autogenerated stuff isn't it? Is it Angus> possible to first modify $prefix as something like: Angus> prefix_safe=$prefix prefix="'$prefix'" # invoke Angus> ac_sub_configure_args ... prefix=prefix_safe unset prefix_safe It is probably possible. Angus> Well, no, not really. The reLyX configure script is being Angus> passed stuff that it is complaining about. It would be best if Angus> it didn't complain, no? Sure. Angus> I take it that you'd like all this stuff to work perfectly on Angus> both *nix and on Windows before I commit it to the 1.3.x tree? No, but it would be probably a good idea to commit for 1.3.x and 1.4.x at the same time and do the modifications on both trees afterwards. I guess it will be easier to work if you commit the patch. Angus> Things to do post patch: 1. PATHs. There's stuff hard-coded to Angus> set the PATH on a Mac to include a bunch of directories Angus> including that of the LyX executable so that reLyX et al are Angus> found. Some such similar thing is needed on Windows, so I'd Angus> guess that a LyXRC variable is the best solution here. We can keep that for later, but I think the lyx binary path should always be added for osx and windows. Having an LyXRC::extra_path variable is probably a good idea. Angus> 2. LyX currently doesn't behave too well if the root temp Angus> directory does not exist. I guess that it should try to create Angus> it and exit if it fails. In which cases does this happen? JMarc
