× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi James, thanks for your answer :-)
I succesfully compiled the tn5250 under aix at least, but unfortunately
every time i try to launch it i get a "segmentation fault(coredump)" error.
The compiler was XLC , seems that with GCC there still are problems.
I will try to do some tests and i'll let you know :-)
Thanks.
Ciao
Alberto.

"James Rich" <james@xxxxxxxxxxx> ha scritto nel messaggio
news:mailman.26695.1273172180.2580.linux5250@xxxxxxxxxxxxxxx
On Thu, 6 May 2010, Carey Evans wrote:

AIX redefines accept to naccept in sys/socket.h:

#define recvfrom nrecvfrom
#define accept naccept
#define getpeername ngetpeername
#define getsockname ngetsockname

which means that line 466 of sslstream.c ends up trying to assign to
the naccept member of the struct. You could try using the C++ compiler
instead, which uses an inline function instead of #define, or simply
add #undef accept near the top of the file.

I've been searching for a way to handle this in autoconf. Surely we can't
be the only ones who have this problem. I haven't found anything useful
so far.

Alberto, I think you need the #undef at the top of sslstream.c.

James Rich

if you want to understand why that is, there are many good books on
the design of operating systems. please pass them along to redmond
when you're done reading them :)
- Paul Davis on ardour-dev



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.