[oi-dev] GCC testsuite results

2019-09-25 Thread Aurélien Larcher
Hi,
every time I have rebased the illumos-gcc patchset to provide a new gcc
version on OI I have run the testsuite but have not been able to upload the
results.
I have re-run the testsuite for each version (5-9) we deliver with both
-m64 and -m64 -msave-args, and uploaded tarballs to

http://ovh.to/W1tVK9v

for reference.

Build recipes can be found in the corresponding gcc-* subdirectory in

https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/developer

Now that we have the IPD I expect to upload future test results against any
new -il branch to a dedicated location.

Kind regards

Aurélien

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


Re: [oi-dev] 64 or 32_and_64 for dependency "leaf" ?

2019-09-24 Thread Aurélien Larcher
On Tue, Sep 24, 2019 at 10:53 PM Tim Mooney  wrote:

>
> All-
>
> When rebuilding or updating a component that doesn't have any shared
> libraries, so it's effectively a "leaf" on the dependency tree, should
> the component be built 64 bit or 32_and_64?
>
> The component I'm currently looking at is sound-juicer, but the same
> question likely applies to any other component that is one or two
> executables and support files, with no shared libraries of its own.
>
> I looked at both the "Building with oi-userland" and the "Existing tasks"
> docs on docs.openindiana.org and don't see this discussed.  Apologies if
> it's documented and I missed it.
>

Hello,
except if there is a real incentive to provide 32-bit executables, e.g if
the binary performs code generation defined by the bitness, the current
move is to keep 64-bit only.
That has been the case for example with Python or the X11 stack.

Kind regards,

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
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>


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


Re: [oi-dev] How to create an ISO correctly?

2019-08-27 Thread Aurélien Larcher
On Tue, Aug 27, 2019 at 3:16 PM Gary Mills  wrote:

> On Mon, Aug 26, 2019 at 11:58:42PM +0200, Aurélien Larcher wrote:
> >
> >If you look at:
> >[4]
> https://hipster.openindiana.org/distro_const/text_mode_x86-minimal.x
> >ml
> >pkg_repo_default_authority specifies the repository from which the
> >packages are pulled and thus the image created, while
> >post_install_repo_default_authority stands for the default publisher
> >configured on the ISO itself.
>
> So, they can be different.  That makes it easy for me.
>
> Is that the same as:
>
> /usr/share/distro_const/text_install/text_mode_x86_minimal.xml
>
> which was installed when I installed the distribution-constructor
> package?
>

Probably fairly similar.



>
> What should be the publisher name?  I see that it's openindiana.org in
> the /usr/share/distro_const/text*.xml files.
>

The actual publisher name defined in the pkg repository.
By default for a local repository this would be 'userland'.

>
> >There are packages like this that can be published from metapackage/
> >components.
> >For regular Jenkins jobs `gmake -C components incorporation` is called
> >after publication of new packages to generate such meta-packages.
>
> Thanks.  I'll look into that procedure.
>
> >At least on x86 both usb images and cd iso are created by
> distro_const.
>
> I suppose I'll find out the first time I run it.
>
>
> --
> -Gary Mills--refurb--Winnipeg, Manitoba,
> Canada-
>


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


[oi-dev] HEADS-UP: 11624 Use of modern nawk(1) requires update of generate-history

2019-08-27 Thread Aurélien Larcher
As a consequence to the nawk(1) update in illumos-gate, make sure that your
oi-userland clone contains the following commit to ensure proper history
generation,

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

Aurélien
-- 
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev


Re: [oi-dev] How to create an ISO correctly?

2019-08-26 Thread Aurélien Larcher
On Mon, Aug 26, 2019 at 11:46 PM Gary Mills  wrote:

> Another progress report and some questions: I have now replaced all
> v9os packages with oi-userland packages.  There are no v9os packages
> left.  My T2000 has only oi-userland packages, ones that I have built.
> It boots correctly.  The publisher name is oi-userland, not the usual
> userland or openindiana.org .  That difference raises my first
> question.
>
> I've read the information on distribution-constructor:
>
> http://docs.openindiana.org/dev/distribution-constructor/
>
> as well as the man page for distro_const .  Neither of them answered
> my questions completely.
>
> Will distro_const change the publisher in the ISO file, both for the
> packages and the `pkg publisher' command?  How do I do this?
>

If you look at:

https://hipster.openindiana.org/distro_const/text_mode_x86-minimal.xml

pkg_repo_default_authority specifies the repository from which the packages
are pulled and thus the image created, while
post_install_repo_default_authority stands for the default publisher
configured on the ISO itself.

>
> If not, can the publisher be changed on the host system?  Does the
> publisher in `pkg publisher' have to match the one in the file
> repository?
>
> I see that the XML file used by distro_const specifies `entire' as the
> package that includes all the packages to install to the ISO file.
> My system has no package `entire'.  How do I create and populate it?
> Will it include some packages that do not exist?  Will this be a
> problem?
>

There are packages like this that can be published from metapackage/
components.

For regular Jenkins jobs `gmake -C components incorporation` is called
after publication of new packages to generate such meta-packages.


>
> Finally, how do I create a USB image from the CD image?
>

At least on x86 both usb images and cd iso are created by distro_const.


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


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


Re: [oi-dev] Something is weird with oi-userland

2019-08-17 Thread Aurélien Larcher
On Sat, Aug 17, 2019 at 8:21 PM Andreas Wacknitz  wrote:

>
> 1.
> ➜  libgweather git:(build) gmake publish
> ...
> pkg list: no packages matching the following patterns are installed:
>   /runtime/ruby
> Adding required packages to build environment...
>
>
> 2.
> ➜  libgweather git:(build) cat Makefile
> ...
> # Build dependencies
> REQUIRED_PACKAGES += developer/vala
>
> # Auto-generated dependencies
> REQUIRED_PACKAGES += library/desktop/gdk-pixbuf
> REQUIRED_PACKAGES += library/desktop/geocode-glib
> REQUIRED_PACKAGES += library/desktop/gtk3
> REQUIRED_PACKAGES += library/glib2
> REQUIRED_PACKAGES += library/libsoup
> REQUIRED_PACKAGES += library/libxml2
> REQUIRED_PACKAGES += system/library
> REQUIRED_PACKAGES += system/library/math
>
>
> 3.
> ➜  ~ git:(build) pkg mediator
> MEDIATORVER. SRC. VERSION IMPL. SRC. IMPLEMENTATION
> ...
> rubyvendor2.3 vendor
> ...
>
>
> 4.
> ➜  ~ pkg list|grep ruby
> ...
> runtime/ruby
> 2.6-2018.0.0.0 i--
> runtime/ruby-232.3.7-2018.0.0.0
> i--
>
>
>
> Summary: Our default ruby is 2.3 (see 3.) while the more generic
> runtime/ruby is ruby-2.6 (see 4.).
> At least one package (libgweather; see 1.) requires runtime/ruby but that
> is not listed in its Makefile (see 2.).
> Fun fact: "gmake publish" finds a dependency on runtime/ruby while "gmake
> REQUIRED_PACKAGES" does not.
>

https://github.com/OpenIndiana/oi-userland/blob/681a424df01cea4df46a08efa562fa877eba9b04/make-rules/prep-unpack.mk#L65

>
> How can this be enhanced?
>
> Regards,
> Andreas
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>


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


Re: [oi-dev] Pecular dependancies in publishing print/cups-filters

2019-08-14 Thread Aurélien Larcher
On Wed, Aug 14, 2019 at 4:11 PM Aurélien Larcher 
wrote:

>
>
> On Wed, Aug 14, 2019 at 3:58 PM Gary Mills  wrote:
>
>> On Wed, Aug 14, 2019 at 10:39:22AM +0200, Till Wegmüller wrote:
>> >
>> > PKG uses it's own PATH variable to find libraries. Think of -I for GCC
>> > for example. And that has been modified to include
>> > usr/lib/libjpeg6-ijg/lib already but now also needs usr/gcc/6/lib to be
>> > added.
>>
>> Are you saying that pkg does not use the runtime path from the ELF
>> section at all?  The runtime linker certainly uses that.
>>
>> /usr/gcc/6 is the default compiler for the 2018 version of OI that I'm
>> using.  Surely that element is already in the runtime path that's used
>> by pkg.  I'd expect that jpeg library path to be the one that's
>> absent.
>>
>> > You can override that by either:
>> > - Setting the dependency in the manifest manually and add
>> > pkg.depend-bypass to the files that complain or
>> > - Modify the Include path PKG searches. I am however unsure which exact
>> > knob in oi-userland to tweak here.
>>
>> Do you have examples from other packages of these two techniques?
>> I'd like to start with something that works.
>>
>> > You should see the override either in the Makefile or the Manifest look
>> > for "usr/lib/libjpeg6-ijg/lib" mentioned there.
>>
>> There's nothing in either for the print/cups-filters package.
>>
>
> Look in the Makefile, it should use image/library/libjpeg8-turbo not
> libjpeg6-ijg.
>
> Probably it is not installed on your system, execute gmake env-prep.
>

The error tells you that no package in the REQUIRED_PACKAGES list provides
a suitable dependency.

>
>
>
>
>>
>>
>> --
>> -Gary Mills--refurb--Winnipeg, Manitoba,
>> Canada-
>>
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> https://openindiana.org/mailman/listinfo/oi-dev
>>
>
>
> --
> ---
> Praise the Caffeine embeddings
>


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


Re: [oi-dev] Pecular dependancies in publishing print/cups-filters

2019-08-14 Thread Aurélien Larcher
On Wed, Aug 14, 2019 at 3:58 PM Gary Mills  wrote:

> On Wed, Aug 14, 2019 at 10:39:22AM +0200, Till Wegmüller wrote:
> >
> > PKG uses it's own PATH variable to find libraries. Think of -I for GCC
> > for example. And that has been modified to include
> > usr/lib/libjpeg6-ijg/lib already but now also needs usr/gcc/6/lib to be
> > added.
>
> Are you saying that pkg does not use the runtime path from the ELF
> section at all?  The runtime linker certainly uses that.
>
> /usr/gcc/6 is the default compiler for the 2018 version of OI that I'm
> using.  Surely that element is already in the runtime path that's used
> by pkg.  I'd expect that jpeg library path to be the one that's
> absent.
>
> > You can override that by either:
> > - Setting the dependency in the manifest manually and add
> > pkg.depend-bypass to the files that complain or
> > - Modify the Include path PKG searches. I am however unsure which exact
> > knob in oi-userland to tweak here.
>
> Do you have examples from other packages of these two techniques?
> I'd like to start with something that works.
>
> > You should see the override either in the Makefile or the Manifest look
> > for "usr/lib/libjpeg6-ijg/lib" mentioned there.
>
> There's nothing in either for the print/cups-filters package.
>

Look in the Makefile, it should use image/library/libjpeg8-turbo not
libjpeg6-ijg.

Probably it is not installed on your system, execute gmake env-prep.




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


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


[oi-dev] Location for gcc testsuite results

2019-08-10 Thread Aurélien Larcher
Hi,
I have been running all the gcc testsuites again to compile a more or less
exhaustive database.

Where could I upload the results?

I used to upload them here

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

but this is not an option anymore given that we want to retire the Wiki.

Kind regards,

Aurélien

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


[oi-dev] Hello OpenIndiana!

2019-08-07 Thread Aurélien Larcher
narval> g++-9 --version
g++-9 (OpenIndiana 9.1.0-OI-0) 9.1.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

narval> g++-9 main.cpp
narval> ./a.out
Hello OpenIndiana!

narval> file a.out
a.out:  ELF 64-bit LSB executable AMD64 Version 1, dynamically
linked, not stripped, no debugging information available

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


[oi-dev] oi-userland rebuild failures

2019-08-07 Thread Aurélien Larcher
Hi,
for reference, find the list of rebuild failures, some related to python 3
migration of userland tools and pkg:

cluster/pcs -> invalid manifest after ruby update
desktop/gnome3/libgweather -> broken link
desktop/gnome3/seahorse -> missing dependency? Couldn't find
'usr/lib/amd64/seahorse/xloadimage' in any of the specified search
directories:
desktop/gnome3/evolution-data-server -> ld.so.1: EDataServer-1.2: fatal:
libstdc++.so.6: version 'GLIBCXX_3.4.21' not found
developer/autogen -> 64-bit build fails which: no bash in ((null))
developer/jenkins -> pkgdepend issue
developer/opensp -> broken with new gettext
editor/bvi -> curses issue
editor/emacs -> segmentation fault
library/physfs -> wrong library path
network/openconnect -> obsolete required package and pkgdepend error
network/lftp -> curses issue
openindiana/illumos-closed -> publish does not execute prep
openindiana/qemu-kvm -> ctfmerge: failed to open ../cache-utils.o: File
does not contain CTF data
runtime/jruby -> java internal error
runtime/clisp -> missing localcharset.h probably broken with new gettext
sysutils/gtkperf -> broken with new gettext
sysutils/bacula -> bacula-fd not built in 64-bit
web/icedtea-web -> missing #include , obsolete since npapi dropped?
x11/compat-links -> fix makefile, pkgdepend issue
x11/compatibility -> fix makefile, pkgdepend issue

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


Re: [oi-dev] Toward a SPARC distro of OI

2019-06-17 Thread Aurélien Larcher
On Mon, Jun 17, 2019 at 11:59 AM Gary Mills  wrote:

> I'm part way through this long project now.  I began with v9os
> installed on a Sun T2000.  v9os is a SPARC distribution that uses IPS
> packages.  I've been building IPS packages from oi-userland source.
> This process has gotten easier now that all the build tools I need are
> in IPS packages.  I've been replacing v9os packages with oi-userland
> packages.  My goal is to replace all of them, and finally to produce a
> text ISO and package repository for SPARC that's entirely based on
> oi-userland.
>
> So far, I've built and packaged versions 5, 6, and 7 of the gcc
> compiler.  The commands for IPS packages are all packaged for python
> 2.7.  My system now has 106 packages installed from oi-userland,
> versus 343 packages from v9os.  Most of the oi-userland products
> required very few or no changes to build and package for SPARC.
>
> For perl, I've removed the 5.16.1 version from v9os and installed
> versions 5.22 and 5.24 from oi-userland.  Likewise, for python, I've
> removed 2.6 and installed 2.7 and 3.4.  Perl libraries are all
> packaged for 5.22.  Python libraries are all packaged for 2.7.
>
> I'm submitting this message to the mailing list mostly as a progress
> report.  I would, of course, appreciate a bit of help with this
> project.
>

Congratulations Gary this is great :)
If we get to the point that we can setup a build machine this would secure
your work.
Kind regards

Aurélien



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


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


Re: [oi-dev] On the way to Firefox 68 ESR

2019-05-11 Thread Aurélien Larcher
On Sat, May 11, 2019 at 3:31 PM Aurélien Larcher 
wrote:

>
>
> On Sat, May 11, 2019 at 2:51 PM Michal Nowak  wrote:
>
>> On 05/11/19 02:35 PM, Aurélien Larcher wrote:
>> > Hello,
>> > thanks for doing this.
>> >
>> > with Geoffrey Weiss we started working on the next Firefox ESR:
>> >
>> > https://github.com/OpenIndiana/oi-userland/pull/4999
>> >
>> >
>> > Which clang do you use?
>>
>> developer/clang-40, the only one we have. ?
>>
>
> Ah so I guess I forgot to push 6.0, that may explain some differences I
> had in my zone w.r.t rust.
>

I'll try to push newer clang together with gcc 9.1 next week.

>
>
>
>>
>> > Maybe you should mention that people should not modify gcc headers in
>> > their global zone.
>>
>> Just updated the PR, thanks.
>>
>> >
>> > Aurélien
>> >
>> >
>> >
>> >
>> > oi-dev mailing list
>> > oi-dev@openindiana.org <mailto:oi-dev@openindiana.org>
>> > https://openindiana.org/mailman/listinfo/oi-dev
>> >
>> >
>> >
>> > --
>> > ---
>> > Praise the Caffeine embeddings
>> >
>> >
>> > ___
>> > oi-dev mailing list
>> > oi-dev@openindiana.org
>> > https://openindiana.org/mailman/listinfo/oi-dev
>> >
>>
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> https://openindiana.org/mailman/listinfo/oi-dev
>>
>
>
> --
> ---
> Praise the Caffeine embeddings
>


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


Re: [oi-dev] On the way to Firefox 68 ESR

2019-05-11 Thread Aurélien Larcher
On Sat, May 11, 2019 at 2:51 PM Michal Nowak  wrote:

> On 05/11/19 02:35 PM, Aurélien Larcher wrote:
> > Hello,
> > thanks for doing this.
> >
> > with Geoffrey Weiss we started working on the next Firefox ESR:
> >
> > https://github.com/OpenIndiana/oi-userland/pull/4999
> >
> >
> > Which clang do you use?
>
> developer/clang-40, the only one we have. ?
>

