Sign in Join

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

Mailing lists / fpc-devel / 2006-07

FPC 2.0.4 release candidate 1 testing

8 messages · 5 people · –

Reply by email Subscribe to this list Your subscription

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

Jonas Maebe

Hello,

As part of our effort to make the upcoming release 2.0.4 as bug-free as possible, we'd like to invite some of you to testing our release candidates.

To make things as efficient as possible, we'd like to involve 1-2 people for every platform in the first phase. In next phases we plan to extend testing to wider audience.

If you are interested and have time for thorough testing of installation, command-line compiler and text-mode IDE (or, in case of Mac OS X, Xcode integration) in next few weeks, please add your contact and information about your platform (CPU, OS and particular version of OS/distribution) to
http://www.freepascal.org/wiki/index.php/Testers_2.0.4.

The downloads are available from
ftp://ftp.freepascal.org/fpc/beta/2.0.4-rc1/

Available platforms for 2.0.4-rc1 are:
* Dos
* Linux/i386 and Linux/ppc32 (no deb or rmp, only tar.gz)
* Mac OS X/ppc32 (Xcode integration should also work for Mac OS X/Intel)
* OS/2
* Win32

This list will be expanded for 2.0.4-rc2 and the final 2.0.4.

Thanks,

Jonas

Reply by email

Tomas Hajny

Hello,

As a follow-up to previous message sent by Jonas
(see below), I'd like to ask whether there's
anybody interested in testing of Win32 and
powerpc-linux versions, and at least one more
person for i386-linux.

Tomas

------- Forwarded message follows -------
To: FPC developers' list
From: Jonas Maebe
Date sent: Sun, 9 Jul 2006 19:54:00 +0200
Subject: [fpc-devel] FPC 2.0.4 release candidate 1 testing Send reply to: FPC developers' list

[ Double-click this line for list subscription options ]

Hello,

As part of our effort to make the upcoming release 2.0.4 as bug-free as possible, we'd like to invite some of you to testing our release candidates.

To make things as efficient as possible, we'd like to involve 1-2 people for every platform in the first phase. In next phases we plan to extend testing to wider audience.

If you are interested and have time for thorough testing of installation, command-line compiler and text-mode IDE (or, in case of Mac OS X, Xcode integration) in next few weeks, please add your contact and information about your platform (CPU, OS and particular version of OS/distribution) to
http://www.freepascal.org/wiki/index.php/Testers_2.0.4.

The downloads are available from
ftp://ftp.freepascal.org/fpc/beta/2.0.4-rc1/

Available platforms for 2.0.4-rc1 are:
* Dos
* Linux/i386 and Linux/ppc32 (no deb or rmp, only tar.gz)
* Mac OS X/ppc32 (Xcode integration should also work for Mac OS X/Intel)
* OS/2
* Win32

This list will be expanded for 2.0.4-rc2 and the final 2.0.4.

Thanks,

Jonas

Reply by email

���� ����������� � mail.ru
to Tomas Hajny

TH> Hello,
TH> As a follow-up to previous message sent by Jonas TH> (see below), I'd like to ask whether there's
TH> anybody interested in testing of Win32 and

It's the first bunch of comments. Almost everything is cosmetical.

Win32, Windows98SE, some general comments, one LCD monitor IDE Win-XP comment.

FPC was run from FAR commander shell (under Win98 it masks itself as DOS program due to Win98 lame console problems).

*. There are two html docs archives in 2.0.4 ftp download area. They have strange lengths and one of them is not named according to its contents. (They are shared-2.0.2 and "normal".)

*. Install does not hint to add path to environment (but it is mentioned in README).

*. "Readme" file to read does not list Win64 (but mentions it before and after).

*. cygwin1.dll version would better be listed explicitly in readme (for example, it's older together with API than 1.5.19.4 which I downloaded some time ago). The fact the IDE uses cygwin is not mentioned even in IDE readme file! The same goes to binary utilities (why don't mention them in README?).

