[ECOS] Goahead Web Server on i386

[ECOS] Goahead Web Server on i386

[Fred Woolsey]

Hi all,

Has anyone here successfully built Goahead for ecos running on an i386 =
(ix86) platform?  I've gotten it to compile, but the load process bombs. =
 And to compile it I had to make 3 or 4 mods to the Goahead source...

Thanks in advance,
Fred Woolsey


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] Goahead Web Server on i386

[kjell]

Hi Fred,

We have quite recently built and deployed the latest GoAhead webserver 
onto the latest i386 pc eCos platform (using the newer FreeBSD/KAME 
TCPIP stack).
Agreed, the GoAhead sources needed some fixes to work. I think this is 
due to that the GoAhead was ported to eCos quite a long time ago, and 
the eCos port hasn't been maintained in the GoAhead source/build tree.

While there still seems to be a memleak problem in it that we havent had 
time to bother too much about, the GoAhead generally works just great, 
and we have also successfully added SSL support using the OpenSSL stuff.

We are aiming to make our latest eCos + GoAhead stuff electronically 
easily available, but due to high workload this is unfortunately not the 
case at the moment. In the meanwhile however, drop me an email if You're 
interested in our code and I'll send You a tarball of what we have running.

Cheers, /Kjell
-- 
Kjell Svensson                 Embedded Technology Manager
Techtribe Solutions AB         Tel:  +46 (0)31 706 06 00
Flöjelbergsgatan 12            GSM:  +46 (0)70 270 76 66
SE-431 37  MÖLNDAL             Mail: kjell@techtribe.se
Sweden




Fred Woolsey wrote:
> Hi all,
> 
> Has anyone here successfully built Goahead for ecos running on an i386 =
> (ix86) platform?  I've gotten it to compile, but the load process bombs. =
>  And to compile it I had to make 3 or 4 mods to the Goahead source...
> 
> Thanks in advance,
> Fred Woolsey
> 
> 




-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] Goahead Web Server on i386

[Peter Vandenabeele]

On Sun, Jan 05, 2003 at 08:21:06PM +0100, kjell@techtribe.se wrote:
> Hi Fred,
> 
> We have quite recently built and deployed the latest GoAhead webserver 
> onto the latest i386 pc eCos platform (using the newer FreeBSD/KAME 
> TCPIP stack).

Under what license is it distributed ?

Thanks,

Peter

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] Goahead Web Server on i386

[kjell]

The GoAhead comes with its own non-GPL license, which can be found in 
the "license.txt" file in the top of its source tree (www.goahead.com)

It's a non-exclusive license (e.g. all IPR is kept by GoAhead), 
essentially stating that one may freely and without royalties "use, 
reproduce, modify, copy and distribute" the webserver source code as 
well as the resulting binaries, provided that any modifications to the 
webserver sources are distributed along with it. Additionally, one 
should within 30 days of distribution-start contribute back any source 
modifications to GoAhead, and one is also restricted not to change the 
"server identification field" of the first http response message.

As for what goes for the SSL stuff; I'm aware that there are possible 
patent and licensing issues for some (many?) of the algorithms provided 
in the OpenSSL package. Since we have only wrapped this up for internal 
try-outs, we haven't spent much effort into checking those licensing 
details in any greater depth.

But since the port turned out to be pretty straightforward and the SSL 
proved to be working quite well, maybe someone interested in using the 
SSL would be willing to dig deeper into its licensing and patent details?

Cheers, /Kjell
-- 
Kjell Svensson                 Embedded Technology Manager
Techtribe Solutions AB         Tel:  +46 (0)31 706 06 00
Flöjelbergsgatan 12            GSM:  +46 (0)70 270 76 66
SE-431 37  MÖLNDAL             Mail: kjell@techtribe.se
Sweden





Peter Vandenabeele wrote:
> On Sun, Jan 05, 2003 at 08:21:06PM +0100, kjell@techtribe.se wrote:
> 
>>Hi Fred,
>>
>>We have quite recently built and deployed the latest GoAhead webserver 
>>onto the latest i386 pc eCos platform (using the newer FreeBSD/KAME 
>>TCPIP stack).
> 
> 
> Under what license is it distributed ?
> 
> Thanks,
> 
> Peter
> 
> 





-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] Goahead Web Server on i386

[Andrew Lunn]

