FPCUPdeluxe hangs on `fpmake`
lazarus / 1-Linux

----------------------------------------------------------------------
yay · 2024-03-12 09:45

Hello all,

I'm interested in  trying out FreePascal, so for the last few days
(not a good sign) I have been trying to install the thing, and it
straight up doesn't work. Attempting to install FPC and Lazarus
"stable" on Ubuntu 22.04 with FPCUPdeluxe (v2.4.0d build 492) does a
bunch of stuff then hangs indefinitely (and, yes, I mean indefinitely,
unless there is some planet where compiling should take more than 12
hours) on the following line:

`./fpmake compile --threads=16 --localunitdir=.. --os=linux
--cpu=x86_64 -o -Ur -o -Xs -o -O2 -o -n -o -Cg -o -Sg -o -vw-n-h-l-d-
u-t-p-c- -o -dx86_64 -o -dRELEASE --compiler=/home/user/Applications/F
PCUPdeluxe/stable/fpcsrc/compiler/ppcx64 -bu -o -XX -o -CX`

Now, to my eye, the `ppcx64` at the end of the path there stands out
as being blatantly wrong, but what do I know about build systems? Next
to nothing, and I'd ideally like for it to remain that way.

Is this really the recommended way of installing FPC/Lazarus? What
have I done wrong?

Thank you kindly in advance.

----------------------------------------------------------------------
dbannon · 2024-03-12 11:04

fpupdeluxe is a recommended way to install FPC/Lazarus. There are
others.

Your U22.04 has the current compiler, FPC322 available in its repo. If
its just a superficial "trying out" even the Lazarus in the repo would
be OK. But I'd recommend you update it if and when you are convinced
its a good thing.

With your repo installed FPC, you could very easily install Lazarus
3.2 from source, remove the Repo lazarus, download the source, one
command. Maybe a few more to set things up.

You can also get deb packages from source forge. So lots of options.
https://wiki.freepascal.org/Installing_Lazarus_on_Linux

(And you can bet fpudeluxe will be fixed soon and it will be a good
option again.)

Davo

----------------------------------------------------------------------
TRon · 2024-03-12 12:03

Quote from: this-sucks on March 12, 2024, 10:45:53 amI'm interested
in  trying out FreePascal, so for the last few days (not a good sign)
I have been trying to install the thing, and it straight up doesn't
work.
Not that it matter much or is of interest to you but "it works for me"
tm

