Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2008-07

FPC version 2.2.2 RC2 is out

9 messages · 4 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Michael Van Canneyt

Hello,

After some testing and fixing minor installation and other issues, RC2 for version 2.2.2 is available for testing. Downloads for major platforms (Linux/Windows/FreeBSD/Mac OS X/Dos) are available from

ftp://ftp.freepascal.org/fpc/beta/2.2.2rc2

(this should propagate to mirrors soon)

A list of major changes (unchanged when compared to RC 1) is available in the Wiki:
http://wiki.freepascal.org/User_Changes_2.2.2

A major issue that was fixed when compared to RC1 was that the Linux RPM installation installed units in a location where the compiler wasn't searching, so testing of the RPMs can proceed now.

We urge everybody to test this release candidate thoroughly. If all goes well, this will become the final release "real soon now".

Enjoy !

Michael.

Reply by email

Cesar Romero
to Michael Van Canneyt

I wrote a appserver with fpc +Indy, all works just fine in OpenSuse 11, but when I install in a Fedora box (I tried Fedora 7, 8 and 9) it just dont run and raises the exception:

An unhandled exception occurred at $08159DC9 : EIdCouldNotBindSocket : Could not bind socket. Address and port are already in use. $08159DC9 $0817CC21 $0817D404 $0817C8F5 $0806610D $08065D43 $08064228 $08048F7B "EIdSocketError : Socket Error # 98"

Im using a custom port number and Im sure that it is not in use, does anyone know if I should install custom packages in Fedora to have this working?

Regards,

Cesar Romero
http://blogs.liws.com.br/cesar

Reply by email

Michael Van Canneyt
to Cesar Romero
Cesar Romero wrote 11 lines
I wrote a appserver with fpc +Indy, all works just fine in OpenSuse 11, but when I install in a Fedora box (I tried Fedora 7, 8 and 9) it just dont run and raises the exception: An unhandled exception occurred at $08159DC9 : EIdCouldNotBindSocket : Could not bind socket. Address and port are already in use. $08159DC9 $0817CC21 $0817D404 $0817C8F5 $0806610D $08065D43 $08064228 $08048F7B "EIdSocketError : Socket Error # 98" Im using a custom port number and Im sure that it is not in use, does anyone know if I should install custom packages in Fedora to have this working?

Things that jump to mind:
- If the port number is below 1024, you must run as root.
- It's also possible that the firewall settings are different on fedora by default
- Maybe selinux is installed and it doesn't allow anything by default ?

Michael.

Reply by email

Cesar Romero
to Michael Van Canneyt

Hi Michael,

Show quoted text 18 lines
> I wrote a appserver with fpc +Indy, all works just fine in OpenSuse 11, but > when I install in a Fedora box (I tried Fedora 7, 8 and 9) it just dont run > and raises the exception: > > An unhandled exception occurred at $08159DC9 : EIdCouldNotBindSocket : Could > not bind socket. Address and port are already in use. $08159DC9 $0817CC21 > $0817D404 $0817C8F5 $0806610D $08065D43 $08064228 $08048F7B > "EIdSocketError : Socket Error # 98" > > Im using a custom port number and Im sure that it is not in use, does anyone > know if I should install custom packages in Fedora to have this working? > Things that jump to mind: - If the port number is below 1024, you must run as root.

The port Im using in 8090 or 8099 and Im already runnig as root for this tests.

- It's also possible that the firewall settings are different on fedora by default

No firewall started

- Maybe selinux is installed and it doesn't allow anything by default ?

I disabled that too.

I tested:

Hardware:
OpenSuse 11 - works fine
Fedora 7 - do not work

VM:
Fedora 8: do not work
Fedora 9: do not work

Reply by email

Marco van de Voort
to Cesar Romero
Show quoted text 13 lines
>> Im using a custom port number and Im sure that it is not in use, does anyone >> know if I should install custom packages in Fedora to have this working? > > Things that jump to mind: > - If the port number is below 1024, you must run as root. > The port Im using in 8090 or 8099 and Im already runnig as root for this tests. > - It's also possible that the firewall settings are different on fedora by default > No firewall started > - Maybe selinux is installed and it doesn't allow anything by default ? I disabled that too.

I agree with Michael, and the only thing I can think of is selinux. However in case of doubt, use strace.

