[OpenIndiana-discuss] Rust 1.29

[Aurélien Larcher]

Hi,
based on the work by Carsten inspired by the pkgsrc package, then Michal's
modification of my 1.28 recipe, Rust 1.29 was pushed to the repository:

http://pkg.openindiana.org/hipster/info/0/developer%2Flang%2Frustc%401.29.0%2C5.11-2018.0.0.0%3A20180920T025956Z

I tested compilation of a few packages and rust-by-example.

Thanks go to Nikita Baksalyar, Jonathan Perkin, and Solaris engineers for
making Rust on SunOS possible.
Kind regards,

Aurélien

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] Rust 1.28 testing package

[Aurélien Larcher]

For anyone interested there is a testing package of rust 1.28 at

https://pkg.openindiana.org/gcc-next/

pkg://userland/developer/lang/rustc@1.28.0,5.11-2018.0.0.0:20180912T121658Z

The repository is built with gcc-8 so a new BE and a good bandwidth are
required.

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] compile package

[Aurélien Larcher]

On Tue, Sep 11, 2018 at 11:30 PM, Francis.D  wrote:

> Sorry I haven't tested yet.
> Yesterday I broke my system. I'm going to make myself a dedicated
> environment because on my laptop it's not ideal.
> I'm going to install an IO on a dedicated desktop. I noticed that there is
> a lot of library missing to compile packages. By using sources.
> I have tested some applications but there is still a library missing or the
> version is too old.
>

Can you be more specific?

>
>
> Le mar. 11 sept. 2018 à 15:48, Aurélien Larcher <
> aurelien.larc...@gmail.com>
> a écrit :
>
> > On Mon, Sep 10, 2018 at 5:58 PM, Aurélien Larcher <
> > aurelien.larc...@gmail.com> wrote:
> >
> > >
> > >
> > > On Mon, Sep 10, 2018 at 5:01 PM, Francis.D  wrote:
> > >
> > >> I have downloaded the vlc archive.
> > >> It seems there are a few Warnings and I can't go any further. I'll try
> > >> to fix the problems.
> > >>
> > >
> > I updated my ffmpeg and vlc branches to 3.2.11 and 3.0.4 respectively.
> > I tested that the resulting package works reasonably well.
> >
> >
> >
> > >
> > > You need to update ffmpeg and recompile gstreamer plugins first.
> > > See https://github.com/OpenIndiana/oi-userland/pull/4034
> > >
> > > Also oi-userland provides set environment variables and such to avoid
> > > issues e.g related to using non-GNU commands.
> > > It is better to use the same environment especially if you are not
> > > experienced with packaging on OI.
> > >
> > > Clone oi-userland, gmake setup at the top directory, then pull my
> ffmpeg
> > > and vlc branches.
> > >
> > >
> > >>
> > >> here is the result of the command ./configure
> > >>
> > >> root@oifanboy:~/paquet/vlc-3.0.4# ./configure
> > >> ./configure: line 4734: : cannot execute [Is a directory]
> > >> ./configure[4734]:  | sed -e 's/\\//g': not found [No such file or
> > >> directory]
> > >> checking build system type... i386-pc-solaris2.11
> > >> checking host system type... i386-pc-solaris2.11
> > >> checking for a BSD-compatible install... /usr/bin/ginstall -c
> > >> checking whether build environment is sane... yes
> > >> checking for a thread-safe mkdir -p... /usr/bin/gmkdir -p
> > >> checking for gawk... gawk
> > >> checking whether make sets $(MAKE)... yes
> > >> checking whether make supports nested variables... yes
> > >> checking whether UID '0' is supported by ustar format... yes
> > >> checking whether GID '0' is supported by ustar format... yes
> > >> checking how to create a ustar tar archive... gnutar
> > >> checking whether make supports nested variables... (cached) yes
> > >> checking whether to enable maintainer-specific portions of
> Makefiles...
> > >> yes
> > >> checking for gcc... gcc
> > >> checking whether the C compiler works... yes
> > >> checking for C compiler default output file name... a.out
> > >> checking for suffix of executables...
> > >> checking whether we are cross compiling... no
> > >> checking for suffix of object files... o
> > >> checking whether we are using the GNU C compiler... yes
> > >> checking whether gcc accepts -g... yes
> > >> checking for gcc option to accept ISO C89... none needed
> > >> checking whether gcc understands -c and -o together... yes
> > >> checking whether make supports the include directive... yes (GNU
> style)
> > >> checking dependency style of gcc... gcc3
> > >> checking how to run the C preprocessor... gcc -E
> > >> checking for grep that handles long lines and -e... /usr/bin/ggrep
> > >> checking for egrep... /usr/bin/ggrep -E
> > >> checking for ANSI C header files... yes
> > >> checking for sys/types.h... yes
> > >> checking for sys/stat.h... yes
> > >> checking for stdlib.h... yes
> > >> checking for string.h... yes
> > >> checking for memory.h... yes
> > >> checking for strings.h... yes
> > >> checking for inttypes.h... yes
> > >> checking for stdint.h... yes
> > >> checking for unistd.h... yes
> > >> checking minix/config.h usability... no
> > >> checking minix/config.h presence... no
> > >> checking for minix/config.h... no
> > >> checking whether it is safe to define __EXTENSIONS__...

Re: [OpenIndiana-discuss] kde on openindiana

[Aurélien Larcher]

On Tue, Sep 11, 2018 at 10:19 PM, Tim Mooney  wrote:

> In regard to: [OpenIndiana-discuss] kde on openindiana, Martin
> Lindkvist...:
>
> So if anyone can point me in the right direction... where to find KDE i
>> would be happie ... or is it that i have to compile it and is it anything
>> that I have to think about when i compile on Unix compared to if i compile
>> it on GNU/Linux?
>>
>
Another task would be to update Qt from 5.8 to 5.9 since 5.9 is a LTS.
I added 5.8 but have no time to look at 5.9, it should not be too hard.



>
> It's a very small group of people that are currently advancing the parts
> of OI that are only present on OI.  Everyone likes choice and flexibility,
> but packaging and testing multiple graphical desktop environments would
> reduce the time that the core contributors could spend on other things.
> They've settled on MATE as the single desktop environment they want to
> provide.
>
> Keep in mind too that they have their own reasons for using and
> contributing to OI, so spending a bunch of time porting, building, and
> packaging something that they won't personally use is probably not very
> appealing.
>
> People with the time, drive, and interest to contribute other environments
> are welcome, but something as big as KDE isn't a contribution that's
> ever "done".  It's a bit of a long-term commitment to try provide a second
> graphical desktop environment.  It would be counterproductive to have
> one KDE version packaged and provided but then have it go un-maintained and
> bit-rot or have security issues go unpatched.
>
> Tim
> --
> Tim Mooney tim.moo...@ndsu.edu
> Enterprise Computing & Infrastructure  701-231-1076 (Voice)
> Room 242-J6, Quentin Burdick Building  701-231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] compile package

[Aurélien Larcher]

On Mon, Sep 10, 2018 at 5:58 PM, Aurélien Larcher <
aurelien.larc...@gmail.com> wrote:

>
>
> On Mon, Sep 10, 2018 at 5:01 PM, Francis.D  wrote:
>
>> I have downloaded the vlc archive.
>> It seems there are a few Warnings and I can't go any further. I'll try
>> to fix the problems.
>>
>
I updated my ffmpeg and vlc branches to 3.2.11 and 3.0.4 respectively.
I tested that the resulting package works reasonably well.



>
> You need to update ffmpeg and recompile gstreamer plugins first.
> See https://github.com/OpenIndiana/oi-userland/pull/4034
>
> Also oi-userland provides set environment variables and such to avoid
> issues e.g related to using non-GNU commands.
> It is better to use the same environment especially if you are not
> experienced with packaging on OI.
>
> Clone oi-userland, gmake setup at the top directory, then pull my ffmpeg
> and vlc branches.
>
>
>>
>> here is the result of the command ./configure
>>
>> root@oifanboy:~/paquet/vlc-3.0.4# ./configure
>> ./configure: line 4734: : cannot execute [Is a directory]
>> ./configure[4734]:  | sed -e 's/\\//g': not found [No such file or
>> directory]
>> checking build system type... i386-pc-solaris2.11
>> checking host system type... i386-pc-solaris2.11
>> checking for a BSD-compatible install... /usr/bin/ginstall -c
>> checking whether build environment is sane... yes
>> checking for a thread-safe mkdir -p... /usr/bin/gmkdir -p
>> checking for gawk... gawk
>> checking whether make sets $(MAKE)... yes
>> checking whether make supports nested variables... yes
>> checking whether UID '0' is supported by ustar format... yes
>> checking whether GID '0' is supported by ustar format... yes
>> checking how to create a ustar tar archive... gnutar
>> checking whether make supports nested variables... (cached) yes
>> checking whether to enable maintainer-specific portions of Makefiles...
>> yes
>> checking for gcc... gcc
>> checking whether the C compiler works... yes
>> checking for C compiler default output file name... a.out
>> checking for suffix of executables...
>> checking whether we are cross compiling... no
>> checking for suffix of object files... o
>> checking whether we are using the GNU C compiler... yes
>> checking whether gcc accepts -g... yes
>> checking for gcc option to accept ISO C89... none needed
>> checking whether gcc understands -c and -o together... yes
>> checking whether make supports the include directive... yes (GNU style)
>> checking dependency style of gcc... gcc3
>> checking how to run the C preprocessor... gcc -E
>> checking for grep that handles long lines and -e... /usr/bin/ggrep
>> checking for egrep... /usr/bin/ggrep -E
>> checking for ANSI C header files... yes
>> checking for sys/types.h... yes
>> checking for sys/stat.h... yes
>> checking for stdlib.h... yes
>> checking for string.h... yes
>> checking for memory.h... yes
>> checking for strings.h... yes
>> checking for inttypes.h... yes
>> checking for stdint.h... yes
>> checking for unistd.h... yes
>> checking minix/config.h usability... no
>> checking minix/config.h presence... no
>> checking for minix/config.h... no
>> checking whether it is safe to define __EXTENSIONS__... yes
>> checking whether gcc  supports C11... yes
>> checking for g++... g++
>> checking whether we are using the GNU C++ compiler... yes
>> checking whether g++ accepts -g... yes
>> checking dependency style of g++... gcc3
>> checking how to run the C preprocessor... gcc -E
>> checking for gcc... gcc
>> checking whether we are using the GNU Objective C compiler... yes
>> checking whether gcc accepts -g... yes
>> checking dependency style of gcc... gcc3
>> checking for egrep... (cached) /usr/bin/ggrep -E
>> checking whether make sets $(MAKE)... (cached) yes
>> checking dependency style of gcc... gcc3
>> checking for flex... flex
>> checking lex output file root... lex.yy
>> checking lex library... -ll
>> checking whether yytext is a pointer... yes
>> checking for bison... bison -y
>> checking for desktop-file-validate... desktop-file-validate
>> checking for c11-gcc... no
>> checking for c11... no
>> checking for c99-gcc... no
>> checking for c99... c99
>> checking for an ANSI C-conforming const... yes
>> checking for inline... inline
>> checking for C/C++ restrict keyword... __restrict
>> checking whether g++ supports C++11 features by default... yes
>> checking whether C compiler accepts -Werror=unknown-warning-option... no
>> checking wheth

Re: [OpenIndiana-discuss] compile package

[Aurélien Larcher]

t; checking for DVDNAV... yes
> checking for dvdnav_stream_cb in dvdnav/dvdnav.h... yes
> checking for BLURAY... yes
> checking for OPENCV... no
> configure: WARNING: Library opencv > 2.0 needed for opencv was not found
> checking for SMBCLIENT... yes
> checking for DSM... no
> configure: WARNING: Library libdsm >= 0.2.0 needed for dsm was not found
> checking for SFTP... yes
> checking for NFS... no
> configure: WARNING: Library libnfs >= 1.10.0 needed for nfs was not found
> checking linux/videodev2.h usability... no
> checking linux/videodev2.h presence... no
> checking for linux/videodev2.h... no
> checking sys/videoio.h usability... no
> checking sys/videoio.h presence... no
> checking for sys/videoio.h... no
> checking DeckLinkAPIDispatch.cpp usability... no
> checking DeckLinkAPIDispatch.cpp presence... no
> checking for DeckLinkAPIDispatch.cpp... no
> configure: WARNING: Blackmagic DeckLink SDI include files not found
> checking for cdrom_msf0 in linux/cdrom.h... no
> checking for scsireq in sys/scsiio.h... no
> checking for ioc_toc_header in sys/cdio.h... no
> checking for LIBCDDB... yes
> checking for Linux DVB version 5.1... no
> checking for VNC... no
> configure: WARNING: Library libvncclient >= 0.9.9 needed for vnc was not
> found
> checking for FREERDP... no
> configure: WARNING: Library freerdp >= 1.0.1 needed for freerdp was not
> found
> checking for ASDCP... no
> checking for DVBPSI... yes
> checking gme/gme.h usability... no
> checking gme/gme.h presence... no
> checking for gme/gme.h... no
> checking for SID... no
> configure: WARNING: No package 'libsidplay2' found (required for sid).
> checking for OGG... yes
> checking for LIBVORBIS... yes
> checking for OGG... yes
> checking for SHOUT... no
> configure: WARNING: Library shout >= 2.1 needed for shout was not found
> checking for MATROSKA... yes
> checking for LIBMODPLUG... no
> configure: WARNING: No package 'libmodplug' found
> No package 'libmodplug' found.
> checking mpc/mpcdec.h usability... no
> checking mpc/mpcdec.h presence... no
> checking for mpc/mpcdec.h... no
> checking mpcdec/mpcdec.h usability... yes
> checking mpcdec/mpcdec.h presence... yes
> checking for mpcdec/mpcdec.h... yes
> checking for SHINE... no
> configure: WARNING: Library shine >= 3.0.0 needed for shine was not found
> checking for libcrystalhd/libcrystalhd_if.h... no
> checking mad.h usability... yes
> checking mad.h presence... yes
> checking for mad.h... yes
> checking for mad_bit_init in -lmad... yes
> checking for MPG123... no
> configure: WARNING: Library libmpg123 needed for mpg123 was not found
> checking for GST_APP... yes
> checking for GST_VIDEO... yes
> checking for libavutil variant... ffmpeg
> checking for AVCODEC... no
> configure: error: Requested 'libavcodec >= 57.37.100' but version of
> libavcodec is 56.60.100. Pass --disable-avcodec to ignore this error.
> root@oifanboy:~/paquet/vlc-3.0.4#
>
>
> 2018-09-10 10:19 UTC−04:00, Aurélien Larcher :
> > On Mon, Sep 10, 2018 at 4:14 PM, Francis.D  wrote:
> >
> >> Merci Jean-Pierre.
> >>
> >> I checked the qt version install and actually the 2 versions of qt are
> >> installed on hipster.  Yesterday I also installed * build-essential *
> >> and I would like to build some packages because we are really limited
> >> or we have old versions.
> >> but I need to study and understand the process of building Oi userland.
> >> This is not a criticism. The team is small and if I can contribute it
> >> will make me happy.
> >>
> >>
> > Some notes at:
> >
> > - https://wiki.openindiana.org/oi/2.+Overview+of+the+Build+System
> > - https://wiki.openindiana.org/oi/3.+Common+Tasks
> >
> >
> >> But for the moment I'm trying some local compilations. I'am also tried
> >> gnumeric without no success.
> >>
> >> I'm going to drop smplayer because it seems to be missing files to
> >> compile under OI
> >> I will try VLC 3.0.4
> >>
> >
> > You can look at updating my recipe:
> >
> > https://github.com/OpenIndiana/oi-userland/pull/4035
> >
> >
> >
> >>
> >> regard
> >>
> >> 2018-09-10 3:20 UTC−04:00, Jean-Pierre :
> >> > Francis.D wrote:
> >> >> Hi all,
> >> >> I'm trying to compile smplayer. I have previously installed gcc +
> >> >> automake
> >> >> + autoconf
> >> >>
> >> >> I downloaded the source package smplayer-18.6.0.tar.bz2 package and
> >> >> unzip.
> >> >> Then I 

Re: [OpenIndiana-discuss] compile package

[Aurélien Larcher]

On Mon, Sep 10, 2018 at 4:14 PM, Francis.D  wrote:

> Merci Jean-Pierre.
>
> I checked the qt version install and actually the 2 versions of qt are
> installed on hipster.  Yesterday I also installed * build-essential *
> and I would like to build some packages because we are really limited
> or we have old versions.
> but I need to study and understand the process of building Oi userland.
> This is not a criticism. The team is small and if I can contribute it
> will make me happy.
>
>
Some notes at:

- https://wiki.openindiana.org/oi/2.+Overview+of+the+Build+System
- https://wiki.openindiana.org/oi/3.+Common+Tasks


> But for the moment I'm trying some local compilations. I'am also tried
> gnumeric without no success.
>
> I'm going to drop smplayer because it seems to be missing files to
> compile under OI
> I will try VLC 3.0.4
>

You can look at updating my recipe:

https://github.com/OpenIndiana/oi-userland/pull/4035



>
> regard
>
> 2018-09-10 3:20 UTC−04:00, Jean-Pierre :
> > Francis.D wrote:
> >> Hi all,
> >> I'm trying to compile smplayer. I have previously installed gcc +
> >> automake
> >> + autoconf
> >>
> >> I downloaded the source package smplayer-18.6.0.tar.bz2 package and
> >> unzip.
> >> Then I executed the command cd
> >> root@oifanboy:~/downloads/smplayer-18.6.0#
> >> When I run the command ./configure I always get this message
> >> bash: ./configure: No such file or directory
> >
> > Being curious, I downloaded the source file, and there is
> > no configure in it (actually there are a couple of them, but
> > they are not targeted at building smplayer).
> >
> > There is a Makefile, which relies on qmake, so you have to
> > install qt and adjust the Makefile to the current version of
> > qt and to the appropriate paths...
> >
> > qt is apparently available on
> > http://sfe.opencsw.org/localhostoih/en/catalog.shtml
> >
> > This is a good start for learning how to develop or port
> > applications to OI.
> >
> >> I tried ./configure --prefix=usr without no success
> >>
> >> I also install intltool and I tried with another software * gnumeric*
> >> without not more success
> >>
> >> If anyone have a tuto step by step OI, what I need to install for
> compile
> >> software etc...
> >>
> >> thank
> >>
> >
> >
> >
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> >
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] OI Hipster: GDL not working because of broken plplot

[Aurélien Larcher]

On Fri, Sep 7, 2018 at 4:04 PM, Alexander Pyhalov  wrote:

> Hi.
>
> The issue is that we set relative paths in cmake.mk. I see that
> userland-gate cmake.mk uses full paths there. We coud either patch plplot
> to respect CMAKE_PREFIX in include files or fix cmake.mk. But if we touch
> cmake.mk,
> affected components should be checked.
>
> Aurelen, what do you think?
>
>
When I wrote cmake.mk I checked in the documentation that
CMAKE_INSTALL_FOODIR paths were defined as relative to CMAKE_INSTALL_PREFIX
so our cmake.mk is correct. Absolute path are given by
CMAKE_INSTALL_FULL_FOODIR.
If solaris-userland defines them otherwise then they do not follow the
convention.