Ah so I guess I forgot to push 6.0, that may explain some differences I had
in my zone w.r.t rust.



>
> > Maybe you should mention that people should not modify gcc headers in
> > their global zone.
>
> Just updated the PR, thanks.
>
> >
> > Aurélien
> >
> >
> >
> >
> > oi-dev mailing list
> > oi-dev@openindiana.org <mailto:oi-dev@openindiana.org>
> > https://openindiana.org/mailman/listinfo/oi-dev
> >
> >
> >
> > --
> > ---
> > Praise the Caffeine embeddings
> >
> >
> > ___
> > oi-dev mailing list
> > oi-dev@openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev
> >
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>


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


Re: [oi-dev] On the way to Firefox 68 ESR

2019-05-11 Thread Aurélien Larcher
Hello,
thanks for doing this.

with Geoffrey Weiss we started working on the next Firefox ESR:
>
>https://github.com/OpenIndiana/oi-userland/pull/4999
>

Which clang do you use?
Maybe you should mention that people should not modify gcc headers in their
global zone.

Aurélien






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


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


Re: [oi-dev] pulseaudio issues

2019-04-02 Thread Aurélien Larcher
On Tue, Apr 2, 2019 at 4:19 PM Udo Grabowski (IMK) 
wrote:

> On 02/04/2019 15:57, Gary Mills wrote:
> > On Tue, Apr 02, 2019 at 10:54:25AM +, Alexander Pyhalov wrote:
> >
> >> If selection of device in mate-volume-control works for you, we can
> >> just make it honor AUDIODEV is it set.
> >
> > It may already do that, although perhaps not correctly.
> >
> >> Your patches make pulseaudio use mod_solaris module, and it doesn't
> >> provide interfaces necessary to select device in
> >> mate-volume-control. So we either fix mod_solaris to support these
> >> interfaces or fix our mod_oss patches to honor AUDIODEV.
> >
> > Yes, mod_solaris seemed most appropriate since illumos was derived
> > from Solaris.  Mod_oss seems to be for the Linux version of OSS.
> >
>
> On OI_151a versions this has always been OSS and it worked - so
> if pulse audio only delivers a "Linux version" of OSS this should
> be fixed. Please don't fall back to ancient mod_solaris, that was
> history already ten years ago...
>

Agreed.
I have seen patches to fix the multiple device issue in the pulseaudio OSS
module about two years ago, but cannot remember where.
So probably the solution is not to fiddle with configuration flags or cope
with obsolete interfaces.



> --
> 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
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>


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


Re: [oi-dev] Firefox 60esr

2018-11-09 Thread Aurélien Larcher
On Fri, Nov 9, 2018 at 8:46 PM Michal Nowak  wrote:

> Aurélien,
>
> does Firefox 60esr build from what's in your 'firefox60' branch?
>
> I pulled from your 'firefox60' branch but I am unable to build Firefox,
> it fails with: "NSModules are not ordered appropriately". More at:
> https://paste.ec/paste/u-QGkgcO#Jf182EbyHq3Zt5s8MU9VVNHp3daKhtM-+z1OSxDkIrN
>
> If I remove that check from firefox-60.3.0/toolkit/library/libxul.mk it
> fails with missing "Undefined symbol 'sendfile'":
> https://paste.ec/paste/Ov5E1DuC#s1uY-Msq9w7alg5xMgWPJLONv0kypS3yulQPjDxBh2b.
>
> When I fix it manually, it later hangs at:
>
> Executing
> /export/home/newman/ws/oi-userland/components/web/firefox/build/amd64/dist/bin/shlibsign
>
> -v -o ../../dist/firefox/libsoftokn3.chk -i
> ../../dist/firefox/libsoftokn3.so
> moduleSpec configdir='' certPrefix='' keyPrefix='' secmod=''
> flags=noCertDB, noModDB
>
> The process takes one whole core for an hour doing something. When I
> make SIGN_LIBS from firefox-60.3.0/toolkit/mozapps/installer/packager.py
> empty, it finally publishes, but the firefox process eventually dumps
> core (which is not that surprising for me reading your IRC posts :) ):
>

Yeah I did not push the patches for these issues as they are a bit
"piggy"...


