Now I will just approach this vewy vewy quietly so no one misunderstands..........

On a Linux machine as user tytower I issue a build command as below . Because I am logged in as user, not root I cannot write to  /usr  so the compiler says I will write to  /home/tytower/d  instead. It does not in fact do this as no directory /home/tytower/d exists or is created ,Even if I create this directory it is not used. It actually write to the current directory which in this case is the same as the directory the program is in.

[tytower@linuxbox MyStuff]$ dsss build -D maintry.d
Default prefix /usr is unwritable, using /home/tytower/d instead.

Now what I am suggesting is that the message out from the compiler is ....wait for it ...wrong. Not that it worries me or there is more I don't understand , but merely to tell someone there that this exits and is ....wrong.

On Mon, 03 Mar 2008 01:53:51 -0500, Ty Tower wrote:

> Now what I am suggesting is that the message out from the compiler is ...wrong.

Yes, it looks like a mistake somewhere. I do not use Linux nor DSSS, but it looks like this message is issued by DSSS or Rebuild and not the DMD compiler. I'm just guessing though.

In an effort to help you isolate the source of the message, is this a simple program such that you can use the DMD command line or is DSSS needed for this one? If you can though, just try the dmd command line to see if you still get the message.


-- 
Derek
(skype: derek.j.parnell)
Melbourne, Australia
3/03/2008 5:58:43 PM

On Mon, 03 Mar 2008 18:05:41 +1100, Derek Parnell wrote:

> On Mon, 03 Mar 2008 01:53:51 -0500, Ty Tower wrote:
> 
>> Now what I am suggesting is that the message out from the compiler is ...wrong.
> 
> Yes, it looks like a mistake somewhere. I do not use Linux nor DSSS, but it looks like this message is issued by DSSS or Rebuild and not the DMD compiler. I'm just guessing though.
> 
> In an effort to help you isolate the source of the message, is this a simple program such that you can use the DMD command line or is DSSS needed for this one? If you can though, just try the dmd command line to see if you still get the message.

Derek,
I just wish to inform you that your assumption is correct in it being a
message generated by DSSS. The fact is there is no reason to print that
message, so I don't know why it does. All it seems to have done is made
some confusion. If you would like more detail about it I would be happy
to tell you. If I see GragorR around I will attempt to inform him of
making a correction.

On Mon, 3 Mar 2008 07:45:12 +0000 (UTC), Jesse Phillips wrote:
> Derek,
> If you would like more detail about it I would be happy
> to tell you.

No, I'm fine with that.


-- 
Derek Parnell
Melbourne, Australia
skype: derek.j.parnell

Ty Tower wrote:
> Now I will just approach this vewy vewy quietly so no one misunderstands..........
> 
> On a Linux machine as user tytower I issue a build command as below . Because I am logged in as user, not root I cannot write to  /usr  so the compiler says I will write to  /home/tytower/d  instead. It does not in fact do this as no directory /home/tytower/d exists or is created ,Even if I create this directory it is not used. It actually write to the current directory which in this case is the same as the directory the program is in.
> 
> [tytower@linuxbox MyStuff]$ dsss build -D maintry.d
> Default prefix /usr is unwritable, using /home/tytower/d instead.
> 
> Now what I am suggesting is that the message out from the compiler is ....wait for it ...wrong. Not that it worries me or there is more I don't understand , but merely to tell someone there that this exits and is ....wrong.

This is not a bug. You didn't install anything, so it didn't actually need to use the prefix.

 - Gregor Richards

Reply to Gregor,