Code: [Select]info: FPC Native Installer (GetModule: FPC): Start
checkout/update of FPC sources.
info: FPC Native Installer (GitClient: FPC): Running GIT checkout or
update of tag release_3_2_2.
info: Performing SVN/GIT/HG/FTP/URL checkout/download. Please wait,
could take some time.
Start of compile error summary.
fatal: No annotated tags can describe
'0d122c49534b480be9284c21bd60b53d99904346'.
Executing: /usr/bin/git describe HEAD (working dir:
/media/ramdisk/install/fpcsrc)
info: FPC Native Installer (GitClient: FPC): Current commit name:
release_3_2_2.
info: FPC Native Installer (GitClient: FPC): Current commit message:
requiredversion to 3.2.0 and 3.2.2git-svn-id: tags/release_3_2_2@49371
-.
info: FPC Native Installer (GetModule: FPC): FPC was at revision/hash:
FRET_UNKNOWN_REVISION.
info: FPC Native Installer (GetModule: FPC): FPC is now at
revision/hash: 0d122c49.
Start of compile error summary.
fatal: No annotated tags can describe
'0d122c49534b480be9284c21bd60b53d99904346'.
Executing: /usr/bin/git describe HEAD (working dir:
/media/ramdisk/install/fpcsrc)
info: FPC Native Installer (GetModule: FPC): No FPC patches defined.
info: FPC Native Installer (BuildModule: FPC): Going to build FPC.
info: FPC Native Installer (BuildModule: FPC): Detected source version
FPC (source): 3.2.2.
info: FPC Native Installer (BuildModule: FPC): To compile this FPC, we
need (required) a compiler with version 3.2.0 or 3.2.2.
info: FPC Native Installer (BuildModule: FPC): FPCUP bootstrapper was
not available. Found another one. Going to it: /home/scripts/fpc.
info: FPC Native Installer (BuildModule: FPC): To compile this FPC, we
will use the (already available) compiler with version : 3.2.2.
info: FPC Native Installer (BuildModuleCustom: FPC): Using FPC
bootstrap compiler with version: 3.2.2.
info: FPC Native Installer (BuildModuleCustom: FPC): Running
CleanModule once more, due to previous clean failure.
info: FPC Native Installer (CleanModule: FPC): Running make distclean
twice.
info: FPC Native Installer (CleanModule: FPC): Removal of stale build
files and directories for x86_64-linux. May take a while.
info: FPC Native Installer (BuildModule: FPC): Now building FPC.
info: FPC Native Installer (CreateFPCScript): Creating fpc script:.
info: FPC Native Installer (CreateFPCScript): Created launcher script
for FPC:/media/ramdisk/install/fpc/bin/x86_64-linux/fpc.sh.
info: FPC Native Installer (BuildModule: FPC): Found valid fpcmkcfg
executable in /media/ramdisk/install/fpc/bin/x86_64-linux.
info: FPC Native Installer (BuildModule: FPC): Creating
/media/ramdisk/install/fpc/bin/x86_64-linux/fp.cfg.
info: FPC Native Installer (BuildModule: FPC): Creating
/media/ramdisk/install/fpc/bin/x86_64-linux/fp.ini.
info: FPC Native Installer (BuildModule: FPC): Creating
/media/ramdisk/install/fpcpkgconfig/fppkg.cfg.
info: FPC Native Installer (BuildModule: FPC): Creating
/media/ramdisk/install/packages.fppkg/config/default.
info: FPC Native Installer (BuildModule: FPC): Creating
/media/ramdisk/install/fpc/bin/x86_64-linux/fpc.cfg.
info: FPC Native Installer (BuildModule: FPC): Creating/checking
default configuration file(s) success.
info: FPC Native Installer (BuildModule: FPC): Going to tune fpc.cfg
to our needs.
info: FPC Native Installer (BuildModule: FPC): Removal of stale build
files and directories for x86_64-linux. May take a while.
info: Lazarus Native Installer (CheckModule: Lazarus): Checking
Lazarus sources with Git Client.
info: Lazarus Native Installer (GetModule: Lazarus): Start
checkout/update of Lazarus sources.
info: Lazarus Native Installer (GitClient: Lazarus): Running GIT
checkout or update of tag lazarus_3_2.
info: Performing SVN/GIT/HG/FTP/URL checkout/download. Please wait,
could take some time.
info: Lazarus Native Installer (GitClient: Lazarus): Current commit
name: lazarus_3_2.
info: Lazarus Native Installer (GitClient: Lazarus): Current commit
message: LazUtils: Remove WriteLn() from
TStringListUTF8Fast.InsertItem. Causes trouble on Windows.(cherry
picked from commit 2c81dff5d9d1b945cc15bb7420e343420e89ce63).
info: Lazarus Native Installer (GetModule: Lazarus): Lazarus was at
revision/hash: FRET_UNKNOWN_REVISION.
info: Lazarus Native Installer (GetModule: Lazarus): Lazarus is now at
revision/hash: 9c6333cd.
info: Lazarus Native Installer (GetModule: Lazarus): No Lazarus
patches defined.
info: Lazarus Native Installer (ConfigModule: Lazarus): Created
Lazarus primary config directory:
/media/ramdisk/install/config_lazarus.
info: Lazarus Native Installer (BuildModuleCustom: Lazbuild): Running:
make lazbuild.
info: Lazarus Native Installer (BuildModuleCustom: UserIDE): Now
building UserIDE.
info: Lazarus Native Installer (BuildModuleCustom: UserIDE): Running
lazbuild to get IDE with user-specified packages.
info: Lazarus Native Installer (BuildModuleCustom: StartLazarus):
Running: make starter.
info: Universal Installer (GetModule: suggestedpackages): Getting
module suggestedpackages.
info: Universal Installer (GetModule: suggestedpackages): No
suggestedpackages patches defined.
info: Universal Installer (ConfigModule: suggestedpackages): Packages
were installed.
info: Universal Installer (ConfigModule: suggestedpackages): Going to
rebuild Lazarus.
info: Universal Installer (ConfigModule: suggestedpackages): Running
lazbuild to get IDE with user-specified packages.
info: Universal Installer (BuildModule: suggestedpackages): Going to
build suggestedpackages running all InstallExecute commands in:
Name=suggestedpackages,"Description=""Selection of various IDE
packages that can be handy when developing""",Enabled=1,AddPackage1=$(
lazarusdir)/components/tdbf/dbflaz.lpk,AddPackage2=$(lazarusdir)/compo
nents/fpcunit/ide/fpcunitide.lpk,AddPackage3=$(lazarusdir)/components/
daemon/lazdaemon.lpk,AddPackage4=$(lazarusdir)/components/leakview/lea
kview.lpk,AddPackage5=$(lazarusdir)/components/tachart/tachartlazarusp
kg.lpk,AddPackage6=$(lazarusdir)/components/codetools/ide/cody.lpk,Add
Package7=$(lazarusdir)/components/sdf/sdflaz.lpk,AddPackage8=$(lazarus
dir)/components/projecttemplates/projtemplates.lpk,AddPackage9=$(lazar
usdir)/components/sqldb/sqldblaz.lpk,AddPackage10=$(lazarusdir)/compon
ents/memds/memdslaz.lpk,AddPackage12=$(lazarusdir)/components/jcf2/Ide
Plugin/lazarus/jcfidelazarus.lpk,AddPackage13=$(lazarusdir)/components
/chmhelp/packages/idehelp/chmhelppkg.lpk,AddPackage14=$(lazarusdir)/co
mponents/instantfpc/instantfpclaz.lpk,AddPackage15=$(lazarusdir)/compo
nents/externhelp/externhelp.lpk,AddPackage16=$(lazarusdir)/components/
datetimectrls/datetimectrls.lpk,AddPackage17=$(lazarusdir)/components/
datetimectrls/design/datetimectrlsdsgn.lpk,AddPackage18=$(lazarusdir)/
components/lazcontrols/design/lazcontroldsgn.lpk,Category=miscellaneou
s.
info: Universal Installer (GetModule: fpdebug): Getting module
fpdebug.
info: Universal Installer (GetModule: fpdebug): No fpdebug patches
defined.
info: Universal Installer (ConfigModule: fpdebug): Packages were
installed.
info: Universal Installer (ConfigModule: fpdebug): Going to rebuild
Lazarus.
info: Universal Installer (ConfigModule: fpdebug): Running lazbuild to
get IDE with user-specified packages.
info: Universal Installer (BuildModule: fpdebug): Going to build
fpdebug running all InstallExecute commands in:
Name=fpdebug,"Description=""FpDebug is a debugger written in Pascal
for Pascal.""",Enabled=1,AddPackage=$(lazarusdir)/components/lazdebugg
ers/lazdebuggerfp/lazdebuggerfp.lpk,Category=miscellaneous.
info: Lazarus Native Installer (BuildModuleCustom: InstallLazarus):
Skipping install step: Lazarus source and install locations are the
same.
fpcupdeluxe: Done !!

