Recent

Author Topic: Trunk 3.3.1 access violation  (Read 1231 times)

peter.dell

  • New Member
  • *
  • Posts: 16
Trunk 3.3.1 access violation
« on: April 25, 2024, 01:38:41 am »
Hello,

I'm new to the forum, so this may be the wrong place to post. Please advise if that's the case.
I've pulled the latest 3.3.1 from Git and during the "make all" I get this error at 30% completion:

make all
....
Target OS: Win32 for i386
Compiling fppkg\pkglnet.pp
PPU Loading fppkg\units\i386-win32\lftp.ppu
pkglnet.pp(10,9) Fatal: Can't find unit lftp used by pkglnet
Fatal: Compilation aborted

  $00427393
  $00427651
  $0042C1FF
  $0042C6B6
  $0042DA4C
  $0042D427
  $0042E278
  $0042680C
  $00407E11
make[2]: *** [Makefile:2904: all] Error 1
make[2]: Leaving directory '/cygdrive/c/jac/system/Windows/Programming/Repositories/fpc/utils'
make[1]: *** [Makefile:3090: utils_all] Error 2
make[1]: Leaving directory '/cygdrive/c/jac/system/Windows/Programming/Repositories/fpc'
make: *** [Makefile:3294: build-stamp.i386-win32] Error 2

Any suggestion on what I could do?

Kind regards, Peter-


JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4479
  • I like bugs.
Re: Trunk 3.3.1 access violation
« Reply #1 on: April 25, 2024, 08:16:41 pm »
I'm new to the forum, so this may be the wrong place to post. Please advise if that's the case.
I've pulled the latest 3.3.1 from Git ...
Yes it was a wrong place. This thread is about a dot release FPC 3.2.4.  Your issue is with FPC trunk (3.3.1).
Please open a new thread.
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

marcov

  • Administrator
  • Hero Member
  • *
  • Posts: 11531
  • FPC developer.
Re: Trunk 3.3.1 access violation
« Reply #2 on: April 25, 2024, 08:23:31 pm »
I splitted off the topic to save the OP work.

dbannon

  • Hero Member
  • *****
  • Posts: 2854
    • tomboy-ng, a rewrite of the classic Tomboy
Re: Trunk 3.3.1 access violation
« Reply #3 on: April 26, 2024, 02:07:05 pm »
Oh Peter, I was hoping someone who knows what they are talking about would answer but not looking good. So, I'll try...

I'll start with what you have not told us. That is, why are you using main ? I ask because main is the developmental branch, it will from time to time completely fall over. So, perhaps not a great choice for someone who might just be new to FPC ?  The developers push changes to main, often only tested on their own system, to see if they work. Its expected to be broken from time to time. Especially on less than mainstream platforms.

So, why did you choose main ?  Because you want to compile some old code you found that, when first written, needed something in main ?  If so, its likely that something is now in in the release, FPC3.2.2. So, try that perhaps ?

If you need something newer than FPC3.2,2, perhaps for something like supporting openssl 3.0, then consider FPC fixes, aka 3.2.3. Its a lot less likely to break (but no guarantee).

Really, really must have main ?  Wait a few days and download a fresh copy, maybe what ever the problem is has been fixed. Otherwise, time do do some debugging I am afraid.

Davo

Lazarus 3, Linux (and reluctantly Win10/11, OSX Monterey)
My Project - https://github.com/tomboy-notes/tomboy-ng and my github - https://github.com/davidbannon

 

TinyPortal © 2005-2018