> Best regards,
> Alexander Pyhalov,
> system administrator of Southern Federal University IT department
>
>
>
> 
> От: Udo Grabowski (IMK) 
> Отправлено: 7 сентября 2018 г. 15:36:51
> Кому: openindiana-discuss@openindiana.org
> Тема: Re: [OpenIndiana-discuss] OI Hipster: GDL not working because of
> broken plplot
>
> On 07/09/2018 14:06, Udo Grabowski (IMK) wrote:
> > On 07/09/2018 14:01, Udo Grabowski (IMK) wrote:
> >> On 07/09/2018 13:45, Udo Grabowski (IMK) wrote:
> >>> Says the most important driver for plplot, xwin, is not compiled
> >>> into plplot. I'm convinced it is, otherwise delivering plplot would
> >>> be futile, so it seems that something else is broken here:
> >>>
> >>> ro sunth7 ~ # ldd /usr/bin/gdl|grep plplot
> >>> libplplot.so.15 =>   /usr/lib/64/libplplot.so.15
> >>> libplplotcxx.so.13 =>/usr/lib/64/libplplotcxx.so.13
> >>>
> >>> ro sunth7 ~ # gdl
> >>>
> >>>   GDL - GNU Data Language, Version 0.9.7
> >>>
> >>> - For basic information type HELP,/INFO
> >>> - Default library routine search path used (GDL_PATH/IDL_PATH env.
> var. not
> >>> set):
> >>>   +/usr/share/gnudatalanguage/lib
> >>> - No startup file read (GDL_STARTUP/IDL_STARTUP env. var. not set).
> >>> - Please report bugs, feature or help requests and patches at:
> >>>   http://sourceforge.net/projects/gnudatalanguage/
> >>>
> >>> GDL> plot,findgen(100)
> >>>
> >>> *** PLPLOT WARNING ***
> >>> Unable to open cmap0 file cmap0_default.pal
> >>>
> >>> *** PLPLOT WARNING ***
> >>> Unable to open cmap0 file cmap0_default.pal
> >>>
> >>> *** PLPLOT WARNING ***
> >>> Unable to open cmap1 .pal file cmap1_default.pal
> >>>
> >>> *** PLPLOT ERROR, ABORTING OPERATION ***
> >>> plInitDispatchTable: Could not open drivers directory, aborting
> operation
> >>> % PLplot installation lacks the requested driver: xwin
> >>> % Execution halted at: $MAIN$
> >>> GDL>
> >>>
> >>> ro sunth7 ~ # ll  /usr/share/plplot5.13.0/
> >>> total 581
> >>> -r--r--r--   1 root bin55.9K Aug 17 12:04 cglobe.map
> >>> -r--r--r--   1 root bin  131 Aug 17 12:04
> cmap0_alternate.pal
> >>> -r--r--r--   1 root bin  195 Aug 17 12:04
> cmap0_black_on_white.pal
> >>> -r--r--r--   1 root bin  131 Aug 17 12:04 cmap0_default.pal
> >>> -r--r--r--   1 root bin  195 Aug 17 12:04
> cmap0_white_bg.pal
> >>> -r--r--r--   1 root bin   51 Aug 17 12:04
> cmap1_blue_red.pal
> >>> -r--r--r--   1 root bin  220 Aug 17 12:04
> cmap1_blue_yellow.pal
> >>> -r--r--r--   1 root bin   80 Aug 17 12:04 cmap1_default.pal
> >>> -r--r--r--   1 root bin   69 Aug 17 12:04 cmap1_gray.pal
> >>> -r--r--r--   1 root bin   51 Aug 17 12:04
> cmap1_highfreq.pal
> >>> -r--r--r--   1 root bin  105 Aug 17 12:04 cmap1_lowfreq.pal
> >>> -r--r--r--   1 root bin  426 Aug 17 12:04 cmap1_radar.pal
> >>> drwxr-xr-x   9 root sys   23 Aug 17 12:04 examples/
> >>> -r--r--r--   1 root bin32.8K Aug 17 12:04 globe.map
> >>> -r--r--r--   1 root bin2.30K Aug 17 12:04 pkgIndex.tcl
> >>> -r--r--r--   1 root bin6.26K Aug 17 12:04 plstnd5.fnt
> >>> -r--r--r--   1 root bin57.4K Aug 17 12:04 plxtnd5.fnt
> >>> drwxr-xr-x   2 root sys4 Aug 17 12:04 tcl/
> >>> -r--r--r--   1 root bin43.5K Aug 17 12:04 usa.map
> >>> -r--r--r--   1 root bin74.9K Aug 17 12:04 usaglobe.map
> >>>
> >>> ro sunth7 ~ # pkg list -a|fgrep -i plplot
> >>> image/plplot5.13.0-2018.0.0.0  i--
> >>>
> >>>
> >>> ro sunth7 ~ # pkg list -a | fgrep -i gdl
> >>> library/libgdl  3.28.0-2018.0.0.0  i--
> >>> scientific/gdl  0.9.7-2018.0.0.2   i--
> >>>
> >>
> >> Part1 of the problem has an explanation: The code searches for the
> files not
> >> in "/usr/share/plplot...", but in "share/plplot..." (and /usr/local as
> >> last resort) ! This insane:
> >>
> >> 3869:   open("cmap0_default.pal", O_RDONLY) Err#2 ENOENT
> >> 3869:   open("share/plplot5.13.0/cmap0_default.pal", O_RDONLY) Err#2
> ENOENT
> >> 3869:   open("/usr/local/plplot/lib/cmap0_default.pal", O_RDONLY)
> Err#2 ENOENT
> >>
> >> *** PLPLOT WARNING ***
> >> 3869:   write(2, "\n * * *   P L P L O T  ".., 

[OpenIndiana-discuss] GCC 8.2

[Aurélien Larcher]

Hi,
back from vacation, GCC 8.2 available for testing from the main repository
in a moment.
Additionnally I just fixed some component rebuilds and
pkg.openindiana.org/gcc-next built with gcc-8 is now in sync again with the
main repository, modulo that GCC 8.2 was already republished there.

Aurelien


-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] No audio on Ryzen system

[Aurélien Larcher]

Probably fix the Pulseaudio OSS backend or merge Alexander's PR to
default libmatemixer to OSS.

On 7/6/18, Gary Mills  wrote:
> I'm running OI-hipster on a system with an ASUS PRIME B350M-A
> motherboard and an AMD Ryzen 3 1200 Quad-Core Processor.  The device
> driver shows two audio hardware devices, both with drivers:
>
>   Audio   Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon
>   HD 6450 / 7450/8450/8490 OEM / R5 230/235/235X OEM] audiohd
>
>   Audio   Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh)
>   HD Audio Controller audiohd
>
> I also have an add-on video card, that shows up this way:
>
>   Video   Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO
>   [Radeon HD 7450]vgatext
>
> I have my speakers plugged into the light green jack on the back of
> the computer, but I get no sound from them.  I suspect that OI is
> using the wrong audio hardware device.  I have this device link:
>
>   lrwxrwxrwx   1 root root   7 Sep 20  2017 /dev/audio ->
> sound/0
>
> That corresponds to the Caicos HDMI Audio device.  There are actually
> two devices with single-letter names:
>
>   lrwxrwxrwx   1 root root   9 Sep 20  2017 /dev/sound/0 ->
> audiohd:0
>   lrwxrwxrwx   1 root root   9 Sep 20  2017 /dev/sound/1 ->
> audiohd:1
>
> The second one corresponds to the HD Audio Controller audio device.
>
> What's the best way to get sound working on this system?
>
> --
> -Gary Mills-  -refurb--Winnipeg, Manitoba, Canada-
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>


-- 
---
Praise the Caffeine embeddings

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] GCC 8 repository

[Aurélien Larcher]

Hi,
Two weeks ago I reactivated the Jenkins job on my buildbot to build
oi-userland with gcc-8.

The repository is synchronized at every PR at:

https://pkg.openindiana.org/gcc-next

These packages are compiled on my buildbot, only provided for testing and
debugging code produced with gcc-8.

There are two know issues:
1) Firefox on my laptop had a default User-Agent containing non-ASCII
characters.
2) Terminals do not forward CTRL^C so the terminal itself is killed.

Kind regards,

Aurélien

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] Move to category directories and pending component updates

[Aurélien Larcher]

Hi,
a while ago the decision was made to reorganize the components by category
in oi-userland as the number of items in 'components' directory made it
difficult to skim through the repo.

The layout is described at:

https://wiki.openindiana.org/oi/Categories+layout

Some weeks ago I scripted the move + some cosmetic modifications:

https://github.com/OpenIndiana/oi-userland/pull/3974

but 50 components still need to be processed: usually it means that these
components have not been touched in a while and need some love (update,
security patches, conversion to 64-bit).
Therefore instead of a blind mass move, a move-on-update would be better...

Would you be interested in starting to contribute to oi-userland, this is
one of the possible tracks.

You can choose one component in the list, cherry-pick the corresponding
commit from my branch, make it yours and update/patch the component if
applicable...

Kind regards,

Aurélien

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] how to write device drivers

[Aurélien Larcher]

Hi Ken,
Welcome to the mailing list!

You can refer to the illumos book "Writing Device Drivers":

https://illumos.org/books/wdd/preface.html

Specifically:

https://illumos.org/books/wdd/character-21002.html#character-21002

https://illumos.org/books/wdd/block-34861.html#block-34861

Kind regards,

Aurélien

On Fri, Jun 1, 2018 at 5:04 PM,  wrote:

> Hi,
>
> I am application engineer, but I want  to write device driver
> that run in user process.
>
> Character and Block device I want to write,
> But I do not know where am I start.
>
> chardev? very easy way , look /dev/null you lough,
> but I do not know where it place.
>
> and I do not know the magic number
> that how can I decide dev_no,
> more, the rule of /devices/.
>
> I order my new machine, the sandbox
> please tell me how to write drivers.
>
>
> Best regards,
> ken.
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] GCC 8 build status

[Aurélien Larcher]

Three components left:

developer/clang-40
> developer/gcc-5 (does not compile)
> runtime/sbcl (core dump)
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] GCC 8 build status

[Aurélien Larcher]

Aside from:

developer/clang-40
developer/gcc-5
developer/gcc-6
developer/gcc-7
runtime/sbcl

All the packages have been recompiled with gcc-8 and published to the
http://pkg.openindiana.org/gcc-6 repository.

I updated two machines for testing and two issues are present:
1) For some reason Firefox has a default User-Agent containing non-ASCII
characters that upset webservers. Overriding it with another string is
enough to work around the problem.
2) Similarly to tmux when linked to values-xpg(4|6).o, mate-terminal is
killed with CTRL^C instead of sending the signal.

I initially encountered some terminal resizing issue through ssh but cannot
reproduce them now after rebuilding and republishing another batch of
components.








On Fri, May 25, 2018 at 10:29 PM, Aurélien Larcher <
aurelien.larc...@gmail.com> wrote:

> Updated list:
>
> developer/clang-40
> developer/gcc-5
> developer/gcc-6
> developer/gcc-7
> developer/golang-18
> library/webkitgtk
> runtime/sbcl [coredump, sorry Alexander :( ]
>
> I have tested the resulting packages on my workstation and laptop
> (currently typing on the X230).
>
>>
>
> --
> ---
> Praise the Caffeine embeddings
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] GCC 8 build status

[Aurélien Larcher]

Updated list:

developer/clang-40
developer/gcc-5
developer/gcc-6
developer/gcc-7
developer/golang-18
library/webkitgtk
runtime/sbcl [coredump, sorry Alexander :( ]

I have tested the resulting packages on my workstation and laptop
(currently typing on the X230).

>

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] GCC 8 build status

[Aurélien Larcher]

Coffee break involves checking the build bot :)


> desktop/gnumeric
> desktop/gparted
> developer/clang-40
> developer/gcc-5
> developer/gcc-6
> developer/gcc-7
> developer/golang-18
> image/graphviz
> library/http-parser
> library/libraw
> library/webkitgtk
> runtime/sbcl [coredump, sorry Alexander :( ]
> scientific/hdf5
>

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] GCC 8 build status

[Aurélien Larcher]

Looking at the build results, only

desktop/gnumeric
desktop/gparted
developer/clang-40
developer/gcc-5
developer/gcc-6
developer/gcc-7
developer/golang-18
image/graphviz
library/http-parser
library/libodfgen
library/libraw
library/libsass
library/libwps
library/physfs
library/webkitgtk
library/zeromq/czmq
network/asterisk
network/udpxy
runtime/sbcl
scientific/hdf5

did not publish for various reasons.
The build zone repo sitory is synced at http://pkg.openindiana.org/gcc-6/
(reusing the old one).

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] mkvmerge fails

[Aurélien Larcher]

On Wed, May 23, 2018 at 5:44 PM, Apostolos Syropoulos via
openindiana-discuss  wrote:

>
>  >See if ffmpeg works for you.  Something like>
> >ffmpeg -i video.avi -i audio.avi -map 0:0 -map 1:0 -c copy -f matroska
> games.mkv
>
> First I have compiled both ffmpeg and mkvtools.
>
> fmpeg --version
> ffmpeg version 3.4.1 Copyright (c) 2000-2017 the FFmpeg developers
>   built with gcc 4.9.4 (GCC)
>   configuration: --prefix=/opt/gnu --enable-shared --enable-static
> --enable-libx264 --enable-gpl --enable-libmp3lame --enable-libvpx
> --enable-libvorbis --enable-libfdk-aac --enable-nonfree
>   libavutil  55. 78.100 / 55. 78.100
>   libavcodec 57.107.100 / 57.107.100
>   libavformat57. 83.100 / 57. 83.100
>   libavdevice57. 10.100 / 57. 10.100
>   libavfilter 6.107.100 /  6.107.100
>   libswscale  4.  8.100 /  4.  8.100
>   libswresample   2.  9.100 /  2.  9.100
>   libpostproc54.  7.100 / 54.  7.100
> Unrecognized option '-version'.
> Error splitting the argument list: Option not found
>
> Obviously, this cannot be distributed but this works just fine.
> But mkvmerge and mkvextract core dump immediately.
>

Multimedia libraries were updated recently, though advertized as ABI
compatible.
If you compiled mkvmerge and mkvextract yourself then you may need to
rebuild them.



>
> A.S.
>
>
> --
> Apostolos Syropoulos
> Xanthi, Greece
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] mkvmerge fails

[Aurélien Larcher]

On Wed, May 23, 2018 at 5:31 PM, Aurélien Larcher <
aurelien.larc...@gmail.com> wrote:

>
>
> On Wed, May 23, 2018 at 5:28 PM, Apostolos Syropoulos via
> openindiana-discuss <openindiana-discuss@openindiana.org> wrote:
>
>>  After upgrading I have noticed that neither mkvmerge nor mkvextract
>> work anymore!
>> $ mkvmerge -D audio.avi -A video.avi -o GAMES.mkv
>> terminate called after throwing an instance of 'std::bad_cast'
>>   what():  std::bad_cast
>> Abort (core dumped)
>>
>> I have no idea what this KTPI thing does but it certainly has
>> made my life more difficult. How can I deactivate it?
>>
>
What is the OI package containing mkvmerge?



>
>
>>
>> A.S.
>>
>>
>> --
>> Apostolos Syropoulos
>> Xanthi, Greece
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>
>
>
> --
> ---
> Praise the Caffeine embeddings
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] mkvmerge fails

[Aurélien Larcher]

On Wed, May 23, 2018 at 5:28 PM, Apostolos Syropoulos via
openindiana-discuss  wrote:

>  After upgrading I have noticed that neither mkvmerge nor mkvextract
> work anymore!
> $ mkvmerge -D audio.avi -A video.avi -o GAMES.mkv
> terminate called after throwing an instance of 'std::bad_cast'
>   what():  std::bad_cast
> Abort (core dumped)
>
> I have no idea what this KTPI thing does but it certainly has
> made my life more difficult. How can I deactivate it?
>

I am not sure this is related, this seems to be a plain runtime error.


>
> A.S.
>
>
> --
> Apostolos Syropoulos
> Xanthi, Greece
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] hwloc ABI incompatible update

[Aurélien Larcher]

Hi,
hwloc was updated to 2.x and requires recompilation of dependent code.
If you use parallel numerical libraries like PETSc you are affected by the
update.
Kind regards

Aurelien

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] OmniOS CE LX Zones and bhyve

[Aurélien Larcher]

On Fri, May 18, 2018 at 11:56 PM, Rasaki Temidire  wrote:

> Hello,
>
>
>
> Are there any plans to pull in any of the recent additions from omniOS CE
> illumos work that introduced LX zones and bhyve?  If it is already in the
> openIndiana repository, how can I update my current hipster 2018.04
> installation to take in those additions?  If not, are there any plans to
> pull those additions in or is openIndiana going to stay on vanilla
> illumos-gate like Tribblix (although he has an omniOS variant of late with
> the changes).
>

The project needs help to pull this type of thing and maintain it in the
long run.
Unless one or two persons volunteer and commit to rebase the branch once in
a while OpenIndiana will stay vanilla.
There is already quite a lot of work ongoing for modernizing the toolchain
and maintain the current set of packages.
LX itself is scattered across 900+ commits and merging it cleanly would
take a considerable amount of dedication :)

Kind regards,

Aurélien

>
>
>
> Rasaki
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] AMD graphics, revisited.

[Aurélien Larcher]

On Thu, May 17, 2018 at 5:22 AM, <srvr_...@srvr-tmpl.ikhider.com> wrote:

> You have less than that.
>
> : - )


We do have some AMD xorg driver but it is an old version as newer require
drm.



>
>
>
>
> On 16.05.2018 13:24, Aurélien Larcher wrote:
>
>> On Wed, May 16, 2018 at 7:18 PM, <srvr_...@srvr-tmpl.ikhider.com> wrote:
>>
>> Hello All,
>>>
>>> I installed OI on another laptop, this one has AMD graphics 6310
>>> (wrestler).
>>>
>>> This page:
>>> https://wiki.openindiana.org/oi/Graphics+Adapters
>>>
>>> Indicates some support for AMD graphics card. Is there a way to extend
>>> this support, perhaps to include cards like this?
>>>
>>> I figure the drivers that already exist might cover a range of products.
>>>
>>>
>> We do not have a drm driver for AMD adapters.
>>
>>
>>
>>> SM
>>>
>>> ___
>>> openindiana-discuss mailing list
>>> openindiana-discuss@openindiana.org
>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>>
>>>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] AMD graphics, revisited.

[Aurélien Larcher]

On Wed, May 16, 2018 at 7:18 PM,  wrote:

> Hello All,
>
> I installed OI on another laptop, this one has AMD graphics 6310
> (wrestler).
>
> This page:
> https://wiki.openindiana.org/oi/Graphics+Adapters
>
> Indicates some support for AMD graphics card. Is there a way to extend
> this support, perhaps to include cards like this?
>
> I figure the drivers that already exist might cover a range of products.
>

We do not have a drm driver for AMD adapters.


>
> SM
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Start Xvnc on 2018.04

[Aurélien Larcher]

On Sat, May 12, 2018 at 4:57 PM, Jacques Hugo 
wrote:

> Hi all,
>
>
>
> Just double-checking here:  but no one has ever seen this error on a new
> install?
>
>
I did not have time to check but the actual error seems:

Could not setppriv() PRIV_PERMITTED_XSERVTransmkdir: Owner of /tmp/.X11-unix
should be set to root

_XSERVTransmkdir: Owner of /tmp/.X11-pipe should be set to root

This package worked as expected the last time I updated Xorg, so not sure
what happened.

Andreas, can you check it?