> Ty Tower wrote:
> 
>> Now I will just approach this vewy vewy quietly so no one
>> misunderstands..........
>> 
>> On a Linux machine as user tytower I issue a build command as below .
>> Because I am logged in as user, not root I cannot write to  /usr  so
>> the compiler says I will write to  /home/tytower/d  instead. It does
>> not in fact do this as no directory /home/tytower/d exists or is
>> created ,Even if I create this directory it is not used. It actually
>> write to the current directory which in this case is the same as the
>> directory the program is in.
>> 
>> [tytower@linuxbox MyStuff]$ dsss build -D maintry.d Default prefix
>> /usr is unwritable, using /home/tytower/d instead.
>> 
>> Now what I am suggesting is that the message out from the compiler is
>> ....wait for it ...wrong. Not that it worries me or there is more I
>> don't understand , but merely to tell someone there that this exits
>> and is ....wrong.
>> 
> This is not a bug. You didn't install anything, so it didn't actually
> need to use the prefix.
> 

So the message is with regards to installing only, not for building docs or general building?

> - Gregor Richards
> 

BCS wrote:
> Reply to Gregor,
> 
>> Ty Tower wrote:
>>
>>> Now I will just approach this vewy vewy quietly so no one
>>> misunderstands..........
>>>
>>> On a Linux machine as user tytower I issue a build command as below .
>>> Because I am logged in as user, not root I cannot write to  /usr  so
>>> the compiler says I will write to  /home/tytower/d  instead. It does
>>> not in fact do this as no directory /home/tytower/d exists or is
>>> created ,Even if I create this directory it is not used. It actually
>>> write to the current directory which in this case is the same as the
>>> directory the program is in.
>>>
>>> [tytower@linuxbox MyStuff]$ dsss build -D maintry.d Default prefix
>>> /usr is unwritable, using /home/tytower/d instead.
>>>
>>> Now what I am suggesting is that the message out from the compiler is
>>> ....wait for it ...wrong. Not that it worries me or there is more I
>>> don't understand , but merely to tell someone there that this exits
>>> and is ....wrong.
>>>
>> This is not a bug. You didn't install anything, so it didn't actually
>> need to use the prefix.
>>
> 
> So the message is with regards to installing only, not for building docs or general building?
> 
>> - Gregor Richards
>>
> 
> 

Yeah. DSSS does the same basic configuration regardless of which process it's doing, so it would be fairly difficult to suppress this message if you weren't installing.

That said, right now I'm doing some rearchitecting and this should probably be fixed there. Maybe :)

 - Gregor Richards

Gregor Richards Wrote:

> Ty Tower wrote:
> > Now I will just approach this vewy vewy quietly so no one misunderstands..........
> > 
> > On a Linux machine as user tytower I issue a build command as below . Because I am logged in as user, not root I cannot write to  /usr  so the compiler says I will write to  /home/tytower/d  instead. It does not in fact do this as no directory /home/tytower/d exists or is created ,Even if I create this directory it is not used. It actually write to the current directory which in this case is the same as the directory the program is in.
> > 
> > [tytower@linuxbox MyStuff]$ dsss build -D maintry.d
> > Default prefix /usr is unwritable, using /home/tytower/d instead.
> > 
> > Now what I am suggesting is that the message out from the compiler is ....wait for it ...wrong. Not that it worries me or there is more I don't understand , but merely to tell someone there that this exits and is ....wrong.
> 
> This is not a bug. You didn't install anything, so it didn't actually need to use the prefix.
> 
>   - Gregor Richards


So it doesn't need to tell me then -  it is an un-necessary and misleading output , perhaps an extra line of code could be added?

BCS Wrote:

Tell me     Why do you open a new thread for your posts? Is there something to be gained there?  Just seems to cause a discontinuity of  posts . Is this perhaps done by the program ?

Either way when I search a subject I do not seem to get these dis-associated posts

"Ty Tower" <tytower@hotmail.com.au> wrote in message news:fqik87$2d2$1@digitalmars.com...
> BCS Wrote:
>
> Tell me     Why do you open a new thread for your posts? Is there something to be gained there?  Just seems to cause a discontinuity of posts . Is this perhaps done by the program ?
>
> Either way when I search a subject I do not seem to get these dis-associated posts

It's the terribly buggy web interface that does it.  :\