Questions and Answers :
Unix/Linux :
FreeBSD port
Message board moderation
Author | Message |
---|---|
Send message Joined: 1 Sep 04 Posts: 506 Credit: 118,619 RAC: 0 |
(The argument that "our compiler generates code only for a given platform" only proves the speaker's incompetence in using devices such as computers.) I find this statement rather offensive, actually. This is precisely the reason there's no port other than Windows or Linux, and in this case it's for very good reasons. I shan't expand upon it here - it's been covered extensively in the boards. I assume that the writer of the above remark is sufficiently competent in the use of computers and the English language to find it himself. ...or maybe he isn't ;-) Gaspode the UnDressed http://www.littlevale.co.uk |
Send message Joined: 7 Aug 05 Posts: 60 Credit: 73,746 RAC: 0 |
I find your posting offense, displaced and incompetent. You have to respect the reasons of the project not to relase a binary for every unix. Also you have to respect, that the would not release the source code. Why do you not let the linux binaries run in the linux emulation under FreeBSD ? |
Send message Joined: 1 Mar 08 Posts: 1 Credit: 0 RAC: 0 |
darwin (Mac os X) is not supported too and lhc@home. I don't think LHC calculation required anything very specific (no gui for example) and port for other unix should be possible. |
Send message Joined: 7 Aug 05 Posts: 60 Credit: 73,746 RAC: 0 |
darwin (Mac os X) is not supported too and lhc@home. I don't think LHC calculation required anything very specific (no gui for example) and port for other unix should be possible. As obove stated. It is a compiler issue. LHC used a compiler which is only available for Linux and Windows and not on other Unixes. |
Send message Joined: 30 Nov 06 Posts: 234 Credit: 11,078 RAC: 0 |
darwin (Mac os X) is not supported too and lhc@home. I don't think LHC calculation required anything very specific (no gui for example) and port for other unix should be possible. Thank you. The people who created SixTrack choose a strange compiler (don't ask why I don't know) and this means that there are only Linux and Windows applications for LHC@home. Also this: The argument that "our compiler generates code only for a given platform" only proves the speaker's incompetence in using devices such as computers. Bang out of order I support Open Source (FF, TB, OOo etc etc) and run a system based on BSD (OSX) but this kind of zealot talk gives the community a bad name. If we could port to BSD and OSX we would have by now, if only because a few people involved down the years (including myself) are Mac users. As for making the code open source that is not my decision to make but you don't need to run it if it hurts your sensibilities (and I bet I will find identical posts on other BOINC forums from you stating similar things about other projects) but I don't think you'll be modelling any supermagnets in large particle accelerators any time soon. |
Send message Joined: 12 May 08 Posts: 1 Credit: 0 RAC: 0 |
I have read and big problem it's for only processor with 32 bit and don't support 64 bit processor. it's very strange you can use intel processor with Windows and linux but OS X intel, with X11 why it's not suppoted... |
Send message Joined: 17 Apr 09 Posts: 1 Credit: 0 RAC: 0 |
Came here looking into contributing some CPU cycles to LHC@home. Disappointing to read that minority OSes aren\'t welcomed in this volunteer project with cold responses of \"Thanks but no thanks.\" |
Send message Joined: 9 Oct 09 Posts: 1 Credit: 0 RAC: 0 |
Came here looking into contributing some CPU cycles to LHC@home. I agree. I run FreeBSD, Linux and Windows on several of my machines, but thanks to the absurd (in this day and age) path taken by these lazy programmers, LHC@home will never see any of my 16 cores thanks to this lousy approach. I say \"thanks, but NO THANKS\", LHC@home - I will stick with protein folding, which is more important anyway. |
Send message Joined: 23 Jan 17 Posts: 29 Credit: 375,570 RAC: 0 |
Cool that people are interested in a FreeBSD port! I know one of the SixTrack developers was looking into it yesterday, I'll forward him this thread - it might actually not be that hard to do... Regarding the compiler, we can actually compile with either gfortran, ifort, or nagfor on the Fortran side; and either gcc, icc, or clang on the C side. The problem is not compiling SixTrack itself, but rather to compile and link BOINC's zip libraries on Windows with Mingw on MSYS2. Which is why we're now pushing to use libarchive for that functionality. If you're interested in the code, see https://github.com/SixTrack/SixTrack/issues/39 and https://github.com/SixTrack/SixTrack/pull/173 --- Kyrre, SixTrack developer. |
©2024 CERN