>
> -Jacques
>
>
>
>
>
> Jacques Hugo
>
> Three Two Labs
>
> Information Technology | Solaris Engineering 32L
>
> Phone +44 7939 433701
>
>   jacques.h...@threetwo.co.uk
>
>
>
> From: Jacques Hugo [mailto:jacques.h...@threetwo.co.uk]
> Sent: 08 May 2018 20:25
> To: 'openindiana-discuss@openindiana.org'
> 
> Subject: Start Xvnc on 2018.04
>
>
>
> Hi guys,
>
>
>
> Any help appreciated.  I'm trying to start Xvnc which have worked fine
> until
> build a new host running 2018.04; the error message is below.  It complains
> about fonts but I'm not a 100% sure if that really is the issue.  All the
> pkg dependencies I have double  checked with
>
> `pkg contents -r -o fmri,type -t depend xvnc`
>
> and they are all installed.
>
>
>
> The /tmp/.X11- is not being set to root correctly although Xvnc is
> running with the default SGUID bit set
>
> `$ ls -l /usr/bin/Xvnc
>
> -r-xr-sr-x   1 root root 13577016 May  7 16:06 /usr/bin/Xvnc
>
> `
>
>
>
> Not really sure what is causing this.  Has anyone else seen this before?
>
>
>
> Cheers,
>
> Jacques
>
>
>
>
>
>
>
>
>
> $ vncserver
>
>
>
> WARNING: The first attempt to start Xvnc failed, possibly because the font
>
> catalog is not properly configured.  Attempting to determine an appropriate
>
> font path for this system and restart Xvnc using that font path ...
>
> Could not start Xvnc.
>
>
>
> Could not setppriv() PRIV_PERMITTED_XSERVTransmkdir: Owner of
> /tmp/.X11-unix
> should be set to root
>
> _XSERVTransmkdir: Owner of /tmp/.X11-pipe should be set to root
>
>
>
> Xvnc TigerVNC 1.7.1
>
> Copyright (C) 1999-2016 TigerVNC Team and many others (see README.txt)
>
> See http://www.tigervnc.org for information on TigerVNC.
>
> Underlying X server release 11906000, The X.Org Foundation
>
>
>
> (EE)
>
> (EE) Backtrace:
>
> (EE) 0: /usr/bin/Xvnc (xorg_backtrace+0x49) [0x81020a9]
>
> (EE) 1: /usr/bin/Xvnc (OsSigHandler+0x64) [0x8108f54]
>
> (EE) 2: /lib/libc.so.1 (__sighndlr+0x15) [0xfebfed05]
>
> (EE) 3: /lib/libc.so.1 (call_user_handler+0x292) [0xfebf35b3]
>
> (EE) 4: /usr/bin/Xvnc (AddResource+0x2c) [0x80f07ec]
>
> (EE) 5: /usr/bin/Xvnc (PictureInit+0x143) [0x819d6d3]
>
> (EE) 6: /usr/bin/Xvnc (miPictureInit+0x23) [0x819b303]
>
> (EE) 7: /usr/bin/Xvnc (fbPictureInit+0x23) [0x8116913]
>
> (EE) 8: /usr/bin/Xvnc (vfbScreenInit+0x497) [0x80b8877]
>
> (EE) 9: /usr/bin/Xvnc (AddScreen+0xce) [0x80ca88e]
>
> (EE) 10: /usr/bin/Xvnc (InitOutput+0x147) [0x80b8a57]
>
> (EE) 11: /usr/bin/Xvnc (dix_main+0x258) [0x80ceba8]
>
> (EE) 12: /usr/bin/Xvnc (main+0x2a) [0x81fde6a]
>
> (EE) 13: /usr/bin/Xvnc (_start_crt+0x97) [0x80b64a8]
>
> (EE) 14: /usr/bin/Xvnc (_start+0x1a) [0x80b637a]
>
> (EE)
>
> (EE) Segmentation Fault at address 0x1
>
> (EE)
>
> Fatal server error:
>
> (EE) Caught signal 11 (Segmentation Fault). Server aborting
>
> (EE)
>
> Could not setppriv() PRIV_PERMITTED_XSERVTransmkdir: Owner of
> /tmp/.X11-unix
> should be set to root
>
> _XSERVTransmkdir: Owner of /tmp/.X11-pipe should be set to root
>
>
>
> Xvnc TigerVNC 1.7.1
>
> Copyright (C) 1999-2016 TigerVNC Team and many others (see README.txt)
>
> See http://www.tigervnc.org for information on TigerVNC.
>
> Underlying X server release 11906000, The X.Org Foundation
>
>
>
> (EE)
>
> (EE) Backtrace:
>
> (EE) 0: /usr/bin/Xvnc (xorg_backtrace+0x49) [0x81020a9]
>
> (EE) 1: /usr/bin/Xvnc (OsSigHandler+0x64) [0x8108f54]
>
> (EE) 2: /lib/libc.so.1 (__sighndlr+0x15) [0xf8d5ed05]
>
> (EE) 3: /lib/libc.so.1 (call_user_handler+0x292) [0xf8d535b3]
>
> (EE) 4: /usr/bin/Xvnc (AddResource+0x2c) [0x80f07ec]
>
> (EE) 5: /usr/bin/Xvnc (PictureInit+0x143) [0x819d6d3]
>
> (EE) 6: /usr/bin/Xvnc (miPictureInit+0x23) [0x819b303]
>
> (EE) 7: /usr/bin/Xvnc (fbPictureInit+0x23) [0x8116913]
>
> (EE) 8: /usr/bin/Xvnc (vfbScreenInit+0x497) [0x80b8877]
>
> (EE) 9: /usr/bin/Xvnc (AddScreen+0xce) [0x80ca88e]
>
> (EE) 10: /usr/bin/Xvnc (InitOutput+0x147) [0x80b8a57]
>
> (EE) 11: /usr/bin/Xvnc (dix_main+0x258) [0x80ceba8]
>
> (EE) 12: /usr/bin/Xvnc (main+0x2a) [0x81fde6a]
>
> (EE) 13: /usr/bin/Xvnc (_start_crt+0x97) [0x80b64a8]
>
> (EE) 14: /usr/bin/Xvnc (_start+0x1a) [0x80b637a]
>
> (EE)
>
> (EE) Segmentation Fault at address 0x1
>
> (EE)
>
> Fatal server error:
>
> (EE) Caught signal 11 (Segmentation Fault). Server aborting
>
> (EE)
>
>
>
>
>
> Jacques Hugo
>
> Three Two Labs
>
> Information Technology | Solaris 

Re: [OpenIndiana-discuss] lightdm fails!

[Aurélien Larcher]

On Fri, May 4, 2018 at 6:51 PM, Apostolos Syropoulos via
openindiana-discuss  wrote:

> Back in January I tried to enable lightdm which failed and I got this:
>
>
> lightdm: Got tty: '/dev/vt/7'[ Ιαν 25 22:22:54 Stopping because service
> disabled. ][ Ιαν 25 22:22:54 Executing stop method
> ("/lib/svc/method/svc-lightdm stop").
>  ]
> kill: 2493: no such process
> [ Ιαν 25 22:22:54 Method "stop" exited with status 1. ]
> [ Ιαν 25 22:22:54 Executing stop method ("/lib/svc/method/svc-lightdm
> stop").
>  ]
> kill: 2493: no such process
> [ Ιαν 25 22:22:54 Method "stop" exited with status 1. ]
> [ Ιαν 25 22:22:54 Executing stop method ("/lib/svc/method/svc-lightdm
> stop").
>  ]
> kill: 2493: no such process
> [ Ιαν 25 22:22:54 Method "stop" exited with status 1. ]
> [ Ιαν 26 13:55:28 Disabled. ]
> [ Ιαν 27 14:46:05 Disabled. ]
>
>
> I have checked on the new BE and I get similar messages.
>

Could it be that you are missing a dependency?

How did you migrate to MATE? Did you install mate_install?


>
> Request: Can I have the gdm bits back please?
>

This is unfortunately impossible, the code has been deprecated a long time
ago and cannot be maintained independently.

>
> --
> Apostolos Syropoulos
> Xanthi, Greece
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] lightdm fails!

[Aurélien Larcher]

On Fri, May 4, 2018 at 5:44 PM, Apostolos Syropoulos via
openindiana-discuss  wrote:

> In order to try to understand what is possible wrong, I tried to run
> lightdm in my porevious BE
> that contained thed November 2017 bits. When I enter the following command
> a black screen pops up
> that disappears immediately and I see some messages on the terminal:
>
> $ /usr/sbin/lightdm --test-mode debug
>
> ** (lightdm:1009): WARNING **: Failed to get list of logind seats:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.freedesktop.login1 was not provided by any .service files
>
> ** (lightdm:1009): WARNING **: Error getting user list from
> org.freedesktop.Accounts: 
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown:
> The name org.freedesktop.Accounts was not provided by any .service files
>
> ** (lightdm:1009): WARNING **: Could not enumerate user data directory
> /var/lib/lightdm-data: Permission denied
> lightdm: Got tty: '/dev/dtlocal'
> ** (process:1013): WARNING **: Error getting user list from
> org.freedesktop.Accounts: 
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown:
> The name org.freedesktop.Accounts was not provided by any .service files
>
> ** (lightdm:1009): WARNING **: Could not create user data directory
> /var/lib/lightdm-data/apostolo: Error creating directory: Permission
> denied
>
> $ root@adalind:/var/lib# ls -l
> total 21
> drwxr-xr-x   2 root root   3 Απρ 21  2016 dbus
> drwxr-xr-x   2 root sys3 Νοε  1  2016 freeipmi
> drwxrwx--T  13 root gdm   15 Δεκ 28  1986 gdm
> drwxrwx--T   4 root lightdm5 Μαΐ  4 18:32 lightdm-data
> drwxr-xr-x   2 root bin2 Ιαν 22  2017 smartmontools
>
>
> Note that when I tried to run as root the command above it worked...
>



Could not enumerate user data directory /var/lib/lightdm-data: Permission
denied

If running the thing as root set the permissions incorrectly may be the fix
is not too difficult.

>
> A.S.
>
> --
> Apostolos Syropoulos
> Xanthi, Greece
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] gcc bug and OpenIndiana

[Aurélien Larcher]

On Thu, Apr 5, 2018 at 4:08 PM, Jason Martin  wrote:

> Does this bug affect OpenIndiana or has it been mitigated?
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40411
>
> I have built several programs now where I cannot get TESTS to fully pass.
>
> openeuphoria
> goffice
> oorexx
>
> oorexx now passes all tests after reading about bug.
>

This should take care of it:

https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/developer/gcc-6/patches/001-illumos-gcc.patch#L406



> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Audio issue (was: BTX halted)

[Aurélien Larcher]

On Tue, Mar 20, 2018 at 5:18 PM, Francis.D  wrote:

> I don't want to start the discussion again.
> Yes I read that in a previous post, but for me it didn't work.
>

What we need is a proper fix, so please discuss the issues :)
Presumably Alexander's PR for adding OSS support to libmatemixer would
allow you to overcome Pulseaudio's limitations and select the proper device
without manual intervention.


>
> I have deleted OI on the Laptop for now but I will coming back when the
> next stable release will be launched.
>
> I keep OI on my test desktop.
>
> regard
>
> 2018-03-20 10:17 GMT-04:00 Priyadarshan via openindiana-discuss <
> openindiana-discuss@openindiana.org>:
>
> > On 2018-03-20 14:21, Francis.D wrote:
> >
> >> hi,
> >>
> >> On your Lenovo W541 did you test the sound?
> >> Does the sound work fully for you  on realtek HD driver ?
> >>
> >>
> >> Because for me on all my installation the sound doesn't work properly.
> >> I've already posted on the channel but there doesn't seem to be a
> solution
> >> that works.
> >> So I'm curious about the sound experience of other users
> >>
> >> regard
> >>
> >
> > Hello,
> >
> > Yes, I had the same issue.
> >
> > I fixed it with the steps detailed in a previous mail:
> > https://openindiana.org/pipermail/openindiana-discuss/2018-
> > March/021949.html
> >
> > Admittedly, they are a bit unrefined (sorry about that).
> >
> > Aurelien Larcher's replies showed the proper way of investigating and
> > fixing that issue.
> >
> > Priyadarshan
> >
> > PS: I love OpenIndiana! If only I could have it run on our workstations,
> > it would be my dream OS.
> >
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> >
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Greek keyboard

[Aurélien Larcher]

On Fri, Mar 16, 2018 at 10:11 AM, Apostolos Syropoulos <
asyropou...@yahoo.com> wrote:

> >Would you mind pasting the output of setxkbmap -v ?
>
> Initially it was set to a sun something
>
> >At least on a Swedish keyboard, level 3 works >properly only with a
> Generic PC 105 layout, not the >Sun one
>
> $ setxkbmap -v
> Trying to build keymap using the following components:
> keycodes:   xfree86+aliases(qwerty)
> types:  complete
> compat: complete
> symbols:pc+us+inet(pc105)+gr:2+group(alt_shift_toggle)+eurosign(e)+
> terminate(ctrl_alt_bksp)
> geometry:   pc(pc105)
>
> But no still nothing changes. It seems that
> whole infrastructure is problematic.
>
> >I figured that I cannot type any valid accented >characters on my Swedish
> laptop keyboard unless >~/.dmrc specifies Language=fr_FR.UTF-8.
>
> Initially there was no entry for language. I added
>
> Language=el_GR.UTF-8
>
> but nothing happened and of course (!) changing to
> fr.FR.UTF-8 did not work either.
>
> It seems I have to revert to the old BE and forget
> updating for a while. BTW, who is actually "touching"
> these files?It would be nice to tell them that they
> do more harm than good.
>

The issue is that people change the way and location locales are picked up
depending on the distribution and they break existing behaviour without
telling (like requiring ibus to make layouts work).
I have installed and tested the updates for some time before pushing: I
still cannot break my setting on the workstation while the laptop setting
breaks for a different combination of language/keyboard layout.
For me defining a Language and rebooting (you need lightdm to pass the
setting to X) works around the problem for my laptop and desktop.
On the workstation where I have a french locale defined I never encountered
any breakage.



>
> Best regards,
>
> A.S.
>
> --
> Apostolos Syropoulos
> Xanthi, Greece
>
>
>


-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Greek keyboard

[Aurélien Larcher]

On Wed, Mar 14, 2018 at 8:12 PM, Aurélien Larcher <
aurelien.larc...@gmail.com> wrote:

>
>
> On Wed, Mar 14, 2018 at 11:01 AM, Apostolos Syropoulos via
> openindiana-discuss <openindiana-discuss@openindiana.org> wrote:
>
>> Hello,
>> I installed ibus andI run  ibus-daemon but I see the same behavior.
>>
>
> Alright strange...
>
> Would you mind pasting the output of setxkbmap -v ?
>
> At least on a Swedish keyboard, level 3 works properly only with a Generic
> PC 105 layout, not the Sun one.
> Kind regards
>

I figured that I cannot type any valid accented characters on my Swedish
laptop keyboard unless ~/.dmrc specifies Language=fr_FR.UTF-8.

Somebody somewhere seems to think that no Language defined means that we do
not want to type accents.




>
> Aurelien
>
>
>
>> A.S.
>>
>> --
>> Apostolos Syropoulos
>> Xanthi, Greece
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>
>
>
> --
> ---
> Praise the Caffeine embeddings
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Greek keyboard

[Aurélien Larcher]

On Wed, Mar 14, 2018 at 11:01 AM, Apostolos Syropoulos via
openindiana-discuss  wrote:

> Hello,
> I installed ibus andI run  ibus-daemon but I see the same behavior.
>

Alright strange...

Would you mind pasting the output of setxkbmap -v ?

At least on a Swedish keyboard, level 3 works properly only with a Generic
PC 105 layout, not the Sun one.
Kind regards

Aurelien



> A.S.
>
> --
> Apostolos Syropoulos
> Xanthi, Greece
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Greek keyboard

[Aurélien Larcher]

On Tue, Mar 13, 2018 at 7:39 PM, Nikola M <minik...@gmail.com> wrote:

> On 03/13/18 07:22 PM, Aurélien Larcher wrote:
>
>> On Tue, Mar 13, 2018 at 7:16 PM, Nikola M <minik...@gmail.com> wrote:
>>
>> On 03/13/18 01:30 PM, Aurelien Larcher wrote:
>>>
>>> Le Mardi 13 mars 2018, Nikola M a écrit :
>>>>
>>>> On 03/13/18 09:40 AM, Apostolos Syropoulos via openindiana-discuss
>>>>> wrote:
>>>>>
>>>>> Roll back data-xkb to previous version.
>>>>>>
>>>>>>> pkg install data-xkb@2.22
>>>>>>>
>>>>>>> I guess they broke the keymaps again...
>>>>>>>
>>>>>>> I did it but still I cannot type Greek in pluma,and in LibreOffice
>>>>>> when
>>>>>> I type ; + vowel I see'v. So I guess they did not broke keymaps,
>>>>>> theyactualy f%^&* them...
>>>>>> A.S.
>>>>>>
>>>>>> Maybe going back to BE where it is all working and figure out on what
>>>>> exact osnet-incorporation and userland-incorporation it were last
>>>>> working, and on what update it started not working.
>>>>>
>>>>> This is since March 7. It seems that the update of data-xkb has sneaky
>>>> side effects since I got two environments with same english+swedish
>>>> keyboards to update differently: one working, one losing the accents.
>>>>
>>>> This obvioiusly can't pass to IPS snapshot before April (ISO) freeze..
>>> Getting back to older that works, whatever.
>>>
>>
>> This does not seem related to the data-xkb update, I have a laptop with
>> 2.22 that shows the same issue and nothing in the keymap commits between
>> 2.22 and 2.23.1 stands out.
>>
>> I have just spent one hour trying to find the cause without success but
>> getting the accents back by using ibus.
>>
>> Now I am trying to figure out how to get ibus to work for lightdm.
>>
>> If you have any idea how to solve the problem...
>>
>
> I have installed Xubuntu, it also uses lightdm.


Do you know if lightdm uses ibus for changing the keyboard layout?


>
>
>
>
>>
>>
>>
>>
>>> And then pkg freeze of a working package and then update the rest
>>>
>>>> (possibly with ' pkg change-facet
>>>>> facet.require.consolidation/userland/userland-incorporation=false '
>>>>> and/or ' pkg uninstall userland-incorporation ' ? )
>>>>>
>>>>> So it seems it is an upstream bug, that might affect other kernel
>>>>> distributions, too?
>>>>> Is it in line to report it on both as OI  Issue and an upstream bug ?
>>>>> Benefits of Rolling-release with spotting bugs early and fixing
>>>>> upstream
>>>>> projects, I presume..
>>>>>
>>>>>
>>>>> ___
>>>>> openindiana-discuss mailing list
>>>>> openindiana-discuss@openindiana.org
>>>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>>>>
>>>>>
>>>>> ___
>>> openindiana-discuss mailing list
>>> openindiana-discuss@openindiana.org
>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>>
>>>
>>
>>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Greek keyboard

[Aurélien Larcher]

On Tue, Mar 13, 2018 at 7:16 PM, Nikola M  wrote:

> On 03/13/18 01:30 PM, Aurelien Larcher wrote:
>
>>
>> Le Mardi 13 mars 2018, Nikola M a écrit :
>>
>>> On 03/13/18 09:40 AM, Apostolos Syropoulos via openindiana-discuss wrote:
>>>
 Roll back data-xkb to previous version.