>
> $ mdb core
> mdb: core file data for mapping at 22fbf7c39000 not saved: Bad address
> mdb: core file data for mapping at 22fbf7c59000 not saved: Bad address
> Loading modules: [ libc.so.1 libnvpair.so.1 libuutil.so.1 libavl.so.1
> ld.so.1 ]
>  > ::status
> debugging core file of firefox (64-bit) from lenovo
> file: /usr/lib/amd64/firefox/firefox
> initial argv: /usr/bin/firefox
> threading model: native threads
> status: process terminated by SIGSEGV (Segmentation Fault), pid=2975
> uid=101 code=-1
>  > $C
> fd7fffdfe730 libc.so.1`_lwp_kill+0xa()
> fd7fffdfe760 libc.so.1`raise+0x20(b)
> 000b
> libxul.so`_ZN13nsProfileLock18FatalSignalHandlerEiP7siginfoPv+0xff()
>
> I am bit more surprised that Firefox 62 from Joyent's binary pkgsrc
> dumps for me as well:
> https://paste.ec/paste/xdeCYjGD#rSuQOzMOl+QmumtxpSLR1LU6WzblzSV7uroLrrua2eE


It seems that there is an issue with loading the profile (32bit vs 64bit?).
If you mv the directory it should start but it is still shaky.

Also pkgsrc does not use some Solaris specific code, instead patches code
used by BSDs...
Due to the inconsistency of ifdefs (SOLARIS, OS_SOLARIS) there is a mixed
bag of code used...




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



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

Re: [oi-dev] Mate Schema error ?

2018-11-09 Thread Aurélien Larcher
On Fri, Nov 9, 2018 at 8:09 PM Michal Nowak  wrote:

> On 11/09/18 05:41 PM, Udo Grabowski (IMK) wrote:
> > On 09/11/2018 17:37, Aurélien Larcher wrote:
> >> Did you install from 2018.10?
> >
> > It's the current Hipster trunk as seen yesterday around Noon (UTC).
> >
> >
> >> I have installed a few testing images in the past two weeks and this
> >> issue does not occur.
> >> I'll try to check if there are differences.
> >>
> >> On 11/9/18, Udo Grabowski (IMK)  wrote:
> >>> On 09/11/2018 16:27, Aurélien Larcher wrote:
> >>>>
> >>>>
> >>>> On Fri, Nov 9, 2018 at 12:06 PM Udo Grabowski (IMK)
> >>>>  >>>> <mailto:udo.grabow...@kit.edu>> wrote:
> >>>>
> >>>> Hi, I noticed that the mouse right click menu is not available on
> >>>> MATE.
> >>> ...
> >>>
> >>
> >>
>
> Do I have it right that you actually login to MATE as a *root*? That's
> something I never tested.
>

Login as root should not be supported by default as root is a role.

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



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

Re: [oi-dev] Mate Schema error ?

2018-11-09 Thread Aurélien Larcher
Did you install from 2018.10?
I have installed a few testing images in the past two weeks and this
issue does not occur.
I'll try to check if there are differences.

On 11/9/18, Udo Grabowski (IMK)  wrote:
> On 09/11/2018 16:27, Aurélien Larcher wrote:
>>
>>
>> On Fri, Nov 9, 2018 at 12:06 PM Udo Grabowski (IMK)
>> > <mailto:udo.grabow...@kit.edu>> wrote:
>>
>> Hi, I noticed that the mouse right click menu is not available on
>> MATE.
>>
>>
>> Hi!
>> What you mean by "right click menu"?
>> I have not seen any regression in my environments so I am not sure what
>> you are
>> referring to.
>
> Right mouse button click on root background. Should open a little
> context menu, but does not in the default configuration.
>
> Mostly boils down to Caja not running at login (since it handles the
> desktop icons and this context menu), but when setting it as active
> startup application, it still doesn't read the correct switches which
> are seemingly stored in .config/{caja,dconf}.
>
> You always have to issue the dconf write command, and as soon as
> caja dies that setting is lost (or not read at next startup).
> And caja quits instead of going to the background when the little
> close icon in the upper right window corner is hit.
> So multiple problems combine here.
>
> When logging into gnome instead, nautilus is automatically started
> in the background, and doesn't simply quit when closing its window,
> and it remembers the last configuration settings.
>
> And this doesn't happen when converting as old Gnome2 user to mate,
> something is set there from gnome that a fresh mate user doesn't get
> by default.
>
> --
> 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
>
>


-- 
---
Praise the Caffeine embeddings

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

Re: [oi-dev] Mate Schema error ?

2018-11-09 Thread Aurélien Larcher
On Fri, Nov 9, 2018 at 12:06 PM Udo Grabowski (IMK) 
wrote:

> Hi, I noticed that the mouse right click menu is not available on
> MATE.


Hi!
What you mean by "right click menu"?
I have not seen any regression in my environments so I am not sure what you
are referring to.


> The necessary switch for this should be org.mate.desktop.background
> 'show-desktop-icons' = true. However, despite it is show in dconf
> under the org/mate/desktop/ schema, the name of this switch is
> shown and configurable only as org.mate.background. Possible ommission
> of the /desktop/ folder ? That would explain why the right mouse
> still doesn't work even when switching this (and the corresponding
> gnome/ entry) off and on again.
> --
> 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
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



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

[oi-dev] Font packaging

2018-11-06 Thread Aurélien Larcher
Hi,
I merged a few modifications to simplify font components, adapted from
solaris-userland (thanks for that!).

For an example of TrueType font you can look at

https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/fonts/google-droid/Makefile

In most case I boils down to specifying:

- COMPONENT_FONT_NAME = name of the font in the fmri and install path (if
different than COMPONENT_NAME)
- COMPONENT_FONT_SRC_DIR = relative path to the font directory within the
source tree
- COMPONENT_FONT_FILES  += *.ttf (add all files to copy to
usr/share/fonts)
- COMPONENT_FONTCONF_SRC_DIR =  relative path to the font configuration
directory within the source tree, set it to empty if none
- COMPONENT_FONTCONF_FILES = font configuration files, set it to empty if
none

Kind regards,

Aurélien

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

Re: [oi-dev] GCC 7.3.0-il-1

2018-11-01 Thread Aurélien Larcher
On Thu, Nov 1, 2018 at 9:45 AM Jean-Pierre 
wrote:

> Aurélien Larcher wrote:
> > Hello,
> > about 2.5 years ago I started playing with more recent versions of GCC:
> > the intent was to support illumos by providing a testing environment for
> > new compilers.
> > I added GCC 5.x in Aug 2016, GCC 6.x in Jan 2017, GCC 7.x in April 2017,
> > then GCC 8.x in Jan 2018.
> >
> > With the help of Rich Lowe illumos patches were rebased to allow
> > building illumos and userland wih the same compiler: GCC 5/6 in Feb 2017
> > , GCC 7 in April 2017, GCC 8 in Jan 2018.
> > Dates are a good way to measure that many things that happened since the
> > first stages.
> >
> > Thanks to Toomas who relentlessly fixed illumos-gate with gcc-7 we are
> > now able to build it (I have been running for almost a year
> > cherry-picking his patches on the go).
> >
> > Rich finally pushed GCC 7.3.0-il-1 as the new candidate for the default
> > illumos compiler:
> >
> > https://github.com/illumos/gcc/releases
> >
> > This is a great achievement, congratulations to Toomas, Rich, and
> > everybody involved.
>
> I will add you to my congratulation list.
>

Thanks!

>
> > A shadow compilaton with gcc-7 was added recently to illumos-gate to
> > identify possible issues introduced by RTIs.
> >
> > Our gcc-7 paclage will be updated soon with the il-1 patchset (same
> > patchset except one patch has been improved by John Levon): gcc
> > 7.3.0-OI-2 will become gcc 7.3.0-il-1.
>
> Are these patches to gcc to be pushed upstream ?
> (or are they only required for compiling kernel code ?)
>

They are unlikely to be upstreamed and essentially used for kernel code.
One patch for standard conformance (which similar fix was integrated by
Rainer Orth in gcc-8) and some minor build fixes as well.

>
> IOW how about building a cross-compiler for developing
> user level code ?
>

I have not looked into that... but I do not think the changes affect this.

>
> Jean-Pierre
>
> > We still provide testing build based on gcc-8 for userland, and gcc-7
> > for illumos-gate:
> >
> > https://pkg.openindiana.org/gcc-next/
> >
> > While illumos-gate does not build yet with gcc-8 the patchset has been
> > around for a while: looking forward to the next GCC 8.x.0-il.
> >
> > Kind regards,
> >
> > Aurélien
> >
> > --
> > ---
> > Praise the Caffeine embeddings
> >
> >
> > ___
> > oi-dev mailing list
> > oi-dev@openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev
> >
>
>
>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>


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

[oi-dev] GCC 7.3.0-il-1

2018-10-31 Thread Aurélien Larcher
Hello,
about 2.5 years ago I started playing with more recent versions of GCC: the
intent was to support illumos by providing a testing environment for new
compilers.
I added GCC 5.x in Aug 2016, GCC 6.x in Jan 2017, GCC 7.x in April 2017,
then GCC 8.x in Jan 2018.

With the help of Rich Lowe illumos patches were rebased to allow building
illumos and userland wih the same compiler: GCC 5/6 in Feb 2017 , GCC 7 in
April 2017, GCC 8 in Jan 2018.
Dates are a good way to measure that many things that happened since the
first stages.

Thanks to Toomas who relentlessly fixed illumos-gate with gcc-7 we are now
able to build it (I have been running for almost a year cherry-picking his
patches on the go).

Rich finally pushed GCC 7.3.0-il-1 as the new candidate for the default
illumos compiler:

https://github.com/illumos/gcc/releases

This is a great achievement, congratulations to Toomas, Rich, and everybody
involved.
A shadow compilaton with gcc-7 was added recently to illumos-gate to
identify possible issues introduced by RTIs.

Our gcc-7 paclage will be updated soon with the il-1 patchset (same
patchset except one patch has been improved by John Levon): gcc 7.3.0-OI-2
will become gcc 7.3.0-il-1.

We still provide testing build based on gcc-8 for userland, and gcc-7 for
illumos-gate:

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

While illumos-gate does not build yet with gcc-8 the patchset has been
around for a while: looking forward to the next GCC 8.x.0-il.

Kind regards,

Aurélien

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

Re: [oi-dev] Security patch for Xorg 19.x

2018-10-31 Thread Aurélien Larcher
On Wed, Oct 31, 2018 at 9:10 AM Udo Grabowski (IMK) 
wrote:

> On 30/10/2018 11:25, Peter Tribble wrote:
> >
> >
> > On Tue, Oct 30, 2018 at 10:13 AM Udo Grabowski (IMK) <
> udo.grabow...@kit.edu
> > > wrote:
> >
> > This Xorg patch should be immediately merged in Hipster:
> >
> >
> > It was merged and updated packages published last Thursday, by the looks
> of it:
> >
> > commit b694face8cd955399d90fae658d6a01fb1fa9c5b
> > Author: Aurelien Larcher  > >
> > Date:   Thu Oct 25 19:31:53 2018 +0200
> >
> > xorg-server: CVE-2018-14665
> >
> >
> >
> > <
> https://gitlab.freedesktop.org/xorg/xserver/commit/50c0cf885a6e91c0ea71fb49fa8f1b7c86fe330e
> >
> >
> > That check had been part of older Xorgs ,e.g., on oi_151a9.
> >
> > See the really nasty CVE-2018-14665:
> > 
> > --
> > ...
> > --
> > -Peter Tribble
> > http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
>
> Indeed, didn't find x11 because I was on the wrong branch
> 
> instead of
> 
>
> Security bugs like that completely destroy my approach of jumping
> from one 'stable' release to the next, so the only secure way is indeed
> a rolling release if you don't have enough manpower to maintain a
> cherry-picking 'stable' major-bugfix-only branch.
>

You can probably just unlock the version facet to allow update of xorg only
while keeping the rest of userland-incorporation in place.



> --
> 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
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



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

Re: [oi-dev] Security patch for Xorg 19.x

2018-10-30 Thread Aurélien Larcher
On Tue, Oct 30, 2018 at 11:26 AM Peter Tribble 
wrote:

>
>
> On Tue, Oct 30, 2018 at 10:13 AM Udo Grabowski (IMK) <
> udo.grabow...@kit.edu> wrote:
>
>> This Xorg patch should be immediately merged in Hipster:
>>
>
> It was merged and updated packages published last Thursday, by the looks
> of it:
>
> commit b694face8cd955399d90fae658d6a01fb1fa9c5b
> Author: Aurelien Larcher 
> Date:   Thu Oct 25 19:31:53 2018 +0200
>
> xorg-server: CVE-2018-14665
>

Indeed :)
I also posted on Twitter:
https://twitter.com/OpenIndiana/status/109789831430144

>
>
>
>> <
>> https://gitlab.freedesktop.org/xorg/xserver/commit/50c0cf885a6e91c0ea71fb49fa8f1b7c86fe330e
>> >
>>
>> That check had been part of older Xorgs ,e.g., on oi_151a9.
>>
>> See the really nasty CVE-2018-14665:
>> 
>> --
>> 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
>>
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> https://openindiana.org/mailman/listinfo/oi-dev
>
>
>
> --
> -Peter Tribble
> http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



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

Re: [oi-dev] Packages only in the main repository

2018-10-25 Thread Aurélien Larcher
On Wed, Oct 24, 2018 at 5:44 PM Alan Coopersmith <
alan.coopersm...@oracle.com> wrote:

> On 10/24/18 06:14 AM, Udo Grabowski (IMK) wrote:
> > On 24/10/2018 14:39, Aurélien Larcher wrote:
> > Motif is still needed for some applications, but isn't there OpenMotif ?
>
> Yes - but it's not binary compatible with the old Solaris Motif 1.2 or 2.1
> so you'll need to recompile the apps to use it.
>
> > libXaw is still needed, but again, freedesktop.org has a free
> alternative.
>
> Right - these are the X11R4 & X11R5 versions for backwards binary
> compatibility.
> X.Org currently ships libXaw7 upstream, which is in a different OI package.
>
> > CDE is dead, and people that used it should be, too (I feel sick...).
>
> Hey!  Just because we're old doesn't mean we're useless!
>
> > libowconfigoh my god, OpenWindows, olwm ?
>
> That was  a badly named Xsun configuration library - I have no idea why
> anything would still be using it.  We dropped it in Solaris 11.4 after
> modifying fbconfig (SPARC graphics config utility) to stop using it:
>
> https://github.com/oracle/solaris-xorg/commit/ecb865891b0685db5d
>
> > SUNWxwinc/plt are just Meta-incorporation packages for Xwindows
> > application groups; useful as such, they may be renamed and kept.
>
> They were a transition aid for old SVR4 packages that depended on
> the SVR4 SUNWxwplt & SUNWxwinc, which bundled all the X libraries
> and clients together before we split them into individual packages
> to match upstream.
>
> If you want to publish them, the sources are in:
>
> https://github.com/oracle/solaris-xorg/tree/1c94357064e1b34d3bcec7c43b60ba45ba3114e1/pkg/manifests
>
> (We also dropped them in Solaris 11.4.)
>

Alan, thank you for providing all this background information and pointers
to solaris-xorg.

Would you recommend still providing binaries for Motif and the old Athena
Widgets?

Kind regards,

Aurélien



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



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

Re: [oi-dev] prep failure in /oi-userland/components/developer/libtool

2018-10-24 Thread Aurélien Larcher
On Wed, Oct 24, 2018 at 5:36 PM Andreas Wacknitz  wrote:

> Am 24.10.18 um 12:52 schrieb Rich Reynolds:
>
> odd1@userlandbuild:/codebase/oi-userland/components/developer/libtool$
> gmake prep
> Makefile:106: warning: overriding recipe for target
> '/codebase/oi-userland/components/developer/libtool/libtool-1.5.22/.unpacked'
> /codebase/oi-userland/make-rules/prep-unpack.mk:75: warning: ignoring old
> recipe for target
> '/codebase/oi-userland/components/developer/libtool/libtool-1.5.22/.unpacked'
> /bin/rm -f -r
> /codebase/oi-userland/components/developer/libtool/libtool-2.4.6
> /usr/bin/env RUBY_VERSION=2.3 /codebase/oi-userland/tools/userland-unpack
> /codebase/oi-userland/archives/libtool-2.4.6.tar.gz
> /usr/bin/touch
> /codebase/oi-userland/components/developer/libtool/libtool-2.4.6/.unpacked
> /bin/rm -f -r
> /codebase/oi-userland/components/developer/libtool/libtool-1.5.22
> /codebase/oi-userland/tools/userland-unpack
> /codebase/oi-userland/archives/libtool-1.5.22.tar.gz
> /usr/bin/touch
> /codebase/oi-userland/components/developer/libtool/libtool-1.5.22/.unpacked
> /usr/gnu/bin/patch -d
> /codebase/oi-userland/components/developer/libtool/libtool-2.4.6 --strip=1
> --backup --version-control=numbered < patches/001-dlsearch.patch
> patching file m4/libtool.m4
> /usr/bin/touch
> /codebase/oi-userland/components/developer/libtool/libtool-2.4.6/.patched-001-dlsearch.patch
> /usr/bin/touch
> /codebase/oi-userland/components/developer/libtool/libtool-2.4.6/.patched
> /usr/bin/touch
> /codebase/oi-userland/components/developer/libtool/libtool-1.5.22/.prep
> (cd /codebase/oi-userland/components/developer/libtool/libtool-2.4.6 ;
> ./bootstrap --force)
> bootstrap: warning: Consider installing git-merge-changelog from gnulib.
> bootstrap: running: git clone --depth 365 'git://git.sv.gnu.org/gnulib'
> 'gnulib'
> Cloning into 'gnulib'...
> remote: Counting objects: 14469, done.
> remote: Compressing objects: 100% (8867/8867), done.
> remote: Total 14469 (delta 9438), reused 7733 (delta 5579)
> Receiving objects: 100% (14469/14469), 8.77 MiB | 809.00 KiB/s, done.
> Resolving deltas: 100% (9438/9438), done.
> bootstrap: running: git submodule init -- gnulib
> error: pathspec 'gnulib' did not match any file(s) known to git
> bootstrap: running: git submodule update -- gnulib
> error: pathspec 'gnulib' did not match any file(s) known to git
> bootstrap: running: gnulib/gnulib-tool --no-changelog --avoid=dummy
> --libtool --macro-prefix=GL --aux-dir=build-aux --m4-base=m4 --local-dir=gl
> --symlink --import announce-gen bootstrap...
> gnulib/gnulib-tool: *** minimum supported autoconf version is 2.63. Try
> adding AC_PREREQ([2.63]) to your configure.ac.
> gnulib/gnulib-tool: *** Stop.
> gmake: *** [/codebase/oi-userland/make-rules/prep.mk:41:
> /codebase/oi-userland/components/developer/libtool/libtool-2.4.6/.prep]
> Error 1
>
> simple typo
>
> diff configure.ac configure.ac.orig
> 27c27
> < AC_PREREQ([2.63])
> ---
> > AC_PREREQ(2.62)
>
> Why did that used to work before? libtool-2.4.6 ist more than three years
> old.
> Do you want to create a PR for this?
>

Because it has been broken 41 hours ago :)

http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=844f63f9576ebb74fde62e5017bf838c69db22c4



>
> Regards,
> Andreas
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



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

[oi-dev] Packages only in the main repository

2018-10-24 Thread Aurélien Larcher
Hi,
this list contains packages installed on my system that cannot be published
from oi-userland:

compatibility/packages/SUNWxwinc
compatibility/packages/SUNWxwplt
consolidation/cde/cde-incorporation
consolidation/dbtg/dbtg-incorporation
consolidation/jdmk/jdmk-incorporation
consolidation/man/man-incorporation
developer/macro/cpp
driver/network/ce
library/desktop/gtk1
library/glib1
library/medialib
library/motif
system/font/truetype/arphic-uming
system/font/truetype/hanyang-ko-core
system/font/truetype/ipafont
system/font/truetype/lohit
system/font/xorg/iso8859-1
system/font/xorg/xorg-core
system/input-method/library/libanthy
system/input-method/library/libchewing
system/input-method/library/libhangul
system/install/locale
system/library/c++/sunpro
system/library/iconv/extra
system/library/iconv/unicode
system/library/iconv/utf-8
system/library/iconv/utf-8/manual
system/library/iconv/xsh4/latin
system/manual/locale/ca
system/manual/locale/ja
system/osnet/locale/fr
system/osnet/locale/ja
system/xvm/xvmstore
text/auto_ef
text/doctools/ja
x11/compatibility/links-svid
x11/library/dps
x11/library/libowconfig
x11/library/toolkit/libxaw4
x11/library/toolkit/libxaw5
x11/network/rstart

The question is: what can we deprecate?

As usual I can deal with x11/ and I know that iconv will be a pain...

Kind regards,

Aurélien

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

Re: [oi-dev] Help with 2018.10 release notes

2018-10-22 Thread Aurélien Larcher
On Mon, Oct 22, 2018 at 7:49 PM ken mays via oi-dev 
wrote:

> Michael,
>
> 1. illumos refresh - any known MAJOR issues with current (>=2018/10/22)?
> 2. Spacing issue in page: "Pidgin was updated(_)to 2.13.0."
> 3. Can decide to mention about Firefox ESR 60.0.2 exclusion. (NO time for
> deadline, etc...).
>

Yes, could mention that Firefox, Xorg, and VLC will be updated after the
snapshot.
No time to push them given required testing.

We could also list the continued migration to 64-bit userland and the
addition of Jenkins in the repo.


>
> 4. Any known installation issues and workarounds?
>

ACPI hang.


> 5. Any known issues on AMD ThreadRipper/Ryzen installs?
>
>

> ~K
>

> On Monday, October 22, 2018, 12:46:20 AM PDT, Michal Nowak <
> mno...@startmail.com> wrote:
>
>
> Hi,
>
> I drafted 2018.10 release notes at
> https://wiki.openindiana.org/oi/2018.10+Release+notes. Please join me in
> adding what you feel should be mentioned in the release notes of the
> upcoming 2018.10 snapshot.
>
> Sofar I added entries of "XXX updated to version ###" nature. I
> obviously tend to add things I worked on, so don't be shy and add what
> you worked on during last 6 months.
>
> Though, feel free to remove what you don't find significant enough, fix
> errors etc, merge entries.
>
> I especially miss updates in following sections: Nodejs, X-stack,
> toolchain, illumos, oi-userland build.
>
> This link shows what got merged since April 27 (2018.04 snapshot):
>
>
> https://github.com/OpenIndiana/oi-userland/pulls?page=17=is%3Apr+merged%3A%3E%3D2018-04-27=%E2%9C%93
>
> If you feel the release notes wiki page should be in "contributors-only
> mode", hidden for the public, please make it so (can't do it on my own).
>
> Thanks!
> Michal
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



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

[oi-dev] [HEADS-UP] VLC upgrades and cache regeneration.

2018-10-22 Thread Aurélien Larcher
Hi,
VLC will be first updated to a 64-bit binary then later upgraded to 3.x
In case you encounter problems after upgrade the local plugin cache may
need to be rebuilt.
There is a known issue causing plugins to not load properly due to a
failure in cache regeneration.
If that happens, run:

sudo /usr/lib/amd64/vlc/vlc-cache-gen

Kind regards,

Aurélien

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

[oi-dev] [HEADS-UP] Packages lame and twolame migrated to userland from 2018-10-23.

2018-10-22 Thread Aurélien Larcher
Hi,
since software patents have expired for MP3 packages lame and twolame have
now been migrated to userland.
Therefore, the upgrade to Gstreamer 1.14.4 tonight will get
gst-plugins-good to include support for MP3.
In case you encounter any issue with the update, you should set the
encumbered publisher to non-sticky to allow cross-publisher update:

pfexec pkg set-publisher --non-sticky hipster-encumbered

Kind regards,

Aurélien

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

Re: [oi-dev] Whitespace in Makefiles in oi-userland keep causing Problems

2018-10-22 Thread Aurélien Larcher
On Mon, Oct 1, 2018 at 12:41 PM Joerg Schilling <
joerg.schill...@fokus.fraunhofer.de> wrote:

> Till Wegmüller  wrote:
>
> > I managed to get it Working by hardcoding every Value with a Whitespace
> > inside it in the Package manifest.
> >
> > Looks like the problem seems to be the way gmake passes Variables to
> > pkgmogrify. It usualy does so by specifying -D $VARIABLE on the command
> > line. That seems not to be working consistently.
>
> Well, it is obvious that you need double quotes to make this work
> correctly, in
> other words: you did not hit onne of the problems that are caused by
> whitespace
> handling in gmake.
>

FYI tracked down to an issue in pkg for the generation of intermediate
manifests.


>
> Jörg
>
> --
>  EMail:jo...@schily.net(home) Jörg Schilling D-13353
> Berlin
> joerg.schill...@fokus.fraunhofer.de (work) Blog:
> http://schily.blogspot.com/
>  URL: http://cdrecord.org/private/
> http://sf.net/projects/schilytools/files/'
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>


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

Re: [oi-dev] mate-system-monitor 1.20.1 dumps core

2018-10-14 Thread Aurélien Larcher
did you updated everything to the latest hipster (including MATE themes,
> Nimbus, and GTK+ 3.24.1)?
>
Yes everything is updated to latest:

phainos> LANG=C pkg info gtk3
 Name: library/desktop/gtk3
  Summary: GTK+ - GIMP Toolkit Library for creation of graphical
user
   interfaces
 Category: Desktop (GNOME)/Libraries
State: Installed
Publisher: userland
  Version: 3.24.1
   Branch: 2018.0.0.0
   Packaging Date: Sun Oct 14 06:03:10 2018
Last Install Time: Sun Oct 14 14:47:33 2018
 Size: 87.19 MB
 FMRI: pkg://userland/library/desktop/gtk3@3.24.1-2018.0.0.0
:20181014T060310Z
  Project URL: https://www.gtk.org/
   Source URL:
http://ftp.gnome.org/pub/GNOME/sources/gtk+/3.24/gtk+-3.24.1.tar.xz


> (gdb) bt

> > Python Exception  long too big to
> convert:
> > Python Exception  long too big to
> convert:
> > Python Exception  long too big to
> convert:
> > Python Exception  long too big to
> convert:
>
> I guess this is a GDB pretty-printer error?
>
> > #0  0x in _free_unlocked ()#1  0x in
> > free ()#2  0x in
> >
> Glib::Container_Helpers::ArrayKeeper
>
> >  >::~ArrayKeeper() ()#3  0x in
> > Gtk::IconTheme::set_search_path(std::vector > std::allocator > const&) [clone .cold.74] ()#4
> > 0x004445e9 in procman::IconThemeWrapper::load_icon(Glib::ustring
> > const&, int, Gtk::IconLookupFlags) const ()
> > #5  0x0042e4cc in PrettyTable::get_icon_from_theme(ProcInfo
> > const&) ()
> > #6  0x0042efdf in PrettyTable::set_icon(ProcInfo&) ()
>
> Do you use some custom pre-MATE 1.20 theme? Can you try with some stock
> MATE 1.20 or Nimbus theme?
>

I use stock Nimbus theme.


>
> Is there some relevant error output from mate-system-monitor other than
> deprecation warnings wrt gtk-widgets.css?
>

Nothing aside from deprecations in the css.


>
> Michal
>
> > #7  0x00429e33 in insert_info_to_tree(ProcInfo*, ProcData*,
> > bool) [clone .constprop.206] ()
> > #8  0x0042c448 in proctable_update_list(ProcData*) ()
> > #9  0x0042d1fa in proctable_update(ProcData*) ()
> > #10 0x00425d88 in cb_switch_page(_GtkNotebook*, _GtkWidget*,
> > int, void*) ()
> > #14 0x in  > [GtkNotebook]> (instance=, signal_id=,
> > detail=)
> >  at gsignal.c:3447
> >  #11 0x in g_closure_invoke (closure=0x89cb60,
> > return_value=0x0, n_param_values=3, param_values=0xfd7fffdfee30,
> > invocation_hint=0xfd7fffdfedd0) at gclosure.c:806
> >  #12 0x in signal_emit_unlocked_R
> > (node=node@entry=0x4e43f0, detail=detail@entry=0,
> > instance=instance@entry=0x77a240,
> > emission_return=emission_return@entry=0x0,
> > instance_and_params=instance_and_params@entry=0xfd7fffdf---Type
> >  to continue, or q  to quit---
> > ee30) at gsignal.c:3635
> >  #13 0x in g_signal_emit_valist (instance= > out>, signal_id=, detail=,
> > var_args=var_args@entry=0xfd7fffdfefe8) at gsignal.c:3391
> > Python Exception  long too big to
> convert:
> > Python Exception  long too big to
> convert:
> > #15 0x in gtk_notebook_button_press ()#16
> > 0x in _gtk_marshal_BOOLEAN__BOXEDv ()#17
> > 0x in _g_closure_invoke_va (closure=0x468950,
> > return_value=0xfd7fffdff2a0, instance=0x77a240,
> > args=0xfd7fffdff398, n_params=1, param_types=0x49a2b0) at
> gclosure.c:869
> > #18 0x in g_signal_emit_valist (instance=0x77a240,
> > signal_id=, detail=,
> > var_args=var_args@entry=0xfd7fffdff398) at gsignal.c:3300
> > #19 0x in g_signal_emit (instance=,
> > signal_id=, detail=) at gsignal.c:3447
> > Python Exception  long too big to
> convert:
> > Python Exception  long too big to
> convert:
> > Python Exception  long too big to
> convert:
> > Python Exception  long too big to
> convert:
> > Python Exception  long too big to
> convert:
> > #20 0x in gtk_widget_event_internal ()#21
> > 0x in propagate_event ()#22 0x in
> > gtk_main_do_event ()#23 0x in _gdk_event_emit ()#24
> > 0x in gdk_event_source_dispatch ()#25 0x
> > in g_main_context_dispatch (context=0x4b79e0)
> >  at gmain.c:3177
> > #26 0x in g_main_context_dispatch
> > (context=context@entry=0x4b79e0) at gmain.c:3830
> > #27 0x in g_main_context_iterate (context=0x4b79e0,
> > block=block@entry=1, dispatch=dispatch@entry=1, self=)
> at
> > gmain.c:3903
> > #28 0x in g_main_loop_run (loop=0x975f70) at gmain.c:4099
> > ---Type  to continue, or q  to quit---
> > Python Exception  long too big to
> convert:
> > #29 0x in gtk_main ()#30 0x00422f16 in main ()
> >
> > --
> > ---
> > Praise the Caffeine embeddings
> >
> >
> > 

[oi-dev] mate-system-monitor 1.20.1 dumps core

2018-10-14 Thread Aurélien Larcher
Hi,
clicking on the Processes tab crashes mate-system-monitor, see below.
So far the experience is overall very positive with MATE 1.20.
Kind regards,

Aurélien

(gdb) bt
Python Exception  long too big to convert:
Python Exception  long too big to convert:
Python Exception  long too big to convert:
Python Exception  long too big to convert:
#0  0x in _free_unlocked ()#1  0x in free
()#2  0x in
Glib::Container_Helpers::ArrayKeeper
>::~ArrayKeeper() ()#3  0x in
Gtk::IconTheme::set_search_path(std::vector > const&) [clone .cold.74] ()#4
0x004445e9 in procman::IconThemeWrapper::load_icon(Glib::ustring
const&, int, Gtk::IconLookupFlags) const ()
#5  0x0042e4cc in PrettyTable::get_icon_from_theme(ProcInfo const&)
()
#6  0x0042efdf in PrettyTable::set_icon(ProcInfo&) ()
#7  0x00429e33 in insert_info_to_tree(ProcInfo*, ProcData*, bool)
[clone .constprop.206] ()
#8  0x0042c448 in proctable_update_list(ProcData*) ()
#9  0x0042d1fa in proctable_update(ProcData*) ()
#10 0x00425d88 in cb_switch_page(_GtkNotebook*, _GtkWidget*, int,
void*) ()
#14 0x in  (instance=, signal_id=,
detail=)
at gsignal.c:3447
#11 0x in g_closure_invoke (closure=0x89cb60,
return_value=0x0, n_param_values=3, param_values=0xfd7fffdfee30,
invocation_hint=0xfd7fffdfedd0) at gclosure.c:806
#12 0x in signal_emit_unlocked_R (node=node@entry=0x4e43f0,
detail=detail@entry=0, instance=instance@entry=0x77a240,
emission_return=emission_return@entry=0x0,
instance_and_params=instance_and_params@entry=0xfd7fffdf---Type
 to continue, or q  to quit---
ee30) at gsignal.c:3635
#13 0x in g_signal_emit_valist (instance=, signal_id=, detail=,
var_args=var_args@entry=0xfd7fffdfefe8) at gsignal.c:3391
Python Exception  long too big to convert:
Python Exception  long too big to convert:
#15 0x in gtk_notebook_button_press ()#16
0x in _gtk_marshal_BOOLEAN__BOXEDv ()#17 0x
in _g_closure_invoke_va (closure=0x468950, return_value=0xfd7fffdff2a0,
instance=0x77a240, args=0xfd7fffdff398, n_params=1,
param_types=0x49a2b0) at gclosure.c:869
#18 0x in g_signal_emit_valist (instance=0x77a240,
signal_id=, detail=,
var_args=var_args@entry=0xfd7fffdff398)
at gsignal.c:3300
#19 0x in g_signal_emit (instance=,
signal_id=, detail=) at gsignal.c:3447
Python Exception  long too big to convert:
Python Exception  long too big to convert:
Python Exception  long too big to convert:
Python Exception  long too big to convert:
Python Exception  long too big to convert:
#20 0x in gtk_widget_event_internal ()#21
0x in propagate_event ()#22 0x in
gtk_main_do_event ()#23 0x in _gdk_event_emit ()#24
0x in gdk_event_source_dispatch ()#25 0x in
g_main_context_dispatch (context=0x4b79e0)
at gmain.c:3177
#26 0x in g_main_context_dispatch
(context=context@entry=0x4b79e0)
at gmain.c:3830
#27 0x in g_main_context_iterate (context=0x4b79e0,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3903
#28 0x in g_main_loop_run (loop=0x975f70) at gmain.c:4099
---Type  to continue, or q  to quit---
Python Exception  long too big to convert:
#29 0x in gtk_main ()#30 0x00422f16 in main ()

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

Re: [oi-dev] 2018.10 targets

2018-10-02 Thread Aurélien Larcher
On Tue, Oct 2, 2018 at 7:03 PM Michal Nowak  wrote:

> On 09/29/18 06:19 PM, Aurélien Larcher wrote:
> >
> >
> > On Sat, Sep 29, 2018 at 9:01 AM Michal Nowak  > <mailto:mno...@startmail.com>> wrote:
> >
> > On 09/28/18 10:41 AM, Alexander Pyhalov via oi-dev wrote:
> >  > Hi, folks.
> >  >
> >  > We are approaching October. While I have limited time now, I want
> to
> >  > coordinate priorities and targets, what should we do till end of
> >  > October (and due to personal reasons, I'd better announce snapshot
> >  > till 20 October or earlier or allow someone else to do this).
> >  >
> >  > We have several regressions and problems, which would be good to
> >  > fix.
> >  >
> >  > 1) Virtualbox failure after FPU changes
> >  > https://www.illumos.org/issues/9761 ,
> >  > https://www.virtualbox.org/ticket/17947 is a serious one, but I'm
> >  > afraid I lack skills to fix it in reasonable time. The stack trace
> >  > itself doesn't seem related to illumos-gate changes, but likely it
> >  > is. In KVM Joyent fixed this using new hma_fpu_* API, but
> Virtualbox
> >  > structures to store VM registers differ and from brief overlook it
> >  > has several asm functions to store/restore Host/Base registers
> state.
> >  > So far I don't have an idea how convert one to another. So, this
> >  > likely will be broken in 2018.10 unless someone skillful dig into
> >  > this.
> >  >
> >  > 2) sbcl issues - threaded sbcl can not be built after KPTI
> changes,
> >  > it fails FLOCK and posix tests. Needs investigation. It's a
> serious
> >  > issue, because threaded sbcl is needed to build pgloader.
> >  >
> >  > 3) Our Mate is a bit old, but newer Mate requires updated GTK3 .
> >  > Updated GTK3 IIRC has dropped support for theme engines, and so
> our
> >  > Nimbus theme based on unico engine doesn't work. Also I've heard
> >  > there were issues with new mate-terminal. Michal, do you have some
> >  > comments here?
> >
> > I run MATE 1.20 as seen in the PR and it works fine but:
> >
> > (1) Nimbus theme. I stick to "Traditional" theme.
> >
> > (2) Pluma text editor's text area blinks annoyingly. Might be an
> > Intel-only issue. Upstream issue reported.
> >
> > (3) MATE Terminal requires new vte library which does not work for
> us.
> >   From my investigation I noticed that some #ifdef __sun were removed
> > from newer vte. Also I haven't seen new vte for non-Linux OS (pkgsrc,
> > BSDs, ...).
> >
> > I don't think I am able to do anything about those.
> >
> >
> > Which version does pkgsrc deliver? J. Perkin seems to have worked on
> > MATE 1.20.
>
> Thanks for pointing that out, Aurélien! Indeed Jonathan ported it to
> __sun: https://github.com/NetBSD/pkgsrc/tree/trunk/x11/vte3. I'll have a
> look at it.
>
> >
> >
> >  >
> >  > 4) As for new features, I really want to see KVM zones, perhaps,
> I'll
> >  > dig into this shortly.
> >  >
> >  > Does somebody have another targets/comments?
> >
> > I will work on openQA tests for them to be in shape for the snapshot
> > and
> > test the images once test-snapshot is available.
> >
> > Also I had some progress with Meson but can't promise this.
> >
> >
> > I packaged Meson last year but this is a mess...
> > Need to implement the specificities of illumos systems all over again...
> > and the way it is structures looks like the usual entangled "if(totoOS)
> > {} else if (babarOS) else if (fooOS) {} etc" all over the place.
> > First thing back then was to notice that GCC => GNU ld in their rules...
>
> I didn't get even that far, but it's noticeable from OS/HW detection
> that Meson has Linux in mind.
>

I am not sure I still have that work from last year... I am not really
motivated in reinventing the wheel unless it is necessary... :S


>
> Michal
>
> >
> >
> > Michal
> >
> >  >
> >  > Please, avoid turning this topic in bike-shedding, I want to hear
> OI
> >  > developers in a way "I ll take item #N" or "I expect to finish
> >  > feature A before snapshot", not "please, also fix this and that".
> >  >
> >

Re: [oi-dev] 2018.10 targets

2018-09-29 Thread Aurélien Larcher
On Sat, Sep 29, 2018 at 9:01 AM Michal Nowak  wrote:

> On 09/28/18 10:41 AM, Alexander Pyhalov via oi-dev wrote:
> > Hi, folks.
> >
> > We are approaching October. While I have limited time now, I want to
> > coordinate priorities and targets, what should we do till end of
> > October (and due to personal reasons, I'd better announce snapshot
> > till 20 October or earlier or allow someone else to do this).
> >
> > We have several regressions and problems, which would be good to
> > fix.
> >
> > 1) Virtualbox failure after FPU changes
> > https://www.illumos.org/issues/9761 ,
> > https://www.virtualbox.org/ticket/17947 is a serious one, but I'm
> > afraid I lack skills to fix it in reasonable time. The stack trace
> > itself doesn't seem related to illumos-gate changes, but likely it
> > is. In KVM Joyent fixed this using new hma_fpu_* API, but Virtualbox
> > structures to store VM registers differ and from brief overlook it
> > has several asm functions to store/restore Host/Base registers state.
> > So far I don't have an idea how convert one to another. So, this
> > likely will be broken in 2018.10 unless someone skillful dig into
> > this.
> >
> > 2) sbcl issues - threaded sbcl can not be built after KPTI changes,
> > it fails FLOCK and posix tests. Needs investigation. It's a serious
> > issue, because threaded sbcl is needed to build pgloader.
> >
> > 3) Our Mate is a bit old, but newer Mate requires updated GTK3 .
> > Updated GTK3 IIRC has dropped support for theme engines, and so our
> > Nimbus theme based on unico engine doesn't work. Also I've heard
> > there were issues with new mate-terminal. Michal, do you have some
> > comments here?
>
> I run MATE 1.20 as seen in the PR and it works fine but:
>
> (1) Nimbus theme. I stick to "Traditional" theme.
>
> (2) Pluma text editor's text area blinks annoyingly. Might be an
> Intel-only issue. Upstream issue reported.
>
> (3) MATE Terminal requires new vte library which does not work for us.
>  From my investigation I noticed that some #ifdef __sun were removed
> from newer vte. Also I haven't seen new vte for non-Linux OS (pkgsrc,
> BSDs, ...).
>
> I don't think I am able to do anything about those.
>

Which version does pkgsrc deliver? J. Perkin seems to have worked on MATE
1.20.


>
> >
> > 4) As for new features, I really want to see KVM zones, perhaps, I'll
> > dig into this shortly.
> >
> > Does somebody have another targets/comments?
>
> I will work on openQA tests for them to be in shape for the snapshot and
> test the images once test-snapshot is available.
>
> Also I had some progress with Meson but can't promise this.
>

I packaged Meson last year but this is a mess...
Need to implement the specificities of illumos systems all over again...
and the way it is structures looks like the usual entangled "if(totoOS) {}
else if (babarOS) else if (fooOS) {} etc" all over the place.
First thing back then was to notice that GCC => GNU ld in their rules...


>
> Michal
>
> >
> > Please, avoid turning this topic in bike-shedding, I want to hear OI
> > developers in a way "I ll take item #N" or "I expect to finish
> > feature A before snapshot", not "please, also fix this and that".
> >
> > Best regards, Alexander Pyhalov, system administrator of Southern
> > Federal University IT department
> >
> >
> >
> > ___ oi-dev mailing list
> > oi-dev@openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev
> >
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>


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

Re: [oi-dev] Git dependency to

2018-09-28 Thread Aurélien Larcher
On Fri, Sep 28, 2018 at 1:50 PM Alexander Pyhalov via oi-dev <
oi-dev@openindiana.org> wrote:

> Hi.
> It's part of g11n. These are illumos-specific iconv libraries for
> converting files between characterr sets. Something should go very wrong
> for git to get dependency on them.
>

Thanks for the hint Alexander.
Until the cause is found I will ignore the git component.

BTW, where are old g11n repositories now that hg.openindiana.org has gone?




>
> С уважением,
> Александр Пыхалов,
> программист отдела телекоммуникационной инфраструктуры
> управления информационно-коммуникационной инфраструктуры ЮФУ
>
>
> ________
> От: Aurélien Larcher 
> Отправлено: 28 сентября 2018 г. 14:00:19
> Кому: OpenIndiana Developer mailing list
> Тема: [oi-dev] Git dependency to
>
> Hi,
> latest git component failed to publish in the gcc-8 build zone since it
> depends on /system/library/iconv/extra.
>
> A quick check shows that
>
> system/library/iconv/extra@0.5.11,5.11-2013.0.0.0:20151027T075807Z<
> http://pkg.openindiana.org/hipster/info/0/system%2Flibrary%2Ficonv%2Fextra%400.5.11%2C5.11-2013.0.0.0%3A20151027T075807Z
> >
>
> is one of those package that have not been migrated to oi-userland.
>
> Any idea where it is located or whether this dependency is actually
> required at all?
> The only missing file in the workspace is
> '/usr/share/man/man1/git-commit-graph.1'
>
> Aurélien
> --
> ---
> Praise the Caffeine embeddings
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



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

Re: [oi-dev] Whitespace in Makefiles in oi-userland keep causing Problems

2018-09-28 Thread Aurélien Larcher
On Fri, Sep 28, 2018 at 1:48 PM Till Wegmüller  wrote:

> I managed to get it Working by hardcoding every Value with a Whitespace
> inside it in the Package manifest.
>
> Looks like the problem seems to be the way gmake passes Variables to
> pkgmogrify. It usualy does so by specifying -D $VARIABLE on the command
> line. That seems not to be working consistently.
>
> So lesson from that seems to be that we need to hardcode values with
> whitespace into the manifest.
>
> Thanks for the pointers.
>

I am not sure this is the case, there are other instances of values with
whitespaces.
The way values are quoted should be influencial depending on how the recipe
passes them to pkgmogrify.
There is a similar problem with non-escaping dots in PKG_MACROS.



>
> Greetings
> Till
>
> On 09/28/18 12:23 PM, Joerg Schilling wrote:
> > Till Wegmüller  wrote:
> >
> >> A Makefile like so:
> >>
> >> 
> >> COMPONENT_NAME=salt
> >> COMPONENT_VERSION=2018.3.2
> >> COMPONENT_SUMMARY='Portable, distributed, remote execution and
> >> configuration management system'
> >> COMPONENT_PROJECT_URL=http://saltstack.com
> >> COMPONENT_FMRI=system/management/$(COMPONENT_NAME)
> >> COMPONENT_CLASSIFICATION='System/Administration and Configuration'
> >> 
> >>
> >> Something like COMPONENT_CLASSIFICATION would break pkgmogrify with:
> >> pkgmogrify: File
> >>
> /export/home/toast/workspace/openindiana/userland/components/python/salt/build/manifest-i386-salt-27.p5m
> >> line 18: Malformed action at position: 90: whitespace in key:
> >> set name=info.classification
> >> value=org.opensolaris.category.2008:System/Administration and
> Configuration
> >
> > It would help if you could investigate and report on what happenes that
> causes
> > your problem and whether you are unhappy with "make" or with the called
> > program...
> >
> > BTW: do you use "gmake" or make?
> > gmake is known to have a buggy white space handling.
> >
> > Jörg
> >
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



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

[oi-dev] Git dependency to

2018-09-28 Thread Aurélien Larcher
Hi,
latest git component failed to publish in the gcc-8 build zone since it
depends on /system/library/iconv/extra.

A quick check shows that

system/library/iconv/extra@0.5.11,5.11-2013.0.0.0:20151027T075807Z


is one of those package that have not been migrated to oi-userland.

Any idea where it is located or whether this dependency is actually
required at all?
The only missing file in the workspace is
'/usr/share/man/man1/git-commit-graph.1'

Aurélien
-- 
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] 2018.10 targets

2018-09-28 Thread Aurélien Larcher
On Fri, Sep 28, 2018 at 10:41 AM Alexander Pyhalov via oi-dev <
oi-dev@openindiana.org> wrote:

> Hi, folks.
>
> We are approaching October.
> While I have limited time now, I want to coordinate priorities and
> targets, what should we do till end of October (and due to personal
> reasons, I'd better announce snapshot till 20 October or earlier or allow
> someone else to do this).
>
> We have several regressions and problems, which would be good to fix.
>
> 1) Virtualbox failure after FPU changes
> https://www.illumos.org/issues/9761 ,
> https://www.virtualbox.org/ticket/17947 is a serious one, but I'm afraid
> I lack skills to fix it in reasonable time. The stack trace itself doesn't
> seem related to illumos-gate changes, but likely it is. In KVM Joyent fixed
> this using new hma_fpu_* API, but Virtualbox structures to store VM
> registers differ and from brief overlook it has several asm functions to
> store/restore Host/Base registers state. So far I don't have an idea how
> convert one to another. So, this likely will be broken in 2018.10 unless
> someone skillful dig into this.
>
> 2) sbcl issues - threaded sbcl can not be built after KPTI changes, it
> fails FLOCK and posix tests. Needs investigation. It's a serious issue,
> because threaded sbcl is needed to build pgloader.
>
> 3) Our Mate is a bit old, but newer Mate requires updated GTK3 .  Updated
> GTK3 IIRC has dropped support for theme engines, and so our Nimbus theme
> based on unico engine doesn't work. Also I've heard there were issues with
> new mate-terminal.
> Michal, do you have some comments here?
>
> 4) As for new features, I really want to see KVM zones, perhaps, I'll dig
> into this shortly.
>
> Does somebody have another targets/comments?
>
> Please, avoid turning this topic in bike-shedding, I want to hear OI
> developers in a way "I ll take item #N" or "I expect to finish feature A
> before snapshot", not "please, also fix this and that".
>

Hi Alexander,
I'll be busy as well and my skills are not up to tasks #1 or #2... the only
tracks I can pursue for now are:
1) fixing pkg and gfx-drm components so that we can migrate userland to
gcc-8 before or after the snapshot.
2) pushing Firefox 60esr
3) updating Xorg to latest
4) fixing openmpi which has been broken before summer

If I have time to fix audacity then we can also update ffmpeg and vlc.
I had some fixes for drm/i915 but my Intel box died 4 months ago so this is
on hold until I can replace it.
Kind regards,

Aurélien


>
> Best regards,
> Alexander Pyhalov,
> system administrator of Southern Federal University IT department
>
>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>


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

[oi-dev] Rust 1.29

2018-09-20 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] MATE 1.18: updates for Sept 2018 refresh

2018-09-13 Thread Aurélien Larcher
On Wed, Sep 12, 2018 at 11:50 PM, ken mays via oi-dev <
oi-dev@openindiana.org> wrote:

> Hi,
>
> Ref: https://github.com/OpenIndiana/oi-userland/pull/4433
>
> I've submitted this PR for the latest updates to OI MATE 1.18.
>

Modulo the two changes that I suggested and that you have now fixed, all
the components published and work as expected.

Thank you

Aurélien

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



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

Re: [oi-dev] Rust 1.28 testing package

2018-09-13 Thread Aurélien Larcher
On Thu, Sep 13, 2018 at 9:18 AM, Michal Nowak  wrote:

> On 09/12/18 08:42 PM, Till Wegmüller wrote:
>
>> Hi Aurelian
>>
>> Nice work.
>>
>> I tested a few Rust programs acros github trending at random to see how
>> we are with workflow compliance.
>>
>> cargo seems to work and can be used to install programs.
>> Tested:
>> https://github.com/sharkdp/bat simple cat clone: Does not work the
>> termios library does not know about us.
>>
>> https://github.com/rust-lang-nursery/rustup.rs/ Seems to be very
>> unstable... They recomend that a packager pckages it. We maybe should
>> aswell seing that many rust utilities seem to require their very
>> specific version of rust.. Including firefox.
>>
>> https://github.com/uutils/coreutils Does not seem to like that our libc
>> has no ENOATTR
>>
>
> I guess https://github.com/Stebalien/xattr/issues/18 is what you see?
> There's workaround for this in xattr v0.2.2, but I thought is fixed by
> following rust's libc patches which define ENOATTR as ENODATA:
>
> * src_vendor_libc_src_unix_solaris_mod.rs.patch
> * src_liblibc_src_unix_solaris_mod.rs.patch
>
> But yes along the way there are another platform-specific problems like:
>
> error[E0432]: unresolved import `self::libc::TIOCGWINSZ`
>  --> /export/home/newman/.cargo/registry/src/github.com-1ecc6299d
> b9ec823/termsize-0.1.5/src/nix.rs:4:33
>   |
> 4 | use self::libc::{STDOUT_FILENO, TIOCGWINSZ, c_ushort};
>   | ^^ no `TIOCGWINSZ` in the root
>

Thank you both for testing the package :)

We should probably get in touch with Rust developers to fix the build issue
when rustc is installed and see what it would take to get some level of CI
up and running.

Then we can look at Firefox 60esr...



>
> Michal
>
>
>
>> All in all i would say the compiler works it was saying that many
>> packages were compiling without errors. But the work has just begun.
>> There seems to be very much platform specific code in rust libraries in
>> the wild.
>>
>> Keep up the good work
>> Greetings
>> Till
>>
>> On 09/12/18 02:30 PM, Aurélien Larcher wrote:
>>
>>> 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:2
>>> 0180912T121658Z
>>>
>>> The repository is built with gcc-8 so a new BE and a good bandwidth are
>>> required.
>>>
>>> --
>>> ---
>>> Praise the Caffeine embeddings
>>>
>>>
>>> ___
>>> oi-dev mailing list
>>> oi-dev@openindiana.org
>>> https://openindiana.org/mailman/listinfo/oi-dev
>>>
>>>
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> https://openindiana.org/mailman/listinfo/oi-dev
>>
>>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



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

[oi-dev] Rust 1.28 testing package

2018-09-12 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Rust in userland?

2018-08-23 Thread Aurélien Larcher
On Thu, Aug 23, 2018 at 8:21 AM, Michal Nowak  wrote:

> On 08/21/18 11:16 PM, Aurélien Larcher wrote:
>
>>
>>
>> On Tue, Aug 21, 2018 at 11:10 PM, Michal Nowak > <mailto:mno...@startmail.com>> wrote:
>>
>> On 08/16/18 07:31 PM, Aurélien Larcher wrote:
>>
>>
>>
>> On Thu, Aug 16, 2018 at 7:18 PM, Aurélien Larcher
>> mailto:aurelien.larc...@gmail.com>
>> <mailto:aurelien.larc...@gmail.com
>>
>> <mailto:aurelien.larc...@gmail.com>>> wrote:
>>
>>
>>
>>
>>
>> https://github.com/cgrzemba/oi-userland/tree/rust/components
>> /developer/rust
>> <https://github.com/cgrzemba/oi-userland/tree/rust/component
>> s/developer/rust>
>> <https://github.com/cgrzemba/o
>> i-userland/tree/rust/components/developer/rust
>> <https://github.com/cgrzemba/oi-userland/tree/rust/component
>> s/developer/rust>>
>>
>>
>>  I remember now updating my recipe to yours but I needed
>> some
>>  configuration tweaks to deal with a few issues:
>>  - /usr/bin/cc is default used as linker but it is
>> sunstudio 12.1
>>  so you need to override it,
>>  - AR should be specified,
>>  - this recipe assumes that GCC runtime libraries are in
>>  /usr/lib/$(MACH64) which is not true for us with GCC >=
>> 6,
>>  - the linker should be specified for the target as it
>> is not
>>  passed from the global settings.
>>
>>  Also rustc will eat up to 3GB of RAM so the host should
>> have
>>  enough memory.
>>
>>
>>  Just rebased my change over Carsten's branch:
>>
>> https://github.com/alarcher/oi-userland/tree/rust123
>> <https://github.com/alarcher/oi-userland/tree/rust123>
>>  <https://github.com/alarcher/oi-userland/tree/rust123
>> <https://github.com/alarcher/oi-userland/tree/rust123>>
>>
>>
>> More work:
>>
>> helios> rustc hello.rs <http://hello.rs> <http://hello.rs>
>> error[E0463]: can't find crate for `std`
>>
>> error: aborting due to previous error
>>
>> helios> ls /usr/lib/amd64/rustlib/x86_64-sun-solaris/
>> analysis/ lib/
>>
>> but rust looks for libraries in /usr/lib/rustlib
>>
>> Symlinked like a piggy to check it and it is the problem...
>>
>> Also rustc does not put /usr/lib/amd64 in the search path so
>> executables are broken.
>>
>>
>> I build Aurélien's branch inside a zone, but it fails for me with:
>>
>> error: could not exec the linker `/usr/gcc/6/bin/gcc`: Not enough
>> space (os error 12)
>>
>> For full log, see
>> https://paste.ec/paste/JxbabBm7#Kn+gh58pAwBhweYcTzrk6gzVSH7R
>> c6Npg2eXEmoCMv1
>> <https://paste.ec/paste/JxbabBm7#Kn+gh58pAwBhweYcTzrk6gzVSH7
>> Rc6Npg2eXEmoCMv1>.
>>
>> I am quite sure that I have plenty of disk space available:
>>
>> $ df -h .
>> Filesystem Size   Used  Available Capacity  Mounted on
>> rpool/zones/build/build-userland/ROOT/zbe-125
>> 114G  14.7G  74.9G17%/
>>
>> Any idea what the problem might be? I build it on Lenovo X220 (4
>> cores, 6 GB of memory + 3 GB of swap), OS is updated to latest
>> packages. I don't think I limited the zone in any way when I created
>> it.
>>
>>
>>
>> I have seen one instance of rustc take more than 3GB so you probably ran
>> out of mem.
>>
>
> I guess that's the only logical explanation, especially when the same
> component sources work for you. Hence I don't have a suitable system to
> work this on.
>
> I also tried to bump rust to 1.28 but failed short as "-nodefaultlibs" is
> getting my way: https://github.com/mno-hime/oi
> -userland/tree/rust/components/developer/rust.
>

Is it again some config picking /usr/bin/cc instead of the specified
compiler?


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



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

Re: [oi-dev] Rust in userland?

2018-08-21 Thread Aurélien Larcher
On Tue, Aug 21, 2018 at 11:10 PM, Michal Nowak  wrote:

> On 08/16/18 07:31 PM, Aurélien Larcher wrote:
>
>>
>>
>> On Thu, Aug 16, 2018 at 7:18 PM, Aurélien Larcher <
>> aurelien.larc...@gmail.com <mailto:aurelien.larc...@gmail.com>> wrote:
>>
>>
>>
>>
>>
>> https://github.com/cgrzemba/oi-userland/tree/rust/components
>> /developer/rust
>> <https://github.com/cgrzemba/oi-userland/tree/rust/component
>> s/developer/rust>
>>
>>
>> I remember now updating my recipe to yours but I needed some
>> configuration tweaks to deal with a few issues:
>> - /usr/bin/cc is default used as linker but it is sunstudio 12.1
>> so you need to override it,
>> - AR should be specified,
>> - this recipe assumes that GCC runtime libraries are in
>> /usr/lib/$(MACH64) which is not true for us with GCC >= 6,
>> - the linker should be specified for the target as it is not
>> passed from the global settings.
>>
>> Also rustc will eat up to 3GB of RAM so the host should have
>> enough memory.
>>
>>
>> Just rebased my change over Carsten's branch:
>>
>> https://github.com/alarcher/oi-userland/tree/rust123
>> <https://github.com/alarcher/oi-userland/tree/rust123>
>>
>>
>> More work:
>>
>> helios> rustc hello.rs <http://hello.rs>
>> error[E0463]: can't find crate for `std`
>>
>> error: aborting due to previous error
>>
>> helios> ls /usr/lib/amd64/rustlib/x86_64-sun-solaris/
>> analysis/ lib/
>>
>> but rust looks for libraries in /usr/lib/rustlib
>>
>> Symlinked like a piggy to check it and it is the problem...
>>
>> Also rustc does not put /usr/lib/amd64 in the search path so executables
>> are broken.
>>
>
> I build Aurélien's branch inside a zone, but it fails for me with:
>
> error: could not exec the linker `/usr/gcc/6/bin/gcc`: Not enough space
> (os error 12)
>
> For full log, see https://paste.ec/paste/JxbabBm
> 7#Kn+gh58pAwBhweYcTzrk6gzVSH7Rc6Npg2eXEmoCMv1.
>
> I am quite sure that I have plenty of disk space available:
>
> $ df -h .
> Filesystem Size   Used  Available Capacity  Mounted on
> rpool/zones/build/build-userland/ROOT/zbe-125
>114G  14.7G  74.9G17%/
>
> Any idea what the problem might be? I build it on Lenovo X220 (4 cores, 6
> GB of memory + 3 GB of swap), OS is updated to latest packages. I don't
> think I limited the zone in any way when I created it.
>


I have seen one instance of rustc take more than 3GB so you probably ran
out of mem.


>
> Thanks,
> Michal
>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



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

Re: [oi-dev] latest loader branch + ACPI patches

2018-08-18 Thread Aurélien Larcher
On Sat, Aug 18, 2018 at 4:45 PM, Toomas Soome  wrote:

>
>
> On 18 Aug 2018, at 15:20, Aurélien Larcher 
> wrote:
>
>
>
> On Sat, Aug 18, 2018 at 8:45 AM, Toomas Soome via oi-dev <
> oi-dev@openindiana.org> wrote:
>
>> hi!
>>
>> I have built the latest state + ACPI patches from Robert, the images are
>> available at: http://148.52.235.80.sta.estpak.ee
>>
>
> Hi Toomas,
> thanks for doing this :)
> Should we mirror the images on dlc-int ?
>
> Also I have published your gcc7 branch + ACPI patches to
> pkg.openindiana.org/gcc-next
> That's what I am using right now on my workstation.
>
> I could add your loader patches if you want.
>
>
>
> Hm, I do not mind. The loader branch also has gcc7 (of course).
>

Currently in the gcc-next zone illumos-gate builds with gcc-6 (non-debug
only).
Would it make sense to move to gcc-7 already? (e.g. to catch any regression)


>
> rgds,
> toomas
>
>


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

Re: [oi-dev] latest loader branch + ACPI patches

2018-08-18 Thread Aurélien Larcher
On Sat, Aug 18, 2018 at 8:45 AM, Toomas Soome via oi-dev <
oi-dev@openindiana.org> wrote:

> hi!
>
> I have built the latest state + ACPI patches from Robert, the images are
> available at: http://148.52.235.80.sta.estpak.ee
>

Hi Toomas,
thanks for doing this :)
Should we mirror the images on dlc-int ?

Also I have published your gcc7 branch + ACPI patches to
pkg.openindiana.org/gcc-next
That's what I am using right now on my workstation.

I could add your loader patches if you want.

Kind regards,

Aurélien





>
> rgds,
> toomas
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



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

Re: [oi-dev] GCC 8.2

2018-08-17 Thread Aurélien Larcher
On Thu, Aug 16, 2018 at 12:49 AM, Adam Števko  wrote:

> Hey Aurelien,
>
> wonderful job!
>

Hullo Adam ;)
No problem.

In about two hours illumos-gate will be published to the repository with
Robert Mustacchi's ACPI development changeset,
cherry-picked to https://github.com/alarcher/illumos-gate/tree/gcc-next

Anyone interested can help by updating to a new BE and testing it.

Aurélien


>
> Regards,
> Adam
>
> On Wed, Aug 15, 2018 at 11:01 PM, Aurélien Larcher <
> aurelien.larc...@gmail.com> wrote:
>
>> 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
>>
>>
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> https://openindiana.org/mailman/listinfo/oi-dev
>>
>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



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

Re: [oi-dev] Build server not building new illumos

2018-08-16 Thread Aurélien Larcher
On Thu, Aug 16, 2018 at 10:40 AM, Andreas Wacknitz 
wrote:

>
>
> Am 16.08.2018 um 09:13 schrieb Michal Nowak:
>
>> Hi,
>>
>> it seems that our build server is not producing new illumos builds for a
>> couple of days. The error at https://hipster.openindiana.or
>> g/logs/illumos-gate/latest/openindiana.illumos-gate.publish.log is:
>>
>> From git://github.com/illumos/illumos-gate
>>  * branch  HEAD   -> FETCH_HEAD
>> error: Your local changes to the following files would be overwritten by
>> merge:
>> usr/src/lib/libc/port/mapfile-vers
>> Please commit your changes or stash them before you merge.
>> Aborting
>> Updating 6640c13bea..9fed930b55
>>
>> Can someone with access to the build server fix it, please?
>>
> Alas, I can't. I have already tried to contact alp and xenol but no luck
> yet.
>

Fixed.


>
> Regards,
> Andreas
>
>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



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

Re: [oi-dev] Rust in userland?

2018-08-16 Thread Aurélien Larcher
On Thu, Aug 16, 2018 at 7:18 PM, Aurélien Larcher <
aurelien.larc...@gmail.com> wrote:

>
>
>
>
>>> https://github.com/cgrzemba/oi-userland/tree/rust/components
>>> /developer/rust
>>>
>>
>> I remember now updating my recipe to yours but I needed some
>> configuration tweaks to deal with a few issues:
>> - /usr/bin/cc is default used as linker but it is sunstudio 12.1 so you
>> need to override it,
>> - AR should be specified,
>> - this recipe assumes that GCC runtime libraries are in
>> /usr/lib/$(MACH64) which is not true for us with GCC >= 6,
>> - the linker should be specified for the target as it is not passed from
>> the global settings.
>>
>> Also rustc will eat up to 3GB of RAM so the host should have enough
>> memory.
>>
>
> Just rebased my change over Carsten's branch:
>
> https://github.com/alarcher/oi-userland/tree/rust123
>

More work:

helios> rustc hello.rs
error[E0463]: can't find crate for `std`

error: aborting due to previous error

helios> ls /usr/lib/amd64/rustlib/x86_64-sun-solaris/
analysis/ lib/

but rust looks for libraries in /usr/lib/rustlib

Symlinked like a piggy to check it and it is the problem...

Also rustc does not put /usr/lib/amd64 in the search path so executables
are broken.


>
>
>
>
>
>>
>>
>>> --
>>> Carsten Grzemba
>>>
>>>
>>> ___
>>> oi-dev mailing list
>>> oi-dev@openindiana.org
>>> https://openindiana.org/mailman/listinfo/oi-dev
>>>
>>
>>
>>
>> --
>> ---
>> Praise the Caffeine embeddings
>>
>
>
>
> --
> ---
> Praise the Caffeine embeddings
>



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

Re: [oi-dev] Rust in userland?

2018-08-16 Thread Aurélien Larcher
>> https://github.com/cgrzemba/oi-userland/tree/rust/components
>> /developer/rust
>>
>
> I remember now updating my recipe to yours but I needed some configuration
> tweaks to deal with a few issues:
> - /usr/bin/cc is default used as linker but it is sunstudio 12.1 so you
> need to override it,
> - AR should be specified,
> - this recipe assumes that GCC runtime libraries are in /usr/lib/$(MACH64)
> which is not true for us with GCC >= 6,
> - the linker should be specified for the target as it is not passed from
> the global settings.
>
> Also rustc will eat up to 3GB of RAM so the host should have enough memory.
>

Just rebased my change over Carsten's branch:

https://github.com/alarcher/oi-userland/tree/rust123




>
>
>> --
>> Carsten Grzemba
>>
>>
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> https://openindiana.org/mailman/listinfo/oi-dev
>>
>
>
>
> --
> ---
> Praise the Caffeine embeddings
>



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

Re: [oi-dev] Rust in userland?

2018-08-16 Thread Aurélien Larcher
On Thu, Aug 16, 2018 at 7:22 AM, Carsten Grzemba 
wrote:

>
>
> On 15.08.18 23:03, *Aurélien Larcher *  wrote:
>
>
>
> On Wednesday, August 15, 2018, Michal Nowak  wrote:
>
>> On 08/14/18 09:01 AM, Till Wegmüller wrote:
>>
>>> Hi
>>>
>>> Could you use an earlier version of Rust as bootstrap for the current
>>> rust?
>>>
>>> There should be a guide for rust bootstraping around on the internet.
>>>
>>> You can look at golang 1.8 how bootstraping with an earlier version
>>> works.
>>>
>>> The Reason for that is, that we build all packages on a buildserver with
>>> jenkins. Where we will not install pkgsrc packages.
>>>
>>> Can you also check platform support? Last I remember solarish systems
>>> where a secondary platform and required patches.
>>>
>>> In any case when you need a reviewer just tag me on github i'll gladly
>>> take a look.
>>>
>>> Thanks and Greetings
>>> Till
>>>
>>>
>> Hi Till,
>>
>> I noticed that Joyent has very recent rust bootstraps, e.g.
>> https://us-east.manta.joyent.com/pkgsrc/public/pkg-bootstrap
>> s/rust-1.28.0-x86_64-sun-solaris.tar.gz, which we could leverage as an
>> internal payload of the rust component. At least initially.
>
>
> That's what I used.
> Modulo a spurious compiler flag things went well.
>
>>
>> Looking at platform support (https://forge.rust-lang.org/p
>> latform-support.html), Solaris is Tier 2 platform for which standard
>> library is guaranteed to build, though looking at Joyent's rust it seems to
>> me that rustc and cargo are doable as well.
>>
>> Thank you for your support, I'll get back to you when something
>> materialize :).
>>
>> Michal
>>
>> On 13.08.2018 22:39, Michal Nowak wrote:
>>>
>>>> Hi,
>>>>
>>>> it seems that rust lang is needed for compilation of Thunderbird 60 and
>>>> Firefox 60 ESR. Did anyone worked on rust component for userland?
>>>>
>>>> If not, I thought on packaging it (and cargo) from scratch using
>>>> pkgsrc's Makefile and Joyent's rust in binary pkgsrc as rust is needed
>>>> for building itself.
>>>>
>>>> Michal
>>>>
>>>> ___
>>>> oi-dev mailing list
>>>> oi-dev@openindiana.org
>>>> https://openindiana.org/mailman/listinfo/oi-dev
>>>>
>>>
>>> ___
>>> oi-dev mailing list
>>> oi-dev@openindiana.org
>>> https://openindiana.org/mailman/listinfo/oi-dev
>>>
>>>
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> https://openindiana.org/mailman/listinfo/oi-dev
>
>
>
> --
> ---
> Praise the Caffeine embeddings
>
> --
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
> I notice this already, here are my recipe and patches adopted/inspired
> from Joyents pkgsrc
>
> https://github.com/cgrzemba/oi-userland/tree/rust/
> components/developer/rust
>

I remember now updating my recipe to yours but I needed some configuration
tweaks to deal with a few issues:
- /usr/bin/cc is default used as linker but it is sunstudio 12.1 so you
need to override it,
- AR should be specified,
- this recipe assumes that GCC runtime libraries are in /usr/lib/$(MACH64)
which is not true for us with GCC >= 6,
- the linker should be specified for the target as it is not passed from
the global settings.

Also rustc will eat up to 3GB of RAM so the host should have enough memory.


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



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

Re: [oi-dev] Rust in userland?

2018-08-15 Thread Aurélien Larcher
On Wednesday, August 15, 2018, Michal Nowak  wrote:

> On 08/14/18 09:01 AM, Till Wegmüller wrote:
>
>> Hi
>>
>> Could you use an earlier version of Rust as bootstrap for the current
>> rust?
>>
>> There should be a guide for rust bootstraping around on the internet.
>>
>> You can look at golang 1.8 how bootstraping with an earlier version works.
>>
>> The Reason for that is, that we build all packages on a buildserver with
>> jenkins. Where we will not install pkgsrc packages.
>>
>> Can you also check platform support? Last I remember solarish systems
>> where a secondary platform and required patches.
>>
>> In any case when you need a reviewer just tag me on github i'll gladly
>> take a look.
>>
>> Thanks and Greetings
>> Till
>>
>>
> Hi Till,
>
> I noticed that Joyent has very recent rust bootstraps, e.g.
> https://us-east.manta.joyent.com/pkgsrc/public/pkg-bootstrap
> s/rust-1.28.0-x86_64-sun-solaris.tar.gz, which we could leverage as an
> internal payload of the rust component. At least initially.


That's what I used.
Modulo a spurious compiler flag things went well.

>
> Looking at platform support (https://forge.rust-lang.org/p
> latform-support.html), Solaris is Tier 2 platform for which standard
> library is guaranteed to build, though looking at Joyent's rust it seems to
> me that rustc and cargo are doable as well.
>
> Thank you for your support, I'll get back to you when something
> materialize :).
>
> Michal
>
> On 13.08.2018 22:39, Michal Nowak wrote:
>>
>>> Hi,
>>>
>>> it seems that rust lang is needed for compilation of Thunderbird 60 and
>>> Firefox 60 ESR. Did anyone worked on rust component for userland?
>>>
>>> If not, I thought on packaging it (and cargo) from scratch using
>>> pkgsrc's Makefile and Joyent's rust in binary pkgsrc as rust is needed
>>> for building itself.
>>>
>>> Michal
>>>
>>> ___
>>> oi-dev mailing list
>>> oi-dev@openindiana.org
>>> https://openindiana.org/mailman/listinfo/oi-dev
>>>
>>
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> https://openindiana.org/mailman/listinfo/oi-dev
>>
>>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev



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

[oi-dev] GCC 8.2

2018-08-15 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Rust in userland?

2018-08-15 Thread Aurélien Larcher
On Wed, Aug 15, 2018 at 7:56 AM, Carsten Grzemba 
wrote:

>
>
> On 14.08.18 18:38, *Andreas Wacknitz *  wrote:
>
> Am 13.08.18 um 22:39 schrieb Michal Nowak:
> > Hi,
> >
> > it seems that rust lang is needed for compilation of Thunderbird 60
> > and Firefox 60 ESR. Did anyone worked on rust component for userland?
> >
> > If not, I thought on packaging it (and cargo) from scratch using
> > pkgsrc's Makefile and Joyent's rust in binary pkgsrc as rust is needed
> > for building itself.
>
>
I wrote a rust component last year and use it for a while but I had no time
to follow up.
Not sure on which machine it was, I'll have a look in the week-end.


> >
> > Michal
> >
> > ___
> > oi-dev mailing list
> > oi-dev@openindiana.org
> > https://openindiana.org/mailman/listinfo/oi-dev
> Go for it!
>
> Regards
> Andreas
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
> --
> Carsten Grzemba
> I did this
>
> https://github.com/cgrzemba/oi-userland/tree/rust
>
> but I havn't any time for test.
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



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

Re: [oi-dev] What to do about missing aclocal and automake versions?

2018-06-24 Thread Aurélien Larcher
On Sun, Jun 24, 2018 at 3:47 PM, Gary Mills  wrote:

> While building openindiana/illumos-gcc, I noticed these errors during
> the build of the mpfr component:
>
> WARNING: `aclocal-1.11' is missing on your system.  You should only need
> it if
>  you modified `acinclude.m4' or `configure.ac'.  You might want
>  to install the `Automake' and `Perl' packages.  Grab them from
>  any GNU archive site.
> ...
> WARNING: `automake-1.11' is missing on your system.  You should only need
> it if
>  you modified `Makefile.am', `acinclude.m4' or `configure.ac'.
>  You might want to install the `Automake' and `Perl' packages.
>  Grab them from any GNU archive site.
>
> These versions are not available in the oi-userland repository.


