Clay 0.1.2

[Joe Groff]

Hi everyone. I've prepared a new maintenance release, Clay 0.1.2. This
updates Clay 0.1 to use LLVM 3.1 and fixes a bunch of bugs. Source
code compatibility with earlier 0.1 releases should remain.

Release notes: https://github.com/jckarter/clay/blob/v0.1.2/ReleaseNotes.txt
Browse the source: https://github.com/jckarter/clay/tree/v0.1.2
Download as a tarball: https://github.com/jckarter/clay/tarball/v0.1.2
Download as a zipball: https://github.com/jckarter/clay/zipball/v0.1.2

I've prepared new Windows binaries under
https://github.com/jckarter/clay/downloads as well.

As always, if you find bugs, submit them to Github at
https://github.com/jckarter/clay/issues .

Clay is a systems programming language with a focus on generic
programming. A brief introduction is at http://claylabs.com/clay/ .

-Joe

[Stepan Koltsov]

Hi.

http://claylabs.com/clay/ latest news is 0.1 release and there's no download link to the latest release anywhere.

--
Stepa

[KS Sreeram]

I've updated the page.

- KS

[Rodéric Vicaire]

I just tried both Windows version and I get the following error :

"

clang: error: unable to execute command: program not executable

clang: error: linker command failed with exit code 1 (use -v to see invocation)

"

I've no clue what's going wrong, anyone else tried them ?

   Rodéric.

[Joe Groff]

On Fri, Aug 3, 2012 at 4:04 AM, Rodéric Vicaire
<roderic...@gmail.com> wrote:
> I just tried both Windows version and I get the following error :
> "
> clang: error: unable to execute command: program not executable
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> "
> I've no clue what's going wrong, anyone else tried them ?

What version of Windows are you using? x86 or x64? Does executing clang work?

-Joe

[Szabó Antal]

You have to run clay in a Windows SDK or Visual Studio command prompt,
because clay invokes the sístem linker (link.exe), which isn't
normally in the path.

2012/8/3 Rodéric Vicaire <roderic...@gmail.com>:

[Szabó Antal]

*system

2012/8/3 Szabó Antal <szabo.a...@gmail.com>:

[Rodéric Vicaire]

So much for me trying to do thing from scratch late in the week ;p

I fixed it at home using my setup batch... felt stupid.

However I get this :

libcmt.lib(chkstk.obj) : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'

clang: error: linker command failed with exit code 1112 (use -v to see invocation)

running clay64 on Windows 7 Home Premium x64.

Is that expected ?

   Rodéric.

Le vendredi 3 août 2012 19:05:34 UTC+1, Sh4rK a écrit :

*system

2012/8/3 Szabó Antal :

> You have to run clay in a Windows SDK or Visual Studio command prompt,
> because clay invokes the sístem linker (link.exe), which isn't
> normally in the path.
>

> 2012/8/3 Rodéric Vicaire :

[Szabó Antal]

I guess that's because you are running the 64 bit clay compiler in a
32 bit environment, and "link" tries to link together 32 and 64 bit
objects, which is not possible. Try the 32 bit clay compiler, or a 64
bit build environment.

For example I use the Windows SDK Command Prompt, and when it launches
I type "setenv /x64 /Release" to set the environment to 64 bit (and
release, but I think that doesn't matter to the linker) then run clay.

2012/8/3 Rodéric Vicaire <roderic...@gmail.com>:

[Rodéric Vicaire]

Yes, I realized it a couple minutes after I posted but my computer was already off by then ^^

That will teach me to post on a Friday night !

I definetly need a less tiring working environment.

Le vendredi 3 août 2012 22:25:14 UTC+1, Sh4rK a écrit :

I guess that's because you are running the 64 bit clay compiler in a
32 bit environment, and "link" tries to link together 32 and 64 bit
objects, which is not possible. Try the 32 bit clay compiler, or a 64
bit build environment.

For example I use the Windows SDK Command Prompt, and when it launches
I type "setenv /x64 /Release" to set the environment to 64 bit (and
release, but I think that doesn't matter to the linker) then run clay.

2012/8/3 Rodéric Vicaire :

[Shyam Sundar T R]

Unable to install using homebrew because homebrew installs LLVM 3.2 as a dependency and the tarball is at an older version of the code which uses LLVM 3.1 as the Release Notes read. I guess the fix is to wait for the next stable version which would use LLVM 3.2. And for now, installing LLVM 3.1 using homebrew seems difficult, leave alone trying to make the homebrew formula depend on LLVM 3.1!

Any pointers on a temporary fix? When can the next stable version be expected?

-- trss

[trss]

Figured out the temporary fix involving manually configuring homebrew to install LLVM 3.1.

For those who haven't installed older versions of software using homebrew before:-

Try

brew versions llvm

It currently says

3.2 git checkout 3e7aaa1 /usr/local/Library/Formula/llvm.rb

3.1 git checkout 7d15192 /usr/local/Library/Formula/llvm.rb

But cd to Formula first

cd /usr/local/Library/Formula

Then checkout using git

git checkout 7d15192 llvm.rb

Now the usual should work

brew install clay

-- trss

[Joe Groff]

On Sat, May 18, 2013 at 12:00 PM, Shyam Sundar T R <trs...@gmail.com> wrote:

Unable to install using homebrew because homebrew installs LLVM 3.2 as a dependency and the tarball is at an older version of the code which uses LLVM 3.1 as the Release Notes read. I guess the fix is to wait for the next stable version which would use LLVM 3.2. And for now, installing LLVM 3.1 using homebrew seems difficult, leave alone trying to make the homebrew formula depend on LLVM 3.1!

You should bring this up with the homebrew package maintainer for LLVM. Different versions of the LLVM libraries are never compatible, so they should be handled as separate packages instead of different versions of the same package.

 

Any pointers on a temporary fix? When can the next stable version be expected?

Unfortunately I don't really have time to put releases together anymore. Jyun-Yan You did the work of updating the v0.1 branch in Git to LLVM 3.2, so you could compile from source to get an LLVM 3.2-compatible version.

-Joe