Unable to find file "datetimepicker.pas"

[eenplus]

Hello, I just installed the the latest versions of FPC (3.2.2 ) and the 3.99 IDE - screenshots attached.
I've removed (previously), all references to older installations, using PKG uninstaller, deleted the .lazarus
folder and removed all *.ppu and *.o files to make sure the installation could be done in a clean
environment. Unfortunately, whatever component I try to install, I end up with this error  message
"Unable to find file "datetimperpicker.pas".

All path's are being set default as how the installer installed them.

Bit clueless on how to resolve this.

Any help would be appreciated.

/Dirk

macOS BigSur on MacBook Air

[jamie]

if you are able to get to the IDE, navigate to the components tree in the install and look for the Datecontrls.

In that should be the file you are looking for.

Also, you can use the packager to open that package and compile it, then there should be an exposed file with bin, etc.


 You really shouldn't need to do all of this however, have you tried doing a Clean All Build on the IDE ?

[eenplus]

Hello, and sorry for net getting back sooner.

I seem to be running in circles. I did everything you suggested, but to no avail. When I do a Clean All Build on the iDE I keep on being stuck on this cannot find unit DateTimePicker.pas used by DateTimeCrtls. Preceeded by a compiler warning . Checksum changed for /Applications/Lazarus/lcl/units/x86_64_darwin/lclintf.ppu

? Now, what i do see, is quite some *.ppu files that appear twice. Maybe related to former installation of Fpcupdelux. So, before removing certain directories or files. Referencing a default install, what shoud be the correct path ?

sh-3.2# locate interfacebase.ppu
/Applications/Lazarus/lcl/units/x86_64-darwin/interfacebase.ppu
/Users/Dirk/.lazarus/lib/LCLBase/units/x86_64-darwin/interfacebase.ppu
sh-3.2#

Regards,

/Dirk

[TRon]

sh-3.2# locate interfacebase.ppu
/Applications/Lazarus/lcl/units/x86_64-darwin/interfacebase.ppu
/Users/Dirk/.lazarus/lib/LCLBase/units/x86_64-darwin/interfacebase.ppu

The above seem to suggest that you have (at one time or now with your current installation) installed Lazarus into a directory were it has/had no write rights and therefor Lazarus rebuild the units and stored them into a location where it does have write rights.

If you later (re-)installed Lazarus then I could imagine that Lazarus has some issues with that. What that most probably means in/for your current situation is that that your previous installation was not entirely cleaned up/removed before you re-installed.

My advise to provide atm and imho (note I might be wrong) is to remove everything and start from scratch and this time make sure that you have no remnants of a previous installation left. That is unless someone else has a better advise (other then build Lazarus manual and situate the Lazarus directory to somewhere where you do have full access control).

[jamie]

I am no Linux expert but I seem to remember you need to be in ROOT or SUDO xxxx to install Lazarus etc.

I could be wrong but that is my assessment. Linux is like my wife, no sense of humor!

[TRon]

I am no Linux expert but I seem to remember you need to be in ROOT or SUDO xxxx to install Lazarus etc.

Yeah, and that is exactly where the world is starting to tumble down.

Lazarus needs to rebuild itself when installing for example a new component, can't store the results in the write protected directory and circumvent that by storing the results in the configuration directory. (*)

So far, everything is alright and honky dory.

But then.. you decide to upgrade Lazarus or add another installation of Lazarus and the shit hits the fan because people seem to forget that either a) you need to clearly distinct between the two installed versions (--pcp) or b) make sure there are no remnants of another installation left.

Linux is like my wife, no sense of humor!

I wouldn't dare to comment on that but I do can tell you that you can bend the will(power) of Linux so that it starts listening to what you want. Just stay the h*ll away from those installation packages and package managers. It makes things overly complicated for nothing.

edit: * unless starting Lazarus with sudo/admin rights as well, which defeats the whole purpose of having a separated user account (with less privileges).

[eenplus]

To All,

guess I'll give it some time, and 'll do an install on another machine to find out if this issue keeps coming up.
Best solution will be, agreed upon, to do a clean install on this machine, I guess. Has been in use since 2013. A clean OS install won't hurt by now :-)

Thanks anyway for trying to help me. /Dirk