search

radiasoft / devops

sysadmin
Apache License 2.0
11 stars 4 forks source link

Synergia2 'devel' branch doesn't build inside RadiaSoft containers #37

Closed bruhwiler closed 8 years ago

bruhwiler commented 8 years ago

The official Synergia build system doesn't work inside our containers.

I know some sort of fix is being used to make this work for Synergia installation when the containers are built.

RadiaSoft personnel need to be able to clone and build the latest version of Synergia2.

Is the fix documented somewhere? Even better, can we communicate with the Synergia development team to make the fix unnecessary? Presumably the OS being used in our containers is sufficiently 'standard' that the Synergia team will want to support it?

robnagler commented 8 years ago

The build system works. You can say, for example,

curl radia.run | bash -s code synergia

This is the same used inside the container. I'm building a new container now.

bruhwiler commented 8 years ago

Thanks, Rob.

I verified the command works. This is great.

It appears that source and build files are put into /var/tmp/.../ and then get cleaned up afterwards.

I created this issue, because I wanted to git clone the Synergia repository and obtain a development environment. The Synergia build process failed before even the main source directories were pulled from the git repository, so I couldn't even see the source code, much less compile it.

This is not a priority for now, so I'll close the issue, but it seems strange that the native Synergia build system fails inside our container...

robnagler commented 8 years ago

Just to follow up:

I verified the command works.

Thanks for letting me know.

It appears that source and build files are put into /var/tmp/.../ and then get cleaned up afterwards.

Yes, that's how it works.

I created this issue, because I wanted to git clone the Synergia repository and obtain a development environment. The Synergia build process failed before even the main source directories were pulled from the git repository, so I couldn't even see the source code, much less compile it.

The installer uses the synergia build process, but it has to fix things up to make it actually work. Synergia is difficult to build.

This is not a priority for now, so I'll close the issue, but it seems strange that the native Synergia build system fails inside our container...

Unfortunately, most codes need some help to compile. That's why we have a build process based on a single operating system inside a docker container. :)