Re: [lazarus] Compile fails on project with long pathname (MacOS X)
On Wed, 24 May 2006 01:47:14 +0200 Tom Verhoeff [EMAIL PROTECTED] wrote: On Mon, May 22, 2006 at 08:07:30AM +0200, Vincent Snijders wrote: Tom Verhoeff wrote: I recently upgraded to 0.9.14 and started a project, whose code is in a deeply nested directory tree with fairly long directory names, where one of the directory names contains a space. When compiling from the ide, this fails at the assembler. It seems to report a cut off path (the part with the space is included), though this could only be in the message printed (and not in the argument that it received). Does anyone have an idea what is the problem here? There has been a similar bug report (but not the same), which I tried hard to reproduce, but could not. The bug report was closed. http://www.freepascal.org/mantis/view.php?id=900 If you are willing to help me to reproduce this error, you can submit a new bug report. I'll try, but it is not that simple. Part of the problem may be that Lazarus supplies full (absolute) paths to the compiler (at least in the way I am using it; though I did not change many options from their defaults). However, when I use fpc separately (not with Lazarus), I typically provide relative paths (which are much shorter). I added an option to the Compiler Options - Show Options dialog. And I changed the paths of the .compiled file to use relative paths. Mattias _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Compile fails on project with long pathname (MacOS X)
On Mon, May 22, 2006 at 08:07:30AM +0200, Vincent Snijders wrote: Tom Verhoeff wrote: I recently upgraded to 0.9.14 and started a project, whose code is in a deeply nested directory tree with fairly long directory names, where one of the directory names contains a space. When compiling from the ide, this fails at the assembler. It seems to report a cut off path (the part with the space is included), though this could only be in the message printed (and not in the argument that it received). Does anyone have an idea what is the problem here? There has been a similar bug report (but not the same), which I tried hard to reproduce, but could not. The bug report was closed. http://www.freepascal.org/mantis/view.php?id=900 If you are willing to help me to reproduce this error, you can submit a new bug report. I'll try, but it is not that simple. Part of the problem may be that Lazarus supplies full (absolute) paths to the compiler (at least in the way I am using it; though I did not change many options from their defaults). However, when I use fpc separately (not with Lazarus), I typically provide relative paths (which are much shorter). Tom -- E-MAIL: T.Verhoeff @ TUE.NL | Fac. of Math. Computing Science PHONE: +31 40 247 41 25| Eindhoven University of Technology FAX:+31 40 247 54 04| PO Box 513, NL-5600 MB Eindhoven http://www.win.tue.nl/~wstomv/ | The Netherlands _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Compile fails on project with long pathname (MacOS X)
Tom Verhoeff wrote: I recently upgraded to 0.9.14 and started a project, whose code is in a deeply nested directory tree with fairly long directory names, where one of the directory names contains a space. When compiling from the ide, this fails at the assembler. It seems to report a cut off path (the part with the space is included), though this could only be in the message printed (and not in the argument that it received). Does anyone have an idea what is the problem here? There has been a similar bug report (but not the same), which I tried hard to reproduce, but could not. The bug report was closed. http://www.freepascal.org/mantis/view.php?id=900 If you are willing to help me to reproduce this error, you can submit a new bug report. Vincent. _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Compile fails on project with long pathname (MacOS X)
Tom Verhoeff wrote: I recently upgraded to 0.9.14 and started a project, whose code is in a deeply nested directory tree with fairly long directory names, where one of the directory names contains a space. When compiling from the ide, this fails at the assembler. It seems to report a cut off path (the part with the space is included), though this could only be in the message printed (and not in the argument that it received). Does anyone have an idea what is the problem here? Yes, I've had all sorts of path chopping issues. Especially it occurs if you specify the -o option to the compiler along with a -k option with some long paths involved. The FPC compiler uses almost all shortstrings to pass options to the linker. The problem does not occur until a total number of options add up to 255 - but it isn't as simple as just counting all your options and adding them up to 255 - rather some options are passed to the linker (such as -o) while others are sent other places, to for example the search functions that verify directory/file location of units in the uses clause. Some limits are not even 255 but rather 50. If you read the fpc-devel list you will see what I mean when I say that I've had the same issues. It generally occurs on computers that have several hundred projects, because when you have this many projects you do use long paths - while most people out there don't have hundreds/thousands of projects on their drive so the bug never pops up - or they just learn to live with it - I had these issues since day one when I was a newbie to FPC and I was blaming it on myself since I thought it was a newbie issue of my own. As more and more projects have been placed on my hard drive, the more the bug has popped up over and over again. Back when my hard drive was not as loaded, it didn't occur much, but did occur. It will require a lot of changes to the FPC source code since FPC source is heavily reliant on shortstrings, and the compiler will be slower. All testing for this bug should be done at the command line and the bug should be reported to FPC section rather than Lazarus section. _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
[lazarus] Compile fails on project with long pathname (MacOS X)
I recently upgraded to 0.9.14 and started a project, whose code is in a deeply nested directory tree with fairly long directory names, where one of the directory names contains a space. When compiling from the ide, this fails at the assembler. It seems to report a cut off path (the part with the space is included), though this could only be in the message printed (and not in the argument that it received). Does anyone have an idea what is the problem here? Tom -- E-MAIL: T.Verhoeff @ TUE.NL | Fac. of Math. Computing Science PHONE: +31 40 247 41 25| Eindhoven University of Technology FAX:+31 40 247 54 04| PO Box 513, NL-5600 MB Eindhoven http://www.win.tue.nl/~wstomv/ | The Netherlands _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Compile fails on project with long pathname (MacOS X)
I had a (possibly) similar problem. I think it is the output directory - in other words, where the compiled files are sent. Out of interest, try creating an output directory on the drive level with a short directory path like cu for compiled units. I'm not sure it is anything to do with spaces in the directory path. I might be wrong, but I work within a deeply nested directory tree. I send my output to a Compiled Units directory normally, and the error reported a path ending in Com so I shortened my output directory to CU and it works. Duncan At 21:49 21/05/2006, you wrote: I recently upgraded to 0.9.14 and started a project, whose code is in a deeply nested directory tree with fairly long directory names, where one of the directory names contains a space. When compiling from the ide, this fails at the assembler. It seems to report a cut off path (the part with the space is included), though this could only be in the message printed (and not in the argument that it received). Does anyone have an idea what is the problem here? Tom -- E-MAIL: T.Verhoeff @ TUE.NL | Fac. of Math. Computing Science PHONE: +31 40 247 41 25| Eindhoven University of Technology FAX:+31 40 247 54 04| PO Box 513, NL-5600 MB Eindhoven http://www.win.tue.nl/~wstomv/ | The Netherlands _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
