Hi, I noticed that in Pharo's homepage now there is a link to a Centos build. However, the necessary 32bits libs are not mentioned. Here is the list of the libs needed. May be it would be a good idea to put it there in the page, somewhere. Or at least inside the README.txt that comes in the zip. I would append something like: "As the Pharo virtual machine is still 32bits you will need some 32bit libraries. You can get them by executing the following command as root: sudo yum install alsa-lib.i686 glibc-devel.i686 mesa-libGLU.i686 libICE-devel.i686 libSM-devel.i686 freetype.i686 And after that Pharo should run perfectly." Cheers Nacho ----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- View this message in context: http://forum.world.st/Pharo-on-Centos-RHEL-7-1-tp4821602.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
nacho wrote
I noticed that in Pharo's homepage now there is a link to a Centos build. However, the necessary 32bits libs are not mentioned.
Thanks! I was holding off on this because there are several such lists out there and I'm not sure which apply to which platforms. For example, https://github.com/philippeback/pharovm-centos65/blob/master/packages-to-ins... is a very different list for Centos65. IIRC now after some info from Philippe, a list of libraries for CentOS should work for all RedHat-based distributions, right? Except what about versions e.g. is the list the same in CentOS 6.5 vs. 7.1? And if not how does one map that to versions of e.g. RHEL? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-on-Centos-RHEL-7-1-tp4821602p4821621.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
centos 6.5 is fine for rhel6. those are clones. centos is built from the same sourcetree has rhel. the pictures are different but the code is the same. havent tested on 7. phil Le 24 avr. 2015 15:02, "Sean P. DeNigris" <sean@clipperadams.com> a écrit :
nacho wrote
I noticed that in Pharo's homepage now there is a link to a Centos build. However, the necessary 32bits libs are not mentioned.
Thanks! I was holding off on this because there are several such lists out there and I'm not sure which apply to which platforms. For example,
https://github.com/philippeback/pharovm-centos65/blob/master/packages-to-ins... is a very different list for Centos65. IIRC now after some info from Philippe, a list of libraries for CentOS should work for all RedHat-based distributions, right? Except what about versions e.g. is the list the same in CentOS 6.5 vs. 7.1? And if not how does one map that to versions of e.g. RHEL?
----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-on-Centos-RHEL-7-1-tp4821602p4821621.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
philippeback wrote
centos 6.5 is fine for rhel6. those are clones.
Do you know if that's true in general for the entire RedHat family (e.g. Fedora)? Or for other families? E.g. Debian/Ubuntu/Mint? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-on-Centos-RHEL-7-1-tp4821602p4821623.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On Fri, Apr 24, 2015 at 3:08 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:
philippeback wrote
centos 6.5 is fine for rhel6. those are clones.
Do you know if that's true in general for the entire RedHat family (e.g. Fedora)? Or for other families? E.g. Debian/Ubuntu/Mint?
I do not use Fedora, so I do not know. Usually Fedora is the leading edge while CentOS/RHEL are the stable things that are maintained for a long time. Debian/Ubuntu/Mint: They are all debian based but that doesn't mean that they are aligned. So, I do not know about those. Phil
----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-on-Centos-RHEL-7-1-tp4821602p4821623.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
nacho wrote
I noticed that in Pharo's homepage now there is a link to a Centos build. However, the necessary 32bits libs are not mentioned.
For now, I put a NB with a link to the 64-bit prep instructions on our GNU/Linux download page [1]. For the known cases, I wonder if the best course wouldn't be to bundle the VMs with a prep64bit.sh e.g. Philippe already has such a script and it seems we could just inject it into the CI build. nacho wrote
Or at least inside the README.txt that comes in the zip.
Unless we can do that programmatically, I'm hesitant to put anything more than a link to [1], because it will be duplicated logic e.g. probably always out of date! In general, it seems there is already a good deal of duplication out there as many of use have rolled our own 32-bit solutions. We're in the process of bringing these under Pharo's GitHub organization, and I'm calling for anyone with a working solution to add it to https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/DownloadI... . It's hard for me to manage all these great contributions via the mailing list :/ Here's what we've accomplished so far: - the method for different platforms leaves you with different products (e.g. Ubuntu -> Launcher, but Debian -> VM-only). [SOLVED]: The downloads were standardized and categorized - default is vm+image.zip for all platforms, other options (e.g. launcher or vm-only) were made explicit - the instructions at http://pharo.org/download are incomplete (e.g. Debian step 2.i.a below)[SOLVED]: We gave the website GNU/Linux instructions a massive overhaul. See http://pharo.org/gnu-linux-installation - Old Lib C downloads out of date: http://files.pharo.org/vm/pharo/linux/old-libc/ last pharovm-ubuntu804.tar.gz is from 8/28/2013, but most recent swing buld is from 9/2014.[SOLVED]: We now have our own libc < 2.15 CI build, with artifacts mirrored to files.pharo.org, and linked from the website - Can we pick up the debian artifact from the Debian build and create a launcher on our CI with it? [SOLVED]: We now have our own libc < 2.15 CI build, with artifacts mirrored to files.pharo.org, and linked - [SOLVED]: Link Launcher instructions to the Launcher tutorial. - [SOLVED]: Remove all GNU/Linux instructions from the main download page. Instead, when a user clicks on the Linux button, they should be taken to a whole different page that explains the intricacies of each platform. - [SOLVED]: put a clear heading for each GNU/Linux flavor (e.g. ###Debian instead of "Looking for a debian distribution?") - [SOLVED]: [OT]: Change all references to Linux -> GNU/Linux. See https://www.gnu.org/gnu/gnu-linux-faq.html#why [1] http://pharo.org/gnu-linux-installation#64-bit-System-Setup ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-on-Centos-RHEL-7-1-tp4821602p4821628.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
participants (3)
-
nacho -
phil@highoctane.be -
Sean P. DeNigris