Good day,

after compiled fpc and lazarus from the trunk branch, when I run the command ./lazarus, the configure lazarus IDE appears with the above error:

FPC sources

Directory: /usr/share/fpcsrc/2.7.1/

Error: directory not found

Please I need your help, Thanks

Isn't it clear enough? The dialog expects you to have FPC source directory and it defaults to that popped-up value, which you could override with your own.

It works here.
Something is different on your system.
Please check
/usr, /usr/share, /usr/share/fpcsrc and /usr/share/fpcsrc/2.7.1

Is any directory a symlink?
On what file system(s) are these directories?

Can you try the following small program:

{$mode objfpc}{$H+}
uses Classes, Sysutils, LazFileUtils;
begin
  writeln(DirectoryExistsUTF8('/usr/share/fpcsrc/2.7.1'));
  writeln(DirPathExists('/usr/share/fpcsrc/2.7.1/'));
end.

You have to compile it with

fpc -Fu/your/lazarus/directory/components/lazutils/lib/yourplatform/ test.pas

Please I need your help, Thanks

Mattias

leledumbo wrote

Isn't it clear enough? The dialog expects you to have FPC source directory and it defaults to that popped-up value, which you could override with your own.

After changed the path to /usr/local/lib/fpc/2.7.1/

I received a warning:

Directory: /usr/local/lib/fpc/2.7.1/

Warning: directory rtl not found

2012/11/8 Eric Kom :

After changed the path to /usr/local/lib/fpc/2.7.1/

This is not the source directory.

Judging from your previous pots you have compiled fpc from svn and sucessfully installed it. make install will only install the binaries and compiled units where they belong, it will not install the fpc source.

But the good news is you don't actually need to install it into any special place, the svn folder where you checked out fpc trunk is perfectly ok already. Simply point Lazarus to the folder that contains the fpc sources from svn and Lazarus will find what it needs there.

That's make sense.

But the good news is you don't actually need to install it into any special place, the svn folder where you checked out fpc trunk is perfectly ok already. Simply point Lazarus to the folder that contains the fpc sources from svn and Lazarus will find what it needs there.

I pointed directly to the fpc/rtl/ directory, still the warning rtl directory not fund.

Eric Kom hat am 8. November 2012 um 13:11
geschrieben:

rtl is just one sub folder of fpc.
Point it to the fpc directory.

Any suggestions how to improve the error message to make this more clear?

Mattias

Thanks a lot for your help everything is fine now

Something like "The directory you have selected does not contain subdirectories rtl, packages and so on." (don't use "etc." in this context).

Could ppcXXX return its build directory? Then provided this existed and perhaps subject to other consistency checks the IDE could suggest it as the default.

2012/11/8 Mark Morgan Lloyd :

Could ppcXXX return its build directory?

This is not a good idea. For example rpm or deb packages would contain a compiler that was compiled in some arbitrary folder and then later the sources will be copied to somewhere else by the installer.

So if I would send you a ppcross68k compiled on my development machine and you would then ask it for it's build directory it would return "/mnt/data/subversion/fpc-build". Would this help you in any way? I think not... (and this is exactly what would happen if you'd use a compiler provided through any package distribution, as you are not normally building from within "/usr/lib" or whatever.

Regards,
Sven

2012/11/8 Bernd :

Since this problem only ever occurs when fpc is installed manually (with make) it might be a better idea to provide another make target in the fpc makefile that would allow to do

sudo make installsource

that would install the sources into $(PREFIX)/share/fpcsrc/$(VERSION) the same place the installer packages would have installed it and lazarus is already looking for it and then the official instructions for installing fpc from source would contain also the above line and everybody who is following the instructions wold not have to wonder whether there is a separate procedure to install the sources or what exactly to install if installing manually, etc.

Any suggestions how to improve the error message to make this more clear?

It would be a bit long, but I hope much clearer:
"Lazarus cannot find the directory in which FPC source code is located (Lazarus assumes it is located in <write the default value here>). The directory should have at least "rtl" and "packages" directory (or more in case of full source code). If you think it's not yet installed, please download one here: <we can give one or more (direct) links here, such as sourceforge or somewhere else>"

Which is why I said "provided this existed and perhaps subject to other consistency checks", and noting that it's for use as a default if nothing has already been specified.

Exactly: that's a case where it wouldn't help so could fall back to something hardcoded. But for people who'd built locally from svn, from a numbered release or from a daily snapshot it would get it right most of the time. Of course, it wouldn't help weirdos like me who copy the sources to /usr/lib/fpc/x.x.x/fpcsrc, but I expect that I'm a minority in that.

Thanks a lot for your support