The version is available in the repository:

http://pkg.openindiana.org/hipster/en/search.shtml?token=automake-111=Search



> The
> expected reconfigure is not done.
>
> The version number comes from the first field of this line in
> configure.ac:
>
> AM_INIT_AUTOMAKE([1.11 no-define dist-bzip2 dist-xz dist-zip])
>
> It's supposed to be the minimum auto tools version needed to build
> the product.  However, it seems to be used as the required version,
> according to these lines in configure:
>
> ACLOCAL=${ACLOCAL-"${am_missing_run}aclocal-${am__api_version}"}
> AUTOMAKE=${AUTOMAKE-"${am_missing_run}automake-${am__api_version}"}
>
> The corresponding lines in Makefile are:
>
> ACLOCAL = ${SHELL} /export/home/mills/Downloads/
> code/oi-userland/components/openindiana/illumos-gcc/
> illumos-gcc-0f5ed4c/mpfr/missing --run aclocal-1.11
> AUTOMAKE = ${SHELL} /export/home/mills/Downloads/
> code/oi-userland/components/openindiana/illumos-gcc/
> illumos-gcc-0f5ed4c/mpfr/missing --run automake-1.11
>
> What is the correct solution here?
>

The package should probably be added to either build-essential or
illumos-gcc's build dependencies.


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



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

