Re: [Lazarus] Problems installing Lazarus on Linux Mint

2024-07-19 Thread Wayne Sherman via lazarus
Giuliano Colla wrote:
> 2) get rid of anything related with Lazarus and fpc your distro has 
> provided...

When trying to clean out leftover fpc and lazarus files, also search
in "/etc" and "~/" ($HOME) for these:
(note that some of these are "hidden")

.fppkg (directory)
instantfpc (directory)
fppkg.cfg
fppkg.bak
fpc.cfg
fpc*.cfg
fp.ini
fp.cfg
fp*.cfg
.lazarus (directory)
lazarus* (directory)

> 3) Use fpcupdeluxe,...it might complain about some system libraries missing.

Follow the instructions here:
https://github.com/LongDirtyAnimAlf/fpcupdeluxe

The instructions list the common dependencies and provide an example
install command for debian like systems:
sudo apt install make binutils build-essential gdb subversion zip
unzip libx11-dev libgtk2.0-dev libgdk-pixbuf2.0-dev libcairo2-dev
libpango1.0-dev
-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Email sending program using Indy stopped working - seems to be an SSL problem

2024-01-13 Thread Wayne Sherman via lazarus
On Sat, Jan 13, 2024 at 9:10 AM Bo Berglund wrote:
> I searched on the net and found this:
> https://tecadmin.net/send-email-from-windows-command-line/

From:  https://learn.microsoft.com/en-us/dotnet/api/system.net.mail.smtpclient

"We don't recommend that you use the SmtpClient class for new
development because SmtpClient doesn't support many modern protocols.
Use MailKit or other libraries instead. For more information, see
SmtpClient shouldn't be used on GitHub."

References:
Mailkit:  https://github.com/jstedfast/MailKit

DE0005: SmtpClient shouldn't be used
https://github.com/dotnet/platform-compat/blob/master/docs/DE0005.md
-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] [fpc-devel] Changes to TProcess

2024-01-03 Thread Wayne Sherman via lazarus
On Wed, Jan 3, 2024 at 5:29 AM Michael Van Canneyt wrote:
> I merged a significant evolution of the TProcess component to FPC trunk...
> There is now a testsuite for the TProcess command, so everything was tested.

A much more flexible TProcess plus tests. Your work is appreciated. Thanks.  :-)
-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Running FPC in the browser...

2023-10-25 Thread Wayne Sherman via lazarus
On Sun, Oct 22, 2023 at 3:20 AM Michael Van Canneyt wrote:
> Thanks to the efforts of Nikolay Nikolov, the FPC compiler can now recompile
> itself to webassembly (the support for the goto statement made this possible).
> As a consequence, this means FPC can now be run in a browser.

Very nice.  Thank you to all who worked on this.
-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Simple ipc server fatal error on start - 0xc000007b

2023-04-01 Thread Wayne Sherman via lazarus
On Fri, Mar 31, 2023 at 9:38 AM Bo Berglund wrote:
> What I want to do is...use the D7 app to read a hardware device on command
> and send the data to the Lazarus app.

