On Saturday 10 September 2011, Roger Luedecke wrote:

How would you go about using Intels compiler in OBS anyway?

Intels icc is distributed as several rpm packages which installs everything below /opt/intel. Quick but dirty I would tar them together and write a spec file simplified like this: Name: icc-all %build unrpm all the intel rpms %install mv opt $BUILDROOT/ %files %defattr(-,root,root,-) /opt/intel/* Then using BuildRequires icc-all for my packages. Of course would be more comfortable to upload the original Intel rpms somehow. Specially because the full icc installation is very large (~2.6G). cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Saturday 10 September 2011, Malcolm wrote:

Binary blobs aren't allowed on OBS....

It's a build requirement only. Spec file could download Intels tar distribution without installing it at all. Nevermind my question was about Intel's license. OBS rules would be another thing to check before using icc. I'm going to contact Intel directly about this particular use case.

Why not download and run your own obs instance, then you can do what you like?

Good point. Probably I will do that. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Saturday 10 September 2011, Mathias Homann wrote:

Am Samstag, 10. September 2011 schrieb Rüdiger Meier:

...

On Saturday 10 September 2011, Roger Luedecke wrote:

...

How would you go about using Intels compiler in OBS anyway?

Intels icc is distributed as several rpm packages which installs everything below /opt/intel. Quick but dirty I would tar them together and write a spec file simplified like this:

question... why?

When developing software it's a real benfit regularly testing at least the build and "make check" using different compilers, watching the logs for errors and warnings. If these build tests happens automatically then it will make your software much more stable and compatible without much more devel efforts. So my primary use case would be simply using it for building my own projects from daily snapshots. There are already many different gcc versions and even a lot cross compilers ready to use on OBS. Icc would be nice to have. Another benefit would be the huge performance improvements when using icc for packages where permormance is relevant. And last but not least there is existing software, which does not compile with gcc at all or which officially supports icc only.

and wouldn't the resultin binaries require some other runtime than glibc on any system using them?

Not when using icc -static-intel or maybe even icc -no-use-intel-optimized-headers -shared-libgcc (Which would decrease the performance benefit.) cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Saturday 10 September 2011, Roger Luedecke wrote:

This sound incredibly reasonable and sane. I think we should look into including the intel compiler in OBS.

I don't think Intel will allow to install it globally on OBS, see my first posted link to the license FAQ about "group project". But anyway I'am going to ask intel these questions: 1. I have signed up for a non-commercial license. Am I allowed to install it on a public build farm where it's only usable by myself but compiled packages could be published? 2. Is it theoretically possible to get a kind of non-commercial group license for the OBS project? If not, how much would be the very roughly estimated expenses in case we could get a sponsor for a commercial license. (Of course I will point out that I am asking for my own interest and not on behalf of the openSUSE project.) If at least 1. would be positive answered then I'am sure we could discuss regarding OBS rules whether and how individual OBS packagers could use their icc on OBS. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Monday, September 19, 2011 01:31:46 AM Andreas Jaeger wrote:

On Saturday, September 10, 2011 18:54:22 Rüdiger Meier wrote:

...

Hi,

I'm courious if it would be legal to use Intel's icc compiler for building packages on OBS, see

http://software.intel.com/en-us/articles/non-commercial-software-download / http://software.intel.com/en-us/articles/non-commercial-software-faq/

What do you think? Could I upload non-published icc rpms to OBS to use them to build my own packages only?

icc is not open source, and we only allow open source packages (plus a few specific exceptions) on our instance of OBS.

Andreas If there are any exceptions, why not one more? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Monday 19 September 2011, Lars Vogdt wrote:

...

If there are any exceptions, why not one more?

I would say: feel free to contact Intel and ask if you can get an official approval for including the icc into the openSUSE Build Service.

I contacted them last week but still waiting for reply ...

All mentioned exceptions in OBS currently have a written down (and legal approved) contract that allows us to put them into OBS.

Just to clear it up. I'am sure Intel would never allow to make the icc available for all users without signing non-com. licences for every user. So never ever there could be an icc.rpm published. But if Intel allows single users to use their own license on OBS (and it should be allowed IMO) when we could discuss whether OBS should allow packagers to do this or not. Publishing icc compiled packages is no problem I think. Of course I don't plan to have icc compiled packages within the standard distro. It would be just a benefit for developers to have another very good compiler available. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Tuesday 20 September 2011, Adrian Schröter wrote:

Am Dienstag, 20. September 2011, 01:01:13 schrieb Rüdiger Meier:

...

I'am sure Intel would never allow to make the icc available for all users without signing non-com. licences for every user. So never ever there could be an icc.rpm published.

That would be a problem, because we have no secure mechanics to disallow download of binaries and to allow server side builds at the same time.

Is it possible to have some kind of home directory for each OBS user which could be mapped into the buildroot somehow? Then the icc problem could be solved with the original intel rpm where the icc actually only works if user has a ~/.intel/licenses. This is the way they do it at other non-commercial groups likes universities etc. Don't know, maybe such home dirs could be also useful to store other things like auth keys, custom environment, macros or whatever. So users could try out things quickly without modifying their packages or the whole underlying distro just to try out things. Of course this would be completely against the idea of having clean buildroots but as a feature for users who know what they're doing I would like to have it. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Monday 19 September 2011, Lars Vogdt wrote:

I would say: feel free to contact Intel and ask if you can get an official approval for including the icc into the openSUSE Build Service.

Finally I've got some answer: On Thursday 29 September 2011 at 20:25, noncomsoftware@intel.com wrote:

On Monday, September 12, 2011 6:27 AM, Ruediger Meier wrote:

...

Am I allowed to install the Intel compiler on a public build farm with many users who all can use different platforms there for compiling software packages? I would be the only one who has granted permissions to use my particular icc installation there.

You are the only user who is permitted to use the license but you can use it on as many different systems as you want as long as you don't get a salary when you are using software.

I was lying a bit about the auth feature we don't have yet. Anyway now I am going to ask about an official approval for this or even about a non-com group license without user authentication. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Am Freitag, 30. September 2011, 07:30:46 schrieb Stephan Kulow:

OBS won't take software that has a non-commercial license, we need free software.

Sorry for the confusion: that's build.opensuse.org's policy, of course you can have your own instance of OBS with intel's compiler. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org