>
> pkg install data-xkb@2.22
>
> I guess they broke the keymaps again...
>
 I did it but still I cannot type Greek in pluma,and in LibreOffice when
 I type ; + vowel I see'v. So I guess they did not broke keymaps,
 theyactualy f%^&* them...
 A.S.

>>> Maybe going back to BE where it is all working and figure out on what
>>> exact osnet-incorporation and userland-incorporation it were last
>>> working, and on what update it started not working.
>>>
>> This is since March 7. It seems that the update of data-xkb has sneaky
>> side effects since I got two environments with same english+swedish
>> keyboards to update differently: one working, one losing the accents.
>>
>
> This obvioiusly can't pass to IPS snapshot before April (ISO) freeze..
> Getting back to older that works, whatever.


This does not seem related to the data-xkb update, I have a laptop with
2.22 that shows the same issue and nothing in the keymap commits between
2.22 and 2.23.1 stands out.

I have just spent one hour trying to find the cause without success but
getting the accents back by using ibus.

Now I am trying to figure out how to get ibus to work for lightdm.

If you have any idea how to solve the problem...




>
>
> And then pkg freeze of a working package and then update the rest
>>> (possibly with ' pkg change-facet
>>> facet.require.consolidation/userland/userland-incorporation=false '
>>> and/or ' pkg uninstall userland-incorporation ' ? )
>>>
>>> So it seems it is an upstream bug, that might affect other kernel
>>> distributions, too?
>>> Is it in line to report it on both as OI  Issue and an upstream bug ?
>>> Benefits of Rolling-release with spotting bugs early and fixing upstream
>>> projects, I presume..
>>>
>>>
>>> ___
>>> openindiana-discuss mailing list
>>> openindiana-discuss@openindiana.org
>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>>
>>>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Greek keyboard

[Aurélien Larcher]

On Tue, Mar 13, 2018 at 9:40 AM, Apostolos Syropoulos  wrote:

> >Roll back data-xkb to previous version.
> >
> >pkg install data-xkb@2.22
> >
> >I guess they broke the keymaps again...
>
> I did it but still I cannot type Greek in pluma,
> and in LibreOffice when I type ; + vowel I see
> 'v. So I guess they did not broke keymaps, they
> actualy f%^&* them...
>


Could you try:

pkg install ibus

then run ibus-setup, accept running as daemon and chose Greek in the menu?





>
> A.S.
> --
> Apostolos Syropoulos
> Xanthi, Greece
>
>
>


-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Greek keyboard

[Aurélien Larcher]

On Tue, Mar 13, 2018 at 9:40 AM, Apostolos Syropoulos  wrote:

> >Roll back data-xkb to previous version.
> >
> >pkg install data-xkb@2.22
> >
> >I guess they broke the keymaps again...
>
> I did it but still I cannot type Greek in pluma,
> and in LibreOffice when I type ; + vowel I see
> 'v. So I guess they did not broke keymaps, they
> actualy f%^&* them...
>

Do you use an English locale for the system?

I think the only difference between my workstation and the media centre is
the locale...

I have accents on the system with a french locale and no accents with an
english locale.
Not sure it is related.



>
> A.S.
> --
> Apostolos Syropoulos
> Xanthi, Greece
>
>
>


-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Something is wrong with gmp.h

[Aurélien Larcher]

On Mon, Mar 12, 2018 at 2:45 PM, Apostolos Syropoulos  wrote:

>
>
>
> >The header fix is delivered since 2016 and we have never delivered
> /usr/include/gmp.h since then:
> >
> >https://github.com/OpenIndiana/oi-userland/tree/
> oi/hipster/components/library/gmp/patches
> 
> >
> >Could it be pulled from SFE?
>
> I did a fresh install of my system in the summer of 2016. Since then I
> just update the system.
> But yes I see this header file in another machine that was installed more
> recently. At any rate.
>

Could you try running this to understand where the file comes from?

helios> pkg search -r gmp.h
INDEX  ACTION VALUE PACKAGE
basename   file   usr/include/gmp/gmp.h pkg:/library/gmp@6.1.2-2018.0.0.2

helios> LC_ALL=C pkg info library/gmp
  Name: library/gmp
   Summary: GNU Multiple Precision Bignum Library
  Category: Development/High Performance Computing
 State: Installed
 Publisher: openindiana.org
   Version: 6.1.2
Branch: 2018.0.0.2
Packaging Date: Sun Feb 11 12:48:54 2018
  Size: 1.96 MB
  FMRI: pkg://openindiana.org/library/gmp@6.1.2-2018.0.0.2:
20180211T124854Z
   Project URL: http://gmplib.org/
Source URL: http://ftp.gnu.org/gnu/gmp/gmp-6.1.2.tar.bz2

Thank you


>
> A.S.
>
> --
> Apostolos Syropoulos
> Xanthi, Greece
>
>
>


-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Something is wrong with gmp.h

[Aurélien Larcher]

On Sat, Mar 10, 2018 at 4:57 PM, Apostolos Syropoulos  wrote:

> >You are right but the header delivered by OI's package has already this
> fix: pkg://openindiana.org/library/ >gmp@6.1.2-2018.0.0.2:
> 20180211T124854Z
> 
> >Did you install gmp manually?
> >
> >We deliver /usr/include/gmp/gmp.h not /usr/include/gmp.h
>
> I am still using the November  2017 bits at home...
>

The header fix is delivered since 2016 and we have never delivered
/usr/include/gmp.h since then:

https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/library/gmp/patches

Could it be pulled from SFE?


> A.S.
> --
> Apostolos Syropoulos
> Xanthi, Greece
>
>
>
>


-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] Pulseaudio now delivered as 64-bit by default.

[Aurélien Larcher]

Hi,
Pulseaudio is now delivered as 64-bits in /usr/bin.
As usual Pulseaudio may not able to cope with its own configuration files
when version or bitness is changed ...
If Pulseaudio does not start after reboot, you may need to remove the
configuration files in ~/.config/pulse/ ...

Aurelien

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Something is wrong with gmp.h

[Aurélien Larcher]

On Sat, Mar 10, 2018 at 4:50 PM, Aurélien Larcher <
aurelien.larc...@gmail.com> wrote:

>
>
> On Sat, Mar 10, 2018 at 4:26 PM, Apostolos Syropoulos via
> openindiana-discuss <openindiana-discuss@openindiana.org> wrote:
>
>> Hello,
>> On OI we have the file /usr/include/gmp.h Today I tried to compile the
>> Glasgow Haskell Compilerand compilation stopped with the following error
>> message:
>>  # error WORD_SIZE_IN_BITS != GMP_LIMB_BITS not supported
>> I am using the 32bit version of the compiler since the 64bit versionfails
>> (at least that was reported in their web site). Now the problemis that in
>> file gmp.h there is the following definition:
>> #define GMP_LIMB_BITS  64
>> while it should be
>> #define GMP_LIMB_BITS  32
>> I think that it should be better to have something like this
>>
>> #if defined(__amd64)
>> #define GMP_LIMB_BITS  64
>> #else
>> #define GMP_LIMB_BITS  32
>> #endif
>>
>
> You are right but the header delivered by OI's package has already this
> fix: pkg://openindiana.org/library/gmp@6.1.2-2018.0.0.2:20180211T124854Z
> Did you install gmp manually?
>

We deliver /usr/include/gmp/gmp.h not /usr/include/gmp.h


>
>
>>
>> At least this solves the problem with GHC.
>> A.S.
>>
>>
>> --
>> Apostolos Syropoulos
>> Xanthi, Greece
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>
>
>
> --
> ---
> Praise the Caffeine embeddings
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Something is wrong with gmp.h

[Aurélien Larcher]

On Sat, Mar 10, 2018 at 4:26 PM, Apostolos Syropoulos via
openindiana-discuss  wrote:

> Hello,
> On OI we have the file /usr/include/gmp.h Today I tried to compile the
> Glasgow Haskell Compilerand compilation stopped with the following error
> message:
>  # error WORD_SIZE_IN_BITS != GMP_LIMB_BITS not supported
> I am using the 32bit version of the compiler since the 64bit versionfails
> (at least that was reported in their web site). Now the problemis that in
> file gmp.h there is the following definition:
> #define GMP_LIMB_BITS  64
> while it should be
> #define GMP_LIMB_BITS  32
> I think that it should be better to have something like this
>
> #if defined(__amd64)
> #define GMP_LIMB_BITS  64
> #else
> #define GMP_LIMB_BITS  32
> #endif
>

You are right but the header delivered by OI's package has already this
fix: pkg://openindiana.org/library/gmp@6.1.2-2018.0.0.2:20180211T124854Z
Did you install gmp manually?


>
> At least this solves the problem with GHC.
> A.S.
>
>
> --
> Apostolos Syropoulos
> Xanthi, Greece
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Fwd: [oi-dev] [call for testing] KPTI images

[Aurélien Larcher]

On Thu, Mar 8, 2018 at 4:52 PM, Francis.D  wrote:

> Hi,
>
> It's possible to set old publisher (151a) for install
> audio/driver/audiocmihd and unset publisher after ?
>

Why do you need to use the old publisher?
What is wrong with the current driver?


>
>
>
> 2018-03-07 12:49 GMT-05:00 Francis.D :
>
> > Hi,
> >
> > I did the real installation on my Lenovo T400 and all works perfectly.
> > The only problem is the sound. I don't have any sound. Even if the
> drivers
> > are installed.
> >
> >
> > result ocmmande
> >
> > ls -l
> >
> > total 224920
> > -rw-r--r-r---1 boo staff 1644 mars 7 12:58 audiosondriverproblem
> >
> >
> > Reference driver
> >
> > pci17aa,20f2
> > Vendor: Intel Corporation
> > Device: 82801I (ICH9 Family) HD Audio
> > Controller
> > Sub-Vendor: Lenovo
> > binding name:   pciexclass,0403
> > devfs path: /pci@0,0/pci17aa,20f2@1b
> > bus addr:   1b
> > pci path:   0,1b,0
> > compatible name:(pciex8086,293e.17aa.20f2.3)(
> > pciex8086,293e.17aa.20f2)(pciex8086,293e.3)(pciex8086,
> > 293e)(pciexclass,040300)(pciexclass,0403)(pci8086,293e.
> > 17aa.20f2.3)(pci8086,293e.17aa.20f2)(pci17aa,20f2)(
> > pci8086,293e.3)(pci8086,293e)(pciclass,040300)(pciclass,0403)
> > driver name:audiohd
> > instance:   0
> > driver state:   Attached
> > fm-errcb-capable:   TRUE
> > fm-ereport-capable: TRUE
> > ddi-no-autodetach:  1
> > audiohd_beep:   1
> > sample-rate:bb80
> > sample-bits:10
> > acpi-namespace: _SB_.PCI0.HDEF
> > assigned-addresses: 8300d810
> > reg:d800
> > compatible: pciex8086,293e.17aa.20f2.3
> > model:  Mixed Mode device
> > power-consumption:  1
> > devsel-speed:   0
> > interrupts: 2
> > subsystem-vendor-id:17aa
> > subsystem-id:   20f2
> > unit-address:   1b
> > class-code: 40300
> > revision-id:3
> > vendor-id:  8086
> >
> > regard
> >
> > 2018-03-06 9:01 GMT-05:00 Priyadarshan via openindiana-discuss <
> > openindiana-discuss@openindiana.org>:
> >
> >> On 2018-03-06 14:55, Till Wegmüller wrote:
> >>
> >>> Hi and welcome in the community
> >>>
> >>>
> >>> On 06.03.2018 14:48, Priyadarshan via openindiana-discuss wrote:
> >>>
> 
> 
>  Thank you very much for the clarification.
> 
>  I am coming from FreeBSD (since 2002, both on servers and
> workstations).
> 
>  I am just getting my feet wet with openindiana.
> 
>  I am studying Pro OpenSolaris, and getting to OpenSolaris Bible later,
>  having my first install on a ThinkPad W541. I must say, I was
> impressed
>  on how smooth and flawless the install was, in comparison to Win 10,
>  FreeBSD 11 or even Linux Mint.
> 
>  From the overall feel of it I know this is home.
> 
>  I would like very much to contribute some packages, when (if ever)
> I'll
>  have enough expertise.
> 
> >>>
> >>> If you are studying the books you will definately have enough
> expertise.
> >>> The Packaging is made with Custom makefiles based on the current
> >>> solaris-gate.
> >>>
> >>> You can find documentation here:
> >>> https://wiki.openindiana.org/oi/Building+with+oi-userland
> >>>
> >>> The Source here: https://github.com/OpenIndiana/oi-userland
> >>>
> >>>
> >>> As I understand, then, it would be better to contribute to openindiana
>  repositories, as found here:https://www.openindiana.org/packages/
> 
>  When the time will come, would I be able to "pester" people on this
>  list, in regards to creating new packages? Or better the oi-dev list?
> 
> 
> >>> For packaging help you will definately get help on oi-dev. We also have
> >>> irc channels on freenode if you prefer that.
> >>>
> >>> Greetings
> >>> Till
> >>>
> >>
> >>
> >> Thank you for the pointers, and the welcome.
> >>
> >>
> >> Priyadarshan
> >>
> >>
> >> ___
> >> openindiana-discuss mailing list
> >> openindiana-discuss@openindiana.org
> >> https://openindiana.org/mailman/listinfo/openindiana-discuss
> >>
> >
> >
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list

Re: [OpenIndiana-discuss] Sound issue [was Fwd: [oi-dev] [call for testing] KPTI images]

[Aurélien Larcher]

On Thu, Mar 8, 2018 at 2:07 AM, Francis.D <ange...@gmail.com> wrote:

> On Laptop T400
>
> boo@OIboo:~$ audioctl list-devices
> audiohd#0
> boo@OIboo:~$ pactl list sources
> Échec lors de la connexion : Connexion refusée
> Échec de pa_context_connect() : Connexion refusée
>
> traduction
> Failure to connect: Connection denied
> Failure of pa_context_connect (): Connection denied
>

Can you check that pulseaudio is actually running?

`pgrep pulseaudio` should return the PID.

If not, try to run `pulseaudio -vvv`

The issue may be related to pulseaudio as your audio device seems detected
by the native audio subsystem.
You can double check that it works using audiotest.

For example:

alarcher@helios:/home/alarcher$ audiotest
Sound subsystem and version: SunOS Audio 4.0 (0x00040003)
Platform: SunOS 5.11 illumos-ff1e230c4f i86pc

*** Scanning sound adapter #2 ***
/dev/sound/audiohd:1dsp (audio engine 1): audiohd#1
  - Performing audio playback test...
 OK
 ...OK
 ..OK









>
>
> 2018-03-07 19:46 GMT-05:00 Aurélien Larcher <aurelien.larc...@gmail.com>:
>
> > I didn't quite understand the solution. Do I need to edit a file?
> > > I also forgot to mention that I have the same sound problem on the
> > > installation I did on my desktop (in virtualbox)
> > >
> > > On the Desktop I have a dedicated Asus D1 sound card whose driver is
> > > cmi8788.
> > >
> > > There seems to be a problem with Pulseaudio.
> > > If you have a solution eventually, I'll apply it.
> > >
> >
> > Could you send the output of:
> >
> > $ audioctl list-devices
> >
> > and
> >
> > $ pactl list sources
> >
> > ?
> >
> >
> >
> > >
> > > 2018-03-07 13:24 GMT-05:00 Priyadarshan via openindiana-discuss <
> > > openindiana-discuss@openindiana.org>:
> > >
> > > > On 2018-03-07 19:18, Aurelien Larcher wrote:
> > > >
> > > >> Le Mercredi 7 mars 2018, Priyadarshan via openindiana-discuss a
> écrit
> > :
> > > >>
> > > >>> On 2018-03-07 18:49, Francis.D wrote:
> > > >>>
> > > >>> > Hi,
> > > >>> >
> > > >>> > I did the real installation on my Lenovo T400 and all works
> > > perfectly.
> > > >>> > The only problem is the sound. I don't have any sound. Even if
> the
> > > >>> drivers are installed.
> > > >>> >
> > > >>> > result ocmmande
> > > >>> >
> > > >>> > ls -l
> > > >>> >
> > > >>> > total 224920
> > > >>> > -rw-r--r-r---1 boo staff 1644 mars 7 12:58 audiosondriverproblem
> > > >>> >
> > > >>> > Reference driver
> > > >>> >
> > > >>> > pci17aa,20f2
> > > >>> > Vendor: Intel Corporation
> > > >>> > Device: 82801I (ICH9 Family) HD Audio
> > > >>> Controller
> > > >>> > Sub-Vendor: Lenovo
> > > >>> > binding name:   pciexclass,0403
> > > >>> > devfs path: /pci@0,0/pci17aa,20f2@1b
> > > >>> > bus addr:   1b
> > > >>> > pci path:   0,1b,0
> > > >>> > compatible name:
> (pciex8086,293e.17aa.20f2.3)(p
> > > >>> ciex8086,293e.17aa.20f2)(pciex8086,293e.3)(pciex8086,293e)(
> > > >>> pciexclass,040300)(pciexclass,0403)(pci8086,293e.17aa.20f2.
> > > >>> 3)(pci8086,293e.17aa.20f2)(pci17aa,20f2)(pci8086,293e.3)(
> > > >>> pci8086,293e)(pciclass,040300)(pciclass,0403)
> > > >>> > driver name:audiohd
> > > >>> > instance:   0
> > > >>> > driver state:   Attached
> > > >>> > fm-errcb-capable:   TRUE
> > > >>> > fm-ereport-capable: TRUE
> > > >>> > ddi-no-autodetach:  1
> > > >>> > audiohd_beep:   1
> > > >>> > sample-rate:bb80
> > > >>> > sample-bits:10
> > > >>> > acpi-namespace: 

Re: [OpenIndiana-discuss] Sound issue [was Fwd: [oi-dev] [call for testing] KPTI images]

[Aurélien Larcher]

I didn't quite understand the solution. Do I need to edit a file?
> I also forgot to mention that I have the same sound problem on the
> installation I did on my desktop (in virtualbox)
>
> On the Desktop I have a dedicated Asus D1 sound card whose driver is
> cmi8788.
>
> There seems to be a problem with Pulseaudio.
> If you have a solution eventually, I'll apply it.
>

Could you send the output of:

$ audioctl list-devices

and

$ pactl list sources

?



>
> 2018-03-07 13:24 GMT-05:00 Priyadarshan via openindiana-discuss <
> openindiana-discuss@openindiana.org>:
>
> > On 2018-03-07 19:18, Aurelien Larcher wrote:
> >
> >> Le Mercredi 7 mars 2018, Priyadarshan via openindiana-discuss a écrit :
> >>
> >>> On 2018-03-07 18:49, Francis.D wrote:
> >>>
> >>> > Hi,
> >>> >
> >>> > I did the real installation on my Lenovo T400 and all works
> perfectly.
> >>> > The only problem is the sound. I don't have any sound. Even if the
> >>> drivers are installed.
> >>> >
> >>> > result ocmmande
> >>> >
> >>> > ls -l
> >>> >
> >>> > total 224920
> >>> > -rw-r--r-r---1 boo staff 1644 mars 7 12:58 audiosondriverproblem
> >>> >
> >>> > Reference driver
> >>> >
> >>> > pci17aa,20f2
> >>> > Vendor: Intel Corporation
> >>> > Device: 82801I (ICH9 Family) HD Audio
> >>> Controller
> >>> > Sub-Vendor: Lenovo
> >>> > binding name:   pciexclass,0403
> >>> > devfs path: /pci@0,0/pci17aa,20f2@1b
> >>> > bus addr:   1b
> >>> > pci path:   0,1b,0
> >>> > compatible name:(pciex8086,293e.17aa.20f2.3)(p
> >>> ciex8086,293e.17aa.20f2)(pciex8086,293e.3)(pciex8086,293e)(
> >>> pciexclass,040300)(pciexclass,0403)(pci8086,293e.17aa.20f2.
> >>> 3)(pci8086,293e.17aa.20f2)(pci17aa,20f2)(pci8086,293e.3)(
> >>> pci8086,293e)(pciclass,040300)(pciclass,0403)
> >>> > driver name:audiohd
> >>> > instance:   0
> >>> > driver state:   Attached
> >>> > fm-errcb-capable:   TRUE
> >>> > fm-ereport-capable: TRUE
> >>> > ddi-no-autodetach:  1
> >>> > audiohd_beep:   1
> >>> > sample-rate:bb80
> >>> > sample-bits:10
> >>> > acpi-namespace: _SB_.PCI0.HDEF
> >>> > assigned-addresses: 8300d810
> >>> > reg:d800
> >>> > compatible: pciex8086,293e.17aa.20f2.3
> >>> > model:  Mixed Mode device
> >>> > power-consumption:  1
> >>> > devsel-speed:   0
> >>> > interrupts: 2
> >>> > subsystem-vendor-id:17aa
> >>> > subsystem-id:   20f2
> >>> > unit-address:   1b
> >>> > class-code: 40300
> >>> > revision-id:3
> >>> > vendor-id:  8086
> >>> >
> >>> > regard
> >>>
> >>> Hi,
> >>>
> >>> I had the same issue, I believe that is common to all OpenSOlaris
> >>> installs.
> >>>
> >>
> >> I believe this is a limitation of the OSS Pulseaudio backend which
> >> picks the first detected device.
> >>
> >
> > Thank you, I was wondering why.
> >
> > If it is common, perhaps it would be nice to add it somewhere on the
> > OpenIndiana wiki or Handbook.
> >
> > I am still testing my system, later on I could send a pull request with
> > that text.
> >
> > The more I use OpenIndiana, the more I love it!
> >
> > Now, I will try to install it on two more machines, an HP Z620
> workstation
> > with Xeon E5, and a custom made workstation with AMD 1950X Threadripper.
> I
> > will report back.
> >
> >
> > Priyadarshan
> >
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> >
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] EDID fixes for drm/intel

[Aurélien Larcher]

On Wed, Mar 7, 2018 at 1:40 PM, Michal Nowak <mno...@startmail.com> wrote:

> On Wednesday, March 7, 2018 at 1:15 PM, Aurélien Larcher <
> aurelien.larc...@gmail.com> wrote:
> > Hi,
> > I have updated quirks and display modes in the EDID code of the drm
> kernel
> > driver at:
> >
> > http://pkg.openindiana.org/xorg-testing/
> >
> > Some display modes for laptop were missing.
> > See if the drm package pushed there helps with the display issues on
> > Thinkpads X220/X230.
> >
> > Aurélien
>
> Forgot what was the issue with Thinkpads X220/X230 but this recent commit
> might be of use: https://cgit.freedesktop.org/xorg/xserver/commit/?id=
> a5e9bcad7ad0887f804905b482894b85751519fb


Thanks for the pointer, definitely cannot hurt:

https://github.com/OpenIndiana/oi-userland/pull/4031

Aurélien


>
>
> Michal
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] EDID fixes for drm/intel

[Aurélien Larcher]

Hi,
I have updated quirks and display modes in the EDID code of the drm kernel
driver at:

http://pkg.openindiana.org/xorg-testing/

Some display modes for laptop were missing.
See if the drm package pushed there helps with the display issues on
Thinkpads X220/X230.

Aurélien

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Fwd: [oi-dev] [call for testing] KPTI images

[Aurélien Larcher]

Hi :)


Yes, I understand that the OI team is small.
>
> I will continue to use this test version but install it on a PC directly.
>

Sure no problem, feel free to post if you encounter any issue :)


>
> Currently the system is fast on boot. Mate envirionment works well.
>

Great!


>
> The only problem encountered is the gcc compiler. Maybe I don't have all
> the packages installed. But I don't know about that. If someone can give me
> the list of packages to install to compile, I'd be happy.
>

We provide a metapackage named "build-essential" which should cover most
development requirements.

You can inspect the list of component provided by this metapackage at

https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/meta-packages/build-essential/build-essential.p5m



Another hint is to look at package dependencies directly, liste in
REQUIRED_PACKAGES:

https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/encumbered/vlc/Makefile

When components are built from oi-userland, calling "gmake env-prep" within
a component directory will install the listed dependencies.



In any case if you deal with multimedia packages you need to add the
hipster-encumbered publisher:

# pkg set-publisher -O http://pkg.openindiana.org/hipster-encumbered/
hipster-encumbered

You need the correct credentials to do so.

Instead of running as root, I prefer to add the "Software Installation"
profile to my user:

usermod -P "Software Installation" username

After this, you can perform action with pkg ad beadm just with pfexec (like
you would do with sudo).

Kind regards

Aurelien






>
> regard
>
> 2018-03-06 5:12 GMT-05:00 Priyadarshan via openindiana-discuss <
> openindiana-discuss@openindiana.org>:
>
> >
> >
> > On 2018-03-06 09:04, Alexander Pyhalov wrote:
> >
> >> On 03/06/18 08:57 AM, Francis.D wrote:
> >>
> >>> Hi,
> >>>
> >>> Download and install in Virtualbox. Installation process work
> perfectly,
> >>> Installation gimp, filezilla, inkscape, Libreoffice52 work with a repo
> >>> sfe.   Installation developer/gcc - gcc-49 build/cmake- cmake/src work
> >>> but
> >>> when I tried to make a compilation of vlc 3.0.1 doesn't work. error
> >>> message
> >>> gcc
> >>>
> >>> Some basic software such as smplayer, vlc, clementine, yarock are
> missing
> >>> in the repository.
> >>>
> >>> For multimedia, this is currently inadequate
> >>>
> >>> basic hardware motherboard asus m5n, AMD Phenom x2 550, 4 go ram, ati
> >>> 5450
> >>> video card,Sound card asus d1 (driver cmi8788) not found.
> >>>
> >>> In the next few days, I'll try an installation on pc.
> >>>
> >>> regard
> >>>
> >>
> >> Hi.
> >> 1) Current testing is not related to multimedia, we want to know
> >> general user experience with new illumos-gate bits.
> >> 2) You can always use http://pkg.openindiana.org/hipster-encumbered/
> >> repository to get a basic set of multimedia packages (basically, vlc
> >> and gstreamer codecs).
> >>
> >
> >
> > 3) If you find that some software is missing, nothing prvents you from
> >> adding it to oi-userland. There's always an issue - the more software
> >> we have, more power we need to support it. And with basic  team of 3-5
> >> men it's a big problem.
> >>
> >
> > I am new to openindiana/illumos, and I was wondering the same. I
> > understand openindiana can use NetBSD's pkgsrc.
> >
> > Would it be best to contribute new packages directly to pkgsrc, so that
> > they would hopefully be maintained by a more numerous team, and still
> > benefitting openindiana (and illumos)?
> >
> > Priyadarshan
> >
> >
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> >
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] Fwd: [oi-dev] [call for testing] KPTI images

[Aurélien Larcher]

-- Forwarded message --
From: John Levon <john.le...@joyent.com>
Date: Mon, Mar 5, 2018 at 2:46 PM
Subject: [oi-dev] [call for testing] KPTI images
To: oi-...@openindiana.org, develo...@lists.illumos.org,
smartos-disc...@lists.smartos.org


Hi all, please see below for test images for the various
distributions. These images include the KPTI (and PCID) work done by
Joyent up to the current kpti-squash branch. They are non-DEBUG except
as noted.

As before, any and all testing is useful, especially with "weird"
things like LDT-using code, older machines, etc.

Thanks to Aurélien Larcher and Andy Fiddaman for building the OI and
OmniOS images below.

thanks
john

OpenIndiana:

http://dlc-int.openindiana.org/users/aurelien/kpti/

OmniOSce (bloody):

# pkg update pkg
# pkg apply-hot-fix --be-name=kpti
https://downloads.omniosce.org/pkg/bloody/kpti.p5p
# init 6

or for DEBUG bits:

# pkg apply-hot-fix --be-name=kpti
https://downloads.omniosce.org/pkg/bloody/kpti-DEBUG.p5p

SmartOS:

https://us-east.manta.joyent.com/jlevon/public/bits/kpti/
platform-20180305T101513Z.iso
https://us-east.manta.joyent.com/jlevon/public/bits/kpti/
platform-20180305T101513Z.tgz

___
oi-dev mailing list
oi-...@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] Xorg 1.19.6

[Aurélien Larcher]

Hullo,
belated update (busy with other things) but I just pushed Xorg 1.19.6 for
testing to

http://pkg.openindiana.org/xorg-testing/

As usual the recommended way to test is to create a new Boot Environment
(BE) to avoid damaging your current install.

# beadm create xorg1196
# beadm mount xorg1196

Note the mounting point to substitute to /path/to/be

# pkg -R /path/to/be change-facet
facet.require.consolidation/userland/userland-incorporation=false
# pkg -R /path/to/be uninstall userland-incorporation
# pkg -R /path/to/be set-publisher -P -O
http://pkg.openindiana.org/xorg-testing/ userland
# pkg -R /path/to/be set-publisher --non-sticky openindiana.org
# pkg -R /path/to/be update -v
# beadm activate xorg1196

... and reboot.

Happy testing!



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Working Filezilla on OpenIndiana

[Aurélien Larcher]

On Sun, Feb 25, 2018 at 7:01 PM, russell 
wrote:

> Hi,
>
> I have successfully built Filezilla 3.3.0.1 on the latest OpenIndiana
> hipster release assembled 12 February 2018 or illumos-1cfad7ce45
>
> Initially I tried to use the gcc-7 and gcc-5 compilers but they created
> ABI version issues, 1011 and 1009 respectively.
>
> Installed the gcc-6 compiler and then built successfully built Filezilla
> 3.3.0.1 with the following commands
>
> $ CC=gcc-6 CXX=g++-6 CPPFLAGS="-I/usr/include/idn -I/usr/include/wx-2.8"
> ./configure  --prefix=/opt/gnu --enable-shared=yes --disable-locales
> --disable-static --disable-autoupdatecheck
>
> $ gmake
>
> # gmake install
>
> I think the gcc-6 compiler should be part of the standard install.
>

gcc-6 is now the default compiler.

Kind regards

Aurelien


>
> Regards
>
> Russell
>
>
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] HEADS-UP: lightdm delivered as 64-bit, known issue if log out right after update.

[Aurélien Larcher]

Hi,
in an hour new packages of lightdm and lightdm-gtk-greeter will be
published to migrate the binaries to 64-bit.
Migrating from 32-bit to 64-bit without a reboot is a not scenario handled
by lightdm: if you log out after updating the package, reloading the binary
registry will fail and put the service into maintenance.

Therefore updating to a new BE is recommended.

If you log out and your login manager does not restart, clearing the
service with:

svcadm clear lightdm

is enough to get the 64-bit version to reload properly.

Kind regards,

Aurélien

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] GCC 7 build zone status

[Aurélien Larcher]

Hi,
find below the list of components left to publish in the gcc 7.3.0 test
zone:

desktop/compiz-plugins-extra
desktop/compiz-plugins-main
developer/gcc-5
library/spidermonkey
python/coherence
runtime/openjdk-8

The repository contains 2092 packages, 6.8GB for now.

I still need to work on the gcc test suites but they take a lot of time and
I have not had the time to deal with setting up something properly.

Further updates will happen there:

https://wiki.openindiana.org/oi/GCC+7

Kind regards

Aurélien

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] [CFT] gcc 6.4.0-built repository available

[Aurélien Larcher]

Hi everyone,
we are happy to announce that a repository containing all the oi-userland
packages built with gcc 6.4.0 is now available for testing.

The repository is located at:

http://pkg.openindiana.org/gcc-6/

It is synchronized with the latest oi-userland bits and contains some minor
updates.
While these packages have been tested for a few weeks now, be aware that
the repository should be used for evaluation only (not in production).

Note that illumos-gate is still built with illumos-gcc 4.4.4.

To test this repository, we recommend that you create a new Boot
Environment (BE) and update manually this newly created BE.

Assume the right credentials using sudo, or pfexec if you have Software
Installation profile: you need to add sudo or pfexec before each of the
following command lines.

$ beadm create 20180207-gcc6

with '20180207-gcc6' an arbitrary BE name.

$ beadm mount 20180207-gcc6
Mounted successfully on: '/tmp/tmp.7mayXC'

with '/tmp/tmp.7mayXC' the mountpoint of the new BE.

Add the gcc-6 repository to the list of publishers and set as preferred:

$ pkg -R /tmp/tmp.7mayXC set-publisher -P -O http://pkg.openindiana.org/
gcc-6/ userland

$ pkg -R /tmp/tmp.7mayXC set-publisher --non-sticky --disable
openindiana.org

$ pkg -R /tmp/tmp.7mayXC publisher
PUBLISHER   TYPE STATUS P LOCATION
userlandorigin   online F http://pkg.openindiana.org/
gcc-6/
openindiana.org (non-sticky, disabled) origin   online F
http://pkg.openindiana.org/hipster/

Finally you can update the new BE:

$ pkg -R /tmp/tmp.7mayXC update -v

Be aware that the update can make up to 3GB of data.

The created BE can be chosen manually at the next reboot, or activated
using:

$ beadm activate 20180207-gcc6

Please report any package dependency issue that may arise.

Happy testing!

Aurélien

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] GCC6 build status

[Aurélien Larcher]

I think I have now republished all the components to the gcc-6 repository
> and two of my machines run these bits.
> Atypical full update takes about 3GB, so FOSDEM may not be the best place
> to try it out :)
>

It seems that I need to republish gcc49 though... so a bit more work
required.



>
> I am wondering now if I should start looking at encumbered or if I should
> update gcc 7 to 7.3.0.
>
>
> On Fri, Feb 2, 2018 at 11:01 AM, Aurélien Larcher <
> aurelien.larc...@gmail.com> wrote:
>
>> Hi,
>> for information the following components are left to republish to the
>> latest gcc-6 repository:
>>
>> developer/gcc49 - does not build with gcc 6.4.0, need to check runpaths
>> for build with self
>> library/boost - linking errors when building with gcc 6.4.0
>> openindiana/illumos-gcc - cc1plus links to system mpfr and gmp
>> web/tomcat-8 - fails to build
>>
>> Kind regards
>>
>> Aurelien
>>
>> --
>> ---
>> Praise the Caffeine embeddings
>>
>
>
>
> --
> ---
> Praise the Caffeine embeddings
>



-- 
---
Praise the Caffeine embedding
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] GCC6 build status

[Aurélien Larcher]

I think I have now republished all the components to the gcc-6 repository
and two of my machines run these bits.
Atypical full update takes about 3GB, so FOSDEM may not be the best place
to try it out :)

I am wondering now if I should start looking at encumbered or if I should
update gcc 7 to 7.3.0.


On Fri, Feb 2, 2018 at 11:01 AM, Aurélien Larcher <
aurelien.larc...@gmail.com> wrote:

> Hi,
> for information the following components are left to republish to the
> latest gcc-6 repository:
>
> developer/gcc49 - does not build with gcc 6.4.0, need to check runpaths
> for build with self
> library/boost - linking errors when building with gcc 6.4.0
> openindiana/illumos-gcc - cc1plus links to system mpfr and gmp
> web/tomcat-8 - fails to build
>
> Kind regards
>
> Aurelien
>
> --
> ---
> Praise the Caffeine embeddings
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] GCC6 build status

[Aurélien Larcher]

Hi,
for information the following components are left to republish to the
latest gcc-6 repository:

developer/gcc49 - does not build with gcc 6.4.0, need to check runpaths for
build with self
library/boost - linking errors when building with gcc 6.4.0
openindiana/illumos-gcc - cc1plus links to system mpfr and gmp
web/tomcat-8 - fails to build

Kind regards

Aurelien

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] [CFT] Icinga2 package

[Aurélien Larcher]

Hi,
thanks to Marianne, a package for Icinga2 [1] is now available for testing.

More information is available at the following thread where Marianne made
the announcement to the Icinga community [2].

I published the testing package to the xorg-testing repository:

http://pkg.openindiana.org/xorg-testing/

Please raise any issue you encounter during installation and testing.

A round of applause for Marianne's efforts on her first OI package :)
Kind regards,

Aurelien


[1] https://www.icinga.com/products/icinga-2/
[2]
https://monitoring-portal.org/t/announcing-icinga2-2-8-1-for-openindiana-testers-needed/922

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] [HEADS UP] Gnome 2 is dead

[Aurélien Larcher]

On Sat, Jan 27, 2018 at 1:14 PM, Nikola M  wrote:

> On 01/25/18 08:52 PM, Alexander Pyhalov wrote:
>
>> On 25.01.2018 20:49, Nikola M wrote:
>>
>> But actually, when issuing command to install mate_install I get this
>>> error message..
>>> .. So how to actually install mate/lightdm?
>>>
>>
>> As always, it's 'update your system first' in IPS dialect  (it seems old
>> packages (@..16350) were removed from the repo).
>> Likely, you want to do it in new BE.
>> ---
>> System Administrator of Southern Federal University Computer Center
>>
>> Seems like mate_install depends on diskinfo
> and diskinfo is removed, without dependencies checked.
>
> So mate_install can't be installed and GNOME->MATE migration is broken
> until mate_install can be installed:
>

The revision number of osnet-incorporation is still the same, did you
update prior to installing mate_install?

The message seems to say: can't install latest diskinfo because you
osnet-incorporation is too old.



>
> $ pfexec pkg install -v -r mate_install > updatelogs/updatelog-openindia
> na-42-mate.txt
>
> pkg install: No matching version of mate_install can be installed:
>   Reject:  pkg://openindiana.org/mate_install@0.1-2017.0.0.17
>   Reason:  No version matching 'conditional' dependency
> diagnostic/diskinfo can be installed
> 
> Reject: pkg://openindiana.org/diagnostic/diskinfo@0.5.11-2017.0.0.
> 16768
>to
> pkg://openindiana.org/diagnostic/diskinfo@0.5.11-2017.0.0.16969
> Reason:  This version is excluded by installed incorporation
> consolidation/osnet/osnet-incorporation@0.5.11-2017.0.0.16350
> 
> $ pfexec pkg uninstall diagnostic/diskinfo
>
> pkg uninstall: 'diagnostic/diskinfo' matches no installed packages
> $ pfexec pkg uninstall pkg://openindiana.org/diagnost
> ic/diskinfo@0.5.11-2017.0.0.16969
>
> pkg uninstall: 'pkg://openindiana.org/diagnostic/diskinfo@0.5.11-2017.0.0.
> 16969' matches no installed packages
>
> $ pfexec pkg uninstall pkg://openindiana.org/diagnost
> ic/diskinfo@0.5.11-2017.0.0.16768
>
> pkg uninstall: 'pkg://openindiana.org/diagnostic/diskinfo@0.5.11-2017.0.0.
> 16768' matches no installed packages
>
> $ pkg contents -r -m  mate_install | grep diskinfo
> depend fmri=diagnostic/diskinfo predicate=consolidation/osnet/
> osnet-incorporation@0.5.11,5.11-2017.0.0.16133 type=conditional
>
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Firefox 32bit future: Rustc