QuoteAttempting to install FPC and Lazarus "stable" on Ubuntu 22.04
with FPCUPdeluxe (v2.4.0d build 492) does a bunch of stuff then hangs
indefinitely (and, yes, I mean indefinitely, unless there is some
planet where compiling should take more than 12 hours) on the
following line:
Debian bookworm here and no it does not take 12 hours, just a couple
of minutes.

Quote`./fpmake compile --threads=16 --localunitdir=.. --os=linux
--cpu=x86_64 -o -Ur -o -Xs -o -O2 -o -n -o -Cg -o -Sg -o -vw-n-h-l-d-
u-t-p-c- -o -dx86_64 -o -dRELEASE --compiler=/home/user/Applications/F
PCUPdeluxe/stable/fpcsrc/compiler/ppcx64 -bu -o -XX -o -CX`
I got the same line:
Quote./fpmake compile --threads=4 --localunitdir=.. --os=linux
--cpu=x86_64 -o -Ur -o -Xs -o -O2 -o -n -o -Cg -o -Sg -o -vw-n-h-l-d-
u-t-p-c- -o -dx86_64 -o -dRELEASE
--compiler=/media/ramdisk/install/fpcsrc/compiler/ppcx64 -bu -o -XX -o
-CX
Since you made it clear that you prefer to not want to know anything
about the buildsystem there is no use explaining.

