View previous topic :: View next topic |
Author |
Message |
BenHinkle
Joined: 27 Mar 2004 Posts: 76
|
Posted: Sun Mar 20, 2005 6:22 am Post subject: -I not working on linux |
|
|
It looks like -I doesn't work on linux. If I try
Code: | build sample.d -I.. -v |
I get a command-line
Code: | Running '/home/bhinkle/dmd/bin/dmd "-v" "-op" "-version=Posix" "-I"/"" "-I"/home/bhinkle/dmd/src/phobos"" "-c" "sample.d" ' |
which seems to have lost my "..". The quoting also looks strange to me: should "-I"/"" be "-I/".
As a side question why is it adding root to the include path anyway? I would think the user should have to do that explicitly if they need root. |
|
Back to top |
|
|
Derek Parnell
Joined: 22 Apr 2004 Posts: 408 Location: Melbourne, Australia
|
Posted: Sun Mar 20, 2005 8:29 am Post subject: Re: -I not working on linux |
|
|
BenHinkle wrote: | It looks like -I doesn't work on linux. If I try
Code: | build sample.d -I.. -v |
I get a command-line
Code: | Running '/home/bhinkle/dmd/bin/dmd "-v" "-op" "-version=Posix" "-I"/"" "-I"/home/bhinkle/dmd/src/phobos"" "-c" "sample.d" ' |
which seems to have lost my "..". |
Not really. It converted the ".." into the real path value. As it is showing "/" then all I can assume is that your CWD at the time was "/something" and thus ".." relative that that is simply "/".
What did you expect when you used -I..? Maybe I'm misunderstanding something.
BenHinkle wrote: | The quoting also looks strange to me: should "-I"/"" be "-I/". |
Yep. I was told by somebody else that the quotes needed to go after the "-I" but I forgot to then not quote the entire switch. I've fixed that now.
BenHinkle wrote: | As a side question why is it adding root to the include path anyway? I would think the user should have to do that explicitly if they need root. |
If by root, you mean the path "/" then I've explained that above. _________________ --
Derek
skype name: derek.j.parnell |
|
Back to top |
|
|
BenHinkle
Joined: 27 Mar 2004 Posts: 76
|
Posted: Sun Mar 20, 2005 8:40 am Post subject: Re: -I not working on linux |
|
|
Derek Parnell wrote: |
Not really. It converted the ".." into the real path value. As it is showing "/" then all I can assume is that your CWD at the time was "/something" and thus ".." relative that that is simply "/". |
My cwd was /home/bhinkle/d/minwin. Maybe there is a bug in expanding cwd?
Derek Parnell wrote: | What did you expect when you used -I..? Maybe I'm misunderstanding something. |
I really wanted -I../.. but when that didn't work I tried -I.. and that didn't work either. Basically I couldn't get -I to work. |
|
Back to top |
|
|
Derek Parnell
Joined: 22 Apr 2004 Posts: 408 Location: Melbourne, Australia
|
Posted: Sun Mar 20, 2005 9:34 am Post subject: Re: -I not working on linux |
|
|
BenHinkle wrote: | Derek Parnell wrote: |
Not really. It converted the ".." into the real path value. As it is showing "/" then all I can assume is that your CWD at the time was "/something" and thus ".." relative that that is simply "/". |
My cwd was /home/bhinkle/d/minwin. Maybe there is a bug in expanding cwd?
Derek Parnell wrote: | What did you expect when you used -I..? Maybe I'm misunderstanding something. |
I really wanted -I../.. but when that didn't work I tried -I.. and that didn't work either. Basically I couldn't get -I to work. |
Ok, I'll look through it again, but later today. I'll keep you posted. _________________ --
Derek
skype name: derek.j.parnell |
|
Back to top |
|
|
Derek Parnell
Joined: 22 Apr 2004 Posts: 408 Location: Melbourne, Australia
|
Posted: Sun Mar 20, 2005 9:45 pm Post subject: Re: -I not working on linux |
|
|
Derek Parnell wrote: | Ok, I'll look through it again, but later today. I'll keep you posted. |
Found it! I assumed that getcwd() would return a string whose last character was the path separator ( / in Unix and \ in Windows). Needless to say, it doesn't But anyway, its working now.
The release should happen later today. _________________ --
Derek
skype name: derek.j.parnell |
|
Back to top |
|
|
|