Re: [oi-dev] libboost incompatible with g++ 6 runtime?

2018-06-19 Thread Aurélien Larcher
On Tue, Jun 19, 2018 at 4:17 PM, Carsten Grzemba 
wrote:

> Hi,
>
> if I attempt link libboost I get the message:
>
> ld: fatal: file /usr/lib//libstdc++.so.6: version 'GLIBCXX_3.4.21' does
> not exist:
> required by file /usr/lib/libboost_filesystem.so
> ld: fatal: file /usr/lib//libstdc++.so.6: version 'CXXABI_1.3.9' does not
> exist:
> required by file /usr/lib/libboost_filesystem.so
>

I am not sure why you get this, boost 1.64.0 delivered in the repository
links to g++-6-runtime libs found in /usr/gcc/6/lib.
What you see is an attempt to link to the libs from g++-4-runtime.


>
> where has libboost the higher versions seen?
>
> $elfdump -v libstdc++
>
> shows:
> ..8<..
>   [21]  GLIBCXX_3.4.19  GLIBCXX_3.4.18
>   [22]  GLIBCXX_3.4.20  GLIBCXX_3.4.19
> ..8<..
>  [30]  CXXABI_1.3.7CXXABI_1.3.6
>   [31]  CXXABI_1.3.8CXXABI_1.3.7
>
> Thanks
>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



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

