Forum > General

Unable to find file "datetimepicker.pas" -- SOLVED -- Sort of.

(1/3) > >>

dormitionskete:
Apparently, there seem to be many people who are getting the following error when you try to build Lazarus:

Unable to find file "datetimepicker.pas"

This appears to be a problem on both Linux and MacOS.

It appears to be a file permissions problem.  When I changed the file permissions to "datetimepicker.pas", I got past that error, only to encounter another similar error.  So when I upgraded permissions to my entire Lazarus installation, it now builds.

On MacOS, I did the following as root:

sh-3.2# cd /Applications/Lazarus/
sh-3.2# pwd
/Applications/Lazarus
sh-3.2# chmod -R 777 *
sh-3.2#

This is obviously not the best way to fix it, but if the admin people will look into this more, this at least appears to be the problem, and a workaround for it.

I hope this helps.

marcos-ebm:
[using the translator]


Thank you very much, this helps me a lot

TRon:

--- Quote from: dormitionskete on January 10, 2024, 11:45:59 pm ---This appears to be a problem on both Linux and MacOS.

It appears to be a file permissions problem.  When I changed the file permissions to "datetimepicker.pas", I got past that error, only to encounter another similar error.  So when I upgraded permissions to my entire Lazarus installation, it now builds.

--- End quote ---
Yes, it is a permission issue. But using chmod is indeed not the way to solve it. You have installed Lazarus/FPC into directory where you do not have enough rights to write in. Simply change the installation directory to something more suitable (and for which you do have enough rights).

The way it imho should be fixed is that you create a directory for your installation, make a group that has (enough) access (rights) to that directory and assign yourself as a user to that group. Alternatively use FPCUpDeluxe and install FPC/Lazarus in your home directory.

Having said that, I still don't grasp why datetimepicker should be recompiled on a Lazarus installation and when it does, that it doesn't automatically defer to the alternative location where Lazarus does have enough rights to write to (there is provision for that in Lazarus in case you install 3th party components)


--- Quote ---This is obviously not the best way to fix it, but if the admin people will look into this more, this at least appears to be the problem, and a workaround for it.

--- End quote ---
It already has been addressed.

msintle:

--- Quote from: TRon on January 13, 2024, 10:48:24 pm ---
--- Quote from: dormitionskete on January 10, 2024, 11:45:59 pm ---This appears to be a problem on both Linux and MacOS.

It appears to be a file permissions problem.  When I changed the file permissions to "datetimepicker.pas", I got past that error, only to encounter another similar error.  So when I upgraded permissions to my entire Lazarus installation, it now builds.

--- End quote ---
Yes, it is a permission issue. But using chmod is indeed not the way to solve it. You have installed Lazarus/FPC into directory where you do not have enough rights to write in. Simply change the installation directory to something more suitable (and for which you do have enough rights).

The way it imho should be fixed is that you create a directory for your installation, make a group that has (enough) access (rights) to that directory and assign yourself as a user to that group. Alternatively use FPCUpDeluxe and install FPC/Lazarus in your home directory.

Having said that, I still don't grasp why datetimepicker should be recompiled on a Lazarus installation and when it does, that it doesn't automatically defer to the alternative location where Lazarus does have enough rights to write to (there is provision for that in Lazarus in case you install 3th party components)


--- Quote ---This is obviously not the best way to fix it, but if the admin people will look into this more, this at least appears to be the problem, and a workaround for it.

--- End quote ---
It already has been addressed.

--- End quote ---

Real glad to see this got noticed by more than just one person (namely, myself).

The current "release" version of Lazarus as served from the project homepage is effectively useless because of this.

Isn't it the responsibility of the installer to ensure that folder permissions are set correctly?

To clarify, this matter wasn't even an issue until the latest 3.0 version of Lazarus.

It didn't reproduce with the 2.2.6 release version, or any older versions across years, for example.

Hansaplast:
+1 seen it here as well when helping out my nephew who wanted to get started with Lazarus.
 
I'm using trunk all the time so I had not seen this issue before. So its good to see it addressed in trunk, but isn't this a fundamental problem for those using the current release version?

In other words: wouldn't it be a good idea for a new release version be uploaded so beginners do not get frustrated with Lazarus right away on their first attempt?

Navigation

[0] Message Index

[#] Next page

Go to full version