On Tuesday 09 September 2003 09:00, you wrote:
Thanks to Tom and Adriaan, my compiler in in order on Mac OSX (but before trying to load the Developper Tools CD from USA1 and not from Europa, I was desesperate). Yet, other problems are coming...
- PATH problems
1a) I'm unable to execute the a.out (nor the hello if using -o) directly but must use the stupid ./a.out (or ./hello). Even if I redefine the variable PATH in ~/.tcshrc (adding to it the current directory .). Where lies the file who defines PATH ? 1b) I construct some modules for toolboxes (like timer.p) or for abstract types (like lists.p) and I would like to put them in a genuine directory such that the compiler could find them from any other directory : how do it ?
Some checks questions on 1a: * The shell has to know the new PATH, either by restarting or by rereading the rc file using the command "source ~/.tcshrc" * Is the PATH variable not overwritten by other resource files? See the man page of tcsh (I cut and paste for your convenience:)
\begin{cut}
Startup and shutdown A login shell begins by executing commands from the system files /etc/csh.cshrc and /etc/csh.login. It then executes commands from files in the user’s home directory: first ~/.tcshrc (+) or, if ~/.tcshrc is not found, ~/.cshrc, then ~/.history (or the value of the histfile shell variable), then ~/.login, and finally ~/.cshdirs (or the value of the dirsfile shell variable) (+). The shell may read /etc/csh.login before instead of after /etc/csh.cshrc, and ~/.login before instead of after ~/.tcshrc or ~/.cshrc and ~/.history, if so compiled; see the version shell variable. (+)
Non-login shells read only /etc/csh.cshrc and ~/.tcshrc or ~/.cshrc on startup.
For examples of startup files, please consult http://tcshrc.source-forge.net.
\end{cut}
For 1b, I think the following extract of a tcsh-script of mine might be sufficient:
setenv SWITCHES "-g -pg --progress-messages --automake -O2 " setenv TARGETSTUFF " --unit-destination-path=obj/obj_fem --executable-file-name= bin/charles " setenv UNITPATH firstunitdir:secondunitdir setenv UNITPATH ${UNITPATH}:thirdunitdir
gpc $SWITCHES $TARGETSTUFF $UNITPATH charles.p
Here UNITPATH points to the directories where the source files of the units used are located. I think automake does a good job checking what of those has to be updated, if required.
For the export problem, I do not know. Anyone else?
Regards,
Marten Jan
- export problem
If I construct a module to implement an abstract type such that rational numbers, how export operators ? Writing : export rationals = (rational, +, -, *, /) ; give me a parse error before '+' (trying to enclose + between ' ' or " " is useless)
Thanks in advance, Dominique