[oi-dev] GCC 8 repository

2018-06-04 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Python 2.7 SPARC build needs an adjusted patch and a new patch

2018-06-03 Thread Aurélien Larcher
On Mon, Jun 4, 2018 at 2:26 AM, Gary Mills  wrote:

> In an attempt to build python2.7 on a T2000 (SPARC), I received this
> error:
>
> /usr/gcc/4.4.4/bin/gcc -m32 -O3 -mno-app-regs -fPIC -DPIC -std=c99
> -D_XOPEN_SOURCE=600 -m32 -fPIC -DPIC -R/usr/gnu/lib -L/usr/gnu/lib  -o
> python \
> Modules/python.o \
> -L. -lpython2.7 -lsocket -lnsl -ldl-lm
> Undefined   first referenced
>  symbol in file
> asm ./libpython2.7.so
> ld: fatal: symbol referencing errors. No output written to python
> collect2: ld returned 1 exit status
>
> This happens because Python/ceval.c contains two instances of code
> like this:
>
>   #if defined(__sparc)
> +   asm("nop");
>   #endif
>
> This code was inserted by a patch called 05-dtrace.patch .  The file
> dtrace.patch.diff, attached to this message, shows the changes I made
> to the patch.  These changes fix the problem.
>
> One of the modules also failed to build, producing these errors:
>
> /export/home/mills/Downloads/code/oi-userland/components/
> python/python27/Python-2.7.14/Modules/_ctypes/libffi/src/sparc/ffi.c:526:
> error: 'asm' undeclared (first use in this function)
> /export/home/mills/Downloads/code/oi-userland/components/
> python/python27/Python-2.7.14/Modules/_ctypes/libffi/src/sparc/ffi.c:526:
> error: expected ';' before 'volatile'
>
> The new patch 31-sparc.patch, also attached, fixes this problem.
> Finally, I updated COMPONENT_REVISION in the Makefile to signal the
> presence of the adjusted patch and the new one as in the file
> Makefile.diff, also attached.
>
> These changes only affect the SPARC build.  Later python versions
> likely require the same changes, but I haven't checked.
>
> I'd appreciate it if somebody could verify that these changes are
> correct.  I assume they are.  The build completes after these changes
> are made.
>

Why not just activate GNU extensions with -std=gnu99?
Python 2.7 was probably compiled with them until I added -std=c99.


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



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