QuoteNow, to my eye, the `ppcx64` at the end of the path there stands
out as being blatantly wrong, but what do I know about build systems?
Next to nothing, and I'd ideally like for it to remain that way.
In that case it is not recommended to use fpcupdeluxe, rather use the
prebuild package(s) instead.

QuoteWhat have I done wrong?
Not enough memory/diskspace assigned to your VM ?

----------------------------------------------------------------------
DonAlfredo · 2024-03-12 13:09

QuoteNow, to my eye, the `ppcx64` at the end of the path there stands
out as being blatantly wrongWould be interesting to know why this is
supposed to be wrong.

----------------------------------------------------------------------
marcov · 2024-03-12 13:32

Does fpcdeluxe check development essentials ?

Afaik fpmake is the first dynamically linked binary in the process, so
missing glibc related files (that are then silently omitted) might
cause problems?

----------------------------------------------------------------------
DonAlfredo · 2024-03-12 13:46

QuoteDoes fpcdeluxe check development essentials ?Some. But only to my
best of knowledge.
You might give some advice about this. Thanks.

----------------------------------------------------------------------
yay · 2024-03-12 14:25

Quote from: DonAlfredo on March 12, 2024, 02:09:34 pmQuoteNow, to my
eye, the `ppcx64` at the end of the path there stands out as being
blatantly wrongWould be interesting to know why this is supposed to be
wrong.

PPC to me means "PowerPC". But again, I know nothing about build
systems.

Despite my admittedly combative initial tone, I'm still interested in
FreePascal, and curious to know why this install process didn't work.
Toolchain management is a beautiful thing, hence why I was excited to
see this kind of tool available, especially as my interests in Pascal
lie strongly in the embedded domain (Arduino, ESP32, RISC V, &c.),
which I will most likely start another topic for.

For now, I've installed the .deb files as per dbannon's suggestion and
am playing around in Lazarus now. It's interesting.

In addition to getting to the bottom of this specific issue, I would
appreciate any nudges toward getting things working for Arduino, if
indeed that is possible.

Thank you all so far for your time and attention.

----------------------------------------------------------------------
TRon · 2024-03-12 14:29

Quote from: marcov on March 12, 2024, 02:32:25 pmDoes fpcdeluxe check
development essentials ?
Aren't the mentioned prerequisites not sufficient enough to have that
covered ?

----------------------------------------------------------------------
marcov · 2024-03-12 14:57

Quote from: TRon on March 12, 2024, 03:29:55 pmQuote from: marcov on
March 12, 2024, 02:32:25 pmDoes fpcdeluxe check development essentials
?
Aren't the mentioned prerequisites not sufficient enough to have that
covered ?

Build-essentials meta package is enough I think. That afaik includes
glibc-devel. But does fpcdeluxe check these requirements, or are they
only requirements to start fpcdeluxe (rather than support building
with it) ?

----------------------------------------------------------------------
Thaddy · 2024-03-12 15:28

build-essentials are afaik in every FPC distribution. It contains
things like gnu make, external linker. etc, etc.
It may be not literally in the distribution but e.g. on linux it is
installed as a dependency.

----------------------------------------------------------------------
marcov · 2024-03-12 15:54

The OP doesn't state that he installed a standalone FPC before
attempting to run fpcdeluxe.

So the question is did he install build-essentials ?

----------------------------------------------------------------------
yay · 2024-03-12 16:18

Quote from: marcov on March 12, 2024, 04:54:11 pmThe OP doesn't state
that he installed a standalone FPC before attempting to run fpcdeluxe.

I didn't. Though now that I do have 3.2.2 installed via the .deb as
stated above, nothing has changed in FPCUPdeluxe.

Quote from: marcov on March 12, 2024, 04:54:11 pmSo the question is
did he install build-essentials ?

