After a crash of my system disk yesterday and the ressurection of the system today I'm getting the following error while trying to insert a citation or label based on the current word:
\autoref{/tmp/temp_textmate.haeIjJ:4: command not found: kpsewhich - show-path=tex cha:auswahl_eines_loesungskonzeptes}
The thing is. It tells me about kpsewhich is not found but it was able to insert the correct label. When I fire up "which kpsewhich" in Terminal, I get the following output:
[Jan@iah] ~ > which kpsewhich /usr/local/texlive/2007/bin/i386-darwin/kpsewhich
Also I have no problem to compile my document.
Maybe it has something to do with PATH, but I'm not sure. Can anyone give me a hint on this?
Thanks, Jan
Not sure what I can suggest, but to begin with does this problem persist after reboot? And what exactly has changed between your system before the crash and your system after? I.e. what exactly do you mean by "resurrection of the system"?
And yeah, let's start with the output to "echo $PATH". Do you have / usr/texbin? If not, does the problem get solved if you create a symbolic link from /usr/texbin to the path /usr/local/texlive/2007/ bin/i386-darwin ?
Haris Skiadas Department of Mathematics and Computer Science Hanover College
On Sep 11, 2008, at 12:23 PM, Jan Michael wrote:
After a crash of my system disk yesterday and the ressurection of the system today I'm getting the following error while trying to insert a citation or label based on the current word:
\autoref{/tmp/temp_textmate.haeIjJ:4: command not found: kpsewhich - show-path=tex cha:auswahl_eines_loesungskonzeptes}
The thing is. It tells me about kpsewhich is not found but it was able to insert the correct label. When I fire up "which kpsewhich" in Terminal, I get the following output:
[Jan@iah] ~ > which kpsewhich /usr/local/texlive/2007/bin/i386-darwin/kpsewhich
Also I have no problem to compile my document.
Maybe it has something to do with PATH, but I'm not sure. Can anyone give me a hint on this?
Thanks, Jan
Haris,
On 11.09.2008, at 23:08, Charilaos Skiadas wrote:
Not sure what I can suggest, but to begin with does this problem persist after reboot? And what exactly has changed between your system before the crash and your system after? I.e. what exactly do you mean by "resurrection of the system"?
In steps:
(1) Clean and fresh install of Leopard 10.5.0 (2) Migration of old profile including apps and library folder (3) Upgrade to 10.5.4 (4) Manual copy of /usr/local from Backup to new system disk
I had MacTeX 2007 installed on the old system. But since than a lot of modification where made by me to the tex tree in /usr/local, so that just copied the tree and didn't do a complete reinstallation.
And yes. The problem persists after reboot.
And yeah, let's start with the output to "echo $PATH". Do you have / usr/texbin? If not, does the problem get solved if you create a symbolic link from /usr/texbin to the path /usr/local/texlive/2007/ bin/i386-darwin ?
This is the requested output from echo $PATH:
[Jan@iah-2] ~ > echo $PATH /usr/local/texlive/2007/bin/i386-darwin:/opt/subversion/bin:/opt/
local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/ bin:/usr/X11/bin
And yes the symbolic link solved the problem!
I already tracked down the method "find_file" in "/Applications/ TextMate.app/Contents/SharedSupport/Support/lib/LaTeXUtils.rb" which produces the error. But even adding /usr/local/texlive/2007/bin/i386-darwin/ to locs in "tex_path" method didn't helped.
Many Thanks! But shouldn't this have worked without the symbolic link?
Cheers,
Jan
On Sep 11, 2008, at 12:23 PM, Jan Michael wrote:
After a crash of my system disk yesterday and the ressurection of the system today I'm getting the following error while trying to insert a citation or label based on the current word:
\autoref{/tmp/temp_textmate.haeIjJ:4: command not found: kpsewhich - show-path=tex cha:auswahl_eines_loesungskonzeptes}
The thing is. It tells me about kpsewhich is not found but it was able to insert the correct label. When I fire up "which kpsewhich" in Terminal, I get the following output:
[Jan@iah] ~ > which kpsewhich /usr/local/texlive/2007/bin/i386-darwin/kpsewhich
Also I have no problem to compile my document.
Maybe it has something to do with PATH, but I'm not sure. Can anyone give me a hint on this?
Thanks, Jan
On Sep 11, 2008, at 5:41 PM, Jan Michael wrote:
Many Thanks! But shouldn't this have worked without the symbolic link?
Yes and no. Frontends like Textmate don't go through the same initialization process as the shell does, so they don't get to know about the value of the PATH variable you see when you try a command in the shell. So for instance you can try the following and it will also work: Remove the symbolic link, close textmate, and on the terminal do "open -a TextMate". This will start TM as a child of the terminal, and hence inheriting the terminal's shell variables. It will then know about your PATH setting, and should be able to find tex just as you do from the terminal. But since TM is not run this way typically, it doesn't know about that.
So given that we can't rely on the shell variables for locating the tex installation, we rely on a series of heuristic checks. The first is looking for /usr/texbin, which has been now accepted as the location of the tex install by the mac community. By this I mean that the MacTeX installation creates the necessary symbolic link there, and other programs can rely on it being there for anyone installing TeX via MacTeX. That is why things were working for you earlier. When you did the migration though, none of the agents involved in the migration process knew about the symlink, so it was not created.
Now, returning to the issue at hand, once this link is not found some other things are tried. And I think was has changed in 10.5 is the message reported by the shell command used to check for kpsewhich in one of these steps. This command used to fail silently in 10.4, but not in 10.5. At least this is my conjecture. It is usually not an issue since for practically everyone the /usr/texbin part works already, and we don't even have to go into the heuristics. Most people who don't keep current with latex installs are probably also not keeping current with OS versions, so those that could have seen the problem if they moved to 10.5 are likely still in 10.4, and not seeing the problem (phew, that was a complicated one).
So anyway, that is probably a longer answer than what you bargained for, but there you have it.
Cheers,
Jan
Haris Skiadas Department of Mathematics and Computer Science Hanover College
-
Charilaos Skiadas -
Jan Michael