You probably don't need the extra complication of IPC, sockets, COM,
or OLE automation.  Instead of creating a D7 app, build a D7 DLL which
exports the function(s) you need.  Import the DLL function(s) to your
Lazarus app and call them directly.
-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] version `GLIBC_2.34' not found error when running app on different PC

2023-03-17 Thread Wayne Sherman via lazarus
On Thu, Mar 16, 2023 at 4:36 PM Bo Berglund wrote:
> when I try to run it:
> videosplitcmb: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found
> (required by videosplitcmb)

There was a discussion and related bug report on this issue:

https://forum.lazarus.freepascal.org/index.php/topic,5.0.html
https://gitlab.com/freepascal.org/fpc/projects/-/issues/3
-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] make all compilation error after 319649fb (Attn: Martin)

2023-01-09 Thread Wayne Sherman via lazarus
On Sun, Jan 8, 2023 Marcus Sackrow wrote:
> make all for at least x86_64-linux does not compile since 319649fb

On Mon, Jan 9, 2023 Martin Frb wrote:
> There is "make" (aka "make all" ?) and "make bigide".

If there is an automatic job for "make all", it apparently did not
catch the build failure reported by Marcus.

On Mon, Jan 9, 2023 at 3:35 PM Maxim Ganetsky via lazarus
 wrote:
> It is no problem to add some `make useride` job. In principle, we can
> even switch e. g. x86_64-win64 job to this (to avoid crowding even more
> our already huge job list).

Another option, if you don't want to create more jobs, is to string
build tests together on the same job:
#pseudocode
make all || echo 'make all failed'; exit 1
make distclean || echo 'make distclean failed'; exit 2
make useride || echo 'make useride failed'; exit 3
-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] make all compilation error after 319649fb (Attn: Martin)

2023-01-08 Thread Wayne Sherman via lazarus
> > make all for at least x86_64-linux does not compile since 319649fb
> thanks it compiles again

About a week ago Lazarus was failing to build with "make useride".
Are these two build targets being run as part of the CI / CD tests?
-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Error building Lazarus Trunk

2023-01-01 Thread Wayne Sherman via lazarus
On Sun, Jan 1, 2023 at 1:51 AM Ondrej Pokorny wrote:
> Ok , 2nd attempt :)
> https://gitlab.com/freepascal.org/lazarus/lazarus/-/commit/71ac105bc728824b849c027a016ad572226002c1

Yes, that fixed it. Thank you.

The build problem was not caught by any of the CI/CD jobs that ran.
To catch failures with lazbuild, should a test be added to CI/CD jobs
to build the Lazarus IDE with it?
-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Error building Lazarus Trunk

2022-12-31 Thread Wayne Sherman via lazarus
> Bisecting: 0 revisions left to test after this (roughly 0 steps)
> [ba918c5eb21b04bc00b7bb12909360f40ee738d4] TLazIDEInterface: add
> OnPackageBuilding handler

Sorry, I did not actually test that last selected commit.  After doing
one more iteration it did turn out to be that commit:

ba918c5eb21b04bc00b7bb12909360f40ee738d4 is the first bad commit
commit ba918c5eb21b04bc00b7bb12909360f40ee738d4
Author: Ondrej Pokorny 
Date:   Fri Dec 30 22:43:17 2022 +0100

TLazIDEInterface: add OnPackageBuilding handler

 components/ideintf/lazideintf.pas | 41 ++-
 packager/packagesystem.pas|  4 
 2 files changed, 44 insertions(+), 1 deletion(-)
-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Error building Lazarus Trunk

2022-12-31 Thread Wayne Sherman via lazarus
> wayne wrote:
> Sorry, getting the same error:

Using git bisect, it seems the failure started happening with this commit:
https://gitlab.com/freepascal.org/lazarus/lazarus/-/commit/ba918c5eb21b04bc00b7bb12909360f40ee738d4

#start a bisect procedure
git bisect start
git bisect bad 2fb475adfb2d124b8b3f6072bb924988150bf2af (*
Instantsearch package)
git bisect good eb59ad598f624f10b273c65630f021d5a9e3cf8c (JCF:
regenerated translations and updated Russian translation)

#repeat these steps
make lazbuild
make useride
git bisect bad (if make useride runs correctly)
git bisect good (if make useride fails)
- iterate until we get this -

Bisecting: 0 revisions left to test after this (roughly 0 steps)
[ba918c5eb21b04bc00b7bb12909360f40ee738d4] TLazIDEInterface: add
OnPackageBuilding handler
-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Error building Lazarus Trunk

2022-12-31 Thread Wayne Sherman via lazarus
> Ondrej Pokorny wrote:
> Please update and retest. It should be fixed.

Sorry, getting the same error:

cd ~/2022-12-31_lazarus_trunk
git fetch origin
git reset --hard origin/main

git log --name-status HEAD^..HEAD
commit 09845999ff4ee6424b4cee11c589d7cfcbe45857 (HEAD -> main,
origin/main, origin/HEAD)
Author: Ondrej Pokorny 
Date:   Sun Jan 1 03:06:58 2023 +0100

fix AV

M   components/ideintf/lazideintf.pas

make distclean [ok]
make lazbuild  [ok]
make bigide [ok]

./lazbuild --lazarusdir=. --build-ide=
Hint: (lazarus) Compiler unit paths changed for DebuggerIntf 0.1
  
Old="/home/wsherman/2022-12-31_lazarus_trunk/packager/units/x86_64-linux;/home/wsherman/2022-12-31_lazarus_trunk/components/lazdebuggers/lazdebuggerintf/lib/x86_64-linux;/home/wsherman/2022-12-31_lazarus_trunk/components/lazutils/lib/x86_64-linux;/home/wsherman/2022-12-31_lazarus_trunk/components/freetype/lib/x86_64-linux;/home/wsherman/2022-12-31_lazarus_trunk/lcl/units/x86_64-linux;/home/wsherman/2022-12-31_lazarus_trunk/components/debuggerintf"
  
Now="/home/wsherman/2022-12-31_lazarus_trunk/packager/units/x86_64-linux;/home/wsherman/2022-12-31_lazarus_trunk/components/lazdebuggers/lazdebuggerintf/lib/x86_64-linux;/home/wsherman/2022-12-31_lazarus_trunk/components/lazutils/lib/x86_64-linux;/home/wsherman/2022-12-31_lazarus_trunk/components/debuggerintf"
  State 
file="/home/wsherman/2022-12-31_lazarus_trunk/components/debuggerintf/lib/x86_64-linux/DebuggerIntf.compiled"
An unhandled exception occurred at $009B6FB0:
EAccessViolation: Access violation
  $009B6FB0  DOCALLPACKAGEBUILDINGHANDLER,  line 774 of lazideintf.pas
  $005AFCAA  COMPILEPACKAGE,  line 4265 of ../packager/packagesystem.pas
  $005AE928  COMPILEREQUIREDPACKAGES,  line 3972 of
../packager/packagesystem.pas
  $0040366A  COMPILEAUTOINSTALLPACKAGES,  line 683 of lazbuild.lpr
  $004032A9  BUILDLAZARUSIDE,  line 621 of lazbuild.lpr
  $0040817F  RUN,  line 1503 of lazbuild.lpr
  $0040AA09  main,  line 1879 of lazbuild.lpr

make useride
./lazbuild --lazarusdir=. --build-ide=
Hint: (lazarus) Missing state file of DebuggerIntf 0.1:
/home/wsherman/2022-12-31_lazarus_trunk/components/debuggerintf/lib/x86_64-linux/DebuggerIntf.compiled
An unhandled exception occurred at $009B6FB0:
EAccessViolation: Access violation
  $009B6FB0  DOCALLPACKAGEBUILDINGHANDLER,  line 774 of lazideintf.pas
  $005AFCAA  COMPILEPACKAGE,  line 4265 of ../packager/packagesystem.pas
  $005AE928  COMPILEREQUIREDPACKAGES,  line 3972 of
../packager/packagesystem.pas
  $0040366A  COMPILEAUTOINSTALLPACKAGES,  line 683 of lazbuild.lpr
  $004032A9  BUILDLAZARUSIDE,  line 621 of lazbuild.lpr
  $0040817F  RUN,  line 1503 of lazbuild.lpr
  $0040AA09  main,  line 1879 of lazbuild.lpr

make: *** [Makefile:3804: useride] Error 217
-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


[Lazarus] Error building Lazarus Trunk

2022-12-31 Thread Wayne Sherman via lazarus
System Xubuntu 20.04 64-bit with latest updates

lazarus_2_2_4 (latest stable) builds successfully, but I am getting an
error trying to build Lazarus trunk.  The same error happens with both
fpc stable and fpc trunk.

Running this:

git clone https://gitlab.com/freepascal.org/lazarus/lazarus.git
2022-12-31_lazarus_trunk
cd ./2022-12-31_lazarus_trunk

make distclean [ok]
make lazbuild  [ok]
make bigide [ok]

make useride  [fails]
./lazbuild --lazarusdir=. --build-ide=  [fails]

Build messages:
Hint: (lazarus) Missing state file of DebuggerIntf 0.1:
/home/wsherman/2022-12-31_lazarus_trunk/components/debuggerintf/lib/x86_64-linux/DebuggerIntf.compiled
An unhandled exception occurred at $009B6FB0:
EAccessViolation: Access violation
  $009B6FB0  DOCALLPACKAGEBUILDINGHANDLER,  line 774 of lazideintf.pas
  $005AFCAA  COMPILEPACKAGE,  line 4265 of ../packager/packagesystem.pas
  $005AE928  COMPILEREQUIREDPACKAGES,  line 3972 of
../packager/packagesystem.pas
  $0040366A  COMPILEAUTOINSTALLPACKAGES,  line 683 of lazbuild.lpr
  $004032A9  BUILDLAZARUSIDE,  line 621 of lazbuild.lpr
  $0040817F  RUN,  line 1503 of lazbuild.lpr
  $0040AA09  main,  line 1879 of lazbuild.lpr

There appears to be two problems:
1) Some state is not as lazbuild expects.
2) lazbuild should not generate an access violation.

Can anyone confirm this issue?
-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] How to list available serial orts on Ubuuntu?

2022-11-28 Thread Wayne Sherman via lazarus
> My solution has been to scan all possible port names, such
> as /dev/ttyS*, dev/ttyUSB*, /dev/ttyXR*, etc. and then attempt
> to open each one by using SerOpen (in Serial.pp from fpcsrc- add
> "Serial"  the Uses clause) If successful the port exists, and I add
> it to my list, if not, it doesn't exist.

If the port is in use (already open in another process), you will get
a SerOpen error and incorrectly exclude that port.

Some other ways to find Linux serial ports are discussed here:
https://stackoverflow.com/questions/2530096/how-to-find-all-serial-devices-ttys-ttyusb-on-linux-without-opening-them
-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus