Re: [oi-dev] Porting of the Epiphany Browser
Maybe I just wasted my time your time, too, with this stupid GNOME sh8t. Just tried to compile it with clang-90 and it failed, again. Having to edit meson.build to commenting out flags again. They can't even make their software compile cleanly without having to turn off error checking flags. Or these morons just paranoid and turned every fuckin flags on when in fact they should not be considered as errors? It seemed they hard coded the compiler and linker commands, too. Environment variables can't overwrite this. Regardless of everything, it stills invoke the incorrect command to link. Even if I use the make file you wanted to give me that integrated with your oi-userland stuffs, I think so. That sh8t will not compile if we do not patch these fuckin meson build scripts ourselves. I hate this meson sh8t. They intended to replace cmake, another sh8t, that only to be another PoS. Maybe their Pythonic syntax you are already familiar with you could deal easier than me. I give up on this sh8t altogether. On Sun, 10 Jan 2021 12:47:50 +0700 Hung Nguyen Gia via oi-dev wrote > I guest I figured out how to make libdazzle compiles, but I fails at the > linking stage. Not related to the Solaris patch, though. That patch doesn't > help. > > Let me describe the problems in details: > > libdazzle fails to compile because of a compiler flag. With this flag on, it > will fail with this error: https://pastebin.com/bqnZUUrN > > We have to edit meson.build and comment out > '-Werror=incompatible-pointer-types', from test_c_args like this: > https://pastebin.com/DWbE4xSE > > The it will build happily. But will suddenly fail because the system was > hard coded to use gcc-7! > > See this: https://pastebin.com/8K4XR7fv > > After installing gcc-7 with pkg, gcc-7 replaced gcc-10 as the default > compiler. We now could get over this. > > But again, it suddenly fails because it can't execute 'cc'. Unlike other > Unix system, OpenIndiana doesn't have the binary 'cc' available by default. > > This, too, caused many minor but annoying problems when porting software. A > simple symbolic link solved this: > > sudo ln -s /usr/bin/gcc /usr/bin/cc > > I wonder why this symlink doesn't created by default? This would save the > porters from many troubles! > > So finally, the command is this: > > CC='cc -m64' meson .. > > ninja --verbose > > The compilation fine, but the final linking stage fails, because of: > > ld: fatal: file > /export/home/giahung/Downloads/libdazzle-3.38.0/build/tmp-introspect2wjcgx9j/Dazzle-1.0.o: > wrong ELF class: ELFCLASS64 > ld: fatal: file processing errors. No output written to > /export/home/giahung/Downloads/libdazzle-3.38.0/build/tmp-introspect2wjcgx9j/Dazzle-1.0 > > collect2: error: ld returned 1 exit status > > See here for more detail: https://pastebin.com/Uvm62jNm > > That same old misery on any Illumos based system! Now, OI developers, this > is you have to deal with this to have libdazzle packaged in your repo. > > After that, I could continue with Epiphany itself. > > On Sun, 10 Jan 2021 09:53:21 +0700 Hung Nguyen Gia via oi-dev > wrote > > > More detail: > > > > Packages needed to install on OI: gcc-10 cmake ninja meson git pkg-config > vala > > > > Environment variable to set: export > PKG_CONFIG_PATH='/usr/lib/64/pkgconfig' > > > > We're doing a 64 bit build. I don't know why, but gobject-introspection > is not available on/usr/lib/pkgconfig, so we forced to do a 64 bit build > > > > Get the latest 3.x release of them: > > > > https://gitlab.gnome.org/GNOME/epiphany > > > > https://gitlab.gnome.org/GNOME/libdazzle > > > > Follow the build instructions. > > > > mkdir build && cd build > > > > CC='gcc -m64' CXX='g++ -m64' meson .. > > > > ninja --verbose > > > > The error will be straight forward of you. > > > > It's a compilation error. So your patch of the linker part doesn't help. > > > > ___ > > oi-dev mailing list > > oi-dev@openindiana.org > > https://openindiana.org/mailman/listinfo/oi-dev > > > > ___ > oi-dev mailing list > oi-dev@openindiana.org > https://openindiana.org/mailman/listinfo/oi-dev > ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] Shipping the nano editor alongside with vi
Maybe... I'm impolite. But what if I'm just visit here once for this purpose then? I only care about the result. Maybe I'm posted on the wrong mailing list. Maybe OI-discuss more fit? The only thing I want to see and to care is: the next version of OI, nano is included alongside of vi in the text and minimal version. It's just simple as that. Why make thing complicated? Or this whole DIY stuffs here is just a polite way to say: we don't care about your concern and it you could send we a pull request we may 'optionally' consider it? Then just said: 'Fuck off! We don't care!'. Straight forward so I could know to silently go away. This will not waste our time with a bunch of back and forth emails. On Sun, 10 Jan 2021 14:19:14 +0700 Tim Mooney via oi-dev wrote > In regard to: Re: [oi-dev] Shipping the nano editor alongside with vi, > Hung...: > > > Yes, it's just a single line. But why you give me a read-only file and > > asked me to modified it? > > > > It's much more simpler for developer with write access to do it, not me. > > And it's within a second, just a single line. > > I don't know if other languages and cultures have an equivalent, but there > is a proverb[1] that applies here: > > If you give a man a fish, you feed him for a day. > If you teach a man to fish, you feed him for a lifetime. > > Teaching someone (or helping them learn) how to do something is often > more useful than just doing something (once) for them. > > Aurélien is trying to help you to learn to fish. > > Learning how to clone oi-userland, create a branch, make a very simple > change like this, and submit a pull request (PR) is very useful knowledge > to have for anyone that wants to contribute to OI. There are certainly > other ways to contribute, but since you're posting to the oi-dev list, > it seems like you might be interested in the development process. Knowing > the workflow for submitting a change is potentially beneficial to you. > > Yes, he could do it in just a couple minutes. But then you've missed an > opportunity to learn something that might allow you to contribute to OI. > > [1] the origin of this proverb appears to be quite contested, but it > seems like it might be Lao-Tzu. > > Tim > > > On Sun, 10 Jan 2021 00:49:50 +0700 Aurélien Larcher > > wrote > > > > > > > > > > > On Sat, Jan 9, 2021 at 9:09 AM Hung Nguyen Gia via oi-dev > > > wrote: > > > This should be done for none desktop OI flavors: OI text and OI minimal. > > > > > > It will help novice user like me very much. Please consider it, > > > developers. I have trouble using the vi editor even though I have my > > > mobile phone with me as a backup showing the vi tutorial. And I think > > > many other novice users have the same trouble as me. > > > > > > Doing as Fedora is a step too far: > > > https://www.phoronix.com/scan.php?page=news_item=Fedora-33-Nano-Is-The-Default > > > > > > > > > I only asked for shipping nano alongside with vi. The link I put above > > > just to note that nano has pretty much become the default editor on the > > > Linux world and most of us come from Linux. It will be easier for us. > > > Thanks. > > > > > > Hello, > > > basically one could add the nano package to: > > > > > > https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/meta-packages/install-types/includes/minimal > > > > > > > > > Kind regards, > > > > > > Aurélien > > > > > > > > > > > > ___ > > > oi-dev mailing list > > > oi-dev@openindiana.org > > > https://openindiana.org/mailman/listinfo/oi-dev > > > > > > > > > -- > > > --- > > > Praise the Caffeine embeddings > > > ___ > > > oi-dev mailing list > > > oi-dev@openindiana.org > > > https://openindiana.org/mailman/listinfo/oi-dev > > > > > > > ___ > > oi-dev mailing list > > oi-dev@openindiana.org > > https://openindiana.org/mailman/listinfo/oi-dev > > > > -- > Tim Mooney tim.moo...@ndsu.edu > Enterprise Computing & Infrastructure / > Division of Information Technology/701-231-1076 (Voice) > North Dakota State University, Fargo, ND > 58105-5164___ > oi-dev mailing list > oi-dev@openindiana.org > https://openindiana.org/mailman/listinfo/oi-dev > ___ oi-dev mailing list oi-dev@openindiana.org https://openindiana.org/mailman/listinfo/oi-dev