[Aurélien Larcher]

On Fri, Jan 26, 2018 at 10:11 AM, Carsten Grzemba 
wrote:

>
> 
> On 25.01.18 19:58, Alan Coopersmith   wrote:
> >
> > On 01/25/18 10:40 AM, russell wrote:
> > > Is there any immediate danger of Mozilla retiring the 32bit version of
> Firefox?
> >
> > I believe the most immediate item of concern is that Firefox now uses
> code
> > written in Rust, so you'll be limited to platforms that the Rust compiler
> > generates code for, and I don't know if anyone is bothering to do 32-bit
> code
> > generation for Solaris/illumos in Rust.
> >
> I did some attempts to package rustc for OI, based on the kind of SmartOS,
> but with no success for now:
> https://github.com/cgrzemba/oi-userland/tree/rust/
> components/developer/rust
>
> For Rust community is Solaris a tier 3 platform which means no support.
> But the recipe tries to download the rust-std library wich is not
> available for Solaris.
> I have no pkgsrc build system to see how it works for SmartOS.
> I would be grateful if anyone can give some advice.
>

I created a component for Rust some time ago.
I'll try to push it later today as an example.
Not sure whether it will work with recent versions.


> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Trying to understand limits and scalability.

[Aurélien Larcher]

Definitely swapping.
The system should recover at some point.
I wonder if the recently upstreamed SmartOS patch for #8493 would help
the system to recover better under such memory pressure?

On 1/25/18, Jason Martin  wrote:
> Hard power off!
> ssh into before I run scripts.
> each 28M * 161 = 4508M plus what is already running. Not sure if it gets to
> swap.
>
> Captured before unresponsive on ssh into machine
>
> load averages:  0.34,  0.17,  0.07;   up
> 0+00:03:54
> 10:33:58
> 258 processes: 189 sleeping, 55 running, 13 zombie, 1 on cpu
> CPU states: 40.2% idle, 21.6% user, 38.1% kernel,  0.0% iowait,  0.0% swap
> Kernel: 1182 ctxsw, 153317 trap, 4886 intr, 9486 syscall, 35 fork, 151799
> flt
> Memory: 3966M phys mem, 15M free mem, 1983M total swap, 1983M free swap
> ARC:357M Total, 250M MRU, 36M MFU, 288K Anon, 1631K Header, 69M Other
>
>PID USERNAME NLWP PRI NICE  SIZE   RES STATETIMECPU COMMAND
>878 agrellum3  590  215M   63M sleep0:04  2.07% Xorg
>   1231 agrellum4  590   37M   21M sleep0:00  0.79%
> mate-terminal
>   1274 agrellum1  420   30M   28M sleep0:00  0.73% rexx
>   1373 agrellum1  400   30M   28M sleep0:00  0.54% rexx
>   1237 agrellum1  490   30M   28M sleep0:00  0.53% rexx
>   1238 agrellum1  490   30M   28M sleep0:00  0.52% rexx
>   1334 agrellum1  420   30M   28M sleep0:00  0.52% rexx
>   1308 agrellum1  450   30M   28M sleep0:00  0.48% rexx
>   1328 agrellum1  460   30M   28M sleep0:00  0.48% rexx
>   1310 agrellum1  450   30M   28M sleep0:00  0.48% rexx
>   1318 agrellum1  450   30M   28M sleep0:00  0.48% rexx
>   1301 agrellum1  450   30M   28M sleep0:00  0.48% rexx
>   1289 agrellum1  450   30M   28M sleep0:00  0.47% rexx
>   1297 agrellum1  490   30M   28M sleep0:00  0.47% rexx
>   1309 agrellum1  450   30M   28M sleep0:00  0.47% rexx
>   1312 agrellum1  490   30M   28M sleep0:00  0.47% rexx
>   1354 agrellum1  400   30M   28M sleep0:00  0.46% rexx
>   1390 agrellum1  400   30M   28M sleep0:00  0.46% rexx
>   1268 agrellum1  460   30M   28M sleep0:00  0.46% rexx
>   1241 agrellum1  490   30M   28M sleep0:00  0.46% rexx
>   1321 agrellum1  490   30M   28M sleep0:00  0.46% rexx
>   1331 agrellum1  490   30M   28M sleep0:00  0.46% rexx
>   1292 agrellum1  450   30M   28M sleep0:00  0.46% rexx
>   1239 agrellum1  490   30M   28M sleep0:00  0.45% rexx
>   1299 agrellum1  450   30M   28M sleep0:00  0.45% rexx
>   1395 agrellum1  400   30M   28M sleep0:00  0.45% rexx
>   1314 agrellum1  450   30M   28M sleep0:00  0.45% rexx
>   1290 agrellum1  450   30M   28M sleep0:00  0.45% rexx
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>


-- 
---
Praise the Caffeine embeddings

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Trying to understand limits and scalability.

[Aurélien Larcher]

Hi,
I see that the machine can hold maximum 4GB.
How is the memory usage during your run?

On 1/25/18, Jason Martin  wrote:
> Have been using OpenIndiana since May 2017.
>
> Very happy, seems to be in really capable developers hands.
>
> Two machines up to date with jenkins build this morning.
>
> Built and have been testing oorexx from svn for days now.
>
> I have 161 tested scripts that produce no output or little output.
>
> I can run one at a time in just a few minutes.
> for filename in *.rexx
> do
> rexx $filename
> done
>
> Now on this machine:
> https://www.cnet.com/products/hp-pavilion-p6203w-b-tower-athlon-ii-x2-215-2-7-ghz-4-gb-500-gb-lcd-20/specs/
>
> Run all in background
> for filename in *.rexx
> do
> rexx $filename &
> done
>
> Scripts finish in terminal.
>
> Machine become unresponsive.
>
> Can ping from another.
>
> Cannot ssh into from another.
>
> I realize I put heavy load on it with 161 scripts at once.
>
> Will kernel ever get back control?
>
> How long before kernel gives me back some control?
>
> Should a user be allowed to do this?
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>


-- 
---
Praise the Caffeine embeddings

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Floating accents doesn't work in 2017.10

[Aurélien Larcher]

On Wed, Jan 17, 2018 at 11:39 PM, Jacobo Da Riva  wrote:

> Regards from Spain,
>
> Recently I've installed a 2017.10 release on an intel PC. The installation
> works fine but the keyboard doesn't works properly. The floating accents
> doesn't works. I've tried all the configurations of spanish keyboards...
> even the french configuration.
>

French keyboard are not supposed to have dead keys for accents. Maybe
select a layout with dead keys.
At least in French it is not the default configuration.


>
> When I press the floating accent button, the editor/console/web browser or
> any other program put an accent instead of wait to a vowel. If I press the
> accent and a vowel it writes something like ´a instead of á.
>
> On an Oracle Sun 11.3 installation the keyboard works fine.
>
>
> Regards
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] GCC6 build zone status

[Aurélien Larcher]

Hi Apostolos,

So this means that the next release of hipster will be based on gcc 6? This
> is certainly a big stepforward! Congratulations for this achievement!
>

Thank you for your kind words :)
I guess this is the plan, but we still need to figure out how to proceed to
ensure a smooth transition.

I am now typing from a system fully compiled with GCC 6.4.0 including
Toomas gcc6 branch of illumos.
The machine is a simple ThinkCenter m91p with Intel Graphics that I use as
Kodi media center and OpenIndiana playground.

Best regards,

Aurelien



> A.S.
>
> --
> Apostolos Syropoulos
> Xanthi, Greece
>
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] GCC6 build zone status

[Aurélien Larcher]

With some more help from Ken, remaining packages follow:

>
> > runtime/ocaml
>
> Needs update.
>
> > sysutils/open-vm-tools
>
> Needs update
>
> > library/ spidermonkey
>
> Needs gcc6 patches.


Updated page here https://wiki.openindiana.org/oi/GCC+6 and still openjdk-8
to be considered at some point.

That leaves 4 packages out of 1390.

Thanks

Aurélien

>
> >
> > If someone knows about Lua, there are issues with hexchat and libpeas
> > regarding luajit and LGI support.
> >
> > Kind regards
> >
> > Aurelien
> >
> > --
> > ---
> > Praise the Caffeine embeddings
> >
>
> --
> Envoyé depuis mon Jolla




-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] [oi-dev] GCC6 build zone status

[Aurélien Larcher]

On Fri, Dec 1, 2017 at 4:29 PM, Alexander Pyhalov  wrote:

> On 12/01/17 05:45 PM, Aurelien Larcher wrote:
>
> runtime/clisp
>>>
>>
>> Automake issue? No rule to make mbrtowc.o in gllib to produce libgnu.a
>>
>
> Sounds similar. Does building it with COMPONENT_BUILD_ARGS = -j1 help?
>

Apparently not... i wonder what changed...

>
>
> --
> Best regards,
> Alexander Pyhalov,
> system administrator of Southern Federal University IT department
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] GCC6 build zone status

[Aurélien Larcher]

Hi,
a few packages left to rebuild with GCC6:

desktop/hexchat

library/libpeas

library/trousers

perl/DBI-MySQL

perl/DBI-PostgreSQL

print/hal-cups-utils

python/pylint

runtime/clisp

runtime/ocaml

sysutils/clamav

sysutils/nut

sysutils/open-vm-tools

x11/tigervnc

I have updated two workstations to use the GCC 6 repository, and I have not
noticed any regression so far.

Kind regards

Aurelien

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] .mobi/.epub reader solution for OpenIndiana?

[Aurélien Larcher]

On Wed, Nov 22, 2017 at 9:37 PM, Carsten Grzemba 
wrote:

> --- g...@genashor.com schrieb 
> > I would imagine that Calibre should work as it is python based.
> https://calibre-ebook.com/
> >
> >
> >   Original Message
> > From: openindiana-discuss@openindiana.org
> > Sent: November 22, 2017 1:17 PM
> > To: openindiana-discuss@openindiana.org
> > Subject: Re: [OpenIndiana-discuss] .mobi/.epub reader solution for
> OpenIndiana?
> >
> > 'Atril is a simple multi-page document viewer. It can display and
> printPostScript (PS), Encapsulated PostScript (EPS), DJVU, DVI, XPS and
> PortableDocument Format (PDF) files. When supported by the document, it
> also allowssearching for text, copying text to the clipboard, hypertext
> navigation, andtable-of-contents bookmarks. Atril is a fork of Evince.'
> > Normally, you can use Atril for .epub. You can usually do:example: atril
> 'earth.epub'
> > Need to fix.
> > ~K
> >
> >
> > On Wednesday, November 22, 2017, 8:42:08 AM PST, Jerry Kemp <
> sun.mail.lis...@oryx.us> wrote:
> >
> > Evince works great for PDF files.  There is an, OK, reader for .chm
> files.
> >
> > I currently have nothing to view either .mobi or .epub files in
> OpenIndiana, at
> > least that I am aware of.
> >
> > Are there any .mobi or .epub reader solutions that I am just missing?
> >
> > Thanks,
> >
> > Jerry
> >
> it is pythonqt, which throughs cores for me on  opencsw
>

MuPDF:

https://mupdf.com/

Would be a good alternative.


> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] .mobi/.epub reader solution for OpenIndiana?

[Aurélien Larcher]

On Wed, Nov 22, 2017 at 7:31 PM, Aurélien Larcher <
aurelien.larc...@gmail.com> wrote:

>
>
> On Wed, Nov 22, 2017 at 7:27 PM, <g...@genashor.com> wrote:
>
>> I would imagine that Calibre should work as it is python based.
>> https://calibre-ebook.com/
>
>
> Before adding another piece of software, let us recompile Atril with
> --enable-epub and check if it works :)
>

Well, I tried to open an epub file with recompiled Atril and it fails to
open the document.
The same can be said about the Atril shipped with Debian ...



>
>
>
>>
>>
>>
>>   Original Message
>> From: openindiana-discuss@openindiana.org
>> Sent: November 22, 2017 1:17 PM
>> To: openindiana-discuss@openindiana.org
>> Subject: Re: [OpenIndiana-discuss] .mobi/.epub reader solution for
>> OpenIndiana?
>>
>>  'Atril is a simple multi-page document viewer. It can display and
>> printPostScript (PS), Encapsulated PostScript (EPS), DJVU, DVI, XPS and
>> PortableDocument Format (PDF) files. When supported by the document, it
>> also allowssearching for text, copying text to the clipboard, hypertext
>> navigation, andtable-of-contents bookmarks. Atril is a fork of Evince.'
>> Normally, you can use Atril for .epub. You can usually do:example: atril
>> 'earth.epub'
>> Need to fix.
>> ~K
>>
>>
>> On Wednesday, November 22, 2017, 8:42:08 AM PST, Jerry Kemp <
>> sun.mail.lis...@oryx.us> wrote:
>>
>>  Evince works great for PDF files.  There is an, OK, reader for .chm
>> files.
>>
>> I currently have nothing to view either .mobi or .epub files in
>> OpenIndiana, at
>> least that I am aware of.
>>
>> Are there any .mobi or .epub reader solutions that I am just missing?
>>
>> Thanks,
>>
>> Jerry
>>
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>
>
>
> --
> ---
> Praise the Caffeine embeddings
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] .mobi/.epub reader solution for OpenIndiana?

[Aurélien Larcher]

On Wed, Nov 22, 2017 at 7:27 PM,  wrote:

> I would imagine that Calibre should work as it is python based.
> https://calibre-ebook.com/


Before adding another piece of software, let us recompile Atril with
--enable-epub and check if it works :)



>
>
>
>   Original Message
> From: openindiana-discuss@openindiana.org
> Sent: November 22, 2017 1:17 PM
> To: openindiana-discuss@openindiana.org
> Subject: Re: [OpenIndiana-discuss] .mobi/.epub reader solution for
> OpenIndiana?
>
>  'Atril is a simple multi-page document viewer. It can display and
> printPostScript (PS), Encapsulated PostScript (EPS), DJVU, DVI, XPS and
> PortableDocument Format (PDF) files. When supported by the document, it
> also allowssearching for text, copying text to the clipboard, hypertext
> navigation, andtable-of-contents bookmarks. Atril is a fork of Evince.'
> Normally, you can use Atril for .epub. You can usually do:example: atril
> 'earth.epub'
> Need to fix.
> ~K
>
>
> On Wednesday, November 22, 2017, 8:42:08 AM PST, Jerry Kemp <
> sun.mail.lis...@oryx.us> wrote:
>
>  Evince works great for PDF files.  There is an, OK, reader for .chm files.
>
> I currently have nothing to view either .mobi or .epub files in
> OpenIndiana, at
> least that I am aware of.
>
> Are there any .mobi or .epub reader solutions that I am just missing?
>
> Thanks,
>
> Jerry
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] .mobi/.epub reader solution for OpenIndiana?

[Aurélien Larcher]

On Wed, Nov 22, 2017 at 5:47 PM, Udo Grabowski (IMK) 
wrote:

> On 22/11/2017 17:41, Jerry Kemp wrote:
>
>> Evince works great for PDF files.   There is an, OK, reader for .chm
>> files.
>>
>> I currently have nothing to view either .mobi or .epub files in
>> OpenIndiana, at
>> least that I am aware of.
>>
>> Are there any .mobi or .epub reader solutions that I am just missing?
>>
>>
> In oi-sfe, there used to be the fbreader package.
>

Then let us bring it to oi-userland :)


>
> --
> Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
> http://www.imk-asf.kit.edu/english/sat.php
> KIT - Karlsruhe Institute of Technology   http://www.kit.edu
> Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] GCC6 build zone status

[Aurélien Larcher]

Hi,
find below the list of components left to rebuild with GCC 6.4:

COMPONENT_DIRS += desktop/gnome2/gnome-media
COMPONENT_DIRS += desktop/gnome2/hamster-applet
COMPONENT_DIRS += desktop/gnome2/seahorse-plugins
COMPONENT_DIRS += desktop/hexchat
COMPONENT_DIRS += desktop/xscreensaver
COMPONENT_DIRS += developer/gupc-5
COMPONENT_DIRS += library/libpeas
COMPONENT_DIRS += library/qt5
COMPONENT_DIRS += library/trousers
COMPONENT_DIRS += network/asterisk
COMPONENT_DIRS += network/rtorrent
COMPONENT_DIRS += perl/DBI-MySQL
COMPONENT_DIRS += perl/DBI-PostgreSQL
COMPONENT_DIRS += print/hal-cups-utils
COMPONENT_DIRS += python/pylint
COMPONENT_DIRS += runtime/clisp
COMPONENT_DIRS += runtime/jruby
COMPONENT_DIRS += runtime/ocaml
COMPONENT_DIRS += runtime/openjdk-8
COMPONENT_DIRS += sysutils/clamav
COMPONENT_DIRS += sysutils/freeipmi
COMPONENT_DIRS += sysutils/ngrep
COMPONENT_DIRS += sysutils/nut
COMPONENT_DIRS += sysutils/open-vm-tools
COMPONENT_DIRS += x11/tigervnc

FYI the current number of components is 1390.

Kind regards

Aurelien


-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] wifi card compatibility

[Aurélien Larcher]

On Thu, Nov 16, 2017 at 10:23 PM, Marc Lobelle 
wrote:

> Hello,
>
> I have a notebook that included an apparently unsupported SIERRA wireless
> card. So I bought on ebay an Intel 4965 AGN card, which is in the list of
> the compatible devices. However, both windows and openiniana seem to
> identify it as an ATHEROS AR9287. Is it possible to have an intel card with
> an atheros chipset ? Or does it mean that the label oh the board is fake.
> Any way, is this card usable with open indiana ? If yes with wich driver ?
> and what should I do to install this driver. Thanks
>

The arn driver seems to support AR9285 which is supported by the same ath
driver as AR9287 in FreeBSD.
Nonetheless the corresponding PCI id is not listed in illumos, so it will
not attach.




>
> Marc
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] GCC6 build zone status

[Aurélien Larcher]

Hi,
for your information, the list of components left to publish with GCC 6.4.0:

COMPONENT_DIRS += database/geoip-database
COMPONENT_DIRS += desktop/gnome2/gnome-connection-manager
COMPONENT_DIRS += desktop/gnome2/gnome-media
COMPONENT_DIRS += desktop/gnome2/hamster-applet
COMPONENT_DIRS += desktop/gnome2/seahorse-plugins
COMPONENT_DIRS += desktop/hexchat
COMPONENT_DIRS += desktop/xscreensaver
COMPONENT_DIRS += library/libpeas
COMPONENT_DIRS += library/trousers
COMPONENT_DIRS += library/vte
COMPONENT_DIRS += network/asterisk
COMPONENT_DIRS += network/openssh
COMPONENT_DIRS += network/rtorrent
COMPONENT_DIRS += perl/DBI-MySQL
COMPONENT_DIRS += perl/DBI-PostgreSQL
COMPONENT_DIRS += print/hal-cups-utils
COMPONENT_DIRS += python/pylint
COMPONENT_DIRS += runtime/clisp
COMPONENT_DIRS += runtime/jruby
COMPONENT_DIRS += runtime/ocaml
COMPONENT_DIRS += runtime/openjdk-8
COMPONENT_DIRS += sysutils/clamav
COMPONENT_DIRS += sysutils/freeipmi
COMPONENT_DIRS += sysutils/ngrep
COMPONENT_DIRS += sysutils/nut
COMPONENT_DIRS += sysutils/open-vm-tools
COMPONENT_DIRS += text/hunspell-cs
COMPONENT_DIRS += text/hunspell-es
COMPONENT_DIRS += text/hunspell-fr
COMPONENT_DIRS += text/hunspell-pl
COMPONENT_DIRS += text/hunspell-sv
COMPONENT_DIRS += web/tomcat-8
COMPONENT_DIRS += x11/tigervnc