Yes, many, many moons ago.

Also, for posterity, all options and combinations (of the many that I
have tried by now out of curiosity) in FPCUPdeluxe stall at the exact
same place, i.e. invocation of `./fpmake compile`.

----------------------------------------------------------------------
yay · 2024-03-12 16:23

Perhaps it is worth mentioning that I am using FPCUPdeluxe via the
binary available at
https://github.com/LongDirtyAnimAlf/fpcupdeluxe/releases/tag/v2.4.0d,
in case there is some extra instruction required that I somehow keep
missing.

----------------------------------------------------------------------
TRon · 2024-03-12 16:28

Quote from: this-sucks on March 12, 2024, 05:18:35 pmAlso, for
posterity, all options and combinations (of the many that I have tried
by now out of curiosity) in FPCUPdeluxe stall at the exact same place,
i.e. invocation of `./fpmake compile`.
If you are truly running on a normal system (not VM, not building
on/at a remote drive etc) then you could try (not even sure if you can
indicate it with FPCUpDeluxe) to run in single thread instead of the
16 it is now, and only for testing purpose (the normal buildsystem did
had issues with that in the past).

And to make sure are you absolutely positively certain that you have
selected stable/stable ?  (other combinations not being stable might
fail and for whatever reason though a complete hang is rare in my
experience).

Note that in case FPCUpDeluxe was ever used before and setting were
changed that it might be possible that new/fresh used FPCUpdeluxe pick
up on older settings so try and make certain that the settings are
configured to use the default options because there are a couple of
things you can configure in the setup+ that might influence things
(for the worse).

Quote from: this-sucks on March 12, 2024, 05:23:58 pmPerhaps it is
worth mentioning that I am using FPCUPdeluxe via the binary available
at
https://github.com/LongDirtyAnimAlf/fpcupdeluxe/releases/tag/v2.4.0d,
in case there is some extra instruction required that I somehow keep
missing.
Same binary here.

Select the one that matches your system, select a proper destination
to install to, select stable, stable from the lists at the left and
press the install FPC and Lazarus button. That is normally enough to
get things going.

That is assuming you installed all the mentioned prerequisites (and as
stated you did).

----------------------------------------------------------------------
yay · 2024-03-12 16:42

Yes, I am absolutely, positively certain that I have selected
stable/stable, though also making sure to select literally anything
else makes no difference.

I've tried nuking all files created by FPCUPdeluxe (at least all that
I'm aware of), which also seems not to make any difference.

Any other suggestions as to what is fundamentally causing this problem
are welcome. Only thing I won't do is nuke the whole system, as this
is my production machine and I need it to eat.

----------------------------------------------------------------------
Thaddy · 2024-03-12 16:50

Did you also purge the hidden directories? These contain the config
files.
Usually they are in ~/
Type ls -a to view if these are still there and remove them too.

----------------------------------------------------------------------
yay · 2024-03-12 17:01

I don't see any hidden files/folders that seem to have anything to do
with fpcud.

----------------------------------------------------------------------
DonAlfredo · 2024-03-12 17:05

Fpcupdeluxe only checks (runtime) for the availability of a native
assembler, GNU make and GIT. That might not be enough. And is
certainly not enough to build Lazarus.
However, install-scripts are also available. It is recommended to run
this script before using fpcupdeluxe.

https://github.com/LongDirtyAnimAlf/fpcupdeluxe/blob/master/installscr
ipts/debian.sh

Ps: there are no hidden files; all is located in the install-
directory.

----------------------------------------------------------------------
yay · 2024-03-12 17:13

Quote from: DonAlfredo on March 12, 2024, 06:05:10 pmFpcupdeluxe only
checks (runtime) for the availability of a native assembler, GNU make
and GIT. That might not be enough. And is certainly not enough to
build Lazarus.
However, install-scripts are also available. It is recommended to run
this script before using fpcupdeluxe.

https://github.com/LongDirtyAnimAlf/fpcupdeluxe/blob/master/installscr
ipts/debian.sh

Ps: there are no hidden files; all is located in the install-
directory.

I already ran that, but there was nothing in that script that wasn't
already present on my system.

