Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 156 of 807  Not logged in ELOG logo
    icon2.gif   Re: compiling elog 2.6.1 on solaris platform, posted by Steve Jones on Fri Feb 10 22:31:38 2006 
[quote="Steve Jones"][quote="Stefan Ritt"][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().
    icon2.gif   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)
    icon2.gif   Re: compiling elog 2.6.1 on solaris platform, posted by Steve Jones on Mon Feb 13 18:22:08 2006 
[quote="Stefan Ritt"][quote="Steve Jones"]BTW, Stefan, this code in Makefile does not work on Solaris
[code]
OSTYPE = $(shell uname)
    icon2.gif   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
    icon2.gif   Re: Accessing elog through two apache servers..., posted by Dimitrios Tsirigkas on Tue Feb 14 14:23:04 2006 
Hi Stefan, 

[quote="Stefan Ritt"]
    icon2.gif   Re: Accessing elog through two apache servers..., posted by Dimitrios Tsirigkas on Tue Feb 14 16:06:28 2006 
Hi,

The problem was coming from the fact that elog did not supports request coming from multiple hops through proxies. You got the ful string of them in the
    icon2.gif   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
    icon2.gif   Re: CONCERN: Cross-platform compiling at risk, posted by Steve Jones on Tue Feb 14 22:31:08 2006 
[quote="Steve Jones"][quote="Stefan Ritt"][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,
ELOG V3.1.5-3fb85fa6