and some comments updated on the Wiki at
https://wiki.openindiana.org/oi/GCC+6.
As oi-userland contains almost 1400 components, we are definitely closer to
the end than the beginning.

If you have some time to look at one of these components, your help will be
much appreciated :)

Kind regards

Aurelien


-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] cannot copy text from PDF file using atril

[Aurélien Larcher]

On Sun, Nov 12, 2017 at 5:19 PM, Apostolos Syropoulos  wrote:

>
> >OK so it does not work with any PDF file you created then.
> >I generate mine with pdflatex bundled with TeXLive and have no issue.
> >I guess it would be good to understand the difference.
>
> You have no problem but I do have problem with all PDF files I have tested
> (the creator is irrelevant). And this is exactly why I have asked whether
> this
> is a bug and/or a feature or something peculiar in my system.
>

Sorry, I misread your answer.



>
> A.S.
>
>
> --
> Apostolos Syropoulos
> Xanthi, Greece
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] cannot copy text from PDF file using atril

[Aurélien Larcher]

On Sun, Nov 12, 2017 at 4:37 PM, Apostolos Syropoulos  wrote:

> >Could it be specific to the PDF you are working on?
> >Check File -> Properties -> Security.
> >
> >I just tried with a few PDFs without any problem.
>
> I have created the PDFs with XeLaTeX and there is no security,
> no anything. In fact, marking does not work with any PDF file.
>

OK so it does not work with any PDF file you created then.
I generate mine with pdflatex bundled with TeXLive and have no issue.
I guess it would be good to understand the difference.


>
> A.S.
>
>
> --
> Apostolos Syropoulos
> Xanthi, Greece
>
>
>


-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] cannot copy text from PDF file using atril

[Aurélien Larcher]

On Sun, Nov 12, 2017 at 2:38 PM, Apostolos Syropoulos via
openindiana-discuss  wrote:

> Hello,
> I have noticed that it is almost impossible to mark text on a PDF file and
> copy it when using atril. The previousversion of atril did not show this
> problem. Is this afeature/bug or something I see only on my system?
>

Could it be specific to the PDF you are working on?
Check File -> Properties -> Security.

I just tried with a few PDFs without any problem.



> Regards,A.S.
>
> --
> Apostolos Syropoulos
> Xanthi, Greece
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Virtualbox Xorg video driver compatible with 1.19.5

[Aurélien Larcher]

On Sun, Nov 12, 2017 at 12:30 AM, Michael Huff <mph...@gmail.com> wrote:

>
>
> On 11/11/2017 12:43 PM, Aurélien Larcher wrote:
>
>> Hi
>>
>> I'm doing something wrong here, but I'm not sure what.
>>> I ran pkg update to (presumably) get the new xorg package.
>>> Then I did a pkgrm SUNWvboxguest and rebooted
>>> Then tried to do a reinstall from the autorun prompt -and got the usual
>>> error about the xorg libraries.
>>>
>>> I checked the xorg log and didn't find any autoconfiguration lines.
>>>
>>> I am sure what is the logic with metapackages.
>>
>> pkg info x11/server/xorg/driver/xorg-video-vboxvideo
>>
>> should report that the package is installed.
>>
>> Otherwise you need to install it manually.
>>
>> No xorg.conf was required in my virtual machine.
>>
> I typed that command, and it reported that it's installed.
>
> I still get the same errors trying to install guest additions, but after I
> moved /etc/X11/xorg.conf out of the way I was able to use the GUI to
> specify the resolution I want (in my host/virtualbox; view -> virtual
> screen 1 -> resize to 1920x1080. In my Hipster guest; preferences ->
> hardware -> displays.) .
>
> I'm not sure if the kernel drivers installed or not, but at least I have a
> "normal" resolution.
>

Your xorg.conf was forcing vesa so removing was just enough.
You should see vboxvideo in /var/log/Xorg.0.log



>
> Thanks for your help!
>
>
>> This is my /etc/X11/xorg.conf (autoconfigured when I chose the vesa option
>>> to start the installer dvd/iso);
>>> root@virtdiana:/var/log# cat /etc/X11/xorg.conf
>>> Section "Device"
>>>  Identifier  "Card0"
>>>  Driver  "vesa"
>>> EndSection
>>>
>>> ...that's it. I ran "pkg search vb" to try to find the driver you're
>>> talking about, but nothing came up.
>>>
>>>
>>>
>>> ___
>>> openindiana-discuss mailing list
>>> openindiana-discuss@openindiana.org
>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>>
>>>
>>
>>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Virtualbox Xorg video driver compatible with 1.19.5

[Aurélien Larcher]

Hi

>
> I'm doing something wrong here, but I'm not sure what.
> I ran pkg update to (presumably) get the new xorg package.
> Then I did a pkgrm SUNWvboxguest and rebooted
> Then tried to do a reinstall from the autorun prompt -and got the usual
> error about the xorg libraries.
>
> I checked the xorg log and didn't find any autoconfiguration lines.
>

I am sure what is the logic with metapackages.

pkg info x11/server/xorg/driver/xorg-video-vboxvideo

should report that the package is installed.

Otherwise you need to install it manually.

No xorg.conf was required in my virtual machine.



>
> This is my /etc/X11/xorg.conf (autoconfigured when I chose the vesa option
> to start the installer dvd/iso);
> root@virtdiana:/var/log# cat /etc/X11/xorg.conf
> Section "Device"
> Identifier  "Card0"
> Driver  "vesa"
> EndSection
>
> ...that's it. I ran "pkg search vb" to try to find the driver you're
> talking about, but nothing came up.
>
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] Virtualbox Xorg video driver compatible with 1.19.5

[Aurélien Larcher]

Hi,
we just merged a pull-request to provide the Xorg driver for Virtualbox
compatible with Xorg 1.19:

https://github.com/OpenIndiana/oi-userland/pull/3723

The package x11/server/xorg/driver/xorg-video-vboxvideo is now available in
the repository.
It should be installed with further updates as it is part of the xorg-video
metapackage.

Note that you still need to install the Guest Additions.

After installation the Xorg log should read:

[   243.842] (==) Matched vboxvideo as autoconfigured driver 0
[   243.842] (==) Matched vesa as autoconfigured driver 1
[   243.842] (==) Assigned the driver to the xf86ConfigLayout
[   243.842] (II) LoadModule: "vboxvideo"
[   243.843] (II) Loading /usr/lib/xorg/modules/amd64/drivers/vboxvideo_drv.so
[   243.843] (II) Module vboxvideo: vendor="Oracle Corporation"
[   243.843]compiled for 1.19.5, module version = 1.0.1
[   243.843]Module class: X.Org Video Driver
[   243.843]ABI class: X.Org Video Driver, version 23.0



---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] [oi-dev] Xorg 1.19.5 testing

[Aurélien Larcher]

On Wed, Oct 25, 2017 at 11:46 AM, Nikola M <minik...@gmail.com> wrote:

> On 10/24/17 04:32 PM, ken mays wrote:
>
> Hi Nikola,
>
> Please retry.
>
> Ken
>
>
> I retried after I supposedly changes landed.
> I don't see the point of testing, when I think newer intel driver already
> landed the same day on /hipster repository yesterday?
> (https://hipster.openindiana.org/jenkins/job/oi-userland/3476/changes)
>

The xorg-video-intel update is minor as the UXA backend is barely touched
since 2015, so it does not affect users.
The testing part was more for Xorg itself, namely input devices.



>
> I am on 945 graphics it works even if there is NO xorg.conf (to set up
> vesa use) , I suppose newer driver is used then.
> ( $ cat /etc/X11/xorg.conf
> Section "Device"
> Identifier "Card0"
> Driver "vesa"
> EndSection )
> Everything seems ok, yet VT console switching does not work when not using
> vesa, (screen gets white, like pre-exposed on VT switching with Ctrl+Alt+Fn
> , F7 is to get back to X), but it can get back to X right on F7. I haven't
> tried yet playing video.
>

VT console switching cannot work until somebody works on the i915 *kernel*
driver. This has been the case since we got the KMS intel driver integrated.


>
> Beside that., on my Core2Duo 5600 on Dell D620 laptop, i have, since April
> (bug introduced between January and April), problem with illumos, with
> large CPU use of a random running process on the machine that gets stuck
> for tens of seconds with hight cpu use for no reason, making whole system
> pretty much unusable.
>

Firefox has become very slow due to their recent changes to multithreaded.


>
> Also fonts seems too small on mine 14" 16:10 laptop screen with 1440X900
> resolution upon login
> I aether need to set DPI level on 122 manually in font settings to make it
> more readable or I need to sent default font size form 8 to 9. I think the
> first is better.
>
> If I use vesa in xorg.conf, then everything seems to work, including VT
> switching (except not tested video yet)
>
> I personally don't see why testing communication shouldn't be online and
> seen by other testers on the mailing list.
>

I wanted feedback first from Alexander and Ken before calling for testing.
I do not like wasting people's time with half-baked updates.




> Also don't understand unneeded restrictions on lowering mailing list
> number and see barring people from posting to the mailing list as bad
> practice.
> I suggest also forming new 'oi-testing' mailing list to share testing
> results, beside openindiana-discuss and oi-dev.
> We also had many different mailing lists , yet Adam Stevko (xenol)
> disabled all of them awhile ago.
> --search-first
> Down there are posted update commands and their output with
> '--search-first ' as a solution for updating testing BE.
>


Interesting, I did not know this option. I usually change the priority with
-P.

Thanks for your help

Aurelien


> On 10/24/17 06:58 PM, Aurélien Larcher wrote:
>
> On 10/24/17 01:24 AM, Aurélien Larcher wrote:
>
> What's there to test? pkg dont' see updated packages there. (see update
> tries below)
>
> I guess you should set the xorg-testing repository at a higher priority than 
> openindiana.org.
>
> If not please set the pkg to verbose mode to see which constraint blocks the 
> update.
>
> People who tested the build reported success so far.
>
>
> $ sudo /mnt/bin/pkg -R /mnt update -r -v
> Password:
> Packages to update:4
>  Estimated space available: 12.04 GB
> Estimated space to be consumed: 55.08 MB
>   Rebuild boot archive:   No
>
> Changed packages:
> openindiana.org
>   driver/graphics/agpgart
> 0.5.11-2017.0.0.62:20171024T075702Z -> 0.5.11-2017.0.0.62:
> 20171024T151659Z
>   driver/graphics/drm
> 0.5.11-2017.0.0.62:20171024T075703Z -> 0.5.11-2017.0.0.62:
> 20171024T151700Z
>   x11/library/libdrm
> 2.4.75-2017.0.0.62:20171024T075708Z -> 2.4.75-2017.0.0.62:
> 20171024T151704Z
>   x11/server/xorg/driver/xorg-video-intel
> 2.99.917-2017.0.0.4 -> 2.99.917-2017.0.0.5
>
> DOWNLOADPKGS FILESXFER (MB)
> SPEED
> Completed4/4   6/6  2.0/2.0
> 310k/s
>
> PHASE  ITEMS
> Removing old actions 4/4
> Installing new actions   4/4
> Updating modified actions  15/15
> Updating package state database Done
> Updating package cache   4/4
> Updating image state

Re: [OpenIndiana-discuss] [oi-dev] Xorg 1.19.5 testing

[Aurélien Larcher]

TigerVNC 1.7.1 and libXres 1.2.0 are now also pushed to xorg-testing.

On Wed, Oct 25, 2017 at 7:07 PM, ken mays <maybird1...@yahoo.com> wrote:

> HI Nikola,
>
> Aurelien mentions:
> "VT console switching cannot work until somebody works on the i915
> *kernel* driver. This has been the case since we got the KMS intel driver
> integrated."
>
> Hope to supply a newer Intel kernel update soon after the next snapshot
> release.
>
> Nikola mentions:
> "On Dell D620 laptop, i have, since April (bug introduced between January
> and April), problem with illumos, with large CPU use of a random running
> process on the machine that gets stuck for tens of seconds with high cpu
> use for no reason, making whole system pretty much unusable."
>
> There was a illumos submitted patch that mentioning fixing (somewhat) a
> 'related' high CPU issue.
>
> Set up a Xorg.conf file to disable HW acceleration for the Intel GPU (*Option
> 'Accel'* off) using the intel driver. You can create on another tested
> platform and just use it with the option mentioned to see if you get the
> same issue. Note: This means we are not using the vesa driver for any
> testing info. Test your VT consoles and check for CPU issues. Let us know.
>
> Thanks,
> Ken
>
> On Wednesday, October 25, 2017, 7:23:32 AM PDT, Aurélien Larcher <
> aurelien.larc...@gmail.com> wrote:
>
>
>
>
> On Wed, Oct 25, 2017 at 11:46 AM, Nikola M <minik...@gmail.com> wrote:
>
> On 10/24/17 04:32 PM, ken mays wrote:
>
> Hi Nikola,
>
> Please retry.
>
> Ken
>
>
> I retried after I supposedly changes landed.
> I don't see the point of testing, when I think newer intel driver already
> landed the same day on /hipster repository yesterday?
> (https://hipster.openindiana. org/jenkins/job/oi-userland/ 3476/changes
> <https://hipster.openindiana.org/jenkins/job/oi-userland/3476/changes>)
>
>
> The xorg-video-intel update is minor as the UXA backend is barely touched
> since 2015, so it does not affect users.
> The testing part was more for Xorg itself, namely input devices.
>
>
>
>
> I am on 945 graphics it works even if there is NO xorg.conf (to set up
> vesa use) , I suppose newer driver is used then.
> ( $ cat /etc/X11/xorg.conf
> Section "Device"
> Identifier "Card0"
> Driver "vesa"
> EndSection )
> Everything seems ok, yet VT console switching does not work when not using
> vesa, (screen gets white, like pre-exposed on VT switching with Ctrl+Alt+Fn
> , F7 is to get back to X), but it can get back to X right on F7. I haven't
> tried yet playing video.
>
>
> VT console switching cannot work until somebody works on the i915 *kernel*
> driver. This has been the case since we got the KMS intel driver integrated.
>
>
>
> Beside that., on my Core2Duo 5600 on Dell D620 laptop, i have, since April
> (bug introduced between January and April), problem with illumos, with
> large CPU use of a random running process on the machine that gets stuck
> for tens of seconds with hight cpu use for no reason, making whole system
> pretty much unusable.
>
>
> Firefox has become very slow due to their recent changes to multithreaded.
>
>
>
> Also fonts seems too small on mine 14" 16:10 laptop screen with 1440X900
> resolution upon login
> I aether need to set DPI level on 122 manually in font settings to make it
> more readable or I need to sent default font size form 8 to 9. I think the
> first is better.
>
> If I use vesa in xorg.conf, then everything seems to work, including VT
> switching (except not tested video yet)
>
> I personally don't see why testing communication shouldn't be online and
> seen by other testers on the mailing list.
>
>
> I wanted feedback first from Alexander and Ken before calling for testing.
> I do not like wasting people's time with half-baked updates.
>
>
>
>
> Also don't understand unneeded restrictions on lowering mailing list
> number and see barring people from posting to the mailing list as bad
> practice.
> I suggest also forming new 'oi-testing' mailing list to share testing
> results, beside openindiana-discuss and oi-dev.
> We also had many different mailing lists , yet Adam Stevko (xenol)
> disabled all of them awhile ago.
> --search-first
> Down there are posted update commands and their output with
> '--search-first ' as a solution for updating testing BE.
>
>
>
> Interesting, I did not know this option. I usually change the priority
> with -P.
>
> Thanks for your help
>
> Aurelien
>
>
>
> On 10/24/17 06:58 PM, Aurélien Larcher wrote:
>
> On 10/24/17 01:24 AM, Aurélien

[OpenIndiana-discuss] Help with Wiki navigation and content

[Aurélien Larcher]

Hi,
as I could not sleep last night I tried to improve the Wiki a little bit by
doing some cleanup and adding some structuring content.

For instance the home page

https://wiki.openindiana.org/oi/OpenIndiana+Wiki+Home

or the development page

https://wiki.openindiana.org/oi/Developing+OpenIndiana

have now links to subtopics to guide the reader.

If you want to contribute to OpenIndiana and have a little bit of time to
help with the Wiki, an interesting exercise would be to continue going
through the different top pages and add pointers to subtopics.

The question to answer is: would a newcomer be able to find its way through
the Wiki to find basic information XXX?

If you have information specific to some software like on this page

https://wiki.openindiana.org/oi/Eclipse

you are also welcome to add a page so that we can build a knowledge base.

Kind regards,

Aurélien



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] Wiki fonts

[Aurélien Larcher]

Hi,
I fiddled a bit with the fonts and minor cosmetics:

https://wiki.openindiana.org/oi/OpenIndiana+Wiki+Home

Please tell me if you have any rendering issue.
Kind regards

Aurelien

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] Wiki comments now disabled due to spam

[Aurélien Larcher]

Hi,
Due to very recent spam activity in the comment sections I disabled the
option.

Kind regards

Aurélien

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] Wiki page for upgrading systems is out of date.

[Aurélien Larcher]

Hi,
I was pointed to a Wiki page by a newcomer who was willing to update a
system. He asked for confirmation that the steps described were correct at:

https://wiki.openindiana.org/oi/Upgrading+OpenIndiana

This page was last updated in 2013 and proves again that keeping obsolete
pages on the Wiki is wrong.

I just fixed quickly the page to make it look less irrelevant but we should
definitely vacuum clean the Wiki if nobody steps up for updating the pages:
not in 2 or 4 years but now.
Having such obsolete information on the official Wiki is harmful.

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Is hipster repo slow for pkg commands

[Aurélien Larcher]

On Fri, Mar 24, 2017 at 3:41 PM, Harry Putnam  wrote:

> [Note: comments below NOT to be seen as load complaining]
>
> Running pkg update I've noticed that is seems really slow.  Maybe a
> local network mess I've made? or is the repo pretty slow?


> During pkg update (last was Mar 3) I see speed measured in  700-900 k/s
> during
> pkg downloads, shouldn't I be seeing measurments in at least several
> m/s or so?
>

I am on a university network and reach 10M/s.


>
> pkg  search usually seems quite slow too.  I have rebuilt the search
> database or etc but still it usually seems quite slow
>

pkg does not search only for package names but for actions so it is bound
to be slower than tarball-based package management systems.


>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Recent Wiki Changes unchanged for two months

[Aurélien Larcher]

On Fri, Mar 24, 2017 at 1:45 PM, Gary Mills  wrote:

> It's now been two months since this page:
>
> https://wiki.openindiana.org/oi/Recent+Wiki+Changes
>
> last changed.  Is something wrong?
>
> Same as usual I guess.


>
> --
> -Gary Mills--refurb--Winnipeg, Manitoba,
> Canada-
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] Testing for Xorg video drivers

[Aurélien Larcher]

Hi,
we do have some updates pending for Xorg video drivers in

