On Thu, 2006-07-20 at 09:43 -0500, Larry Evans wrote:
> On 07/20/2006 09:32 AM, skaller wrote:
> > On Thu, 2006-07-20 at 08:06 -0500, Larry Evans wrote:
> [snip]
> >>With this version, at the make step, I got:
> >>
> >>g++ -o test/posix_t1 rtl/flx_arun_static.o test/posix_t1_static.o -Lrtl
> >>-lflx_async_static -lfaio_static -ldemux_static -lflx_pthread_static
> >>-lflx_static -lflx_gc_static -lpthread
> >>bin/flx_arun ./test/posix_t1.so > test/posix_t1.output && diff -b
> >>test/posix_t1.expect test/posix_t1.output
> >
> >
> > Ah good, it works! That's a known bug on some systems which
> > I think has since been corrected. What OS are you using?
> >
> linux:
>
> cd ~/prog_dev/felix/
> uname -a
> Linux null.localdomain.fake 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST
> 2002 i686 GNU/Linux
>
> Compilation finished at Thu Jul 20 09:41:40
>
> I've used debian packages for just about everything on my system.
Hmm .. that's strange.. I'm using Ubuntu/Dapper/Amd64.
posix_t1 looks like this:
----------------------------------------
#import <flx.flxh>
include "flx_faio_posix";
open Faio_posix;
// create a listening socket, spawn a thread to connect to it.
// in case something goes wrong could make test time out with
// spawn_fthread { { sleep 5.0; System::exit 1; }; };
print "felix posix accept/connect test\n";
var port = 0; // let mk_listener choose the port
print "creating listener\n";
var listener: int <- mk_listener(port, 1);
print "spawning connector\n";
// not printing in thread to make output repeatable in
// the face of scheduler changes.
spawn_fthread{ { var c: int; connect(&c, c"127.0.0.1", port); }; };
var s: int;
accept (&s, listener); // async!
if s == -1 then {
System::exit 1;
} else {
print "accepted connection\n";
System::exit 0;
} endif;
--------------------------------------
This is just testing basic socket I/O. On Linux this is using
epoll as a socket state change notifier. This works fine
for me, and I posted rc9 .. I sometimes post a tarball that
doesn't work on OSX, Solaris, Windows or whatever .. but I always
test them on Linux first.
I'm making rc10 now .. watch for the notice.
The best way to access Felix is still via the developer CVS.
[Sourceforge anon CVS is way out of sync at the moment for unknown
reasons] To use that you would need to register with sourceforge
as a developer and send me your username.
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Felix-language mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/felix-language