*. IDE does not look as nice as it pretends (in its README) at high resolution (in WIN-XP console): it does not support big number of columns (even 160). It looks bad in WIN-XP console on LCD monitor at higher resolutions because of almost invisible cursor if you hold an arrow key.

*. IDE states that it is in beta stage in its README, but does not tell it in the Help-About.

DEMO comments

*. You have to type "fpc hello" in demo\text directory, not just demo as README tells.

*. Make demo fails. The reason is broken win32\menu.pp file. Adding "{" in the beginning fixes the first error.

*. Make demo still fails. The reason is broken lister.pas file. Changing line 265 (changing ",+" to something like ",D[D.Cursor]+") helps.

*. Make demo finally succeded. But there were some warnings. Do they DEMOnstrate good programming style.

*. Demo\graph\gravwars has a problem with initial screen width (title does not fit). It draws circles too slow, and missiles --- too fast. It does not leave task list if you exit it by closing a window (simply pressing "X" in upper right corner under Win98).

*. Demo\graph\mandel does not leave task list if you exit it by closing a window (simply pressing "X" in upper right corner under Win98).

*. Demo\graph\maze may have screen size problems. It switches to graphical window and waits for input in text window. Also it suggest wrong keys: IJKMX instead of UpLeftRightDownEsc. It does not leave task list if you exit it by closing a window (simply pressing "X" in upper right corner under Win98).

*. Demo\graph\quad is confusing (help is needed or something).

*. Demo\graph\samegame expects something like alt+shift before entering highscore name. It's confusing. (I was not in non-english keyboard mode.) It does not leave task list if you exit it by closing a window (simply pressing "X" in upper right corner under Win98).

*. Demo\lister is a simple file shell with ability to delete files. It should have some help on the starting screen.

*. Demo\modex would better be in some go32v2 subdirectory.

*. Demo\text\blackbox would better display some help. And the help in blackbox.pp comments is faulty.

*. Demo\text\eratos may write output to display for a long time. It would demonstrate speed by creating text file. Why don't add "eratos.bat"="eratos.exe > PrimesFrom1To1000000.txt" or something?

*. Demo\text\lines tells incorrect number of lines: it does not count the last line (well, it counts only the number of $10 symbols). A typical text file is really one line "longer" than told. A nonempty file is usually considered at least one line long. Well, you may disagree, because FPC uses the same technique.

*. Demo\text\magic dumps much output. It won't fit Win98 console/fullscreen text mode. It would better "readln" from time to time or dump it to a file.

*. Demo\text\qsort has both Demo\text\magic and Demo\text\eratos problems.

*. Demo\win32\dlltest does not show a readable module name.

*. Demo\win32\winhello: windows user expects a button to close the window "normally" ending the application.

--------
ppkk mail ru...

Reply by email

���� ����������� � mail.ru
to ���� ����������� � mail.ru

TH> Hello,
TH> As a follow-up to previous message sent by Jonas TH> (see below), I'd like to ask whether there's
TH> anybody interested in testing of Win32 and

It's the second bunch of comments. Almost everything is cosmetical.

Win32, Windows98SE.

FPC was run from FAR commander shell (under Win98 it masks itself as DOS program due to Win98 lame console problems).

Win98SE.

*. Install step "Select additional tasks" has obsolete vertical scroller.

EXAMPLES

Not many makefile.fpc or makefile present.

*. cdrom\getdiscid while cdrom\showcds shows device name correctly, cdrom\getdiscid defaults to unix style "/dev/cdrom" ("ASPI[0;0;0]" is more typical, and using showcds mechanism would be the most efficient way).

*. fcl\makefile is obsolete. fcl\makefile.fpc is abnormal too (change fpcdir to something and change targetdir to something like ../../units/$(FULL_TARGET)). Makefile still does not have any sense.

*. fcl\asiotest needs FPAsync, which is absent.

*. fcl\cachetest seems to grant a user with infinite complains about invalid slot^.prev.

*. fcl\dbugsrv has to define pascal mode it uses.

*. fcl\debugtest may try to be case insensitive to "STOP" command (or not).

