search

hughperman / pure-lang

Automatically exported from code.google.com/p/pure-lang
0 stars 0 forks source link

expressions are not getting evaluated #10

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
Just running the interpreter or "make check"

What is the expected output? What do you see instead?
In the interpreter I get:
> 1 + 2;
1+2

Shouldn't the output be 3? I am just beginning to use pure.

What version of the product are you using? On what operating system?
Pure 0.23 (i686-pc-linux-gnu)

Please provide any additional information below.
All tests are failing in make check also
The diff shows that all output is missing.

Original issue reported on code.google.com by harshad...@gmail.com on 31 May 2009 at 6:24

GoogleCodeExporter commented 8 years ago 
Hmm, this looks like Pure doesn't find the prelude. Can you please post all 
messages
that you see when you run 'pure' in the shell?

Also, what cpu and specific Linux system do you have?

Original comment by aggraef@gmail.com on 1 Jun 2009 at 1:13

GoogleCodeExporter commented 8 years ago 
Ah, yes! I had missed this message:
"Couldn't find the prelude. Please check your PURELIB environment variable."

I was trying to run the executable without "make install"

Specifying the path to prelude.pure in PURELIB causes a segmentation fault.

I guess this is related to issue #9

Feel free to close this issue.

Original comment by harshad...@gmail.com on 1 Jun 2009 at 3:40

GoogleCodeExporter commented 8 years ago 
Also, please make the "Couldn't find the prelude" message more visible, for the
benefit of future users.

Perhaps a newline before it would make it more noticeable.

Original comment by harshad...@gmail.com on 1 Jun 2009 at 3:42

GoogleCodeExporter commented 8 years ago 
> Specifying the path to prelude.pure in PURELIB causes a segmentation fault.
> I guess this is related to  issue #9 

Are you running Ubuntu 9.04 on x86 (32 bit)? The LLVM 2.5 package is broken 
there.

Otherwise please reopen the issue and post a backtrace, so that we can get it 
sorted out.

> Also, please make the "Couldn't find the prelude" message more visible, for 
the
> benefit of future users.

Done (r1608).

Original comment by aggraef@gmail.com on 1 Jun 2009 at 10:09