Derek,

I've tried a bunch of ways to get build and dmd to work with cygwin and I have not.  I can get gcd to work with cygwin, but not dmd and build.  However, I am working perfectly with the crazy DOS prompt. :-)

Just a thought...

Derek Parnell says...
>
>On Sat, 30 Apr 2005 15:00:09 -0700, Phlip wrote:
>
>> We determined ...CygWin is not (directly) to blame ...
>
>Well, I'm not yet convinced of that. You told us that it's not Cygwin but I haven't got any evidence to suggest you are correct.
>
>Would it be possible for you to use the native Windows command line instead just so we can determine if its a command processor related problem or not.
>
>-- 
>Derek Parnell
>Melbourne, Australia
>http://www.dsource.org/projects/build
>1/05/2005 11:22:42 AM

jicman <jicman_member@pathlink.com> wrote:

[...]
> I've tried a bunch of ways to get build and dmd to work with cygwin and I have not.
[...]

This is cygwin dmd/gdc and digitalmars dmd/build coinstalled on a winXPPro:

<copyPasted>
manfred@home /cygdrive/e/dmd/samples/d
$ which dmd
/usr/bin/dmd

manfred@home /cygdrive/e/dmd/samples/d
$ which build
/cygdrive/e/dmd/bin/build

manfred@home /cygdrive/e/dmd/samples/d
$ build hello
e:\dmd\bin\..\..\dm\bin\link.exe hello,hello.exe,,user32
+kernel32,hello.def/noi;

manfred@home /cygdrive/e/dmd/samples/d
$ hello
hello world
args.length = 1
args[0] = 'e:\dmd\samples\d\hello.exe'
</copyPasted>

So at first glance I do not believe that on a sane Win/cygwin/dmd installation there are any problems. If you meet this requirements I am willing to help.

-manfred

J C Calvarese <jcc7@cox.net> wrote:

[...]
> you're seeming more like a troll all the time.

Thanks for the confirmation.

It has lasted some years that this forum was astonishingly clean.

However, also phlip's reaction on my questions on the desinformation he gave is a typical one: no reactions.

And on the _question_ whether he is a troll: astonishingly no denial but reasoning over things that not has happened.

So I feel that my renaming of the subject to a big welcome is justified by his reaction.

-manfred

J C Calvarese wrote:

> Have you tried that evil cmd.exe program yet? You might get some further suggestions if you'd meet us half way.

The problem now is a rambling thread is hard to read. I repeatedly reported I repeatedly tried CMD.EXE.

Guys - cleansing breath, everyone. Now.

jicman wrote:
>
> Derek,
>
> I've tried a bunch of ways to get build and dmd to work with cygwin and I
have
> not.  I can get gcd to work with cygwin, but not dmd and build.  However,
I am
> working perfectly with the crazy DOS prompt. :-)

I have no need for CygWin: The following question is only because jicman did not make clear the meaning of "get to work". Entirely out of curiosity, and not because anyone is not using CMD.EXE, does "get to work" mean compile into CygWin's GNU platform?

Manfred Nowak wrote:

> However, also phlip's reaction on my questions on the desinformation he gave is a typical one: no reactions.

Apologies, but my disinformations were not technically relevant. They were ice-breakers. They were to lead J C Calvarese to say, "That's okay, we're here to help". If you don't have this reaction, please have none.

If I announce "I have a twenty-year resume, from AmigaDOS to zsh, and I can't install dmd and it's you guy's fault", that's slightly off-putting, right?

-- 
  Phlip
  http://www.c2.com/cgi/wiki?ZeekLand

On Sun, 1 May 2005 04:54:09 -0700, Phlip wrote:

[snip]
> If I announce "I have a twenty-year resume, from AmigaDOS to zsh, and I can't install dmd and it's you guy's fault", that's slightly off-putting, right?

Yep! Especially when no one else is having the problem. Must be a bit embarrassing for you ... oh hang on ... you meant off-putting for us. Sorry. My bad.

But seriously, what else can we do? We have explained what needs to happen, and you have told us you have done such; ... but you are still having problems that we are not having. So all we can assume at this point is that you have made a mistake in installing it and/or setting up the environment correctly, *and* you cannot see your error.

Hundreds of people have followed the installation notes and it works for them. Now true, it may be possible that thousands have also tried to install it and failed, and haven't bothered to mention that to the author or this news group ... but that's straining the probability curve a bit much.

Ok, I've bitten the bullet and installed cygwin to see if I could be of any use. Here is some console output that I got ...

  bash-2.05b$ pwd
  /cygdrive/c/dmd/samples/d
  bash-2.05b$ dmd hello.d
  c:\dmd\bin\..\..\bm\link.exe hello,,,user32=kernel32/noi;
  bash-2.05b$ ./hello
  hello world
  args.length = 1
  args[0] = 'c:\dmd\samples\d\hello.exe'
  bash-2.05b$