----------------------------------------------------------------------
TRon · 2024-03-12 19:04

Could a trace perhaps provide useful information ?

----------------------------------------------------------------------
PascalDragon · 2024-03-12 20:30

Quote from: this-sucks on March 12, 2024, 03:25:49 pmQuote from:
DonAlfredo on March 12, 2024, 02:09:34 pmQuoteNow, to my eye, the
`ppcx64` at the end of the path there stands out as being blatantly
wrongWould be interesting to know why this is supposed to be wrong.

PPC to me means "PowerPC". But again, I know nothing about build
systems.
Just for clarification: the ppc is a prefix for “Pascal Parser &
Compiler” (or something along those lines) and is the same for all
platforms. After that follows the specific platform of the compiler
(in this case x64 for the x86_64 platform). The PowerPC compiler is
named ppcppc for 32-bit PowerPC, ppcppc64 for 64-bit PowerPC or
ppcppc64le for 64-bit PowerPC Little Endian.

----------------------------------------------------------------------
marcov · 2024-03-12 20:35

Quote from: PascalDragon on March 12, 2024, 09:30:07 pmJust for
clarification: the ppc is a prefix for “Pascal Parser & Compiler” (or
something along those lines)

Portable Pascal Compiler, actually.

----------------------------------------------------------------------
PascalDragon · 2024-03-12 20:54

Quote from: marcov on March 12, 2024, 09:35:14 pmQuote from:
PascalDragon on March 12, 2024, 09:30:07 pmJust for clarification: the
ppc is a prefix for “Pascal Parser & Compiler” (or something along
those lines)

Portable Pascal Compiler, actually.

Thanks  Maybe I'll get to remember it this time till I'll need it
again in some years

----------------------------------------------------------------------
marcov · 2024-03-12 21:10

Quote from: PascalDragon on March 12, 2024, 09:54:26 pmThanks  Maybe
I'll get to remember it this time till I'll need it again in some
years

You don't think of it any time you run the compiler? Ouch

----------------------------------------------------------------------
TRon · 2024-03-12 21:11

Quote from: marcov on March 12, 2024, 09:35:14 pmPortable Pascal
Compiler, actually.
Thank you very much for that explanation.

I always wondered what the first P meant.

----------------------------------------------------------------------
dbannon · 2024-03-12 23:15

I just used fpcupdeluxe to install release FPC and Lazarus on a clean
U22.04 VM without problems. I added the usual dependencies but not
using DonAlfredo's script because I did not want to wait around for
Qt5 and Qt6.

( DonAlfredo, do you also install a libqt6Pas library ?  Systems like
U22.04 won't have one of their own and (excepting Trixie and maybe
arch) ones that do will have an old one. And the local libqt5pas won't
work with Laz3 either ....
Oh, and libgtk2.0-0-dev ? wots that ? )

Anyway, all worked here.