[oi-dev] Move to category directories and pending component updates

2018-06-03 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] GCC 8 build status

2018-05-28 Thread Aurélien Larcher
Three components left:

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

Re: [oi-dev] GCC 8 build status

2018-05-26 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] GCC 8 build status

2018-05-25 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] GCC 8 build status

2018-05-25 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] GCC 8 build status

2018-05-24 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] hwloc ABI incompatible update

2018-05-22 Thread Aurélien Larcher
On Tue, May 22, 2018 at 3:16 PM, Alexander Pyhalov <a...@rsu.ru> wrote:

> On 05/22/18 03:44 PM, Aurélien Larcher wrote:
>
>> 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
>>
>
> Hi. Please, add a note about this to https://wiki.openindiana.org/o
> i/oi_hipster .
>

Done!


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



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

[oi-dev] hwloc ABI incompatible update

2018-05-22 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Build of gcc-7.3.0 stops with linker errors

2018-05-21 Thread Aurélien Larcher
On Mon, May 21, 2018 at 4:23 AM, Gary Mills  wrote:

> On Sat, May 19, 2018 at 09:10:26PM -0500, Norm Jacobs wrote:
> >It looks like
> >developer/gcc-7/patches/0008-sol2-enable-full-__cxa_atexit-
> support.patc
> >h may need work for SPARC, particularly in libgcc/config.host.
> Without
> >looking too far into it, I would guess that changing the diffs for
> >libgcc/config.host in the patch to
> [...]
>
> I was suspicious of that patch too, but I didn't know where it fit
> in in the build process.  I'm testing your suggested change now.
>
> Unfortunately, the build stops at an earlier point, complaining
> that AX_PTHREAD is not defined.  I'm investigating that problem.
> I seem to need /usr/share/aclocal/ax_pthread.m4 on this system,
> or perhaps the whole package that contains it.
>
>
I think I added the package as autoconf-archive

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



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

Re: [oi-dev] Build of gcc-7.3.0 stops with linker errors

2018-05-19 Thread Aurélien Larcher
On Sun, May 20, 2018 at 12:19 AM, Gary Mills <gary_mi...@fastmail.fm> wrote:

> On Sat, May 19, 2018 at 10:47:05PM +0200, Aurélien Larcher wrote:
> >
> >Are you sure there is no crtbeginS.o at all in the directory?
>
> Quite sure:
>
> $ find build -name 'crt*.o' -ls
> 227005892 -rw-r--r--   1 millsstaff1416 May 19 10:40
> build/sparcv7/gcc/sparcv9/crt1.o
> 227005874 -rw-r--r--   1 millsstaff3232 May 19 10:40
> build/sparcv7/gcc/sparcv9/crtbegin.o
> 227005882 -rw-r--r--   1 millsstaff 952 May 19 10:40
> build/sparcv7/gcc/sparcv9/crtend.o
> 227005915 -rw-r--r--   1 millsstaff3928 May 19 10:40
> build/sparcv7/gcc/sparcv9/crtfastmath.o
> 227005845 -rw-r--r--   1 millsstaff3928 May 19 10:40
> build/sparcv7/sparc-sun-solaris2.11/sparcv9/libgcc/crtfastmath.o
> 227005782 -rw-r--r--   1 millsstaff 952 May 19 10:40
> build/sparcv7/sparc-sun-solaris2.11/sparcv9/libgcc/crtend.o
> 227005764 -rw-r--r--   1 millsstaff3232 May 19 10:40
> build/sparcv7/sparc-sun-solaris2.11/sparcv9/libgcc/crtbegin.o
> 227005802 -rw-r--r--   1 millsstaff1416 May 19 10:40
> build/sparcv7/sparc-sun-solaris2.11/sparcv9/libgcc/crt1.o
>
> >Should they not be created already from stage-1?
>
> That's what I expected.
>
> >You should be able to set the ld path to them using boot-ldflags.
>
> They don't exist anywhere on the system.
>
> >Also I do not remember if multilib is considered as a native build. If
> >not, you may need to --enable-bootstrap explicitly.
>
> Okay, thanks.
>

Sorry, my memory is a bit shaky on these topics... :S


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



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

Re: [oi-dev] Build of gcc-7.3.0 stops with linker errors

2018-05-19 Thread Aurélien Larcher
On Sat, May 19, 2018 at 11:11 PM, Gary Mills <gary_mi...@fastmail.fm> wrote:

> On Sat, May 19, 2018 at 10:02:49PM +0200, Aurélien Larcher wrote:
> >On Sat, May 19, 2018 at 9:56 PM, Gary Mills <[1]
> gary_mi...@fastmail.fm>
> >wrote:
> > >
> > >  I'm attempting to build the developer/gcc-7 source package from a
> > >  recent version of oi-userland.  The build stops with these error
> > >  messages:
> [...]
> > >  Â  Â  ld: fatal: file crtbeginS.o: open failed: No such file or
> > >  directory
> > >  Â  Â  ld: fatal: file crtendS.o: open failed: No such file or
> > >  directory
> > >  Â  Â  ld: fatal: file processing errors. No output written to
> > >  sparcv9/libgcc_s.so.1.tmp
>
> >Why do you use gcc-4.4.4-il instead of the userland compiler?
>
> What's the userland compiler?  I'm using gcc-4.4.4-il because that's
> the only one I got to build so far.
>

I assumed that you already had a gcc provided with the system like an old
gcc 4.x from MartUX or gccfs from Sun


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



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

Re: [oi-dev] Build of gcc-7.3.0 stops with linker errors

2018-05-19 Thread Aurélien Larcher
On Sat, May 19, 2018 at 10:06 PM, Igor Kozhukhov 
wrote:

>
> On Sat, May 19, 2018 at 9:56 PM, Gary Mills 
> wrote:
>
>> I'm attempting to build the developer/gcc-7 source package from a
>> recent version of oi-userland.  The build stops with these error
>> messages:
>>
>> /export/home/mills/Downloads/code/oi-userland/
>> components/developer/gcc-7/build/sparcv7/./gcc/xgcc
>> -B/export/home/mills/Downloads/code/oi-userland/components
>> /developer/gcc-7/build/sparcv7/./gcc/
>> -B/usr/gcc/7/sparc-sun-solaris2.11/bin/
>> -B/usr/gcc/7/sparc-sun-solaris2.11/lib/ -isystem
>> /usr/gcc/7/sparc-sun-solaris2.11/include -isystem
>> /usr/gcc/7/sparc-sun-solaris2.11/sys-include -O2 -g -O2 -DIN_GCC -W
>> -Wall -Wwrite-strings -Wcast-qual -Wno-format -Wstrict-prototypes
>> -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC
>> -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -shared
>> -nodefaultlibs -Wl,-h,libgcc_s.so.1 -Wl,-z,text -Wl,-z,defs
>> -Wl,-M,libgcc.map -o sparcv9/libgcc_s.so.1.tmp -g -O2 -m64 -B./
>> _muldi3_s.o _negdi2_s.o ... unwind-sjlj_s.o unwind-c_s.o emutls_s.o
>> libgcc.a -lc && rm -f sparcv9/libgcc_s.so && if [ -f
>> sparcv9/libgcc_s.so.1 ]; then mv -f sparcv9/libgcc_s.so.1
>> sparcv9/libgcc_s.so.1.backup; else true; fi && mv
>> sparcv9/libgcc_s.so.1.tmp sparcv9/libgcc_s.so.1 && ln -s
>> libgcc_s.so.1
>> sparcv9/libgcc_s.so
>> ld: fatal: file crtbeginS.o: open failed: No such file or directory
>> ld: fatal: file crtendS.o: open failed: No such file or directory
>> ld: fatal: file processing errors. No output written to
>> sparcv9/libgcc_s.so.1.tmp
>> collect2: error: ld returned 1 exit status
>> Makefile:977: recipe for target 'libgcc_s.so' failed
>> make[6]: *** [libgcc_s.so] Error 1
>> make[6]: Leaving directory '/dpool/export/home/mills/Down
>> loads/code/oi-userland-apr/components/developer/gcc-7/
>> build/sparcv7/sparc-sun-solaris2.11/sparcv9/libgcc'
>>
>> It seems to be building the runtime shared library.  However, the
>> files crtbeginS.o and crtendS.o do not exist in the build directory.
>> Neither do they exist in libgcc.a .  The directory /usr/gcc/7 also
>> does not exist, as the compiler has not been installed yet.  I'm using
>> gcc-4.4.4-il-4 to build it.
>>
> Are you sure there is no crtbeginS.o at all in the directory?
Should they not be created already from stage-1?

You should be able to set the ld path to them using boot-ldflags.
Also I do not remember if multilib is considered as a native build. If not,
you may need to --enable-bootstrap explicitly.



>
>> What's gone wrong?
>>
>
> Why do you use gcc-4.4.4-il instead of the userland compiler?
>
>
> because he is on SPARC V9 :)
> and try bootstrap new another compiler.
>
> Gary,
> You can try take a look and grab compiler on DilOS - i can provide access
> to sparc zone.
> but, i have no gcc-7.3 version yet - still latest one is gcc-6.4
>



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



-- 
---
Praise the Caffeine embeddings

On Sat, May 19, 2018 at 10:06 PM, Igor Kozhukhov 
wrote:

>
> On Sat, May 19, 2018 at 9:56 PM, Gary Mills 
> wrote:
>
>> I'm attempting to build the developer/gcc-7 source package from a
>> recent version of oi-userland.  The build stops with these error
>> messages:
>>
>> /export/home/mills/Downloads/code/oi-userland/
>> components/developer/gcc-7/build/sparcv7/./gcc/xgcc
>> -B/export/home/mills/Downloads/code/oi-userland/components
>> /developer/gcc-7/build/sparcv7/./gcc/
>> -B/usr/gcc/7/sparc-sun-solaris2.11/bin/
>> -B/usr/gcc/7/sparc-sun-solaris2.11/lib/ -isystem
>> /usr/gcc/7/sparc-sun-solaris2.11/include -isystem
>> /usr/gcc/7/sparc-sun-solaris2.11/sys-include -O2 -g -O2 -DIN_GCC -W
>> -Wall -Wwrite-strings -Wcast-qual -Wno-format -Wstrict-prototypes
>> -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC
>> -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -shared
>> -nodefaultlibs -Wl,-h,libgcc_s.so.1 -Wl,-z,text -Wl,-z,defs
>> -Wl,-M,libgcc.map -o sparcv9/libgcc_s.so.1.tmp -g -O2 -m64 -B./
>> _muldi3_s.o _negdi2_s.o ... unwind-sjlj_s.o unwind-c_s.o emutls_s.o
>> libgcc.a -lc && rm -f sparcv9/libgcc_s.so && if [ -f
>> sparcv9/libgcc_s.so.1 ]; then mv -f sparcv9/libgcc_s.so.1
>> sparcv9/libgcc_s.so.1.backup; else true; fi && mv
>> sparcv9/libgcc_s.so.1.tmp sparcv9/libgcc_s.so.1 && ln -s
>> libgcc_s.so.1
>> sparcv9/libgcc_s.so
>> ld: fatal: file crtbeginS.o: open failed: No such file or directory
>> ld: fatal: file crtendS.o: open failed: No such file or directory
>> ld: fatal: file processing errors. No output written to
>> sparcv9/libgcc_s.so.1.tmp
>> collect2: error: ld 

Re: [oi-dev] Build of gcc-7.3.0 stops with linker errors

2018-05-19 Thread Aurélien Larcher
On Sat, May 19, 2018 at 9:56 PM, Gary Mills  wrote:

> I'm attempting to build the developer/gcc-7 source package from a
> recent version of oi-userland.  The build stops with these error
> messages:
>
> /export/home/mills/Downloads/code/oi-userland/components/
> developer/gcc-7/build/sparcv7/./gcc/xgcc
> -B/export/home/mills/Downloads/code/oi-userland/
> components/developer/gcc-7/build/sparcv7/./gcc/
> -B/usr/gcc/7/sparc-sun-solaris2.11/bin/
> -B/usr/gcc/7/sparc-sun-solaris2.11/lib/ -isystem
> /usr/gcc/7/sparc-sun-solaris2.11/include -isystem
> /usr/gcc/7/sparc-sun-solaris2.11/sys-include -O2 -g -O2 -DIN_GCC -W
> -Wall -Wwrite-strings -Wcast-qual -Wno-format -Wstrict-prototypes
> -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC
> -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -shared
> -nodefaultlibs -Wl,-h,libgcc_s.so.1 -Wl,-z,text -Wl,-z,defs
> -Wl,-M,libgcc.map -o sparcv9/libgcc_s.so.1.tmp -g -O2 -m64 -B./
> _muldi3_s.o _negdi2_s.o ... unwind-sjlj_s.o unwind-c_s.o emutls_s.o
> libgcc.a -lc && rm -f sparcv9/libgcc_s.so && if [ -f
> sparcv9/libgcc_s.so.1 ]; then mv -f sparcv9/libgcc_s.so.1
> sparcv9/libgcc_s.so.1.backup; else true; fi && mv
> sparcv9/libgcc_s.so.1.tmp sparcv9/libgcc_s.so.1 && ln -s libgcc_s.so.1
> sparcv9/libgcc_s.so
> ld: fatal: file crtbeginS.o: open failed: No such file or directory
> ld: fatal: file crtendS.o: open failed: No such file or directory
> ld: fatal: file processing errors. No output written to
> sparcv9/libgcc_s.so.1.tmp
> collect2: error: ld returned 1 exit status
> Makefile:977: recipe for target 'libgcc_s.so' failed
> make[6]: *** [libgcc_s.so] Error 1
> make[6]: Leaving directory '/dpool/export/home/mills/
> Downloads/code/oi-userland-apr/components/developer/gcc-
> 7/build/sparcv7/sparc-sun-solaris2.11/sparcv9/libgcc'
>
> It seems to be building the runtime shared library.  However, the
> files crtbeginS.o and crtendS.o do not exist in the build directory.
> Neither do they exist in libgcc.a .  The directory /usr/gcc/7 also
> does not exist, as the compiler has not been installed yet.  I'm using
> gcc-4.4.4-il-4 to build it.
>
> What's gone wrong?
>

Why do you use gcc-4.4.4-il instead of the userland compiler?


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



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

Re: [oi-dev] gmake sample-manifest Replaces to many strings with $(COMPONENT_VERSION) in sample-manifest

2018-05-02 Thread Aurélien Larcher
On Tue, May 1, 2018 at 1:07 PM, Till Wegmüller  wrote:

> Hi fellow developers
>
> I found a bug in our Makefile script sample-manifest.
>

Yep this is known, there is a similar issue with any version number, dot
not being escaped.
I thought it was in pkgmogrify



> It replaces to many string with $(COMPONENT_VERSION) even those which
> are not equal to $(COMPONENT_VERSION) it looks like it treats the . _
> and nospace characters as equal.
>
> This causes problems currently with golang-19 and golang-110 packaging.
> COuld somebody with Makefile knowledge check that script out and see if
> it's fixable?
>
> Thanks and greetings
> Till
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



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

Re: [oi-dev] Out of memory when trying to compile icinga2 with gcc6

2018-03-28 Thread Aurélien Larcher
On Wed, Mar 28, 2018 at 1:05 PM, Marianne Spiller 
wrote:

> Hi,
>
> I'd like to re-compile my icinga2 package with the new oi-userland gcc6
> behaviour; secret masterplan was to finally prepare the pull request.
> With the gcc-4.9 version of oi-userland I got a working package.
>
> But using gcc-6 the package does not longer compile successfully; it
> stops with the following error message:
> [ 63%] Built target icinga-app
>
> cc1plus: out of memory allocating 2727788 bytes after a total of 85975040
> bytes
> make[3]: *** [lib/icinga/CMakeFiles/icinga.dir/build.make:320:lib/icinga/
> CMakeFiles/icinga.dir/icinga_unity.cpp.o] Error 1
> make[3]: Leaving directory '/scratch/oi-userland/
> components/sysutils/icinga2/build/amd64'
> make[2]: *** [CMakeFiles/Makefile2:1656: lib/icinga/CMakeFiles/icinga.dir/all]
> Error 2
> make[2]: Leaving directory '/scratch/oi-userland/
> components/sysutils/icinga2/build/amd64'
> make[1]: *** [Makefile:163: all] Error 2 make[1]: Leaving directory
> '/scratch/oi-userland/components/sysutils/icinga2/build/amd64' gmake: ***
> [/scratch/oi-userland/make-rules/cmake.mk:167: /scratch/oi-userland/
> components/sysutils/icinga2/build/amd64/.built] Error 2
>
> So what to do next? The host has 24GB RAM, 16 of them are available. No
> strange ulimit settings as far as I can see - in fact it is a freshly
> installed Hipster, no big changes made.


