Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Empty Product directory after the build #3868

Closed
xplicit opened this issue Feb 3, 2015 · 16 comments
Closed

Empty Product directory after the build #3868

xplicit opened this issue Feb 3, 2015 · 16 comments

Comments

@xplicit
Copy link

xplicit commented Feb 3, 2015

after running ./build.sh on Ubuntu 14.04

I've got the mesage

...
Repo successfully built.
Product binaries are available at /home/user/coreclr/binaries/Product/amd64/debug

but this directory is empty

@ellismg
Copy link
Contributor

ellismg commented Feb 4, 2015

Since support for Linux is still coming online, we haven't taken the time to actually produce a single directory which contains all the build components you would need to run an application.

The most interesting artifacts are just under the CMake folder right now:

/CMake/src/coreclr/hosts/unixcorerun/corerun (The native application which hosts CoreCLR.)
/CMake/src/dlls/mscoree/coreclr/libcoreclr.so (The CoreCLR Runtime.)

Within the next few days we'll document how to combine these plus managed libraries to get a run-time that can actually run simple managed code (unfortunately the process is quite rough right now). Note the runtime itself is in a very alpha state on Linux right now. Simple things work, but there's still a ton of work to be done.

@piot
Copy link

piot commented Feb 4, 2015

Please let me know if there is anything I can help out with!

Trying to run a hello world now results in:

dlopen failed to open the libcoreclr.so with error /home/peter/test/libcoreclr.so: undefined symbol: CHAIN_SUCCESS_COUNTER

Edit: mscorlib was missing, not sure how to build it on linux.

@janvorli
Copy link
Member

janvorli commented Feb 4, 2015

This is strange, the libcoreclr.so should load fine. I've seen people from the community reporting that in the GIT forums - they get ExecuteAssembly failed - status: 0x80004005, which means that the libcoreclr.so was loaded successfully. The CHAIN_SUCCESS_COUNTER resides in the src\vm\amd64\virtualcallstubamd64.S, so I wonder if it is possible that these files are not being assembled / added to the cee_wks library.
Could you please try to modify the CMakeLists.txt in src/vm folder by adding
message("Assembler files: ${VM_SOURCES_WKS_AMD64_ASM}")
before the add_subdirectory(dac) by the end of the file and run make to see what cmake displays? (cmake will be automatically run by make if there is a change in a CMakeLists.txt)

@directhex
Copy link
Member

FWIW, I am not seeing the issue reported by @piot - maybe it should be split out as a distinct issue from this one?

@sergiy-k
Copy link
Contributor

sergiy-k commented Feb 4, 2015

@piot I’m curious whether you are building a debug or release version of CoreClr?

@sergiy-k
Copy link
Contributor

sergiy-k commented Feb 5, 2015

Binplacing of native CoreCLR binaries on Linux has been enabled today. So the Product folder should no longer be empty. But we still need to publish instruction describing how to build managed framework libraries and applications for Linux before you can actually start playing with it.

@piot
Copy link

piot commented Feb 5, 2015

@sergiy-k Linux binaries are now placed correctly (e.g. binaries/Product/amd64/debug), tested ef73ad8

@piot
Copy link

piot commented Feb 5, 2015

@sergiy-k I used the debug version, is there a way to build mscorlib and run a hello_world.exe?

@piot
Copy link

piot commented Feb 5, 2015

@sergiy-k @directhex I would suggest an official chat room for dotnet/coreclr, but please join https://gitter.im/Piot/coreclr for now.

@ellismg
Copy link
Contributor

ellismg commented Feb 5, 2015

I will be publishing directions on how to run hello world later tonight or tomorrow.

@shahid-pk
Copy link
Contributor

@ellismg
great waiting.

@piot
Copy link

piot commented Feb 5, 2015

I suggest closing this issue, the files are placed correctly now.
The CHAIN_SUCCESS_COUNTER problem is reported as dotnet/coreclr#95.

@janvorli janvorli closed this as completed Feb 5, 2015
@ellismg
Copy link
Contributor

ellismg commented Feb 7, 2015

@piot FYI, I published some directions on how to run build and run Hello World on the wiki

@janvorli
Copy link
Member

janvorli commented Feb 7, 2015

@ellismg Matt, looking at the instructions - we don't need the nasm, we were just considering it at one point, but then dropped the idea.

@ellismg
Copy link
Contributor

ellismg commented Feb 7, 2015

@janvorli Good to know! I will update the docs.

@piot
Copy link

piot commented Feb 7, 2015

Thanks a lot @ellismg!

BruceForstall referenced this issue in BruceForstall/coreclr Aug 18, 2016
Disable failing LONG tests for RyuJIT x86, issue #6778
@msftgits msftgits transferred this issue from dotnet/coreclr Jan 30, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Jan 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants