Mac OS X:
10.5 to 10.12; Carbon (32bit), Cocoa (64bit, not stable), qt and qt5 (32 or 64bit).
Free Pascal Compiler version 3.0.4rc1 [2017/06/29] for x86_64
Copyright (c) 1993-2017 by Florian Klaempfl and others
Target OS: Linux for x86-64
Compiling lazres.pp
Linking ./lazres
/usr/bin/ld: warning: ./link.res contains output sections; did you forget -T?
/usr/bin/ld: /home/peter/fpc-3.0.4/lib/fpc/3.0.4/units/x86_64-linux/rtl/cprt0.o: unrecognized relocation (0x2a) in section `.text'
/usr/bin/ld: final link failed: Bad value
Error: Error while linking
Impressive long list of fixes. When taking Lazarus RC4 tag out of the repository, is there somewhere a fpc 3.0.4 for Win32/64 installer available?FPC 3.0.4 RC1:
FPC 3.0.4 RC1:
http://forum.lazarus.freepascal.org/index.php/topic,37609.0.html
Impressive long list of fixes. When taking Lazarus RC4 tag out of the repository, is there somewhere a fpc 3.0.4 for Win32/64 installer available?
The Lazarus RC4 installer for win contains FPC 3.0.4rc1
AFAIK every Lazarus installer for Windows installs fpc as well.But Bart, it is the underestimated art of UNinstalling that is always the problem...The installer should uninstall (both previous and itself) . It doesn't..Must I get grumpy? Ask!
You can look in the the fpc 3.0.4RC1 released topic (http://forum.lazarus.freepascal.org/index.php/topic,37609.0.html) for download links.
Bart
it is the underestimated art of UNinstalling that is always the problem...The installer should uninstall (both previous and itself) . It doesn't..Must I get grumpy? Ask!....
RC4 have fixed only a part of the bugs reported in https://bugs.freepascal.org/view.php?id=32097 ("Weird-looking IDE (esp. Object Inspector) and tiny icons on high-DPI displays with scaling=300%").
Need I report that as a new bugreport? Or should I somewhat revive the old one (which is marked as resolved)?
I hope the Unity tray icon (https://bugs.freepascal.org/view.php?id=32258) gets fixed in the next oneYou write in the report: "I cannot reproduce it,..."
I hope the Unity tray icon (https://bugs.freepascal.org/view.php?id=32258) gets fixed in the next oneYou write in the report: "I cannot reproduce it,..."
Sorry but how do you expect others to reproduce the problem if you cannot do it even yourself?
Did it work well in RC3?
If you start the IDE from a console (shell/terminal) are there any errors printed out?
NOTE: Window with stalled focus found!, faking focus-out event
[USER] Invalid borders specified for theme pixmap:
/usr/share/themes/Breeze/gtk-2.0/../assets/line-h.png,
borders don't fit within the image
TSourceEditCompletion.ccExecute nil
In case: Did you recompile the IDE, what setting (specially -O# ?) did you use?
Something is wrong with the source editor drawing on gtk2/opensuse.May be a GTK2 version dependent problem in Suse. It uses the QT based KDE. I guess your editor starts to work when you compile the IDE for QT.
Very unlikely to help, but you can also try to compile with
-dVerboseSynEditInvalidate
Then in the output look for
CustomSynEdit.InvalidateTextLines .... FirstLine=11 LastLine=12 rect=....
Where 11 would be the line in the window (0 or 1 based).
This is not the textline. the window always starts with line 1 on top (or 0)....
Then when you edit, the relevant lines should get an invalidate.
The rect should give the area in pixels.
TCustomSynEdit.InvalidateTextLines SynEdit10:TIDESynEditor FirstLine=663 LastLine=663
TCustomSynEdit.InvalidateTextLines TLazSynTextArea FirstLine=662 LastLine=662 rect=l=65,t=1083,r=1102,b=666
TCustomSynEdit.InvalidateTextLines TLazSynTextArea FirstLine=662 LastLine=662 rect=l=65,t=0,r=1102,b=0
TCustomSynEdit.InvalidateTextLines SynEdit10:TIDESynEditor
TCustomSynEdit.InvalidateTextLines SynEdit10:TIDESynEditor FirstLine=630 LastLine=630
TCustomSynEdit.InvalidateTextLines TLazSynTextArea FirstLine=629 LastLine=629 rect=l=65,t=456,r=1102,b=475
TCustomSynEdit.InvalidateTextLines TLazSynTextArea FirstLine=629 LastLine=629 rect=l=65,t=0,r=1102,b=0
TCustomSynEdit.InvalidateTextLines SynEdit10:TIDESynEditor
TCustomSynEdit.InvalidateGutterLines SynEdit8:TIDESynEditor FirstLine=15 LastLine=15
TCustomSynEdit.InvalidateGutterLines TLazSynGutterArea FirstLine=14 LastLine=14 rect=l=0,t=266,r=57,b=285
TCustomSynEdit.InvalidateGutterLines TLazSynGutterArea FirstLine=14 LastLine=14 rect=l=1122,t=266,r=1135,b=285
TCustomSynEdit.InvalidateGutterLines TSourceLazSynSurfaceGutter FirstLine=14 LastLine=14 rect=l=0,t=0,r=57,b=0
TCustomSynEdit.InvalidateGutterLines TSourceLazSynSurfaceGutter FirstLine=14 LastLine=14 rect=l=1122,t=0,r=1135,b=0
TCustomSynEdit.InvalidateGutterLines SynEdit8:TIDESynEditor
TCustomSynEdit.InvalidateGutterLines SynEdit8:TIDESynEditor FirstLine=16 LastLine=16
TCustomSynEdit.InvalidateGutterLines TLazSynGutterArea FirstLine=15 LastLine=15 rect=l=0,t=285,r=57,b=304
TCustomSynEdit.InvalidateGutterLines TLazSynGutterArea FirstLine=15 LastLine=15 rect=l=1122,t=285,r=1135,b=304
TCustomSynEdit.InvalidateGutterLines TSourceLazSynSurfaceGutter FirstLine=15 LastLine=15 rect=l=0,t=0,r=57,b=0
TCustomSynEdit.InvalidateGutterLines TSourceLazSynSurfaceGutter FirstLine=15 LastLine=15 rect=l=1122,t=0,r=1135,b=0
TCustomSynEdit.InvalidateGutterLines SynEdit8:TIDESynEditor
TCustomSynEdit.InvalidateTextLines SynEdit8:TIDESynEditor FirstLine=15 LastLine=15
TCustomSynEdit.InvalidateTextLines TLazSynTextArea FirstLine=14 LastLine=14 rect=l=57,t=266,r=1122,b=285
TCustomSynEdit.InvalidateTextLines TLazSynTextArea FirstLine=14 LastLine=14 rect=l=57,t=0,r=1122,b=0
TCustomSynEdit.InvalidateTextLines SynEdit8:TIDESynEditor
Trying to get back to normal programming with the new versions I notice that if errors occur which are caught in LCL files on a break it does not reuse a copy of the file already opened but opens a new editor instance of the file with the postfix (2) against the name.Is it about symlinked files? Is it a regression?
When you drop FBAdmin on a new project (just empty form) you start having problems when you run and close. Also you get errors when you try to delete that component.Yes if it can be reproduced. Is it a regression?
Shall I file a bug?
The Lazarus team is glad to announce the fourth release candidate of
Lazarus 1.8.
Two outstanding bugs from 1.6.x: (a) projectgroup panel is still forgetting to load the last project group when you open LazIs this reported?
and (b): Laz crashes whenever I switch from two monitors back down to one. This happens when I'm on my docked laptop using two monitors and I undock the laptop. Laz invariably crashes.Can you get a debugger backtrace?
Quoteand (b): Laz crashes whenever I switch from two monitors back down to one. This happens when I'm on my docked laptop using two monitors and I undock the laptop. Laz invariably crashes.Can you get a debugger backtrace?
One thing you can still try:
components\synedit\syneditpointclasses.pas
line 2884...After the whole ifdef, set FForcePaintEvents := True;
procedure TSynEditScreenCaretPainterInternal.Init; begin {$IFDEF LCLCarbon} FForcePaintEvents := True; ...
So it is always true.
It must be something severe, if it upsets your x server enough to crash it.
Trying to get back to normal programming with the new versions I notice that if errors occur which are caught in LCL files on a break it does not reuse a copy of the file already opened but opens a new editor instance of the file with the postfix (2) against the name.Is it about symlinked files?
I know most people don't use the CLASSIC THEME and even if they use it, they probably don't change the standard font, so I guess nobody really cares about this.
FForcePaintEvents := True;
It has not happened, since I put that there, but I have not used Lazarus much in the time
Hey and surely this would be hip in some near future :DI know most people don't use the CLASSIC THEME and even if they use it, they probably don't change the standard font, so I guess nobody really cares about this.
The 90s are calling :o
@RAW: The reported bug is fixed in Lazarus Trunk and has shown some more font issues on Windows 7 / 10 / themed / not themed / High-DPI scaled / not High-DPI scaled, that should be fixed now. So thank you for reporting it!THANK YOU very much for fixing it !!! :)
FForcePaintEvents := True;
It has not happened, since I put that there, but I have not used Lazarus much in the time
Ok, so that needs to be added for gtk2 then. (will do next week)
Right now I'm playing around with FPCupDeluxe to get a nice install so that I can test it...Do you just need Lazarus trunk? You don't need FPCupDeluxe for that. FPC is a little more difficult and for it I also recommend FPCupDeluxe.
Never used this program... normally I don't allow any internet connection from the admin account, but I think I cannot install on a user account... let's see...Yes you can install both FPC and Lazarus using FPCupDeluxe with user account.
Yes you can install both FPC and Lazarus using FPCupDeluxe with user account.Yes.. tried it ... that's nice. (unfortunately I get too many errors.. right now I don't have time to go through it step by step..)
...or similar things with TortoiseSVN etc.I've got the r55758 files dowloaded with TortoiseSVN. I know it's only the first step but better than nothing... was very easy...
I don't understand MAKE // tried "make" and "make bigide" and "make clean bigide"... I get 1600+ error messages... (syntax error)Maybe you have Delphi installed. It comes with an incompatible "make" binary. There is a warning about it here:
e:\fpc311\bin\x86_64-win64\make bigide
The Delphi make is simply necessary in some Delphi scenarios, like compiling their system.pas.Why would somebody compile Delphi's system.pas? :)
Why would somebody compile Delphi's system.pas? :)Oh, multiple reasons:
Don't remove it. Use full path for fpc make. The Delphi make is simply necessary in some Delphi scenarios, like compiling their system.pas.@Thaddy: Thank you very much... works fine... should have tried this right away... :)
But it is correct that he has Delphi's make in a path before the gnu make. So it gets called first.
I use it like this:
Code: [Select]
e:\fpc311\bin\x86_64-win64\make bigide
Russian text...This is an international site, please write in English, for example, use online translators.
thanks ! But the translator can't convey my thoughts))Russian text...This is an international site, please write in English, for example, use online translators.
This problem has already been reported: https://bugs.freepascal.org/view.php?id=32266 (https://bugs.freepascal.org/view.php?id=32266).
В Windows если свернуть Lazarus и развернуть пропадает окно Form остальные окна видно! Приходится заходить проект - формы и выбирать форму ((If I minimize and restore IDE in Windows then the Form pane disappearing (others visible). Must choose "Project" - "Forms" and select the form to activate it.
The Lazarus team is glad to announce the fourth release candidate of
Lazarus 1.8.
....
Mac OS X:
10.5 to 10.12; Carbon (32bit), Cocoa (64bit, not stable), qt and qt5 (32 or 64bit).
Code: [Select]/home/theo/hg/components/pascal/internettools.pas(12,23) Hint: (5023) Unit "xquery__functions" not used in internettools
(1008) 134046 lines compiled, 10.8 sec
(1021) 45 warning(s) issued
(1022) 207 hint(s) issued
(1023) 28 note(s) issued
lazbuild: ../nptl/pthread_mutex_lock.c:117: __pthread_mutex_lock: Zusicherung »mutex->__data.__owner == 0« nicht erfüllt.
/home/theo/hg/programs/internet/xidel/../../../manageUtils.sh: line 156: 21985 Abgebrochen (core dumped) lazbuild $1 $LPI
I'm using linuxmint17 with kde5/plasma.
Whenever I close or restart lazarus, it crashes plasma and the desktop reloads.
Not really a show stopper, but it looks very clunky.
Yeah. Plasma sounds alpha quality. Apps shouldn't be able to crash the windowmanager.That is a little outdated information. Plasma was alpha quality at the time of Linux Mint 17.
I personally use a rolling Manjaro. A rolling SparkyLinux, based on Debian testing, is also good.I also prefer Manjaro but I had to give up on it on Apollo Lake because it kept freezing randomly even with several latest kernels. Linux Mint with backported kernel and Debian testing worked very well, but I gave up on Debian testing because it strangely didn't have Kodi, and building from source had too many problems. So I ended up with Debian stable, although it was awful out of the box until 4.12 was installed. I looked at Sparky but couldn't find anything worth using it over Debian, so I wonder what did you see in it that I missed? Maybe that would be worth another look?
I also prefer Manjaro but I had to give up on it on Apollo Lake because it kept freezing randomly even with several latest kernels.Oh, surprising! I even recommended an "Apollo Lake" Intel N3450 based mini-PC to a person. I myself still have Celeron N3000 in my main computer, ASRock Beebox. It is the earlier Braswell generation. No problems with Manjaro.
Linux Mint with backported kernel and Debian testing worked very well, but I gave up on Debian testing because it strangely didn't have Kodi, and building from source had too many problems.Surprising again. A web search tells you can install it from:
So I ended up with Debian stable, although it was awful out of the box until 4.12 was installed.You mean the older Linux kernels lacked some HW drivers? Otherwise the differences between kernels in a desktop system are difficult to notice.
I looked at Sparky but couldn't find anything worth using it over Debian, so I wonder what did you see in it that I missed? Maybe that would be worth another look?Good question. The main difference was that Sparky is rolling and Debian is not.
Tested with kernel 4.12 and 4.13. Result was the same. Apollo Lake is supported since 4.10, unfortunately only Manjaro was freezing randomly on GIGABYTE GA-J3455N-D3H with 16GB RAM and 8TB HDD, so I had to give up on it after numerous fails to make it stable. Memory was tested with Memtest86+ 5.01 for several days without problems. System is mostly used as a backup server and home media center.I also prefer Manjaro but I had to give up on it on Apollo Lake because it kept freezing randomly even with several latest kernels.Oh, surprising! I even recommended an "Apollo Lake" Intel N3450 based mini-PC to a person. I myself still have Celeron N3000 in my main computer, ASRock Beebox. It is the earlier Braswell generation. No problems with Manjaro.
I could imagine a new kernel coming with rolling Manjaro would work better on a new CPU.
Strangely apt-get can't find Kodi for installation in Debian testing. Look here: https://packages.debian.org/search?keywords=kodi&searchon=names&suite=testing§ion=allQuoteLinux Mint with backported kernel and Debian testing worked very well, but I gave up on Debian testing because it strangely didn't have Kodi, and building from source had too many problems.Surprising again. A web search tells you can install it from:
http://www.deb-multimedia.org/
although I didn't test it myself.
No, I mean that Debian stable comes with 4.09 and Apollo Lake is supported in 4.10. Therefore whole installation process until backporting 4.12 was a frustration, since mouse was erratic and every few seconds the whole system was frozen for 5-10 seconds. That ment that installation took 6-7 looong hours. After 4.12 was installed there were no further problems. I wanted to avoid that by using Debian testing (which had good kernel for Apollo Lake), but had to give up when I found that Kodi was not in available packages and installation from source was abandoned after fixing dozen of problems but more and more were coming. I have to mention that Linux Mint worked well out of the box, but I decided to go for LMDE. Unfortunately I couldn't make LMDE to work at all, so I ended up with Debian stable instead. Lazarus doesn't have any problems with XFCE (unlike with Cinnamon), so that was another reason (I know how to install another desktop manager but I prefer if distro already has my favorite).QuoteSo I ended up with Debian stable, although it was awful out of the box until 4.12 was installed.You mean the older Linux kernels lacked some HW drivers? Otherwise the differences between kernels in a desktop system are difficult to notice.
Somehow I missed that very important feature. I will take another look at Sparky, although I will probably stay with Debian stable on Apollo Lake. For my specific use case of Apollo Lake, rolling release might not be such a good idea after all.QuoteI looked at Sparky but couldn't find anything worth using it over Debian, so I wonder what did you see in it that I missed? Maybe that would be worth another look?Good question. The main difference was that Sparky is rolling and Debian is not.
I'm using linuxmint17 with kde5/plasma.
Whenever I close or restart lazarus, it crashes plasma and the desktop reloads.
Not really a show stopper, but it looks very clunky.
and almost always find that the elements of the forms overlaps with labels and other text when i run the programs in different linuxes/wm... almost everytime i change linux to develop/run i have to redisign the forms and move away the components of forms to avoid their overlap.
Is there any solution to this? or its a linux font problem?
almost everytime i change linux to develop/run i have to redisign the forms and move away the components of forms to avoid their overlap.
Is there any solution to this? or its a linux font problem?
Before the next release could you please fix the long standing bug relating to
the failure of the lazarus uses clause to recognise relative paths in the lpr file.
eg: uses '../../commonfiles/fred.pas'
(clicking the units button shows all files but clicking on the files fails to open them)
eg: uses '../../commonfiles/fred.pas'
I really like the new release candidate, but I found a problem :)
After compiling a weblaz HTTP server application which was created with Lazarus 1.6.4 the project does not work anymore.
The routing seems to not work correctly. The HTTP server just responses
:Module Error The application encountered the following error: Error: Not found
It seems like the routing is not working, I cannot reach any of the existing OnRequest Methods of the TFPWebModule.
The bug is really easy to produce. Just install weblaz (shipped with Lazarus 1.8RC4), and create a new HTTP server application. A simple test does not even require the use of actions, you can just create the following OnRequest method:
procedure TFPWebModule1.DataModuleRequest(Sender: TObject; ARequest: TRequest; AResponse: TResponse; Var Handled: Boolean); begin AResponse.Content:='This test is working, great :)'; AResponse.Code:=200; Handled:=True; end;
Thank you for your work :)
https://bugs.freepascal.org/view.php?id=32266The report has had questions for over 2 months but they are not answered.