Re: compiling elog 2.6.1 on solaris platform, posted by Stefan Ritt on Fri Feb 10 20:29:12 2006
|
[quote="Steve Jones"]Ok, I see what you did. I took a different route since I was not sure how the gnu linker would handle the fact that there would be
two declarations of the forkpty() function when compiled and linked under Linux. Instead, I created a separate forkpty.c module and compiled it separately.
Then, if "solaris", link it in. Otherwise, use library "util" which already has forkpty().
|
|
Re: email problems, posted by Stefan Ritt on Fri Feb 10 21:50:27 2006
|
[quote="Chris Warner"]Do you have an ise when that will be?[/quote]
In about a week from now. |
|
Re: compiling elog 2.6.1 on solaris platform, posted by Stefan Ritt on Fri Feb 10 22:35:20 2006
|
[quote="Steve Jones"]BTW, Stefan, this code in Makefile does not work on Solaris
[code]
OSTYPE = $(shell uname)
|
|
Re: Accessing elog through two apache servers..., posted by Stefan Ritt on Tue Feb 14 13:40:49 2006
|
Hi Dimitrios,
I know where your problem is and you could actually help me in solving it. The reason of the problem is the redirection. After you login, you get redirected |
|
Re: CONCERN: Cross-platform compiling at risk, posted by Stefan Ritt on Tue Feb 14 17:43:15 2006
|
[quote="Steve Jones"]Stefan, I am concerned that there are becoming too many Linux dependencies in terms of required libraries and header files. Although
we have a replacement for the [code]forkpty()[/code] routine, I am running into many other dependencies, the latest of which is pty.h. Aren't there guidelines
in GCC that point out what is available cross-platform and what is not? For example, any SVR# (System Five, Release XX) based Unix will not include the |
|
Re: Accessing elog through two apache servers..., posted by Stefan Ritt on Wed Feb 15 18:13:25 2006
|
| Thanks for the patch, I committed it to Subversion Revision #1657. |
|
Re: CONCERN: Cross-platform compiling at risk, posted by Stefan Ritt on Wed Feb 15 18:25:15 2006
|
[quote="Steve Jones"]Question: Is the functionality really just to issue an arbitrary command-string to a "shell" and have the result stuffed back into
an eLog variable? I'm not an expert but it would seem that such a feature would be universally available or could be used to construct a suitable routine.
|
|
Re: CONCERN: Cross-platform compiling at risk, posted by Stefan Ritt on Fri Feb 17 13:31:00 2006
|
[quote="Steve Jones"]If possible, could one use the [code]int system(const char *s);[/code] function in conjunction with a filei/o function as the means
for getting the results of a system call back into a var. Perhaps [code]char *tmpnam(char *s);[/code], running a command via [code]int system(const char
*s);[/code], then opening that file for a read would accomplish what is being desired?
|