Oracle Solaris 11 and OpenIndiana are two different platform. Why do you expect 
the binary compiled on one will run on the other?




---- On Mon, 18 Jan 2021 06:50:31 +0700 Ali Muhammed Patrash 
<[email protected]> wrote ----

 > > "I used to think about cross compile from Linux. But I can only has the C 
 > > cross compiler working. Everything C++ failed." 
 >  
 > Hello! 
 > Why not to compile from Oracle Solaris 11.3? 
 > I had success to compile gcc-9.2.0, arm-tools, avr-tools with avrdude, 
 > nodejs-v9.9.0 and even qemu-5.1.0 
 > Now i'm learning to write device drivers and pack packages in a better way 
 > for Oracle Solaris 11.3 in hope to apply this knowledge for OI. 
 > But i had no way to install OI on my Microsoft Surface. 
 >  
 > ________________________________________ 
 > From: Hung Nguyen Gia via oi-dev [[email protected]] 
 > Sent: Sunday, January 17, 2021 2:59 AM 
 > To: "Adam Števko" 
 > Cc: Hung Nguyen Gia; OpenIndiana Developer mailing list; Openindiana Discuss 
 > Subject: Re: [oi-dev] OpenIndiana Developer Edition 
 >  
 > Sorry because I had caused all of this misunderstanding. I'm not good at 
 > English. The product of Google Translate + poor human skills created this. 
 > My choice of words is unwise or could be plain wrong. Due to affect of 
 > mental drugs I have to take, I did many weirded things on this list. Sorry 
 > everyone. 
 >  
 > Let me describe what I want to do: 
 >  
 > I'm not going to create a fork. 
 >  
 > The current OI Desktop doesn't include build tools by default. I suggest to 
 > add the build-essential package, so it's possible to build illumos-gate 
 > using the live image, without having to install to HDD, given we had enough 
 > RAM and external disk space. 
 >  
 > Given my experience so far, I think this will not be accepted. So I'm going 
 > to create my own live image of OI, I would called OI Developer Edition, if 
 > I'm allowed to use the name OI. I would use this image for myself, but could 
 > share with others, too. Perhaps I will upload it to my Google Drive. 
 >  
 > I had read about Distribution Constructor. But have no experience with it so 
 > far. So I'm asking for a guide how to use this tool to create my own image 
 > of OI. 
 >  
 > I think I will pull packages from OI's repo but not build anything myself if 
 > it's possible. 
 >  
 > What I wanted to do is nothing other than remastering OI. Remastering a 
 > distro is what we do very regular on Linux. We have tools to do this, e.g: 
 > https://github.com/MX-Linux/mx-snapshot and 
 > https://github.com/MX-Linux/mx-remaster 
 >  
 > I think Distribution Constructor is the equivalent tool on OI. Correct me if 
 > I'm wrong. 
 >  
 > The packages listed other than build-essential is for building Pale Moon. 
 > Yes, Pale Moon again. 
 >  
 > Your project refused to package it. Atenian200 after the clash with you also 
 > no longer provide prebuilt binary. The last version he provided is here: 
 > https://forum.palemoon.org/viewtopic.php?f=40&t=24613 which is a very 
 > outdated one. If someone wanted to get Pale Moon, they have to compile from 
 > source. 
 >  
 > OI currently has problems with my UEFI firmware. I can only run OI as a live 
 > usb but the installed OI I still keep on my SSD is unable to boot. 
 >  
 > Everything I did is seeking for a workaround for this: a live system with 
 > all of the tools needed. 
 >  
 > I'm going to provide up to date prebuilt binary of Pale Moon. Of course, via 
 > my Google Drive. 
 >  
 > But it's all cheap talks if I can't run OI itself. 
 >  
 > I used to think about cross compile from Linux. But I can only has the C 
 > cross compiler working. Everything C++ failed. 
 >  
 > Cross compiling a complex software like Pale Moon also means asking for 
 > troubles. 
 >  
 > ---- On Sun, 17 Jan 2021 00:14:51 +0700 Adam Števko <[email protected]> 
 > wrote ---- 
 >  
 >  > Hello, 
 >  > 
 >  > out or curiosity, what exactly is the point and added of your proposed 
 > fork? Those packages can be easily installed any time after installing OI. 
 >  > 
 >  > I am not sure which exact changes were rejected, but if your raise a 
 > discussion and explain clearly why they are needed, OI developers are more 
 > than happy to accept. 
 >  > 
 >  > So, instead of forking and creating a “new distribution”, further 
 > fragmenting the illumos distribution market, cooperate and help us improve 
 > the existing project. There are lot of gaps where improvements are needed 
 > and extra manpower is more than welcome. At the end, I can’t tell you want 
 > to do, but can try and nicely ask you to collaborate. Please, collaborate 
 > with OI team to improve the current experience, more people will benefit 
 > from it! 
 >  > 
 >  > P.S: Keeping python-27 around is quite dangerous as the upstream ended 
 > any kind of support of Python 2.x and without proper experience you are just 
 > put potential users in danger. 
 >  > 
 >  > Thanks for understanding, 
 >  > Adam 
 >  > 
 >  > 
 >  > 
 >  > > On 16 Jan 2021, at 11:02, Hung Nguyen Gia via oi-dev 
 > <[email protected]> wrote: 
 >  > > 
 >  > > Someone on this list challenged me of forking OpenIndiana in order for 
 > my changes to be accepted. This is exactly what I'm going to do now. But I 
 > will do it moderately, according to my skills. 
 >  > > 
 >  > > I wanted to build something like in the title. 
 >  > > 
 >  > > It's the normal desktop OI plus the following packages: 
 >  > > 
 >  > > build-essential 
 >  > > cmake 
 >  > > ninja 
 >  > > meson 
 >  > > yasm 
 >  > > autoconf-213 
 >  > > header-audio 
 >  > > sunpro 
 >  > > motif 
 >  > > python-27 
 >  > > 
 >  > > More packages would be included in the future, if needed. 
 >  > > 
 >  > > My computer power doesn't allow me to build everything myself, so I 
 > think I will just pull the packages from OI repo. 
 >  > > 
 >  > > The goal is to have a live ISO/USB images contain these additional 
 > packages. 
 >  > > 
 >  > > I have come across this wiki: 
 >  > > 
 >  > > http://docs.openindiana.org/dev/distribution-constructor/ 
 >  > > 
 >  > > But it's still not very clear to me. Any help would be appreciated. 
 >  > > 
 >  > > _______________________________________________ 
 >  > > oi-dev mailing list 
 >  > > [email protected] 
 >  > > https://openindiana.org/mailman/listinfo/oi-dev 
 >  > 
 >  
 > _______________________________________________ 
 > oi-dev mailing list 
 > [email protected] 
 > https://openindiana.org/mailman/listinfo/oi-dev 
 > _______________________________________________
 > oi-dev mailing list
 > [email protected]
 > https://openindiana.org/mailman/listinfo/oi-dev
 > 

_______________________________________________
oi-dev mailing list
[email protected]
https://openindiana.org/mailman/listinfo/oi-dev

Reply via email to