Re: [fpc-devel] Fixes 2.6.1 fails to install under Win32
Graeme Geldenhuys wrote: Hi, I'm using a Win2000, and have a released FPC 2.6.0 installed. I updated my FPC 2.6.1 to r23533 (latest revision to date). I run by usual build.bat script (shown below). FPC, RTL and FCL seems to compile fine, but the 'make install ...' seems to fail. I've never had such issues before. It seems like the Makefile is broken, if you look at the odd directory it tried to create. Anybody else experiencing this, or have a solution? 8<-8<-8<-8<-8< make distclean make all FPC=c:\FPC\2.6.0\bin\i386-win32\ppc386.exe make install INSTALL_PREFIX=c:\fpc\2.6.1\ FPC=c:\FPC\2.6.0\bin\i386-win32\ppc386.exe ...snip... 6.exe --prefix=c:\fpc\2.6.1\ --unitinstalldir=c:\fpc\2.6.1\/units/i386-win32/fcl -web Installing package fcl-web The installer encountered the following error: Failed to create directory "C:\fpc\2.6.1 --unitinstalldir=c:\fpc\2.6.1\\units\i3 86-win32\fcl-web\units\i386-win32\fcl-web\" Looks like using a backslash at the end of INSTALL_PREFIX=xxx argument quotes the following space, and so the whole thing becomes glued "C:\fpc\2.6.1" + space + "--unitinstalldir=...". Do not use a final backslash, like make install INSTALL_PREFIX=c:\fpc\2.6.1 and things should be Ok. It would probably be even cleaner to use slashes everywhere: make install INSTALL_PREFIX=c:/fpc/2.6.1 Disclaimer: I didn't actually test this (not sitting on Windows right now), just guessing :) Michalis ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] Fixes 2.6.1 fails to install under Win32
Hi, I'm using a Win2000, and have a released FPC 2.6.0 installed. I updated my FPC 2.6.1 to r23533 (latest revision to date). I run by usual build.bat script (shown below). FPC, RTL and FCL seems to compile fine, but the 'make install ...' seems to fail. I've never had such issues before. It seems like the Makefile is broken, if you look at the odd directory it tried to create. Anybody else experiencing this, or have a solution? 8<-8<-8<-8<-8< make distclean make all FPC=c:\FPC\2.6.0\bin\i386-win32\ppc386.exe make install INSTALL_PREFIX=c:\fpc\2.6.1\ FPC=c:\FPC\2.6.0\bin\i386-win32\ppc386.exe ...snip... 6.exe --prefix=c:\fpc\2.6.1\ --unitinstalldir=c:\fpc\2.6.1\/units/i386-win32/fcl -web Installing package fcl-web The installer encountered the following error: Failed to create directory "C:\fpc\2.6.1 --unitinstalldir=c:\fpc\2.6.1\\units\i3 86-win32\fcl-web\units\i386-win32\fcl-web\" make[4]: *** [install] Error 1 make[4]: Leaving directory `C:/FPC/2.6.1/src/packages/fcl-web' make[3]: *** [fcl-web_distinstall] Error 2 make[3]: Leaving directory `C:/FPC/2.6.1/src/packages' make[2]: *** [packages_distinstall] Error 2 make[2]: Leaving directory `C:/FPC/2.6.1/src' make[1]: *** [installother] Error 2 make[1]: Leaving directory `C:/FPC/2.6.1/src' make: *** [install] Error 2 8<-8<-8<-8<-8< Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://fpgui.sourceforge.net/ ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] for-in-index loop
29.01.13, 17:23, Hans-Peter Diettrich пишет: Paul Ishenin schrieb: At least it's more fun to implement something very new, instead of working on incomplete parts (loadable libraries, targets) which had been delayed due to problems. The same situation in Lazarus and in many open source projects BTW. Where are your patches for loadable libraries and new targets? Where are the bugs to fix? I don't know. I thought you know that since you wrote about them. Best regards, Paul Ishenin ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] for-in-index loop
Paul Ishenin schrieb: At least it's more fun to implement something very new, instead of working on incomplete parts (loadable libraries, targets) which had been delayed due to problems. The same situation in Lazarus and in many open source projects BTW. Where are your patches for loadable libraries and new targets? Where are the bugs to fix? DoDi ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] Windows 32bits .EXE socket server application on Linux x64
I wanted to share how I have been able to setup a Windows 32 bits executable on Ubuntu x64 using Wine, the EXE has been compiled with Delphi (the same works with Lazarus), the program is an embedded http server listening on port 80, any program listening on low ports (server sockets on ports 25, 80, 110, ...) will obtain WSAEACCESS error when running it, install Wine on your Ubuntu, then sudo setcap cap_net_bind_service=+ep /usr/bin/wine sudo setcap cap_net_bind_service=+ep /usr/bin/wine-preloader sudo setcap cap_net_bind_service=+ep /usr/bin/wineserver sudo setcap cap_net_bind_service=+ep /home/default/Demos/Bin/Ultima.exe you are ready to run your program using: wine /home/default/Demos/Bin/Ultima.exe maybe you will also need sudo capsh --inh=cap_net_bind_service --uid=1000 to obtain the uid of user "default" (if your username is "default"): id default this setup is very light and provide no routing overhead since it is not using the technique of iptables sudo iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8080 which is not always possible since it would require to modify the listing ports inside your program. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Synapse hangs in ARM-Linux
Follow-up:
I d/l'ed the most recent Synapse snapshot and when compiling I get:
Compiling ./synapse/synautil.pas
jedi.inc(512,4) Error: Illegal assembler style specified "INTEL"
This is easily fixed by commenting out the appropriate line in jedi.inc,
but it shows that this Synapse version is not yet tested on ARM.
Now I set the ConnectTimeout to 1 (10 seconds) and retested.
I found that in fact Synapse does return to the user program which
requests a retry but in one test of the same project it finished after
about 30 Minutes and in another it was after more than 60 (I killed the
test after that time.) .
Either some other Timeout definition is used, or the timeout in that
case does not work decently
I found that with Synapse on Windows and PC Linux, the Target (Heating
Controller device) mostly seems to force a timeout (or some other error
resulting in a retry) but sometimes not. With 20 or more seconds connect
timeout I usually get one retry, with 10 Seconds connect Timeout I
usually get two retries. But on ARM the project always hangs on the
third HTTP request (after two successful ones.)
I did do some logging using HTTPSend.Sock.OnStatus. (complete Logs below)
Here in Windows I see a:
"13:10060,Connection timed out"
after 30 Seconds (I think I did set the ConnectTimeout to 3 at this
time)
resulting in a retry requested by my software.
Note that the timeout comes after
"2:IPv4"
("2" being HR_SocketCreate if I am not failed, and "7" = HR_CanWrite /
"5" = HR_Connect are not reached on the first try.)
The Log for the ARM version shows something very different
(unfortunately this version of my software did not yet timestamp the
log. I'll retest with the updated version ASAP.)
"2:IPv4"
"7:"
"5:192.168.71.252:80"
"11:5382"
"13:110,Connection timed out"
Seemingly the connect ( "7" = HR_CanWrite / "5" = HR_Connect) is
performed without a timeout being hit.
Now it does "11" = HR_WriteCount is shown, supposedly indicating my
write request.
and "13" = HR_Error seems shows that a timeout error on that Write
occurred.
Seemingly the target does not understand or like the write request
issued by synapse.
Seemingly this is deterministic and happens all the time.
Is the number given with the "11" = HR_WriteCount log message indeed the
count of bytes that are written in this request or is it an accumulated
count ?
In fact I think I issue not more than 100 bytes per request.
Any additional suggestions ?
Thanks,
-Michael
HTTPSend.Sock.OnStatus Log on Windows (on PC Linux it's similar):
621 OK
>>>29.01.2013 00:18:39>>>3:
>>>29.01.2013 00:18:39>>>0:192.168.71.252:80
>>>29.01.2013 00:18:39>>>1:192.168.71.252:80
>>>29.01.2013 00:18:39>>>2:IPv4
>>>29.01.2013 00:19:09>>>13:10060,Connection timed out
>>>29.01.2013 00:19:09>>>5:192.168.71.252:80
>>>29.01.2013 00:19:09>>>3:
>>>29.01.2013 00:19:09>>>0:192.168.71.252:80
>>>29.01.2013 00:19:09>>>1:192.168.71.252:80
>>>29.01.2013 00:19:09>>>2:IPv4
>>>29.01.2013 00:19:09>>>7:
>>>29.01.2013 00:19:09>>>5:192.168.71.252:80
>>>29.01.2013 00:19:09>>>11:6317
>>>29.01.2013 00:19:09>>>6:
>>>29.01.2013 00:19:09>>>10:450
>>>29.01.2013 00:19:09>>>6:
>>>29.01.2013 00:19:09>>>10:450
>>>29.01.2013 00:19:09>>>6:
>>>29.01.2013 00:19:09>>>10:450
>>>29.01.2013 00:19:09>>>6:
>>>29.01.2013 00:19:09>>>10:450
>>>29.01.2013 00:19:09>>>6:
>>>29.01.2013 00:19:09>>>10:450
>>>29.01.2013 00:19:09>>>6:
>>>29.01.2013 00:19:09>>>10:450
>>>29.01.2013 00:19:09>>>6:
>>>29.01.2013 00:19:09>>>10:450
>>>29.01.2013 00:19:09>>>6:
>>>29.01.2013 00:19:09>>>10:450
>>>29.01.2013 00:19:09>>>6:
>>>29.01.2013 00:19:09>>>10:450
>>>29.01.2013 00:19:09>>>6:
>>>29.01.2013 00:19:09>>>10:450
>>>29.01.2013 00:19:09>>>6:
>>>29.01.2013 00:19:09>>>10:130
>>>29.01.2013 00:19:09>>>6:
>>>29.01.2013 00:19:09>>>13:10054,Connection reset by peer
>>>29.01.2013 00:19:09>>>3:
(1)
Logout OK
Boost OK
0 -> Brenner ist bereits eingeschaltet
Send Mail OK
Login OK
MailCount: 0
Logout ...
OK
CheckMail OK
-- No Mail --
Login OK
MailCount: 0
Logout ...
OK
CheckMail OK
-- No Mail --
Login OK
MailCount: 0
Logout ...
OK
CheckMail OK
-- No Mail --
Login OK
MailCount: 0
Logout ...
OK
CheckMail OK
-- No Mail --
Login OK
MailCount: 0
Logout ...
OK
CheckMail OK
-- No Mail --
Stopped 29.01.2013 00:19:40
>>>29.01.2013 00:19:40>>>3:
I:\Lazarus_Projekte\heizung>
HTTPSend.Sock.OnStatus Log on ARM:
Login OK
MailCount: 1
Mail No. 1:
From: Michael Schnell
To:
heiz...@bschnell.de
Subject: test1
Date: 28-1-13 22:56:41
Body Lines: 9
Deleting Mail No. 1...
OK
Logout ...
OK
CheckMail OK
Sender = Michael Schnell : OK
boost
Command = 1
>>>3:
>>>0:192.168.71.252:80
>>>1:192.168.71.252:80
>>>2:IPv4
>>>7:
>>>5:192.168.71.252:80
>>>11:157
>>>6:
>>>10:450
>>>6:
>>>10:450
>>>6:
>>>10:450
>>>6:
>>>10:450
>>>6:
>>>10:450
>>>6:
>>>10:450
Re: [fpc-devel] Synapse hangs in ARM-Linux
I'll do another test and report... -Michael ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