> Any help or idea would be great :)
>

How many build jobs (-j) did you specifiy with COMPONENT_BUILD_ARGS?

You output suggests that you are building with more than one.
I have just built version 2.8.2 successfully with -j1 on a machine with
48GB RAM (14 avaiable) but I could see that the compilation of icinga_unity.cpp
alone takes up to 1GB RAM.


> Thanks a lot,
>   Marianne
>
>
> --
> "There's nothing wrong with having a tree as a friend."
> - Bob Ross
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



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

[oi-dev] Pulseaudio now delivered as 64-bit by default.

2018-03-10 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Xorg 1.19.6

2018-03-07 Thread Aurélien Larcher
> Thanks for the added instructions. Although most members on this list
> probably know this by heart, I'm very happy that you take the time to
> include it for us who are not as knowing about SunOS>5.9
>
> Thanks,
>

Hi,
You are welcome, I think it is important that people can get instructions
as easily as possible.
Due to the time constraints it is sometimes difficult to spend time on that
(after all we are all contributing in our spare time here), but essential
if we want to be inclusive.

Kind regards

Aurélien


>
> --
> Tony Albers
> Systems administrator, IT-development
> Royal Danish Library, Victor Albecks Vej 1, 8000 Aarhus C, Denmark.
> Tel: +45 2566 2383 / +45 8946 2316
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev




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

Re: [oi-dev] KPTI testing images and repository archive uploaded

2018-03-05 Thread Aurélien Larcher
On Mon, Mar 5, 2018 at 8:12 PM, Michal Nowak <mno...@startmail.com> wrote:

> On 03/05/2018 02:32 PM, Aurélien Larcher wrote:
>
>
>
> On Mon, Mar 5, 2018 at 8:25 AM, Michal Nowak <mno...@startmail.com> wrote:
>
>> On 03/03/2018 09:13 PM, Aurélien Larcher wrote:
>>
>> Hi,
>> I set up this directory with testing resources:
>>
>> http://dlc-int.openindiana.org/users/aurelien/kpti/
>>
>> Live Media, Minimal Text images, and repository as p5p archive are
>> provided.
>>
>> The repository is located at:
>>
>> pkg.openindiana.org/kpti
>>
>> Let me know if you encounter any issue.
>>
>> Kind regards
>>
>> Aurélien
>>
>> Hi,
>>
>> over the weekend I tested KPTI from the repository on Toshiba Satellite
>> L855 laptop (Ivy Bridge-based, has PCID). I run many tests from Phoronix
>> Test Suite 7.8 there and haven't seen any crash nor any other problem
>> (apart from the fact that some tests are not in a good shape for
>> OpenIndiana...). With regards to general use of the system, I haven't seen
>> any noticeable slowdown.
>>
> Same experience here :)
>
> I'd be interested in putting PTS to a better shape. Do you have any inital
> recipe that I could use for creating a component?
>
> Unfortunately I don't... I used source tarball from the project's website
> and manually installed required dependencies.
>
> One "old" issue is that PTS runs 32-bit binaries by default for some tests
> since it expects /usr/bin to deliver 64-bit executables.
>
> I see, that would explain why some tests from the test suite were unable
> to find some binaries (e.g. mpich).
>

MPI libraries should be loaded using module load mpich or module load
openmpi.
Most Linux distributions use a system-wide switch (like Debian
alternatives) which for MPI does not make much sense.


> I also run the KPTI images thru our openQA tests
>> <https://openqa.oi.mnowak.cz/tests/overview?distri=openindiana=hipster=20180302-KPTI=1>
>> and there's no problem, nor slowdown (I can say this from comparison with
>> older runs) as well. Host for the tests was the Ivy Bridge-based laptop.
>>
>> So far great experience. Thanks for putting those images and repos
>> together Aurélien.
>>
> :)
>
> Thanks to you for the openQA testing of the images, it is quite impressive
> :)
>
>
>> Michal
>>
>> ___
>> oi-dev mailing list
>> oi-dev@openindiana.org
>> https://openindiana.org/mailman/listinfo/oi-dev
>>
>
>
>
> --
> ---
> Praise the Caffeine embeddings
>
>
> ___
> oi-dev mailing 
> listoi-dev@openindiana.orghttps://openindiana.org/mailman/listinfo/oi-dev
>
>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



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

Re: [oi-dev] KPTI testing images and repository archive uploaded

2018-03-05 Thread Aurélien Larcher
On Mon, Mar 5, 2018 at 8:25 AM, Michal Nowak <mno...@startmail.com> wrote:

> On 03/03/2018 09:13 PM, Aurélien Larcher wrote:
>
> Hi,
> I set up this directory with testing resources:
>
> http://dlc-int.openindiana.org/users/aurelien/kpti/
>
> Live Media, Minimal Text images, and repository as p5p archive are
> provided.
>
> The repository is located at:
>
> pkg.openindiana.org/kpti
>
> Let me know if you encounter any issue.
>
> Kind regards
>
> Aurélien
>
> Hi,
>
> over the weekend I tested KPTI from the repository on Toshiba Satellite
> L855 laptop (Ivy Bridge-based, has PCID). I run many tests from Phoronix
> Test Suite 7.8 there and haven't seen any crash nor any other problem
> (apart from the fact that some tests are not in a good shape for
> OpenIndiana...). With regards to general use of the system, I haven't seen
> any noticeable slowdown.
>
Same experience here :)

I'd be interested in putting PTS to a better shape. Do you have any inital
recipe that I could use for creating a component?
One "old" issue is that PTS runs 32-bit binaries by default for some tests
since it expects /usr/bin to deliver 64-bit executables.

> I also run the KPTI images thru our openQA tests
> <https://openqa.oi.mnowak.cz/tests/overview?distri=openindiana=hipster=20180302-KPTI=1>
> and there's no problem, nor slowdown (I can say this from comparison with
> older runs) as well. Host for the tests was the Ivy Bridge-based laptop.
>
> So far great experience. Thanks for putting those images and repos
> together Aurélien.
>
:)

Thanks to you for the openQA testing of the images, it is quite impressive
:)


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



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

[oi-dev] Xorg 1.19.6

2018-03-04 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] KPTI testing images and repository archive uploaded

2018-03-04 Thread Aurélien Larcher
On Sun, Mar 4, 2018 at 12:02 AM, Andreas Wacknitz <a.wackn...@gmx.de> wrote:

> Am 03.03.18 um 21:13 schrieb Aurélien Larcher:
>
> Hi,
> I set up this directory with testing resources:
>
> http://dlc-int.openindiana.org/users/aurelien/kpti/
>
> Live Media, Minimal Text images, and repository as p5p archive are
> provided.
>
> I have successfully installed from minimal and live media (text install)
> on my HP DL360 G7.
>

Thank you Andreas for testing the images :)
Kind regards,

Aurélien




>
> Regards
> Andreas
>
> The repository is located at:
>
> pkg.openindiana.org/kpti
>
> Let me know if you encounter any issue.
>
> Kind regards
>
> Aurélien
>
> --
> ---
> Praise the Caffeine embeddings
>
>
> ___
> oi-dev mailing 
> listoi-dev@openindiana.orghttps://openindiana.org/mailman/listinfo/oi-dev
>
>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



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

[oi-dev] KPTI testing images and repository archive uploaded

2018-03-03 Thread Aurélien Larcher
Hi,
I set up this directory with testing resources:

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

Live Media, Minimal Text images, and repository as p5p archive are provided.

The repository is located at:

pkg.openindiana.org/kpti

Let me know if you encounter any issue.

Kind regards

Aurélien

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

Re: [oi-dev] KPTI test image and repository

2018-03-02 Thread Aurélien Larcher
On Fri, Mar 2, 2018 at 10:30 PM, Aurélien Larcher <
aurelien.larc...@gmail.com> wrote:

> Hi,
> nothing official yet but I have built and published the KPTI bits to a
> repository:
>
> pkg.openindiana.org/kpti
>
> and generated a minimal install ISO to:
>
> http://ovh.to/cueUkFZ (link valid 10 days from now)
>

I have other images (GUI and USB) but upload to OVH fails repeatedly...
more than ten times now...

Is it possible to get access to a directory to upload them to dlc-int?

I just updated to illumos-kpti on the X230, so far so good.


> --
> ---
> Praise the Caffeine embeddings
>



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

[oi-dev] KPTI test image and repository

2018-03-02 Thread Aurélien Larcher
Hi,
nothing official yet but I have built and published the KPTI bits to a
repository:

pkg.openindiana.org/kpti

and generated a minimal install ISO to:

http://ovh.to/cueUkFZ (link valid 10 days from now)

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

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

2018-02-24 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] [CFT] gcc 6.4.0-built repository available

2018-02-10 Thread Aurélien Larcher
Hi!


> I added support for additional repository to our openQA tests
> 
> and updated several images which had default installation of Live, Server,
> and Minimal variants from last three releases. Although I haven't found any
> dependency issues, four of the seven updates failed shortly after reboot to
> the new BE (which got created automatically as part of the update process).
>

Thank you for doing this, the tool looks very neat :)
I do not know what would explain the failure from older snapshot but at
least it is good to see that the update would succeed for the latest :)

Kind regards

Aurelien


>
> Live  and Server
>  variants of 20161030 release
> failed with: "Unexpected trap. Unexpected trap. Nested trap." (See the
> red-framed screen in each job run for the error message; other screens and
> video in "Logs & Assets" might be helpful too.)
>
> Live  and Server
>  variants of 20170502 release
> failed with:
>
> krtld: error during initial load/link phase
> krtld could neither locate nor resolve symbols for:
> /platform/i86pc/kernel/amd64/unix
> in the boot archive. Please verify that this file
> matches what is found in the boot archive.
> You may need to boot using the Solaris failsafe to fix this.
>
> All variants of the 20171031 release passes just fine: Live
> , Server
> , Minimal
> .
>
> You can reproduce it by downloading the QCOW2 image from "Logs & Assets"
> of a respective job and starting it on Linux KVM (I use QEMU 2.11.0) via:
>
> qemu-img create -f qcow2 OI-20170502-Server.qcow2 -b
> openindiana-hipster-x86_64-20170502-Server@64bit.qcow2
>
> /usr/bin/qemu-system-x86_64 -soundhw ac97 -vga cirrus -global
> isa-fdc.driveA= -m 3072 -cpu qemu64,+xsave -netdev user,id=qanet0 -device
> virtio-net,netdev=qanet0,mac=52:54:00:12:34:56 -device
> virtio-blk,drive=hd1,serial=1 -drive file=OI-20170502-Server.qcow2,
> cache=unsafe,if=none,id=hd1,format=qcow2 -boot order=c -device usb-ehci
> -device usb-tablet -smp 1 -enable-kvm
>
> OS credentials:
> User: robot
> User password: nots3cr3t (root via sudo is password-less)
>
> Michal
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



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

[oi-dev] [CFT] gcc 6.4.0-built repository available

2018-02-07 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Rust lang for oi

2018-02-07 Thread Aurélien Larcher
Hi Carsten,

I could successfull build and package rust for OI
>
> https://github.com/cgrzemba/oi-userland/tree/rust/components
> /developer/rust


Very nice job! :)
Let me know if you want to publish a package to the testing repository
before dealing with the PR.

Kind regards

Aurelien

>
>
> The build of rustc requieres an already working rust compiler.
>
> On my first attempt I pulled the compiler from joyent.
>

> But for subsequent builds we can use our own pre version rustc for stage0
> bootstrap compiler.
>
> I would do some tests and create than an PR.
>
>
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



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

Re: [oi-dev] GCC6 build status

2018-02-03 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] GCC6 build status

2018-02-03 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] GCC6 build status

2018-02-02 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

[oi-dev] GCC 7.3.0

2018-01-25 Thread Aurélien Larcher
Hi,
I have updated the patchset for GCC 7.3.0 and will hopefully be able to
push it this week end if time permits.
Since it contains a Spectre 2 mitigation backport I was wondering if I
should also spin a zone and build oi-userland alongside GCC 6.4.0.
I have not seen any unofficial backport for GCC 6.
Kind regards

Aurelien

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

[oi-dev] List of components for fix

2018-01-22 Thread Aurélien Larcher
Yesterday oi-userland was rebuilt to test the new handling of
REQUIRED_PACKAGES.

The following list of components failed to publish for various reasons:

image/graphviz (ocaml update broke it)
library/clutter-gst
library/qt4
library/qt5
library/trousers (PIE issue again, used to compiled)
multimedia/totem (used to compile but I got a coredump in libgsttheora now)
openindiana/nvidia (runpath issue)
openindiana/slim_source
ruby/augeas
runtime/jruby
runtime/openjdk-7

Kind regards,

Aurelien

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

[oi-dev] GCC6 branch

2018-01-18 Thread Aurélien Larcher
For reference, this branch is built on a daily basis and published to the
gcc-6 repo:

https://github.com/alarcher/oi-userland/tree/gcc6

The branch is rebased any time a PR is merged.
Sometimes the job fails due to some rebase or zone update issue, so the
changes can be published later (when I notice it).

I am busy lately so basically I let the automatic builds run and update
only from time to time.
Kind regards
-- 
---
Praise the Caffeine embeddings
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] Release major

2018-01-18 Thread Aurélien Larcher
On Thu, Jan 18, 2018 at 8:27 AM, Alexander Pyhalov <a...@rsu.ru> wrote:

> On 01/18/18 01:14 AM, Aurélien Larcher wrote:
>
>> Hi,
>> are we bumping release major right away:
>>
>> https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/m
>> ake-rules/ips-buildinfo.mk
>>
>> or are we waiting post gcc-6 migration?
>>
>
> Hi.
> I'd preserved this for time when it's necessary. Perhaps, really, on gcc-6
> migration, to have clear sign - was package recompiled or not.
>

OK, good.

>
> Do you have any time frames?
>

I keep building oi-userland and illumos-gate everyday, it is more a matter
of deciding the different milestones and have a few people to help as I
cannot spend much time on OpenIndiana right now.
I have been running the system with gcc-6 for more than a month now: the
only regression I could see on the desktop is some graphical artifacts in
Firefox, and for the server side I only use nginx + PostgreSQL, nothing to
report.

Your suggestion was to synchronize my repository on top of the current and
call for testing, then in a second stage update the build server with it
and rebuild all the packages.

So for the first step: how many users would be willing to migrate to a
testing gcc-6 built repository?


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



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

[oi-dev] Release major

2018-01-17 Thread Aurélien Larcher
Hi,
are we bumping release major right away:

https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/make-rules/ips-buildinfo.mk

or are we waiting post gcc-6 migration?

a.


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

Re: [oi-dev] OpenJDK 8 version 151?

2018-01-10 Thread Aurélien Larcher
On Wed, Jan 10, 2018 at 3:56 PM, Alexander Pyhalov  wrote:

> On 01/10/18 05:39 PM, Prakash Surya wrote:
>
>> If you're willing to bump it to the new version, that'd be great! If it's
>> not too time consuming, I could try to do it, but I'd need some
>> help/pointers since I've never done any OI packaging work before.
>>
>
> Quick pointers:
> https://wiki.openindiana.org/oi/Building+with+oi-userland
> https://wiki.openindiana.org/oi/oi-userland+-+best+practices
> http://docs.openindiana.org/dev/userland/
>
> I know, all of them are likely a bit outdated, but that's what we have :)


I wrote a bit more in the (slow) process of structuring a maintainer's
guide.

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


>
>
> --
> Best regards,
> Alexander Pyhalov,
> system administrator of Southern Federal University IT department
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



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

Re: [oi-dev] Providing icinga2 package

2017-12-06 Thread Aurélien Larcher
Hello!


> that's the way I'm trying now, after lots of RTFM ;) First test build is
> running now. What's the reason you never published 2.7.2?
>

The main reason is lacking of testing.
We make sure that packages pushed to the main repository are in a good
shape.


>
> > I wrote some additional notes to build a maintainer's guide (work in
> > progress), you can also have a look at it:
> Very helpful, thank you! Lots of information, especially for a newbie
> like me.
>

I can create a wiki account for you if you want to amend some of the
content.
Juste let me know.


> I'm on freenode, too; when I'm getting stuck, I'll ping you all on
> #oi-dev :)
>

Alright :) Good luck!

Kind regards

Aurelien


>
> Cheers,
>   Marianne
>
> --
> https://www.unixe.de/
> https://www.urban-exploring.eu/
>
> ___
> oi-dev mailing list
> oi-dev@openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>



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

Re: [oi-dev] GCC6 build zone status

2017-12-01 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

Re: [oi-dev] GCC6 build zone status

2017-12-01 Thread 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
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev

  1   2   3   4   5   >