All I can suggest now is that you start again from scratch and double check each step before proceeding to the next step.

(A) Download the two ZIP files ...
    http://ftp.digitalmars.com/dmd.zip
    http://ftp.digitalmars.com/dmd.zip
(B) Unzip these files, using the 'create sub-folders as required' option,
which is usually the default. Let's assume for the purposes of this
discussion, that you installed it onto the C: drive. Thus unzipping these
would have produced the following folders and sub-folders ...

c:\dmd
c:\dmd\bin
c:\dmd\html
c:\dmd\lib
c:\dmd\man
c:\dmd\practice
c:\dmd\samples
c:\dmd\src

c:\dm
c:\dm\bin
c:\dm\html\ctg
c:\dm\html
c:\dm\images
c:\dm\include
c:\dm\lib
c:\dm\html\make_files
c:\dm\samples\me
c:\dm\samples
c:\dm\include\sys
c:\dm\include\win32


(C) Update your PATH symbol so that it includes "c:\dm\bin" and "c:\dmd\bin". You may have to reboot after doing this.

(D) Start up a DOS/WINDOWS command prompt (command.com or cmd.exe depending
on which version of windows you are using).

(E) At the command prompt enter in ...

   dmd c:\dmd\samples\d\hello.d

and expect output such as ...

  c:\dmd\bin\..\..\dm\bin\link.exe hello,,,user32+kernel32/noi;

(F) Now try it with a Cygwin console window.

-- 
Derek Parnell
Melbourne, Australia
http://www.dsource.org/projects/build
1/May/2005 9:59:03 PM

Derek Parnell wrote:

> > If I announce "I have a twenty-year resume, from AmigaDOS to zsh, and I can't install dmd and it's you guy's fault", that's slightly
off-putting,
> > right?
>
> Yep! Especially when no one else is having the problem. Must be a bit embarrassing for you ... oh hang on ... you meant off-putting for us. Sorry. My bad.

Would "I have installed 4 different distros of Ruby on 6 different computers and each one worked right out of the box" be less off-putting? ;-)

> (C) Update your PATH symbol so that it includes "c:\dm\bin" and "c:\dmd\bin". You may have to reboot after doing this.

Gaaarr! I pride myself in only rebooting my WinXP twice a week. The current boot was doing so well, otherwise. Oh well, we'll see which of Sybel's personalities we get this time...

<pause to reboot>

Nope.

C:\dmd\samples>dmd d\hello.d
Error: Error reading file 'object.d'

From here, I can work around like this:

C:\dmd\samples>dmd -IC:\dmd\src\phobos d\hello.d
link hello,,,user32+kernel32/noi;
OPTLINK (R) for Win32  Release 7.50B1
Copyright (C) Digital Mars 1989 - 2001  All Rights Reserved

phobos.lib
 Warning 2: File Not Found phobos.lib
OPTLINK : Warning 23: No Stack

One final question: What's the argument to dmd to help the linker find phobos.lib?

-- 
  Phlip
  http://www.c2.com/cgi/wiki?ZeekLand

Phlip wrote:
> Derek Parnell wrote:
> 
> 
>>>If I announce "I have a twenty-year resume, from AmigaDOS to zsh, and I
>>>can't install dmd and it's you guy's fault", that's slightly
> 
> off-putting,
> 
>>>right?
>>
>>Yep! Especially when no one else is having the problem. Must be a bit
>>embarrassing for you ... oh hang on ... you meant off-putting for us.
>>Sorry. My bad.
> 
> 
> Would "I have installed 4 different distros of Ruby on 6 different computers
> and each one worked right out of the box" be less off-putting? ;-)
> 

Just to stir the pot up more, I found nothing offputting or trollish about your previous posts. ;-)

*runs and ducks as rotten fruit get's thrown in my direction from fellow community members*

Your style of introduction was quite original, though.  Oh and Manfred is always like that, sometimes he's right...sometimes he's wrong depending on how patient he feels at the time.  In this case, it just had to do with the unusual way of your introduction... I know you were trying to be suave and self-deprecating to attract the needed help... but I guess doing that doesn't always work. Might as well be up front.

And considering the characters on this group, I'm very surprised at the reception you got... heh!  As great as this newsgroup is, you have no idea what kind of weird discussions have occurred here... really! This one's mild.

Most of the responses come from the fact that these characters have been around here for awhile, are comfortable with their surroundings, and have developed a certain amount of respect in the community... kind of.  Guaranteed most of these guys, including myself, would have been much more self-conscious about what we post if it were a year ago... but you know how it goes when one's carved a nitch:  now we're allowed to be as opinionated, abrasive, and condescending as we want... especially to new-comers because we're invincible (/not/)! :-D.  See?  It's just like putting on a new suit for work.  Do you think we'd be like this in person? ;-) (well maybe some of us would!)

>>(C) Update your PATH symbol so that it includes "c:\dm\bin" and
>>"c:\dmd\bin". You may have to reboot after doing this.
> 
> 
> Gaaarr! I pride myself in only rebooting my WinXP twice a week. The current
> boot was doing so well, otherwise. Oh well, we'll see which of Sybel's
> personalities we get this time...

You don't usually have to reboot after environment variable updates on WinXP.  You just have to close and reopen the command console.

> <pause to reboot>
> 
> Nope.
> 
> C:\dmd\samples>dmd d\hello.d
> Error: Error reading file 'object.d'
> 
> From here, I can work around like this:
> 
> C:\dmd\samples>dmd -IC:\dmd\src\phobos d\hello.d
> link hello,,,user32+kernel32/noi;
> OPTLINK (R) for Win32  Release 7.50B1
> Copyright (C) Digital Mars 1989 - 2001  All Rights Reserved
> 
> phobos.lib
>  Warning 2: File Not Found phobos.lib
> OPTLINK : Warning 23: No Stack
> 
> One final question: What's the argument to dmd to help the linker find
> phobos.lib?
> 

This is a very strange problem.  Have you tried installing on another computer?  Perhaps you should test to see if another cygwin installation will work.  the "-IC:\dmd\src\phobos"  should be read from sc.ini.  It must not be finding it.  Also, LIB is in sc.ini and should point to where the libraries are situated.  Strange.

In the meantime, just add phobos.lib to the command line, no switch required (full path to it may be necessary).

-JJR

John Reimer wrote:

> Just to stir the pot up more, I found nothing offputting or trollish about your previous posts. ;-)

Well, I once told a forum full of game designers they should write high-level scenario tests for their games instead of making their programmers work all night code-and-fixing. They had a shit fit.

> You don't usually have to reboot after environment variable updates on WinXP. You just have to close and reopen the command console.

I know; I could also have written a new, shorter PATH on a command line. I'l get back to that.

One possibility is something in my (fragged) environment has the same name or signature as some element of the dmd toolchain. So attempting to install on another computer is a good idea. But...

> In the meantime, just add phobos.lib to the command line, no switch required (full path to it may be necessary).

Noop:

C:\dmd\samples>dmd -IC:\dmd\src\phobos d\hello.d c:\dmd\lib\phobos.lib
...
phobos.lib
 Warning 2: File Not Found phobos.lib

C:\dmd\samples>dir c:\dmd\lib\phobos.lib
15-Apr-05  02:30 PM           669,696 phobos.lib

-- 
  Phlip
  http://www.c2.com/cgi/wiki?ZeekLand

Phlip wrote:
> John Reimer wrote:
> 
> 
>>Just to stir the pot up more, I found nothing offputting or trollish
>>about your previous posts. ;-)
> 
> 
> Well, I once told a forum full of game designers they should write
> high-level scenario tests for their games instead of making their
> programmers work all night code-and-fixing. They had a shit fit.
> 


Heh... I hear you.  I guess what I'm saying is "no big deal."  There's plenty of complicated issues in life for people to get disgruntled over.   Your posts weren't one of them.  And I could care less if I get smacked with a rotten tomato for saying that.


>>You don't usually have to reboot after environment variable updates on
>>WinXP. You just have to close and reopen the command console.
> 
> 
> I know; I could also have written a new, shorter PATH on a command line. I'l
> get back to that.
> 
> One possibility is something in my (fragged) environment has the same name
> or signature as some element of the dmd toolchain. So attempting to install
> on another computer is a good idea. But...
> 


Environment does sound messed up.


>>In the meantime, just add phobos.lib to the command line, no switch
>>required (full path to it may be necessary).
> 
> 
> Noop:
> 
> C:\dmd\samples>dmd -IC:\dmd\src\phobos d\hello.d c:\dmd\lib\phobos.lib
> ...
> phobos.lib
>  Warning 2: File Not Found phobos.lib
> 
> C:\dmd\samples>dir c:\dmd\lib\phobos.lib
> 15-Apr-05  02:30 PM           669,696 phobos.lib
> 

!!!  Super wierd  !!!  Well, I think it's more to do with your computer environment then the compiler installation. That's just bizarre.  I don't have much of a clue.

-JJR

John Reimer wrote:

> Environment does sound messed up.

Moving \dm\bin and \dmd\bin to the front of the PATH didn't work either...

> > Noop:
> >
> > C:\dmd\samples>dmd -IC:\dmd\src\phobos d\hello.d c:\dmd\lib\phobos.lib
> > ...
> > phobos.lib
> >  Warning 2: File Not Found phobos.lib
> >
> > C:\dmd\samples>dir c:\dmd\lib\phobos.lib
> > 15-Apr-05  02:30 PM           669,696 phobos.lib
>
> !!!  Super wierd  !!!

Waitaminute! That's just a warning. The compilation worked, and produced an executable. I can live with a warning. (I'l grep -v it out).

-- 
  Phlip
  http://www.c2.com/cgi/wiki?ZeekLand