https://github.com/OpenIndiana/oi-userland/pull/2451

but currently we do not have hardware for testing all of them.

Sync xorg-video-intel with upstream 2017.02
Bump xorg-video-mga to 1.6.5 + exa patches from x-s12
Bump xorg-video-openchrome to 0.5.0
Bump xorg-video-r128 to 6.10.2
Bump xorg-video-nv to 2.1.21
Bump xorg-video-savage to 2.3.9
Bump xorg-video-trident to 1.3.8
Bump xorg-video-vmware to 13.2.1

It would be good to assemble a list of people using specific hardware
(openchrome, mach64, mga, etc..) and willing to help testing new versions.

Thank you,

Aurélien

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] libjpeg-turbo transition status

[Aurélien Larcher]

On Wed, Mar 8, 2017 at 11:15 PM, Adam Števko <adam.ste...@gmail.com> wrote:

> Hey,
>
> that's a lot of packages. It would be great if we migrated before we
> create a new release.
>

Indeed ;)

Also I bumped libjpeg-turbo to 1.5.1 some days ago and added symlinks

/usr/lib/pkgconfig/libjpeg.pc
/usr/lib/amd64/pkgconfig/libjpeg.pc

to libjpeg8-turbo's configuration files.
Therefore some components may pick the new default implementation
automatically at rebuil.




>
> Adam
>
> > On 8 Mar 2017, at 22:24, Aurélien Larcher <aurelien.larc...@gmail.com>
> wrote:
> >
> > Hi,
> > thanks to Tim, we have moved forward with the transition to libjpeg-turbo
> > as default JPEG implementation.
> > I added a page on the Wiki to track the progress:
> >
> > https://wiki.openindiana.org/oi/JPEG+8
> >
> > Whenever one of the packages listed is updated, it should be recompiled
> > against the new default library.
> > Kind regards,
> >
> > Aurélien
> >
> > --
> > ---
> > Praise the Caffeine embeddings
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] libjpeg-turbo transition status

[Aurélien Larcher]

On Wed, Mar 8, 2017 at 11:19 PM, Tim Mooney  wrote:

> In regard to: [OpenIndiana-discuss] libjpeg-turbo transition status,...:
>
> I added a page on the Wiki to track the progress:
>>
>> https://wiki.openindiana.org/oi/JPEG+8
>>
>
> Good, that will be easier to update as various people tackle individual
> components.
>
> Would you like me to add a column to that table for the URL for the
> github pull request, or is that not useful?
>

Yes that would be great! I usually do it but have no time right now.
(like
https://wiki.openindiana.org/oi/Migration+of+consolidations+to+oi-userland)


>
> Whenever one of the packages listed is updated, it should be recompiled
>> against the new default library.
>>
>
> For anyone that's interested in tackling one of these, I've primarily
> been relying on the following documents:
>
> 1) http://docs.openindiana.org/dev/userland/
>
> 2) The older wiki doc that covers a lot of the same stuff:
>
> https://wiki.openindiana.org/oi/Building+with+oi-userland
>
> but only for some of the additional information (like the
> REQUIRED_PACKAGES target) that hasn't yet made it into the userland doc
> from #1.
>
> 3) Aurélien's git workflow notes:
>
> http://hub.openindiana.ninja/?q=content/git-workflow
>
> When everything goes right with the pull request, you only need the info
> from the userland doc (#1, above), it's only when there's something
> "strange" to do with git that I've used info from document #3.
>
>
> Once you understand the development/git/github workflow, the *general*
> process for these components is
>
> 1) be sure you bump the number for the COMPONENT_REVISION (should be in
> the Makefile)
>
> 2) add whatever flags are necessary to get the component to compile
> and link with libjpeg8-turbo.  For the configure-based packages I've
> tried so far, that's something like
>
> CFLAGS   += $(JPEG_CPPFLAGS) $(JPEG_CFLAGS)
> CXXFLAGS += $(JPEG_CPPFLAGS) $(JPEG_CXXFLAGS)
> LDFLAGS  += $(JPEG_LDFLAGS)
>
> There will definitely be components where that won't work or won't be
> enough, but it's the first thing to try for configure-based ones.
>
> 3) build, test, install on your devel box, and ensure that "ldd" shows
> that the binaries from your updated package are linked against
> libjpeg8-turbo, rather than just libjpeg.
>
> 4) update the REQUIRED_PACKAGES setting in the Makefile to specify that
> image/library/$(JPEG_IMPLEM) is a dependency.  If there are no
> REQUIRED_PACKAGES lines in the Makefile, read the wiki doc (#2) about
> the REQUIRED_PACKAGES Makefile target.
>
> 5) submit your pull request as documented in the development workflow
> and wait for feedback.  Early pull requests from me, like this one:
>
> https://github.com/OpenIndiana/oi-userland/pull/2797
>
> generated more feedback and I needed to make more changes based on
> feedback Alexander & Aurélien's comments.  Later pull requests, like
> this one:
>
> https://github.com/OpenIndiana/oi-userland/pull/2832
>
> went more smoothly.
>
> Only very few of the components have been completed so far and I'm
> certainly not getting to them very quickly, so the more people that give
> it a try, the faster this will be completed.
>
> Tim
> --
> Tim Mooney tim.moo...@ndsu.edu
> Enterprise Computing & Infrastructure  701-231-1076
> (Voice)
> Room 242-J6, Quentin Burdick Building  701-231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] libjpeg-turbo transition status

[Aurélien Larcher]

Hi,
thanks to Tim, we have moved forward with the transition to libjpeg-turbo
as default JPEG implementation.
I added a page on the Wiki to track the progress:

https://wiki.openindiana.org/oi/JPEG+8

Whenever one of the packages listed is updated, it should be recompiled
against the new default library.
Kind regards,

Aurélien

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Rhythmbox crashes after large update on 2017-03-07

[Aurélien Larcher]

On Wed, Mar 8, 2017 at 9:16 PM, Aurélien Larcher <aurelien.larc...@gmail.com
> wrote:

>
>
> On Wed, Mar 8, 2017 at 8:37 PM, Will Brokenbourgh <
> will.brokenbourgh2...@gmail.com> wrote:
>
>> On 03/08/17 11:10, Tim Mooney wrote:
>>
>>> I just tried rhythmbox now, and rhythmbox core dumps for me too.
>>>
>>
>> Thanks for that, Tim!
>>
>> At least I know that it isn't something specific to only my system. When
>> I get some time, I'll get in and try troubleshooting but I'm stuck in
>> FreeBSD for the moment.
>>
>
>
> ::stack
libgstreamer-0.10.so.0.30.0`priv_gst_parse_yylex+0x1d(8046314, febe2c91,
80462f8
, feaa803f, 8719620, 8859018)
libgstreamer-0.10.so.0.30.0`priv_gst_parse_yyparse+0xac7(87ad730, 80468bc,
edc10018, f90e3512)
libgstreamer-0.10.so.0.30.0`priv_gst_parse_launch+0xa7(87ad670, 804696c, 0,
0,
fb2abde1, 88e61f0)
libgstreamer-0.10.so.0.30.0`gst_parse_launch_full+0xff(87ad670, 0, 0,
804696c)
libgstreamer-0.10.so.0.30.0`gst_parse_launch+0x21(87ad670, 804696c,
8046988,
f90e6689)

Most likely a border effect of the bison update.





>
>
>>
>> Cheers! :-)
>>
>>
>> Will Brokenbourgh
>>
>> Sent from my FreeBSD desktop
>>
>>
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>
>
>
>
> --
> ---
> Praise the Caffeine embeddings
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Rhythmbox crashes after large update on 2017-03-07

[Aurélien Larcher]

On Wed, Mar 8, 2017 at 8:37 PM, Will Brokenbourgh <
will.brokenbourgh2...@gmail.com> wrote:

> On 03/08/17 11:10, Tim Mooney wrote:
>
>> I just tried rhythmbox now, and rhythmbox core dumps for me too.
>>
>
> Thanks for that, Tim!
>
> At least I know that it isn't something specific to only my system. When I
> get some time, I'll get in and try troubleshooting but I'm stuck in FreeBSD
> for the moment.
>

Our Rhythmbox version is antique.
If it is too involved, I am not sure if it is worth spending time on this
particular instance but rather work on maintained versions.


>
> Cheers! :-)
>
>
> Will Brokenbourgh
>
> Sent from my FreeBSD desktop
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Newly installed VirtualBox gives COM object error when launched

[Aurélien Larcher]

On Mon, Mar 6, 2017 at 8:17 AM, Will Brokenbourgh <
will.brokenbourgh2...@gmail.com> wrote:

> Foon 2017-03-03 09:09 AM, Aurélien Larcher espetanjalah:
>
>> On Thu, Mar 2, 2017 at 1:22 AM, Will Brokenbourgh <
>> will.brokenbourgh2...@gmail.com> wrote:
>>
>> Here is the 'full' truss of /opt/VirtualBox/VirtualBox (run as superuser)
>>>
>>> https://gist.github.com/willbprog127/b1f5813feafcf6a515fc05b1e30a4f3b
>>>
>>
>> I'll have a look this week end probably.
>> Any additional debug information will help.
>> Thanks
>>
>>
> Since deactivating my Intel integrated graphics, installing an Nvidia
> GTX-610 graphics card and updating the system, I have been able to
> re-install the 'special' VirtualBox package and it is now working after a
> reboot.  Hooray!
>

Great! Congratulations!

So I guess there is still something weird with the GL libraries :)

No time this week end but I'll try to fix Virtualbox as soon as Qt 5.8 is
merged.


>
> Many thanks, :-)
>
>
> --
>
> Will Brokenbourgh
> Pacific Northwest, USA
> GMT-8
>
> Sent from my OpenIndiana desktop
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] openindiana-discuss Digest, Vol 80, Issue 5

[Aurélien Larcher]

On Fri, Mar 3, 2017 at 9:38 PM, Mappack Owner  wrote:

> Hello again,
>
> This message is directed to Alexander Pyhalov who replied to my "thread"
> about non-free components in illumos/OpenIndiana. I'm not sure how I
> should reply to a specific thread in a mailing list which comes as a
> daily digest. I'm sorry if this is sent to the wrong place.
>
> Thanks, so the non-free components are mostly a handful of utilities and
> kernel components from Sun?


It contained utilities, closed-source kernel drivers and iconv + the i18n
library.
Some of them (like i18n and several kernel drivers) have been replaced by
opensource versions, some have just been deprecated.



> Also, what are xpg4 and xpg6?
>

You can read about XPG4 and XPG6 in the standards manual page:

https://illumos.org/man/5/standards

Kind regards

Aurelien


> Kind regards,
>
> Joeke de Graaf
>
> On vr, 2017-03-03 at 12:00 +,
> openindiana-discuss-requ...@openindiana.org wrote:
> > Send openindiana-discuss mailing list submissions to
> >   openindiana-discuss@openindiana.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >   https://openindiana.org/mailman/listinfo/openindiana-discuss
> > or, via email, send a message with subject or body 'help' to
> >   openindiana-discuss-requ...@openindiana.org
> >
> > You can reach the person managing the list at
> >   openindiana-discuss-ow...@openindiana.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of openindiana-discuss digest..."
> >
> >
> > Today's Topics:
> >
> >1. Re: usb3 (Apostolos Syropoulos)
> >2. Re: usb3 (Apostolos Syropoulos)
> >3. Hipster & multi-user-desktop (Jacques Hugo)
> >4. Non-free, binary-only components (Mappack Owner)
> >5. Re: Non-free, binary-only components (Alexander Pyhalov)
> >6. Re: Install Solaris 1/13 on Sun Fire X2200 ( )
> >
> >
> > --
> >
> > Message: 1
> > Date: Thu, 2 Mar 2017 13:46:53 + (UTC)
> > From: Apostolos Syropoulos 
> > To: "Joshua M. Clulow" , Discussion list for
> >   OpenIndiana 
> > Cc: Discussion List for OpenIndiana
> >   
> > Subject: Re: [OpenIndiana-discuss] usb3
> > Message-ID: <2124025625.319878.1488462413...@mail.yahoo.com>
> > Content-Type: text/plain; charset=UTF-8
> >
> > >I don't believe you are banned; rather it looks like you're just not
> > >subscribed to the list.? You need to be subscribed with the address
> > >you are using to send mail in order for your messages to the illumos
> > >developer@ and discuss@ list to be accepted.
> >
> > During last August I tried to send a message and it was not posted tothe
> list. Then I tried to send a test message and it was not posted again.The
> second one was posted but not immediately. So? I concluded that forsome
> reason I am blocked. Now, I wanted to explain to people why I was
> > posting the message about the XHCI driver to the OI list while it
> clearlybelonged to some other list. That's all. I have also to add that I
> wasreceiving mails from the list for some time but I haven;t received
> anythingfor sometime. Maybe I have deleted my subscription and I do not
> remember this.
> > But it would be nice to send my initial message about the UBS3 driver
> tothe person who works on it, just in case this can be proved useful to him.
> >
> > A.S.
> >
> >
> > --
> > Apostolos Syropoulos
> > Xanthi, Greece
> >
> >
> >
> >
> >
> >
> >
> > --
> >
> > Message: 2
> > Date: Thu, 2 Mar 2017 13:46:53 + (UTC)
> > From: Apostolos Syropoulos 
> > To: "Joshua M. Clulow" , Discussion list for
> >   OpenIndiana 
> > Cc: Discussion List for OpenIndiana
> >   
> > Subject: Re: [OpenIndiana-discuss] usb3
> > Message-ID: <2124025625.319878.1488462413...@mail.yahoo.com>
> > Content-Type: text/plain; charset=UTF-8
> >
> > >I don't believe you are banned; rather it looks like you're just not
> > >subscribed to the list.? You need to be subscribed with the address
> > >you are using to send mail in order for your messages to the illumos
> > >developer@ and discuss@ list to be accepted.
> >
> > During last August I tried to send a message and it was not posted tothe
> list. Then I tried to send a test message and it was not posted again.The
> second one was posted but not immediately. So? I concluded that forsome
> reason I am blocked. Now, I wanted to explain to people why I was
> > posting the message about the XHCI driver to the OI list while it
> clearlybelonged to some other list. That's all. I have also to add that I
> wasreceiving mails from the list for some 

Re: [OpenIndiana-discuss] Newly installed VirtualBox gives COM object error when launched

[Aurélien Larcher]

On Thu, Mar 2, 2017 at 1:22 AM, Will Brokenbourgh <
will.brokenbourgh2...@gmail.com> wrote:

> Here is the 'full' truss of /opt/VirtualBox/VirtualBox (run as superuser)
>
> https://gist.github.com/willbprog127/b1f5813feafcf6a515fc05b1e30a4f3b


I'll have a look this week end probably.
Any additional debug information will help.
Thanks


>
>
> --
>
> Will Brokenbourgh
> Pacific Northwest, USA
> GMT-8
>
> Sent from my OpenIndiana desktop
>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] oi-userland for SPARC

[Aurélien Larcher]

> Of course SPARC is not an officially supported platform.  That's our
> goal, not the current situation.  We can't reach that goal in one
> giant leap, either.  That's why I, and a few others, are building
> oi-userland components on SPARC.  We will have to take several smaller
> steps to reach that goal.
>

Whenever I bring a component from solaris-userland or from the x-s12 gate I
try to import SPARC patches as well.
Please post to the ML if I forgot some of them.


-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Pending Desktop features for 2017.04 need volunteers

[Aurélien Larcher]

Hi Tim,
sorry for the late reply.


> When I do my next package contribution, I'm going to try keep better
> notes, so I can also submit some feedback or updates for the documentation
> itself.  For example, I found that there were some inconsistencies between
>
> http://docs.openindiana.org/dev/userland/
>
> and
>
> https://wiki.openindiana.org/oi/Building+with+oi-userland
>
> I'll take notes on the rough spots I run into and find ways to help
> improve the docs.
>

Great :) I should also look at reorganizing some notes on the Wiki.


>
> One github pull request per package that gets updated?  Or a pull request
> for each group (batch) of packages that someone gets done in a session of
> work?
>

One PR per package would be better, let us favour incremental changes.
You can pick one package at a time (start with the one you find to be the
easiest) and ask for help/review.
It is also easier to manage for reviewers.


> Also, I noted that many of the packages that need to be updated are
> themselves libraries (tiff, gd, lcms2) that other packages will depend
> upon.
> Are there any special considerations for packages like tiff or gd, or is
> it sufficient to test that e.g. tiff will build correctly with
> libjpeg-turbo, and let the integration system test that dependencies on
> tiff still build?


Technically both jpeg libraries provide the same functionality so there
should not be any issue.
If tests are provided, make sure they pass (or at least reproduce same
failures as before).
If a dependency needs rebuild you need to trigger it by bumping the
COMPONENT_REVISION variable in the makefile (set to zero by default).
You may want to check Debian's migration notes if there are known corner
cases.

Thank you

Aurélien


>
>
> Tim
> --
> Tim Mooney tim.moo...@ndsu.edu
> Enterprise Computing & Infrastructure  701-231-1076
> (Voice)
> Room 242-J6, Quentin Burdick Building  701-231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Oios ????? Re: mailinglist oios

[Aurélien Larcher]

On Sun, Feb 12, 2017 at 1:08 AM, Jim Klimov  wrote:

> 11 февраля 2017 г. 22:36:09 CET, bscuk2  пишет:
> >openindiana was a project name in the past but it evolved to oi and
> >oios
> >as branding and search engine necessities moved it on. Clearly I am not
> >
> >now keen on calling it Hipster now as people suggest. Keep it as it is
> >oi or oios.
> >
> >
> >On 11/02/2017 21:32, Nikola M wrote:
> >> On 01/30/17 01:36 AM, Jerry Kemp wrote:
> >>> Came across this post searching my personal archives for something
> >else.
> >>
> >> I got under impression it's just a nickname he likes to call
> >Openindiana.
> >> Didn't spread much as branding is Openindiana / OI.
> >>
> >>
> >>
> >> ___
> >> openindiana-discuss mailing list
> >> openindiana-discuss@openindiana.org
> >> https://openindiana.org/mailman/listinfo/openindiana-discuss
> >
> >
> >___
> >openindiana-discuss mailing list
> >openindiana-discuss@openindiana.org
> >https://openindiana.org/mailman/listinfo/openindiana-discuss
>
> Actually it is still the OpenIndiana (or OI for short) as a something
> between vendor tag (with no corporate entity though) and distro spec
> (modern direct continuation of OpenSolaris Indiana (IPS edition), general
> purpose for both servers and desktops - and probably upgradeable from old
> OpenSolaris setups over a number of intermediate steps and a mix of light
> and dark magic, voodoo and shaman tamtam dancing during the right phase of
> the blue moon).
>
> There are (or were intended) several distros under this umbrella, subject
> to available manpower, such as 'dev' with original OpenSolaris
> consolidation and package structure and occasional "preview releases" (up
> till 151a9), and OpenIndiana/Hipster as a rolling release still busy
> getting rid of last vestiges of legacy consolidations so a new foundation
> can be used for "stable releases", if someone pops up to define and
> maintain and support those - probably with OpenIndiana/SomethingElse
> name-tag.
>

OpenIndiana/Vintage -> OpenIndiana/Indie -> OpenIndiana/Hipster ->
OpenIndiana/BrutalDeathMetal


>
> Hope this clears it up a bit.
> Jim Klimov
> --
> Typos courtesy of K-9 Mail on my Samsung Android
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>



-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss