Thanks! Sorted.
On Mon, 28 Oct 2019 at 21:04, J. Lewis Muir wrote:
>
> On 10/28, Chavdar Ivanov wrote:
> > After the above message I rebuilt the system and got eventually
> > nvmmctl, which worked. I couldn't start any VM, though, so I proceeded
> > to rebuild wip/qemu-n
After the above message I rebuilt the system and got eventually
nvmmctl, which worked. I couldn't start any VM, though, so I proceeded
to rebuild wip/qemu-nvmm, although there were no changes since my
previous build. This time it worked; I also recreated /dev/nvmm (the
protection changed from 600
Native.
On Sun, 27 Oct 2019 at 16:25, Robert Swindells wrote:
>
>
> Chavdar Ivanov wrote:
> >I do not have MesaLib installed on this v/b guest at all.
>
> Are you running modular or native xorg ?
--
is that on first invocation xfce4 sets use_composing to
true, even if composing is not available or not functional.
On Sun, 27 Oct 2019 at 02:24, wrote:
>
> On Sun, Oct 27, 2019 at 01:30:48AM +0100, Chavdar Ivanov wrote:
> > In my case its also swrast_dri, VirtualBox host. I haven't recent
In my case its also swrast_dri, VirtualBox host. I haven't recently
tried xfce4 on a real hardware with intel, I might di that later.
On Sat, 26 Oct 2019 at 19:25, David H. Gutteridge wrote:
>
> On Sat, 2019-10-26 at 00:40 +, m...@netbsd.org wrote:
> > Can someone who has this issue explain
I've rebuilt my -current system a few hours ago, followed by a build
of wip/qemu-nvmm, I see now at 4.1.
So far everything seems to be working as expected.
BTW I have been getting - on all my qemu-nvmm builds from wip - a PLIST error -
share/locale/bg/LC_MESSAGES/qemu.mo
I also have xfwm4 crash, but only if there is .config/xfce4 directory.
So far if I remove it, xfce4 works fine. Otherwise the trace appeared
similar to the above.
On Wed, 16 Oct 2019 at 11:03, David H. Gutteridge wrote:
>
> On Tue, 15 Oct 2019, at 12:00:42 +0100, Robert Swindells wrote:
> > I
My amd64 build also failed with
...
src/tests/lib/libnvmm/h_mem_assist.c:178:2: error: missing initializer
for field 'off' of 'const struct test'
[-Werror=missing-field-initializers]
...
(and many more).
On Sun, 13 Oct 2019 at 23:48, matthew green wrote:
>
> Robert Swindells writes:
> >
> >
I just did a quick comparison on a 9.99.16 amd64 VirtualBox guest
between firefox 69.0.2 and the latest versions of epiphany and midori.
All of them seem to work reasonably well, but firefox is the most
usable, in terms of reaction to clicks, updates and overall behaviour.
I tried Google maps with
On Fri, 11 Oct 2019 at 20:21, nia wrote:
>
> On Fri, Oct 11, 2019 at 11:05:57AM -0700, bch wrote:
> > I quit running Firefox on my (-current) laptop months ago because the build
> > process (rust, esp) was so brutal. Have there been any community efforts to
> > organize the build artifacts from
e.
I also build -current nightly (and then routinely update it using
sysupdate), plus I run a few - up to 5 at a time - nvmm virtual
machines on this box, which use zvols as a backend...
Your mileage may vary, as they say.
On Fri, 11 Oct 2019 at 19:06, bch wrote:
>
>
>
> On Fri, Oct 11,
I wouldn't bother chasing this. My firefox 69.0.2 runs perfectly well
under 9.99.15, so I'd rebuild. You would need rust 1.38 though, my
build failed with 1.37.
There were some rather substantial changes in the last few versions.
On Fri, 11 Oct 2019 at 17:40, Sad Clouds wrote:
>
> On Fri, 11
I noticed wip/mono6 has been removed, the other mono packages use
earlier versions. Any particular reasons for this worth knowing?
On Tue, 13 Aug 2019 at 09:50, wrote:
>
> wip/mono6 should be a replacement that works on netbsd.
> (still some issues to fix, like LD_LIBRARY_PATH=/usr/X11R7/lib for
Thanks, it's fine. I didn't add 'zfs=YES' to /etc/rc.conf as running
'/etc/rc.d/zfs start' without it did not produce the usual warning of
undefined variable.
On Mon, 16 Sep 2019 at 12:21, Brad Spencer wrote:
>
> Chavdar Ivanov writes:
>
> > Since yesterday I don't get my z
Since yesterday I don't get my zfs fule systems automatically mounted,
I have to issue 'zfs mount -a'.
Should I add some entry in /etc/fstab or place the above command in
one of the scripts?
The zvols are accessible as usual.
On Sat, 7 Sep 2019 at 14:54, Brad Spencer wrote:
>
> m...@netbsd.org
On Thu, 15 Aug 2019 at 15:12, wrote:
>
> On Thu, Aug 15, 2019 at 02:50:52PM +0100, Chavdar Ivanov wrote:
> > BTW I just noticed there are no gnome packages in
> > /usr/pkgsrc/meta-packages any more, while there are still some in x11
> > directory - was there any announce
BTW I just noticed there are no gnome packages in
/usr/pkgsrc/meta-packages any more, while there are still some in x11
directory - was there any announce that it has been phased out?
On Thu, 15 Aug 2019 at 13:09, Chavdar Ivanov wrote:
>
> It actually is a part of the package:
>
ig", 0,
0xff8295b8) Err#2 ENOENT
so there is the directory name twice, in reality the installation
places the file in /usr/pkg/etc/mono/config.
# cd /usr/pkg/etc/mono ; ln -s . mono
sorts it.
On Wed, 14 Aug 2019 at 20:14, wrote:
>
> On Tue, Aug 13, 2019 at 12:00:31PM +0100, Chavda
07d] in :0
--- End of inner exception stack trace ---
at Mono.Driver.Main (System.String[] args) [0x00010] in
:0
LD_LIBRARY_PATH=/usr/X11R7lib in the environment did not make a difference.
On Tue, 13 Aug 2019 at 09:18, Chavdar Ivanov wrote:
>
> Thanks, I didn't have it yer in my wip clone, I pulle
Thanks, I didn't have it yer in my wip clone, I pulled it and am
trying to build now.
On Tue, 13 Aug 2019 at 09:50, wrote:
>
> wip/mono6 should be a replacement that works on netbsd.
> (still some issues to fix, like LD_LIBRARY_PATH=/usr/X11R7/lib for
> graphical stuff being necessary)
--
Hi,
I haven't been able to build lang/mono on -current ( or elsewhere, for
that matter ) for quite some time. I tend to try periodically on
version jumps and pkgsrc updates to build it - not that I have a
particular use for it, but for the bits needed by gnome.
The failure I got this time was of
Lately, perhaps the last 4-5 Firefox and rust builds, I have never had a
single failure. Also I haven’t seen yet a llvm build failure on this
machine.
It’s a 20gb laptop, but I always use make_jobs 1. So perhaps it is indeed a
resource problem.
On Fri, 2 Aug 2019 at 09:31, Chavdar Ivanov wrote
I used to get this a lot weeks or months ago
On Fri, 2 Aug 2019 at 09:07, Martin Husemann wrote:
> On Thu, Aug 01, 2019 at 04:27:29PM -0700, Hisashi T Fujinaka wrote:
> > Oh, duh, I think I remember that the real issue is that you can't run as
> > many $JOBS. Before it would be better about
Hi,
FYI VirtualBox guest cleanly compiles and apparently works under
9.0-BETA; in this case I used fresh svn update:
...
Starting local daemons:12:58:44.643043 main VBoxService 6.0.97
r80012 (verbosity: 0) netbsd.amd64 (Aug 1 2019 13:54:41) release log
12:58:44.643086 main Log opened
On Tue, 30 Jul 2019 at 18:00, Martin Husemann wrote:
>
> On Tue, Jul 30, 2019 at 04:50:19PM +0100, Chavdar Ivanov wrote:
> > The releng build from yesterday still has /bin/tar hard-linked to
> > /bin/cpio.
>
> Which build is that? Maybe you used the .../latest/ symlink and
On Tue, 30 Jul 2019 at 16:48, Martin Husemann wrote:
>
> On Tue, Jul 30, 2019 at 10:44:07PM +0700, Robert Elz wrote:
> > Check your mk.conf and whatever you use to generate builds.
> > If anything has MKBSDTAR=yes that would explain it. The default
> > (and so what the releng builds use), is
got bsdtar in place of the usual one.
On Tue, 30 Jul 2019 at 14:09, Joerg Sonnenberger wrote:
>
> On Tue, Jul 30, 2019 at 10:51:11AM +0100, Chavdar Ivanov wrote:
> > GNU tar reports the extended header and does not restore it by default - the
> > file can be unlinked:
> >
upstream TeXmacs
distribution file. I haven't dealt so far with extended headers and am
apparently somewhat confused where the problem lies.
Chavdar Ivanov
--
Hi,
NFS server - 8.99.51 amd64, /etc/exports contains:
/home/sysbuild/release -maproot=0:10 -network 192.168.0/24
NFS client - an hour ago it was 8.99.50 from about a week ago and worked
fine, I was able to NFS mount the release directory and perform the
usual sysupgrade dance.
Now the client
It builds with the following two patches (the first one almost
certainly wrong, although the result appears to be working):
.
--- ./src/VBox/Runtime/common/path/RTPathAbsEx.cpp.ORIG2019-07-20
11:55:09.661784205 +0100
+++ ./src/VBox/Runtime/common/path/RTPathAbsEx.cpp 2019-07-20
, Chavdar Ivanov wrote:
>
> Hi,
>
>
> On fresh -current I am getting:
>
>
>
> checking for swig... /usr/pkg/bin/swig
> checking swig version... 1.3.38
> configure: Configuring python swig binding
> checking for Python includes... -I/usr/pkg/include/pytho
Hi,
On fresh -current I am getting:
checking for swig... /usr/pkg/bin/swig
checking swig version... 1.3.38
configure: Configuring python swig binding
checking for Python includes... -I/usr/pkg/include/python3.7
checking for compiling Python extensions... gcc -pthread -fPIC
checking for
strike that down, bad update (there was a panic after sysupgrade,
before reboot; subsequent sysupgrade fixed it).
On Thu, 20 Jun 2019 at 19:31, Chavdar Ivanov wrote:
>
> However, on 8.99.47, I am stuck:
> ..
> gcc -Wl,-rpath /usr/X11R7/lib -m64 -o
> /p/Virtu
: ***
[/p/VirtualBox-6.0.8/out/netbsd.amd64/release/obj/VBoxClient/VBoxClient]
Error 1
No idea what this is .
On Thu, 20 Jun 2019 at 08:21, Chavdar Ivanov wrote:
>
> He has done it already.
>
> On Thu, 20 Jun 2019 at 09:10, wrote:
> >
> > On Wed, Jun 19, 2019 at 06:55:06PM +01
He has done it already.
On Thu, 20 Jun 2019 at 09:10, wrote:
>
> On Wed, Jun 19, 2019 at 06:55:06PM +0100, Chavdar Ivanov wrote:
> > ---
> > /p/VirtualBox-6.0.8/src/VBox/Additions/common/VBoxGuest/VBoxGuest-netbsd.c.ORIG
> >2019-06-19 19:48:40.880337377 +0100
&g
. Not that I personally use it, but there are gnome
bits dependend on it ( which I currently comment out ).
On Wed, 19 Jun 2019 at 05:03, wrote:
>
> On Tue, Jun 18, 2019 at 10:02:47PM +0100, Chavdar Ivanov wrote:
> > Hi,
> >
> > Perhaps not for current-users@, but
---
/p/VirtualBox-6.0.8/src/VBox/Additions/common/VBoxGuest/VBoxGuest-netbsd.c.ORIG
2019-06-19 19:48:40.880337377 +0100
+++ /p/VirtualBox-6.0.8/src/VBox/Additions/common/VBoxGuest/VBoxGuest-netbsd.c
2019-06-19 19:48:51.063261324 +0100
@@ -1011,7 +1011,7 @@
error =
Hi,
Perhaps not for current-users@, but on yesterday's -current and with
updated pkgsrc I get the following while building lang/mono:
.
@ymir - /usr/pkgsrc/lang/mono/work/mono-4.0.4/mono/mini -
gdb /usr/bin/ld ld.core
GNU gdb (GDB) 8.3
...
Reading symbols from /usr/bin/ld...
(No debugging
Cool, thanks!
On Tue, 18 Jun 2019 at 21:01, wrote:
>
> On Tue, Jun 18, 2019 at 07:58:07PM +0100, Chavdar Ivanov wrote:
> > /usr/X11R7/lib/pkgconfig/gl.pc file contains:
> >
> > Libs: -Wl,-rpath,${libdir} -L${libdir} -l@GL_PKGCONF_LIB@
> >
> >
>
/usr/X11R7/lib/pkgconfig/gl.pc file contains:
Libs: -Wl,-rpath,${libdir} -L${libdir} -l@GL_PKGCONF_LIB@
There are quite a few packages which fail with the default pkgsrc
setup because of that.
Perhaps the variable GL_PKGCONF_LIB should be defined somewhere? I
guess this depends on
Not any more, I just finished one.
On Mon, 17 Jun 2019 at 19:45, Andreas Gustafsson wrote:
>
> The build is still failing as of source date 2019.06.17.16.34.02:
>
> -- kern-INSTALL ---
> /tmp/bracket/build/2019.06.17.16.34.02-i386/tools/bin/i486--netbsdelf-ld:
> chfs_vfsops.o: in function
I managed to test it already - 8.99.43 installation went fine on a
XCP-NG guest, no screen problems whatsoever.
On Sun, 9 Jun 2019 at 17:12, David Brownlee wrote:
>
> On Sun, 9 Jun 2019 at 09:00, Brett Lymn wrote:
> >
> > On Sat, Jun 08, 2019 at 01:25:24AM +0300, Valery Ushakov wrote:
> > >
> >
I just had the same installing a -current guest under XCP-NG; I
thought there was some problem with the screen emulation, though. I
did manage to complete the installation, as despite the wrong display
overall, the current line is shown correctly and one is able to select
whatever choices one
My HP Envy laptop boots NetBSD-current in EFI mode for quite some time
now, perhaps a year. The GeForce 950M doesn't work, as expected, but
the Intel 530 now works perfectly fine with full 3D acceleration and
quite decent full screen video.
On Wed, 5 Jun 2019 at 20:32, Frank Kardel wrote:
>
>
На 2019-06-01 в 12:33, Kamil Rytarowski написа:
> On 01.06.2019 12:01, matthew green wrote:
>> so, i just updated a few X11 packages in -current. as part
>> of testing, i ran them on the sandy bridge laptop i've seen
>> display glitches with the new intel driver on (mate-terminal).
>>
>> these
На 2019-05-31 в 08:05, matthew green написа:
>> I don't seem to be able to get the core into gdb 8.3 either with target
>> kvm or with target kcore. How does one do this now with this version of
>> gdb?
> christos put the 'target kvm' support back in today.
> update and rebuild gdb and it should
Hi,
Forget about this thread - replacing 'asm' with '__asm' in cpufunc.h
solves the problem, as was indeed mentioned above. VirtualBox
extensions compile ok.
On Fri, 31 May 2019 at 08:11, Chavdar Ivanov wrote:
>
> On Fri, 31 May 2019 at 02:07, Joerg Sonnenberger wrote:
> >
> &
On Fri, 31 May 2019 at 02:07, Joerg Sonnenberger wrote:
>
> On Thu, May 30, 2019 at 09:32:24PM +0100, Chavdar Ivanov wrote:
> > error: 'asm' undeclared (first use in this function)
> > asm volatile ("pause");
> > ^~~
> > ...
> >
Hi,
That was badly described. It is not just hal crash, it is NetBSD panic
when hal is starting. Obvious from the trace, but still.
On Thu, 30 May 2019 at 14:49, Chavdar Ivanov wrote:
>
> Hi,
>
>
> I got a repeatable crash of hal under 8.99.42; running ok under 8.99.41
> from
Hi,
I got a repeatable crash of hal under 8.99.42; running ok under 8.99.41
from the 27th of May. I have disabled hal for the moment. The dmesg of
the panic looks as follows:
...
[ 34.627608] acpibat0: normal capacity on 'charge state'
[ 66.605334] fatal protection fault in supervisor
- should I continue to locally modify
cpufunc.h from the NetBSD src/sys/arch/x86/include/ ? What is the
purpose of having 'asm volatile' if __asm__ does the job (and volatile
is a NOP anyway, according to the gcc manual, it is considered
volatile without the keyword)?
On Sun, 12 May 2019 at 20:5
На 2019-05-30 в 12:56, Martin Husemann написа:
> On Thu, May 30, 2019 at 12:25:42PM +0100, Chavdar Ivanov wrote:
>>> Michael looked into it, and it seems to be code bugs (calculating the
>>> edit field sizes and border coordinates). It is not just resource changes.
>&g
On Thu, 30 May 2019 at 09:29, Martin Husemann wrote:
>
> On Wed, May 29, 2019 at 06:15:52PM -, Christos Zoulas wrote:
> > >> - we have very obvious display bugs at first sight in xdm
> > >
> > >let's revert to the old xdm for now. this one should be easy.
> > >can someone work on it please?
Hi,
with sources updated an hour or so ago I get:
..
/home/sysbuild/amd64/tools/bin/nbmakefs -M 1475346432 -m 1475346432
-B 1234 -F
work.spec -N w
ork/etc
-o bsize=16384,fsize=2048,density=8192
My two pennies...
I use -current on an HP Envy 17 with what is reported as Intel 530
graphics. It also has an NVidia GeForce 950M chip, but this is not
usable for now by NetBSD, although correctly identified. The new
graphics driver together with the Mesa updates finally got me with a
proper
На 2019-05-12 в 07:34, Kamil Rytarowski написа:
> On 12.05.2019 08:09, Martin Husemann wrote:
>> On Sat, May 11, 2019 at 11:25:42PM +0100, Chavdar Ivanov wrote:
>>> There is definitely some recent problem with the new Intel driver. A few
>>> days ago, still under 8
:
>
> On Sat, May 11, 2019 at 11:25:42PM +0100, Chavdar Ivanov wrote:
> > There is definitely some recent problem with the new Intel driver. A few
> > days ago, still under 8.99.37, it worked very well for me (Intel 530).
> > glmark2 completed with no problems, videos were played as
На 2019-05-11 в 06:10, Kamil Rytarowski написа:
> On 11.05.2019 04:54, Kamil Rytarowski wrote:
>> On 10.05.2019 08:29, matthew green wrote:
>>> this is probably the recently discussed intel driver issues.
>>> i've added a build option to use the older driver.
>>>
>>> can you try build with
tion is fine.
On Fri, 10 May 2019 at 20:47, Mayuresh wrote:
>
> On Fri, May 10, 2019 at 08:25:45PM +0100, Chavdar Ivanov wrote:
> > You are using very old VirtualBox version from pkgsrc/wip. This is
> > something I haven't bothered ever to try. I download the source from
>
You are using very old VirtualBox version from pkgsrc/wip. This is
something I haven't bothered ever to try. I download the source from
VirtualBox and build it myself. All you need is kbuild and yasm and
LocalConfig.kmk with the following contents:
...
VBOX_WITHOUT_HARDENING := 1
I had the same. Changed the emulated device to Intel audio, now it boots OK.
On Fri, 10 May 2019 at 18:56, Christoph Badura wrote:
>
> Yesterday I tried booting an amd64 install iso from sources updated
> around 16:00 UTC under virtualbox 6.0.6. The kernel paniced with
> panic:
Sure, although the last time I did this was months ago.
On Fri, 10 May 2019 at 02:29, Mayuresh wrote:
> On Thu, May 09, 2019 at 09:43:10PM +0100, Chavdar Ivanov wrote:
> > While The said version compiles cleanly under 8.99.37 (I did it a few
> > days ago), today under 8.99.39
I haven't tested if this happens on NetBSD8, on -current every time I
reinstall x11-lnks (after osabi, hence on every bump of -current), I
have to:
--- /usr/pkg/share/x11-links/lib/pkgconfig/gl.pc.ORIG 2019-05-09
19:52:57.141922336 +0100
+++ /usr/pkg/share/x11-links/lib/pkgconfig/gl.pc
Hi,
While The said version compiles cleanly under 8.99.37 (I did it a few
days ago), today under 8.99.39 it fails for me as follows:
/p/VirtualBox-6.0.6/out/netbsd.amd64/release/obj/netbsd/include/x86/cpufunc.h:
In function 'x86_pause':
На 2019-04-29 в 18:34, John D. Baker написа:
> I managed to fire up another machine w/intel graphics I have. It uses:
>
> [...]
> i915drmkms0 at pci0 dev 2 function 0: Intel 82946GZ Integrated Graphics
> Device (rev. 0x02)
> [...]
> kern info: [drm] Memory usable by graphics device = 512M
>
Update - it now works fine for me.
On Tue, 23 Apr 2019 at 17:35, Piotr Meyer wrote:
>
> On Wed, Apr 17, 2019 at 01:13:50PM +0100, Chavdar Ivanov wrote:
> [...]
>
> > The problem I am having is with NetBSD-current, amd64. I am able to
> > install it and run it with t
Hi,
A couple of days ago I built wip/qemu-nvmm to find out if I can use
this setup instead of xen on one particular laptop I have in use now.
Cudos to this - my initial tries were very promising, I think I can
easily run some 8-10 VMs on this hardware. I installed a couple of
Linux distributions
FYI I just rebuilt go112 using updated go14 as a bootstrap on two days
old amd64 -current.
On Mon, 15 Apr 2019 at 12:58, Benny Siegert wrote:
>
> Try rebuilding lang/go14 perhaps?
>
> You could also try editing lang/go112/Makefile and setting
> GOROOT_BOOTSTRAP to /usr/pkg/go111.
>
> On Sun, Apr
With these two settings now kdm, xdm and slim work as expected;
previously the username and the password echo did not show properly.
Now my Intel graphics works rather well. I get hangs only when I run
some of the xscreensaver demos in full screen mode, rendering the
mouse/keyboard unresponsive -
Please don't be so quick reverting the Intel driver. With today's build my
laptop is working very well, I have no visible effects, glmark2 executes as
expected with the exception of the crash upon exit, Kde4 was previously
crashing on testing the gl capability, now everything works. Great work, in
I have on occasion similar behaviour on my HP Envy laptop using the
530 graphics, it is rather weird. I also get the messages about not
being able to load the two microcode files, even if I have placed them
in the right location.
On Thu, 11 Apr 2019 at 21:31, Ron Georgia wrote:
>
> My monitor is
FYI glmark2 ran rather well under VirtualBox a moment ago with a few
hours old system, only crashing on exit:
...
Reading symbols from /usr/pkg/bin/glmark2...done.
[New process 1]
[New process 4]
Core was generated by `glmark2'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0
Hi,
On a VirtualBox guest running amd64 -current as of 2-3 hours ago with
the builtin vboxvideo driver I get now:
[87.285] (II) AIGLX: Screen 0 is not DRI2 capable
[87.327] (EE) AIGLX error: dlopen of
/usr/X11R7/lib/modules/dri/swrast_dri.so failed
Very similar experience with kdm in the same environment. Click on the
username, enter it, nothing apperas. Click on the password, enter it,
ditto. Press Enter, and you are in. If you mistype a password, second
time the username is displayed correctly. So far the best experience
has been starting
Just FYI - I am getting the same message whe starting kde4's konqueror:
There was an error loading the module Dolphin View.
The diagnostics is:
Cannot load library /usr/pkg/lib/kde4/dolphinpart.so:
(/usr/X11R7/lib/libGL.so.3: Use of initialized Thread Local Storage
with model initial-exec and
I've files pkg/54105.
On Mon, 8 Apr 2019 at 09:51, Chavdar Ivanov wrote:
>
> OK, I will file a PR against openjade.
>
> On Mon, 8 Apr 2019 at 08:18, Martin Husemann wrote:
> >
> > On Sun, Apr 07, 2019 at 08:21:07PM +0100, Chavdar Ivanov wrote:
> > > :
>
OK, I will file a PR against openjade.
On Mon, 8 Apr 2019 at 08:18, Martin Husemann wrote:
>
> On Sun, Apr 07, 2019 at 08:21:07PM +0100, Chavdar Ivanov wrote:
> > :
> > /home/sysbuild/src/external/bsd/jemalloc/lib/../dist/src/arena.c:271:
> > Failed assertion: "
Hi,
I get:
.
-> Building pdf output
[Checking tools for typesetting...OK]
env SP_ENCODING=iso-8859-1 SGML_CATALOG_FILES= openjade -d
/usr/pkgsrc/doc/guide/work/pkgsrc-guide-20190407/share/default.dsl -c
/usr/pkgsrc/doc/guide/work/pkgsrc-guide-20190407/share/catalog -c
I was able to do a full build with a cvs update some 7 hours ago.
Built-in Xorg is fine with AIGLX enabled now.
On Sat, 6 Apr 2019 at 15:31, Patrick Welche wrote:
>
> On Sat, Apr 06, 2019 at 02:42:57PM +0100, Patrick Welche wrote:
> > On Sat, Apr 06, 2019 at 05:18:58AM +1100, matthew green
and XFCE4, but works OK under ctwm. Go figure...
On Mon, 1 Apr 2019 at 07:42, Chavdar Ivanov wrote:
>
> The patch applied cleanly and the subsequent build finished. However,
> the resulting Xorg does not even load GLX now:
> ...
> [ 412.701] (II) Loading /usr/X11R7/lib/modules/exten
/extensions/libglx.so: Undefined symbol
"glXGetProcAddressARB" (symnum = 492)
Maybe I was wrong to build this with '-u', I might try a full build later.
On Sun, 31 Mar 2019 at 22:00, Chavdar Ivanov wrote:
>
> Thanks, I'll check it out right away.
>
> Chavdar
>
>
Thanks, I'll check it out right away.
Chavdar
On Sun, 31 Mar 2019 at 21:21, matthew green wrote:
>
> > Is there anything I might be missing or our built-in Xorg is lacking
> > for this hardware?
>
> this may be old Mesa on your intel GPU not supporting that.
>
> we're very close to switching
Hi,
On the same hardware (HP Envy 17, Intel 530 + NVidia 950m) I have two
different installations, one using built-in Xorg, the other - Modular.
The rest of the system is identical - kernel and userland - from a
couple of days ago. The modular Xorg packages were built by a separate
-current
Hi,
Has anyone tried to run amd54 - current under VirtualBox, but using
modular Xorg, instead of the in-tree X? I built today the latest
version from Xorg and can't ficure out what to do with the mouse
driver. The graphics part of it works OK, although I can't yet
resizing to work (xrandr lets me
xentools411 builds fine now. Next I might try it with the new ocaml from wip.
On Sat, 16 Mar 2019 at 16:39, Manuel Bouyer wrote:
>
> On Sat, Mar 16, 2019 at 04:43:43PM +0200, Andreas Gustafsson wrote:
> > Martin Husemann wrote:
> > > IMO the most stupid warning ever added to gcc. I would just
Indeed works now. Thanks.
On Sat, 16 Mar 2019 at 21:18, Rin Okuyama wrote:
>
> On 2019/03/17 1:08, Chavdar Ivanov wrote:
> > Still doesn't work for me with
>
> Puzzling...
>
> > (talking about doc/guide). And neither does emacs-git, I am getting:
> >
Still doesn't work for me with
> uname -a
NetBSD ymir 8.99.35 NetBSD 8.99.35 (GENERIC) #7: Sat Mar 16 13:57:26
GMT 2019
sysbuild@ymir:/home/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/GENERIC
amd64
(talking about doc/guide). And neither does emacs-git, I am getting:
CCLD
ld it on amd64 -current as of yesterday.
>
> Are you sure this fix is applied?
> http://cvsweb.netbsd.org/bsdweb.cgi/src/external/bsd/jemalloc/dist/src/jemalloc.c#rev1.7
>
> Thanks,
> rin
>
> On 2019/03/16 20:55, Chavdar Ivanov wrote:
> > On yesterdays amd64 -
On yesterdays amd64 -current and fully updated pkgsrc, trying to build
doc/guide I get:
..
Writing HTML.manifest
-> Building ascii output
[Checking tools for typesetting...OK]
/usr/bin/sed -e 's/[01];/"/g' pkgsrc.html > pkgsrc.tmp.html
/usr/pkg/bin/w3m -dump -O iso-8859-1 -no-graph
Hi,
On today's -current amd64:
gmake[2]: Entering directory
'/usr/pkgsrc/sysutils/xentools411/work/xen-4.11.1/tools'
/usr/pkg/bin/gmake -C xenpmd all
gmake[3]: Entering directory
'/usr/pkgsrc/sysutils/xentools411/work/xen-4.11.1/tools/xenpmd'
gcc -I/usr/pkg/include -I/usr/include
That makes perfect sense. I'll rebuild it without this flag.
On Thu, 14 Mar 2019 at 12:21, Geoff Wing wrote:
>
> On Thursday 2019-03-14 10:57 +, ci4...@gmail.com output:
> :Well, after installing the unstripped zsh+modules and ncurses, I no
> :longer get zsh any crashes. Plus, as I
Well, after installing the unstripped zsh+modules and ncurses, I no
longer get zsh any crashes. Plus, as I mentioned, there was some
jemalloc updates a couple of days ago. Hence, no idea.
On Thu, 14 Mar 2019 at 05:23, matthew green wrote:
>
> > (while none I have ever seen actually do, the
> >
Awesome, thanks! That's a thing which pops up from time to time, I've
had it myself.
On Wed, 13 Mar 2019 at 15:04, Patrick Welche wrote:
>
> On Tue, Mar 12, 2019 at 05:17:10PM +, Chavdar Ivanov wrote:
> > /etc/ttys ?
>
> Absolutely right. This laptop's xdm worked befor
s/gor/got/.
On the other hand there were some jemalloc changes overnight, so I
will update the system first and then try to get zsh crashes.
On Wed, 13 Mar 2019 at 11:32, Chavdar Ivanov wrote:
>
> Setting INSTALL_UNSTRIPPED=yes didn't work for me for zsh and ncurses,
> I still had to
sets.
On Wed, 13 Mar 2019 at 10:23, Chavdar Ivanov wrote:
>
> Thanks. One has to read the manuals from time to time...
>
> On Wed, 13 Mar 2019 at 10:21, Patrick Welche wrote:
> >
> > On Wed, Mar 13, 2019 at 10:06:42AM +, Chavdar Ivanov wrote:
> > > I saw the one
Thanks. One has to read the manuals from time to time...
On Wed, 13 Mar 2019 at 10:21, Patrick Welche wrote:
>
> On Wed, Mar 13, 2019 at 10:06:42AM +, Chavdar Ivanov wrote:
> > I saw the one with the trashed history as well.
> >
> > I don't think it is zsh's problem
OK, I understand. I should carry on using it to see if it will break
again and perhaps get something useful.
On Wed, 13 Mar 2019 at 10:09, Martin Husemann wrote:
>
> On Wed, Mar 13, 2019 at 10:06:42AM +, Chavdar Ivanov wrote:
> > I saw the one with the trashed history as wel
, which is one of the failing ones.
On Tue, 12 Mar 2019 at 21:58, Thomas Klausner wrote:
>
> On Tue, Mar 12, 2019 at 03:33:26PM +, Chavdar Ivanov wrote:
> > On amd64 -curent from yesterday (and a couple of days earlier) I
> > started to get zsh crashes when tab-completing (
/etc/ttys ?
On Tue, 12 Mar 2019 at 16:32, Patrick Welche wrote:
> Had a go with the shiny new X (thanks!) on the sandy bridge laptop
> which no longer likes SNA but works with UX, and xdm seems to sit
> at the prompt waiting for something:
>
> #0 0x7f7ff344285a in poll () from
Hi,
On amd64 -curent from yesterday (and a couple of days earlier) I
started to get zsh crashes when tab-completing (files, directories,
packages), similar to
.
Core was generated by `zsh'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7cf050211540 in permmatches ()
401 - 500 of 687 matches
Mail list logo