Btw, I assume this is indy 10.

Reply by email

Cesar Romero
to Marco van de Voort
Marco van de Voort wrote 25 lines
>>> Im using a custom port number and Im sure that it is not in use, does anyone >>> know if I should install custom packages in Fedora to have this working? >>> >> Things that jump to mind: >> - If the port number is below 1024, you must run as root. >> >> > The port Im using in 8090 or 8099 and Im already runnig as root for this > tests. > >> - It's also possible that the firewall settings are different on fedora by default >> >> > No firewall started > >> - Maybe selinux is installed and it doesn't allow anything by default ? >> > I disabled that too. > I agree with Michael, and the only thing I can think of is selinux. However in case of doubt, use strace. Btw, I assume this is indy 10.

Yes, it is.

Reply by email

Michael Van Canneyt
to Cesar Romero
Cesar Romero wrote 30 lines
Marco van de Voort escreveu: > > > > Im using a custom port number and Im sure that it is not in use, does > > > > anyone > > > > know if I should install custom packages in Fedora to have this > > > > working? > > > > > > > Things that jump to mind: > > > - If the port number is below 1024, you must run as root. > > > > > > > > The port Im using in 8090 or 8099 and Im already runnig as root for this > > tests. > > > > > - It's also possible that the firewall settings are different on fedora > > > by default > > > > > > > > No firewall started > > > > > - Maybe selinux is installed and it doesn't allow anything by default ? > > > > > I disabled that too. > > > > I agree with Michael, and the only thing I can think of is selinux. However > in case of doubt, use strace. > > Btw, I assume this is indy 10. > Yes, it is.

Did you try strace ?

Michael.

Reply by email

Burkhard Carstens
to Cesar Romero: I wrote a appserver with fpc +Indy, all works just fine in OpenSuse 11, but when I…
Cesar Romero wrote 12 lines
I wrote a appserver with fpc +Indy, all works just fine in OpenSuse 11, but when I install in a Fedora box (I tried Fedora 7, 8 and 9) it just dont run and raises the exception: An unhandled exception occurred at $08159DC9 : EIdCouldNotBindSocket : Could not bind socket. Address and port are already in use. $08159DC9 $0817CC21 $0817D404 $0817C8F5 $0806610D $08065D43 $08064228 $08048F7B "EIdSocketError : Socket Error # 98" Im using a custom port number and Im sure that it is not in use, does anyone know if I should install custom packages in Fedora to have this working?

IIRC, this is a bug which shows only on systems having IPv6 support enabled. Make sure to add a IPv4 binding to your server, otherwise it tries to start listening socket for IPv4 and IPv6, which fails (or something like that; can't remember the exact details ..). However, following code solved my problems:

MyServer:=TIdTCPServer.create;
MyServer.DefaultPort:=8099;
MyServer.bindings.add.IPVersion:=Id_IPv4;

regards
Burkhard

Reply by email

Cesar Romero
to Burkhard Carstens

Hi Burkhard,

Show quoted text 26 lines
Am Freitag, 18. Juli 2008 18:04 schrieb Cesar Romero: > I wrote a appserver with fpc +Indy, all works just fine in OpenSuse > 11, but when I install in a Fedora box (I tried Fedora 7, 8 and 9) it > just dont run and raises the exception: > > An unhandled exception occurred at $08159DC9 : EIdCouldNotBindSocket > : Could not bind socket. Address and port are already in use. > $08159DC9 $0817CC21 $0817D404 $0817C8F5 $0806610D $08065D43 $08064228 > $08048F7B "EIdSocketError : Socket Error # 98" > > Im using a custom port number and Im sure that it is not in use, does > anyone know if I should install custom packages in Fedora to have > this working? > IIRC, this is a bug which shows only on systems having IPv6 support enabled. Make sure to add a IPv4 binding to your server, otherwise it tries to start listening socket for IPv4 and IPv6, which fails (or something like that; can't remember the exact details ..). However, following code solved my problems: MyServer:=TIdTCPServer.create; MyServer.DefaultPort:=8099; MyServer.bindings.add.IPVersion:=Id_IPv4;

I figured out that this weekend binding did the trick

MyServer.bindings.add.IPVersion:=Id_IPv4;

Thank you, for the reply.

Best regards,

Reply by email