Bennett Helm wrote:
>> Bennett, could you post the patch of all changes to the list,
>> just to make sure that I don't forget anything.
>
> Here it is. I've left in all the diagnostic stuff. Also, note lines
> 68-69, which you'll probably want to delete.
>
> Bennett
Thanks.
--
Angus
On Feb 15, 2005, at 11:42 AM, Angus Leeming wrote:
Bennett, could you post the patch of all changes to the list,
just to make sure that I don't forget anything.
Here it is. I've left in all the diagnostic stuff. Also, note lines
68-69, which you'll probably want to delete.
Bennett
bennett.diff
Bennett Helm wrote:
Try changing the ss.tellp() bit to something comparing iterators:
That seems to do the trick! (See output below.) I'll do more testing
tomorrow.
Excellent! Thanks for your patience.
I can't find any other problems with this.
Bennett, could you post the patch of all changes to
On Feb 14, 2005, at 5:01 PM, Angus Leeming wrote:
Bennett Helm wrote:
Try changing the ss.tellp() bit to something comparing iterators:
That seems to do the trick! (See output below.) I'll do more testing
tomorrow.
Excellent! Thanks for your patience.
I can't find any other problems with this.
Benn
Angus Leeming <[EMAIL PROTECTED]> writes:
| Andreas Vox wrote:
>
>> Angus Leeming <[EMAIL PROTECTED]> writes:
>>
>>> Well that seems pretty conclusive then. setEnvPath loops over the
>>> elements but doesn't do anything with them.
>>>
>>> Try changing the ss.tellp() bit to something comparing it
Bennett Helm wrote:
>> Try changing the ss.tellp() bit to something comparing iterators:
>
> That seems to do the trick! (See output below.) I'll do more testing
> tomorrow.
Excellent! Thanks for your patience.
--
Angus
On Feb 14, 2005, at 2:51 PM, Angus Leeming wrote:
Well that seems pretty conclusive then. setEnvPath loops over the
elements
but doesn't do anything with them.
Try changing the ss.tellp() bit to something comparing iterators:
That seems to do the trick! (See output below.) I'll do more testing
Andreas Vox wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
>> Well that seems pretty conclusive then. setEnvPath loops over the
>> elements but doesn't do anything with them.
>>
>> Try changing the ss.tellp() bit to something comparing iterators:
>
> Sorry, but that doesn't look like the
Angus Leeming <[EMAIL PROTECTED]> writes:
> Well that seems pretty conclusive then. setEnvPath loops over the elements
> but doesn't do anything with them.
>
> Try changing the ss.tellp() bit to something comparing iterators:
Sorry, but that doesn't look like the logical conclusion.
Is ss.str()
Bennett Helm wrote:
> On Feb 14, 2005, at 12:45 PM, Angus Leeming wrote:
>
>> Angus Leeming wrote:
>>> Thanks, Bennett. What that tells me is that the problem doesn't lie in
>>> PutEnv at all. It lies in the code that calls PutEnv.
>>>
>>> I have a nasty feeling that this, or something like it, w
On Feb 14, 2005, at 12:45 PM, Angus Leeming wrote:
Angus Leeming wrote:
Thanks, Bennett. What that tells me is that the problem doesn't lie in
PutEnv at all. It lies in the code that calls PutEnv.
I have a nasty feeling that this, or something like it, will fix the
problem (still in src/support/fil
Bennett Helm wrote:
> On Feb 14, 2005, at 12:31 PM, Angus Leeming wrote:
>
>> I have a nasty feeling that this, or something like it, will fix the
>> problem (still in src/support/filetools.C)
>>
>> void setEnvPath(string const & name, vector const & env)
>> {
>> char const separator(o
On Feb 14, 2005, at 12:31 PM, Angus Leeming wrote:
I have a nasty feeling that this, or something like it, will fix the
problem (still in src/support/filetools.C)
void setEnvPath(string const & name, vector const & env)
{
char const separator(os::path_separator());
std::ostrings
Angus Leeming wrote:
> Bennett Helm wrote:
>
>>
>> On Feb 14, 2005, at 11:11 AM, Angus Leeming wrote:
>>
>>> Let's try and refine this. Do things work correctly if you use putenv
>>> rather than setenv? (Ie, maybe the problem lies with (our use of) gcc
>>> 2.95's setenv routine.)
>>>
>>> Could
Bennett Helm wrote:
>
> On Feb 14, 2005, at 11:11 AM, Angus Leeming wrote:
>
>> Let's try and refine this. Do things work correctly if you use putenv
>> rather than setenv? (Ie, maybe the problem lies with (our use of) gcc
>> 2.95's setenv routine.)
>>
>> Could you alter this function in src/sup
On Feb 14, 2005, at 11:11 AM, Angus Leeming wrote:
Let's try and refine this. Do things work correctly if you use putenv
rather than setenv? (Ie, maybe the problem lies with (our use of) gcc
2.95's setenv routine.)
Could you alter this function in src/support/filetools.C? Do it in two
steps. Ie, ad
Bennett Helm wrote:
>> So the fault lies in "prependEnvPath". Yet Andreas says that this
>> (identical) code works perfectly for him when using the 1.4.x version.
>> I'm a bit baffled.
>
> It works perfectly for me, too, in 1.4.x. (I use gcc version 3.1 for
> lyx-1.4, but 2.95.2 for lyx-1.3.
Ok.
On Feb 14, 2005, at 10:42 AM, Angus Leeming wrote:
So the fault lies in "prependEnvPath". Yet Andreas says that this
(identical) code works perfectly for him when using the 1.4.x version.
I'm
a bit baffled.
It works perfectly for me, too, in 1.4.x. (I use gcc version 3.1 for
lyx-1.4, but 2.95.2
Bennett Helm wrote:
> My output (confirming my suspicions -- at least I'm not crazy!):
>
> Env var "PATH", "/usr/bin:/bin:/usr/sbin:/sbin:/Users/bennett", is
> prepended with "/Applications/LyX-136.app/Contents/MacOS/"
> result:
How interesting! I've erased the PATH environment variable!
> lyxrc
On Feb 13, 2005, at 12:35 PM, Angus Leeming wrote:
Here it results in output to the console:
lyxrc.path_prefix is /foo/bar
Env var "PATH",
"/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/
angus/bin",
is prepended with "/foo/bar"
result:
/foo/bar:/usr/kerberos/bin:/us
Bennett Helm wrote:
> With recent versions of lyx-1.3.6 (but not 1.4.0), the PATH environment
> is not set up properly. There are two problems:
>
> 1. It looks as though /usr/bin and /usr/local/bin are not properly
> added, so attempting to run the configure script or view files results
> in erro
With recent versions of lyx-1.3.6 (but not 1.4.0), the PATH environment
is not set up properly. There are two problems:
1. It looks as though /usr/bin and /usr/local/bin are not properly
added, so attempting to run the configure script or view files results
in errors like the following:
sh: li
22 matches
Mail list logo
