This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Profile not called
At 10:00 AM 10/25/2004, you wrote:
>"Larry Hall" wrote in message 6.1.0.6.0.20041025093851.04cf8be0@pop.prospeed.net">news:6.1.0.6.0.20041025093851.04cf8be0@pop.prospeed.net...
>[snip]
>> At 04:21 AM 10/25/2004, you wrote:
>> I'll take your word for it but I still think you should heed Brian's advice.
>> Looking at your cygcheck output, one can see that you have Cygwin executables
>> like 'bash.exe', 'cat.exe', and 'gcc.exe' in 'C:\cygwin\bin\', to name a few.
>> This is in direct conflict with your mounts. From your mounts, I'm led to
>> conclude that you installed Cygwin into the directory you downloaded Cygwin
>> to, which has historically caused problems. It's clear that at least at some
>> point in the past, you also installed Cygwin into 'C:\cygwin\bin\'. So I'd
>> recommend looking at this conflict and getting it resolved. Brian's
>> suggestion may be all that's necessary to set this straight.
>[snip]
>
>Thanks. I did that. See my posting in the tread titled
>"startup problem // no longer works // profile not called"
>at clj0b6$lab$1@sea.gmane.org">news://news.gmane.org/clj0b6$lab$1@sea.gmane.org
>
>We can see that there is some problem with
>"bash: kpsexpand: command not found"
And how would you check to find out where 'kpsexpand' came from? Visit
<http://cygwin.com/packages/>, enter 'kpsexpand', and press enter. Presto!
You now know that 'kpsexpand' comes from the 'tetex-bin' package. You
have that installed, so you can either look to see why that's not being found
for you anymore or you can just rerun 'setup.exe' and reinstall it. The
choice is yours.
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/