this-sucks (and I don't like your username), have you some 'alien'
binutils ?  I note you play with the Arduino, I have seen kits around
with the utils names without the $TARGET prefix, if fpcupdeluxe is
finding those, then it sure would be unhappy. If you can build,
locally anything, anyhow, thats not the case.

Otherwise, I suppose we have to assume there is something distinct
about your system. But I understand you are using a VM (good) but a
long term experimental one ?  Other 'interesting' things installed ? 
I keep a clean VM of each OS, then clone it to make a short term
experimental VM, blow that away when finished.

Davo

----------------------------------------------------------------------
TRon · 2024-03-12 23:36

In addition to dbannon's post,

note that in case you indeed use a VM and use a shared directory on
the host for your installation that the filesystem used by the VM can
act differently and which can cause issues (issues of similar nature
were reported and confirmed but in that case you would have seen a lot
of other file-system related errors as well)

----------------------------------------------------------------------
DonAlfredo · 2024-03-13 06:08

@dbannon
The QT6 lib can be found inside this archive.
https://github.com/LongDirtyAnimAlf/fpcupdeluxe/releases/download/cros
slibs_all/Linux_AMD64_Ubuntu_2204.zip

----------------------------------------------------------------------
dbannon · 2024-03-13 12:48

Quote from: DonAlfredo on March 13, 2024, 07:08:20
am......Linux_AMD64_Ubuntu_2204.zip

Wow, have you really collected all the (eg) Qt6 libraries for [how
many] Linux distributions ?  For each current release ? When do you
get time to sleep ?

Thats amazing. Github won't let me see the directory listing of https:
//github.com/LongDirtyAnimAlf/fpcupdeluxe/releases/download/crosslibs_
all so I cannot see how many you have in there. But I won't complain
any more about having to maintain 26 VMs for testing my app !

Davo

----------------------------------------------------------------------
yay · 2024-03-13 14:38

Some interesting info in here, but unfortunately still no luck getting
any of this to work.

By the way, future people, DO NOT run `strace` with fpcud—it rendered
my gui completely useless until my computer was reset.

I should clarify a few things:

I am not running a VM, but rather a normal install. There is nothing
esoteric or exotic about my install, though it does, perhaps, as some
sort of hail-mary attempt at concluding this silliness, bear
mentioning that I am actually using Pop!_OS 22.04, and not, strictly
speaking, Ubuntu.

----------------------------------------------------------------------
TRon · 2024-03-13 16:33

Quote from: yay on March 13, 2024, 03:38:57 pmI should clarify a few
things:
Thank you. I just made a (wrong) assumption based on the naming scheme
you used (which is very un-linuxy and more windowsy   )

QuoteI am actually using Pop!_OS 22.04, and not, strictly speaking,
Ubuntu.
That should not (have to) matter. I did not hear you mention running
something esoteric.

It is still strange though. If it would really be a (generic) problem
then I assume more people would have had complained about the issue
(so there might be something off)

Thank you for mentioning that strace "killed" your GUI, I was not sure
if it could be of help. Unfortunately that is all the approaches I can
think of atm unless compiling with debug info (-glh) would be able to
shed a light.

To be able to determine it is not related to FPCUpDeluxe (which I
think it isn't) the only way to make sure is compile manually from
source (as intended) but that does require more of your time to get
yourself more acquainted with the build-system (see also wiki, but I
personally think the instructions there are rather confusing and at
times even contradictory for someone new).

----------------------------------------------------------------------
yay · 2024-03-13 19:08

An early suggestion that's stuck in my brain had something to do with
limiting the number of cores upon which FPC compiled as part of some
known issue. Is there a way to test that theory with fpcud?

----------------------------------------------------------------------
TRon · 2024-03-13 23:15

Quote from: yay on March 13, 2024, 08:08:03 pmAn early suggestion
that's stuck in my brain had something to do with limiting the number
of cores upon which FPC compiled as part of some known issue. Is there
a way to test that theory with fpcud?
afaik, setup+ then uncheck use jobs for gnu make /then/ press the
install button

----------------------------------------------------------------------
yay · 2024-03-14 04:37

Quote from: TRon on March 14, 2024, 12:15:46 amafaik, setup+ then
uncheck use jobs for gnu make /then/ press the install button

That did it. Hooray! Now that we know the specific nature of the
error, perhaps we can figure out how to rectify it and take advantage
of all those juicy modern cores on my juicy modern processor.

Also worth noting for future people: Lazarus appears to be
incompatible with installs of FPC from the .deb, as attempting to
rebuild the Lazarus as resulted from the recent successful fpcud
install with "Normal IDE" profile results in the error `cannot find
clocale used by lazarus`. Temporarily renaming `/usr/lib/fpc` seems to
indicate that this is, indeed, the root of the issue. So now we have
one more thing to investigate.

----------------------------------------------------------------------
TRon · 2024-03-14 05:00

Quote from: yay on March 14, 2024, 05:37:48 amThat did it. Hooray!
Thank you for the feedback.

I haven't seen this particular issue being reported for quite some
time now so more or less assumed it was fixed...

----------------------------------------------------------------------
DonAlfredo · 2024-03-14 05:58

Good find !
FYI.
The use of jobs is, by default, disabled on Win64, due to errors that
were reported in the past.
This might also de done for (linux) arm and aarch64, to prevent the
current issue. However, I have not encountered this problem myself
(RPi2-5) yet.