*. fcl\dparser has to define pascal mode it uses.

*. fcl\dsockcli and fcl\dsocksvr do not compile (win98se).

*. fcl\htdump does not work as expected (its usage is not very clear and it fails with "kword.xml" from that directory [examples\fcl]).

*. an example picture for fcl\imgconv would be great.

*. fcl\list has to define pascal mode it uses.

*. fcl\showver could check if there are no command line parameters.

*. fcl\sockcli and fcl\socksvr do not compile (win98se).

*. fcl\stringl has to define pascal mode it uses.

*. fcl\testbf needs blowfish, which is absent.

*. fcl\testcgi does not handle exception.

*. fcl\testcp usage/purpose is unclear, it's name is not testopen, and it does not handle exception (e.g., with an .o file).

*. fcl\testdbf name is not dumpdb.

*. fcl\testez does not handle exception.

*. fcl\testib: add "{" in the beginning and specify pascal mode it uses.

*. fcl\testld name is not testopen.

*. fcl\testpop does not handle exception.

*. fcl\testrtf has to define pascal mode it uses.

*. fcl\testser does not handle exception.

*. fcl\tstelcmd and fcl\tstelgtk need "fclel.res", which is missing (Win98SE).

*. fcl\txmldump does not work with fpdoc.dtd in that directory (examples\fcl).

*. opengl: glutdemo would better hint you to download glut32.dll somewhere (tonow it just does not handle exception if there is none around).

*. oracle: examples do not compile, makefile.fpc causes some problems.

---------------------

ppkk mail ru...

Reply by email

Bisma Jayadi
to Jonas Maebe: As part of our effort to make the upcoming release 2.0.4 as bug-free as possible, we'd…

Just a little suggestion... I think we should inform any progress of FPC development on the website. Maybe this has been informed through the Wiki, but I believe not every visitor have time to look at the Wiki. Just like what Firebird project does, they inform every RC on the website.

Just my 2 cents. :)

-Bee-

has Bee.ography at:
http://beeography.wordpress.com

Reply by email

���� ����������� � mail.ru

Это "forwarded" письмо.

Earlier message 29 lines
From: Пётр Косаревский с mail.ru To: Joost van der Sluis Date: Wednesday, July 19, 2006, 3:47:59 AM Subject: [fpc-devel] FPC 2.0.4 release candidate 1 testing ===8<============== Исходный текст =============== >> *. oracle: examples do not compile, makefile.fpc causes some problems. JvdS> At least this last issue is fixed. I coudn't find however what's wrong JvdS> with the makefile.fpc? JvdS> Joost The problems are incorrect paths in makefile.fpc-s. For oracle examples, fpcdir=../../../.. --- it's root dir, not FPC dir on my system (changing it to ../.. helps). ATTENTION: I didn't try to fpcmake all makefile.fpc, for example: examples\opengl has the same problem. (Probably, they were in a more nested place before building the release candidate, and were copied to the current place after creating working makefiles.) ===8<===========Конец исходного текста =========== -- Постарался и переслал владелец адреса

Reply by email

Joost van der Sluis
to ���� ����������� � mail.ru
ϸòð Êîñàðåâñêèé ñ mail.ru wrote 17 lines
>> *. oracle: examples do not compile, makefile.fpc causes some problems. JvdS> At least this last issue is fixed. I coudn't find however what's wrong JvdS> with the makefile.fpc? JvdS> Joost The problems are incorrect paths in makefile.fpc-s. For oracle examples, fpcdir=../../../.. --- it's root dir, not FPC dir on my system (changing it to ../.. helps). ATTENTION: I didn't try to fpcmake all makefile.fpc, for example: examples\opengl has the same problem. (Probably, they were in a more nested place before building the release candidate, and were copied to the current place after creating working makefiles.)

No, the path is correct if you compile from the source-code of fpc. If the examples are installed, the fpcdir is indead incorrect, but that isn't important at that stage.

But I;m sure that there are others that know more about this?

Joost

Reply by email