about vhdl compiling

while i compile any program in window 98 it shows that "error: can't open
nhdl work "

can somebody help on this and how to fix this problem.
The same program compiles successfully in window xp or vista but in 98 it
doesn't.   

On Feb 25, 5:48 am, "ravikumardk" <ravikumarchaura...@gmail.com>
wrote:
> while i compile any program in window 98 it shows that "error: can't open
> nhdl work "
>
> can somebody help on this and how to fix this problem.
> The same program compiles successfully in window xp or vista but in 98 it
> doesn't.

comp.lang.vhdl <- that's where I would post VHDL questions.

Using Win98 for VHDL is either very brave, or very silly.  Stop doing
that.

AL

On Feb 25, 7:48=A0am, "ravikumardk" <ravikumarchaura...@gmail.com>
wrote:

> can somebody help on this and how to fix this problem.
> The same program compiles successfully in window xp or vista but in 98 it
> doesn't. =A0

Did you read the system requirements for the VHDL compiler you're
using?

"LittleAlex" <alex.louie@email.com> wrote in message
news:ddf5ea44-7e48-4058-a88f-1199cd41da6c@o36g2000yqh.googlegroups.com...
> Using Win98 for VHDL is either very brave, or very silly.  Stop doing
> that.

Oh? What does a VHDL compiler need more from an OS than a few file
management functions?

Meindert

"Meindert Sprang" <ms@NOJUNKcustomORSPAMware.nl> wrote in message 
news:49a6717f$0$199$e4fe514c@news.xs4all.nl...
> "LittleAlex" <alex.louie@email.com> wrote in message
> news:ddf5ea44-7e48-4058-a88f-1199cd41da6c@o36g2000yqh.googlegroups.com...
>> Using Win98 for VHDL is either very brave, or very silly.  Stop doing
>> that.
>
> Oh? What does a VHDL compiler need more from an OS than a few file
> management functions?

reliability?

Peter 

On Feb 26, 5:36=A0am, "Meindert Sprang" <m...@NOJUNKcustomORSPAMware.nl>
wrote:

> > Using Win98 for VHDL is either very brave, or very silly. =A0Stop
>
> Oh? What does a VHDL compiler need more from an OS than a few file
> management functions?

A filesystem without VFAT's special quirks, maybe. Ability to use
WinXP drivers to access the debugger maybe. Also if the software
package has any GUI elements, Win98 has all manner of odd internal
limits due to its Win95 16/32bit hybrid legacy. Yes I realize some of
this isn't part of the compiler per se, but the compiler isn't shipped
in a vacuum - it is wrapped by and snuggled against other components.

Whatever the underlying reason, there are definitely pieces of
software you wouldn't expect to have a problem in Win9x, but do have
such problems. Cygwin for instance used to have some quite different
"special" behaviors in Win9x vs. NT-class OSes. Even just building gcc
was fraught with issues.

VHDL dev suites are massive pieces of bloatware (last package I
downloaded from Xilinx was 900MB plus another 400MB of updates and
patches!!!).

zwsdotcom@gmail.com wrote:
> "Meindert Sprang" <m...@NOJUNKcustomORSPAMware.nl> wrote:
>> "LittleAlex" <alex.louie@email.com> wrote:
>> 
>>> Using Win98 for VHDL is either very brave, or very silly.  Stop
>>
>> Oh? What does a VHDL compiler need more from an OS than a few file
>> management functions?
> 
> A filesystem without VFAT's special quirks, maybe. Ability to use
> WinXP drivers to access the debugger maybe. Also if the software
> package has any GUI elements, Win98 has all manner of odd internal
> limits due to its Win95 16/32bit hybrid legacy. Yes I realize some
> of this isn't part of the compiler per se, but the compiler isn't
> shipped in a vacuum - it is wrapped by and snuggled against other
> components.
... snip ...

A compiler needs to read a source file(s) and write output
file(s).  Apart from purely internal operations it needs nothing
more.  Win98 can do this without problems.

Please don't strip attributions for material you quote.  I think I
have restored them correctly.

-- 
 [mail]: Chuck F (cbfalconer at maineline dot net) 
 [page]: <http://cbfalconer.home.att.net>
            Try the download section.

On Feb 26, 5:27=A0pm, CBFalconer <cbfalco...@yahoo.com> wrote:

> A compiler needs to read a source file(s) and write output
> file(s). =A0Apart from purely internal operations it needs nothing
> more. =A0Win98 can do this without problems.

And in practice the environment has large effects. For example what if
your makefile and macros use lowercase filenames (which is just dandy
on on a case-ignoring FS like VFAT), your sourcefiles have mixed-case
names as generated by many text editors (myfile.c vs myfile.C), and
you then try to compile the same project on UNIX, where case is
important? This is an obvious example, there are many more subtle
examples, ESPECIALLY under Windows where many of these cross-compilers
are really cygwin executables.

If you've never struck problems like this, then bully for you, but
don't presume to speak for the universe.

> Please don't strip attributions for material you quote. =A0I think I
> have restored them correctly.

Please don't be so anal. There are much more important things in the
world about which you could worry.