> As for what goes for the SSL stuff; I'm aware that there are possible 
> patent and licensing issues for some (many?) of the algorithms provided 
> in the OpenSSL package. Since we have only wrapped this up for internal 
> try-outs, we haven't spent much effort into checking those licensing 
> details in any greater depth.
> 
> But since the port turned out to be pretty straightforward and the SSL 
> proved to be working quite well, maybe someone interested in using the 
> SSL would be willing to dig deeper into its licensing and patent details?

Is this my OpenSSL port?

If so, i did a tiny amount if research in this area. I basically read
that is says in the OpenSSL distribution about which parts of it are
covered by patents and licenses. I added CDL which made these parts
optionally compilable and by default disabled.

This is a start, but the standard IANAL disclaimer applies and you
should check for yourself.

       Andrew

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] Goahead Web Server on i386

[kjell]

Hi Andrew,

No, it's not based on the port You did. We wanted to try out the very 
latest release of the OpenSSL, so we grabbed those sources directly from 
the OpenSSL.org website.
We have at this point not integrated the OpenSSL into the eCos 
configuration system at all, but only compiled it up into a library that 
can be linked together with an eCos system at build time (like the 
GoAhead). At the top level, we have then only added a few init calls to 
the OpenSSL library into the demo ecos-mainfile within the GoAhead sources.
Up to this point, the OpenSSL port was actually quite trivial and 
trouble-free. However, with all the provided algorithms compiled up the 
openssl library got quite huge, so I think some more work in the 
configurability area would be useful before any "real" use is made.
Your eCos-config work is likely a good way to go there, so if You or 
anyone else is interested in finishing this into a "real" ecos package, 
we'll be delighted to support that work in some (time-limited) way.

We did dig into the licensing descriptions of the OpenSSL about as deep 
as You did, but when we found that there might be issues with the often 
used MD5 algorithm we didn't bother to include it in the stuff we are 
currently building since it was not actually needed.

IANAL either, so I'd be most happy if someone else with a deeper legal 
understanding (or possibly a more reckless mind ;-) could tell the ecos 
list the proper do's and dont's of the eCos/SSL issues.

Cheers, /Kjell
-- 
Kjell Svensson                 Embedded Technology Manager
Techtribe Solutions AB         Tel:  +46 (0)31 706 06 00
Flöjelbergsgatan 12            GSM:  +46 (0)70 270 76 66
SE-431 37  MÖLNDAL             Mail: kjell@techtribe.se
Sweden




Andrew Lunn wrote:
>>As for what goes for the SSL stuff; I'm aware that there are possible 
>>patent and licensing issues for some (many?) of the algorithms provided 
>>in the OpenSSL package. Since we have only wrapped this up for internal 
>>try-outs, we haven't spent much effort into checking those licensing 
>>details in any greater depth.
>>
>>But since the port turned out to be pretty straightforward and the SSL 
>>proved to be working quite well, maybe someone interested in using the 
>>SSL would be willing to dig deeper into its licensing and patent details?
> 
> 
> Is this my OpenSSL port?
> 
> If so, i did a tiny amount if research in this area. I basically read
> that is says in the OpenSSL distribution about which parts of it are
> covered by patents and licenses. I added CDL which made these parts
> optionally compilable and by default disabled.
> 
> This is a start, but the standard IANAL disclaimer applies and you
> should check for yourself.
> 
>        Andrew
> 
> 





-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] Goahead Web Server on i386

[Peter Vandenabeele]

On Mon, Jan 06, 2003 at 10:49:22AM +0100, kjell@techtribe.se wrote:
> The GoAhead comes with its own non-GPL license, which can be found in 
> the "license.txt" file in the top of its source tree (www.goahead.com)

Thanks for this info,

Peter


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] Goahead Web Server on i386

[Andrew Lunn]

On Mon, Jan 06, 2003 at 11:23:37AM +0100, kjell@techtribe.se wrote:
> Hi Andrew,
> 
> No, it's not based on the port You did. We wanted to try out the very 
> latest release of the OpenSSL, so we grabbed those sources directly from 
> the OpenSSL.org website.

OK. 

Given the rate OpenSSL changes, i think it would be good to get the
eCos changes incorporated into the OpenSSL release. Unfortunatly, i
don't have the time to do that at the moment. Do you? You would want
to combine the CDL from my packages with your sources and produce
something that can be sent to the OpenSSL guys.

          Andrew

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] Goahead Web Server on i386

[Grant Edwards]

On Sun, Jan 05, 2003 at 08:21:06PM +0100, kjell@techtribe.se wrote:

> We have quite recently built and deployed the latest GoAhead webserver 
> onto the latest i386 pc eCos platform (using the newer FreeBSD/KAME 
> TCPIP stack).
> Agreed, the GoAhead sources needed some fixes to work. I think this is 
> due to that the GoAhead was ported to eCos quite a long time ago, and 
> the eCos port hasn't been maintained in the GoAhead source/build tree.
> 
> While there still seems to be a memleak problem in it that we havent had 
> time to bother too much about, the GoAhead generally works just great,

I'm aware of one memory leak involving strings allocated for
username or password when security is enabled.  But, if you're
not using authentication, that can't be it.

-- 
Grant Edwards
grante@visi.com

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

[ECOS] C Linkage for C++ Files

[Fred Woolsey]

Hi all,

Can anyone help explain how to go about compiling a C++ file with C linkage?
The eCos reference manual makes a reference to this... Is there a switch or
a #pragma for this?

Thanks and Best Regards,
Fred Woolsey



-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] C Linkage for C++ Files

[Greg Lanthier]

It wouldn't be as simple as wrapping the relevant C++
code in 'extern "C"' decls, would it?

Greg

 --- Fred Woolsey <fwsbcon@fwsbcon.com> wrote: > Hi
all,
> 
> Can anyone help explain how to go about compiling a
> C++ file with C linkage?
> The eCos reference manual makes a reference to
> this... Is there a switch or
> a #pragma for this?
> 
> Thanks and Best Regards,
> Fred Woolsey
> 
> 
> 
> -- 
> Before posting, please read the FAQ:
> http://sources.redhat.com/fom/ecos
> and search the list archive:
> http://sources.redhat.com/ml/ecos-discuss
>  

______________________________________________________________________ 
Post your free ad now! http://personals.yahoo.ca

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] C Linkage for C++ Files

[Fred Woolsey]

Dunno... would it?

Thanks for the help (I think..),
Fred Woolsey

(PS: A question typically expects an answer, not another question.)


----- Original Message -----
From: "Greg Lanthier" <greg_lanthierca@yahoo.ca>
To: "Fred Woolsey" <fwsbcon@fwsbcon.com>; "ecos-discuss"
<ecos-discuss@sources.redhat.com>
Sent: Monday, January 06, 2003 8:11 PM
Subject: Re: [ECOS] C Linkage for C++ Files


> It wouldn't be as simple as wrapping the relevant C++
> code in 'extern "C"' decls, would it?
>
> Greg
>
>  --- Fred Woolsey <fwsbcon@fwsbcon.com> wrote: > Hi
> all,
> >
> > Can anyone help explain how to go about compiling a
> > C++ file with C linkage?
> > The eCos reference manual makes a reference to
> > this... Is there a switch or
> > a #pragma for this?
> >
> > Thanks and Best Regards,
> > Fred Woolsey
> >
> >
> >
> > --
> > Before posting, please read the FAQ:
> > http://sources.redhat.com/fom/ecos
> > and search the list archive:
> > http://sources.redhat.com/ml/ecos-discuss
> >
>
> ______________________________________________________________________
> Post your free ad now! http://personals.yahoo.ca
>
> --
> Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
>
>
>
>



-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] C Linkage for C++ Files

[sai jayram]

On Mon, 6 Jan 2003, Greg Lanthier wrote:

> It wouldn't be as simple as wrapping the relevant C++
> code in 'extern "C"' decls, would it?


This works. I have used such things in my code.

ex: if you want to call a function named "function_in_cplus()" written in
C++ from a C routine, then the following will do.

C function

---
---
---

function_in_cplus();

---
---
---



c++ file

extern "C"
{
	function_in_cplus();
}

function_in_cplus()
{
	----
	----
	----
	---
}

 







> 
> Greg
> 
>  --- Fred Woolsey <fwsbcon@fwsbcon.com> wrote: > Hi
> all,
> > 
> > Can anyone help explain how to go about compiling a
> > C++ file with C linkage?
> > The eCos reference manual makes a reference to
> > this... Is there a switch or
> > a #pragma for this?
> > 
> > Thanks and Best Regards,
> > Fred Woolsey
> > 
> > 
> > 
> > -- 
> > Before posting, please read the FAQ:
> > http://sources.redhat.com/fom/ecos
> > and search the list archive:
> > http://sources.redhat.com/ml/ecos-discuss
> >  
> 
> ______________________________________________________________________ 
> Post your free ad now! http://personals.yahoo.ca
> 
> -- 
> Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> 
> 


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] C Linkage for C++ Files

[Fred Woolsey]

Hi Sai,

Thanks... I did some research after Greg's response and found just what you
so kindly explained... I appreciate it!  BTW- I have tried it and it does in
fact work just fine.

Cheers,
Fred Woolsey

----- Original Message -----
From: "sai jayram" <sai@cdotb.ernet.in>
To: "Greg Lanthier" <greg_lanthierca@yahoo.ca>
Cc: "Fred Woolsey" <fwsbcon@fwsbcon.com>; "ecos-discuss"
<ecos-discuss@sources.redhat.com>
Sent: Monday, January 06, 2003 11:36 PM
Subject: Re: [ECOS] C Linkage for C++ Files


>
> On Mon, 6 Jan 2003, Greg Lanthier wrote:
>
> > It wouldn't be as simple as wrapping the relevant C++
> > code in 'extern "C"' decls, would it?
>
>
> This works. I have used such things in my code.
>
> ex: if you want to call a function named "function_in_cplus()" written in
> C++ from a C routine, then the following will do.
>
> C function
>
> ---
> ---
> ---
>
> function_in_cplus();
>
> ---
> ---
> ---
>
>
>
> c++ file
>
> extern "C"
> {
> function_in_cplus();
> }
>
> function_in_cplus()
> {
> ----
> ----
> ----
> ---
> }
>
>
>
>
>
>
>
>
>
> >
> > Greg
> >
> >  --- Fred Woolsey <fwsbcon@fwsbcon.com> wrote: > Hi
> > all,
> > >
> > > Can anyone help explain how to go about compiling a
> > > C++ file with C linkage?
> > > The eCos reference manual makes a reference to
> > > this... Is there a switch or
> > > a #pragma for this?
> > >
> > > Thanks and Best Regards,
> > > Fred Woolsey
> > >
> > >
> > >
> > > --
> > > Before posting, please read the FAQ:
> > > http://sources.redhat.com/fom/ecos
> > > and search the list archive:
> > > http://sources.redhat.com/ml/ecos-discuss
> > >
> >
> > ______________________________________________________________________
> > Post your free ad now! http://personals.yahoo.ca
> >
> > --
> > Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> > and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> >
> >
>
>
> --
> Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
>
>
>
>



-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] Goahead Web Server on i386

[Jonathan Larmour]

kjell@techtribe.se wrote:
> The GoAhead comes with its own non-GPL license, which can be found in 
> the "license.txt" file in the top of its source tree (www.goahead.com)
> 
> It's a non-exclusive license (e.g. all IPR is kept by GoAhead), 
> essentially stating that one may freely and without royalties "use, 
> reproduce, modify, copy and distribute" the webserver source code as 
> well as the resulting binaries, provided that any modifications to the 
> webserver sources are distributed along with it. Additionally, one 
> should within 30 days of distribution-start contribute back any source 
> modifications to GoAhead, and one is also restricted not to change the 
> "server identification field" of the first http response message.

Given that licence, it would be good if we could get a GoAhead port, and 
although we can't include it in the main sources, we could distribute it 
on the contribs page.

But ideally that dratted memory leak problem would be fixed.

BTW, don't forget folks: Nick Garnett recently added a simple HTTP server 
to eCos.

Jifl
-- 
eCosCentric       http://www.eCosCentric.com/       <info@eCosCentric.com>
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] Goahead Web Server on i386

[Patrick Doyle]

> BTW, don't forget folks: Nick Garnett recently added a simple HTTP server
> to eCos.
I saw that announcement on the patches list, but I don't think it made it to
the general ecos-discuss list.  So this might be news to some.

--wpd


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] Goahead Web Server on i386

[Gary Thomas]

On Tue, 2003-01-07 at 14:31, Patrick Doyle wrote:
> > BTW, don't forget folks: Nick Garnett recently added a simple HTTP server
> > to eCos.
> I saw that announcement on the patches list, but I don't think it made it to
> the general ecos-discuss list.  So this might be news to some.
> 

You also might want to look at [yet] another HTTPD running
on eCos.  See http://www.mlbassoc.com/examples/

This will show you an HTTP server based on "libhttpd". I did 
this as an example of how to port code to eCos, but it's quite 
functional, etc.

-- 
------------------------------------------------------------
Gary Thomas                 |
MLB Associates              |  Consulting for the
+1 (970) 229-1963           |    Embedded world
http://www.mlbassoc.com/    |
email: <gary@mlbassoc.com>  |
gpg: http://www.chez-thomas.org/gary/gpg_key.asc
------------------------------------------------------------


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss