(Fixed) Re: Thunderbird package missing

[Graham Menhennitt]

On 14/12/20 10:03 pm, Graham Menhennitt wrote:

Hello all,
I did a pkg upgrade yesterday and it removed my Thunderbird package.
When I go to install it, I get "No packages available to install
matching 'thunderbird'. I've tried it on two separate systems with the
same result. What's going on?



This is fixed now - the package thunderbird-78.5.1 is available.

Thanks,

Graham

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Thunderbird package missing

[Graham Menhennitt]

Hello all,
I did a pkg upgrade yesterday and it removed my Thunderbird package. 
When I go to install it, I get "No packages available to install 
matching 'thunderbird'. I've tried it on two separate systems with the 
same result. What's going on?


Thanks,
Graham
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: starting virtual box VM instantly crashes FreeBSD after upgrade from 11 to 12

[Graham Menhennitt]

Thanks very much Nikita - that fixed it. Surely this deserves a mention 
in ports/UPDATING and pkg-message.


Thanks again,
    Graham

On 2/4/19 11:27 pm, Nikita Druba wrote:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230460
"turn on VIMAGE support in virtualbox-ose-kmod" Working for me.
Good luck.

02.04.2019 09:53, Graham Menhennitt пишет:
Thanks for replying. Yes I rebuilt and installed virtualbox-ose and 
virtualbox-ose-kmod. The files in /boot/modules are the newly built 
ones. I have rebooted after installing them.


Thanks,
 Graham

On 2/4/19 4:46 pm, Koichiro Iwao wrote:

Hi,

did you rebuild virtualbox-ose-kmod?

On Tue, Apr 02, 2019 at 04:04:49PM +1100, Graham Menhennitt wrote:

Hello all,

I recently upgraded my desktop box from 11-Stable to 12-Stable via 
source.
I've rebuilt and installed the 5.2.26 virtualbox-ose and 
virtualbox-ose-kmod
ports from scratch and made sure that no traces of older versions 
exist.


I start the VirtualBox GUI successfully and see the table of my VMs. I
select one of them and start it and FreeBSD instantly crashes. My 
screen

goes blank and eventually FreeBSD reboots.

The only thing I can see in my /var/log/messages is:

   Apr  2 15:07:14 starker kernel: vboxdrv:  VMMR0.r0
   Apr  2 15:07:14 starker kernel: vboxdrv:  
VBoxDDR0.r0


after the crash and just before the reboot sequence.

I can't see anything in /usr/ports/UPDATING that's relevant. It was 
all

working correctly under 11-Stable.

Does anybody have any clues, please? How can I diagnose further? 


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: starting virtual box VM instantly crashes FreeBSD after upgrade from 11 to 12

[Graham Menhennitt]

Thanks for replying. Yes I rebuilt and installed virtualbox-ose and 
virtualbox-ose-kmod. The files in /boot/modules are the newly built 
ones. I have rebooted after installing them.


Thanks,
    Graham

On 2/4/19 4:46 pm, Koichiro Iwao wrote:

Hi,

did you rebuild virtualbox-ose-kmod?

On Tue, Apr 02, 2019 at 04:04:49PM +1100, Graham Menhennitt wrote:

Hello all,

I recently upgraded my desktop box from 11-Stable to 12-Stable via source.
I've rebuilt and installed the 5.2.26 virtualbox-ose and virtualbox-ose-kmod
ports from scratch and made sure that no traces of older versions exist.

I start the VirtualBox GUI successfully and see the table of my VMs. I
select one of them and start it and FreeBSD instantly crashes. My screen
goes blank and eventually FreeBSD reboots.

The only thing I can see in my /var/log/messages is:

   Apr  2 15:07:14 starker kernel: vboxdrv:  VMMR0.r0
   Apr  2 15:07:14 starker kernel: vboxdrv:  VBoxDDR0.r0

after the crash and just before the reboot sequence.

I can't see anything in /usr/ports/UPDATING that's relevant. It was all
working correctly under 11-Stable.

Does anybody have any clues, please? How can I diagnose further?

Thanks in advance for any help.

Graham

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"



___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

starting virtual box VM instantly crashes FreeBSD after upgrade from 11 to 12

[Graham Menhennitt]

Hello all,

I recently upgraded my desktop box from 11-Stable to 12-Stable via 
source. I've rebuilt and installed the 5.2.26 virtualbox-ose and 
virtualbox-ose ports from scratch and made sure that no traces of older 
versions exist.


I start the VirtualBox GUI successfully and see the table of my VMs. I 
select one of them and start it and FreeBSD instantly crashes. My screen 
goes blank and eventually FreeBSD reboots.


The only thing I can see in my /var/log/messages is:

  Apr  2 15:07:14 starker kernel: vboxdrv:  VMMR0.r0
  Apr  2 15:07:14 starker kernel: vboxdrv:  VBoxDDR0.r0

after the crash and just before the reboot sequence.

I can't see anything in /usr/ports/UPDATING that's relevant. It was all 
working correctly under 11-Stable.


Does anybody have any clues, please? How can I diagnose further?

Thanks in advance for any help.

Graham

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Any clues on Bug 230053 - emulators/virtualbox-ose 5.2.16 failed to build?

[Graham Menhennitt]

On 21/11/18 10:11 am, Jung-uk Kim wrote:

On 18. 11. 20., Graham Menhennitt wrote:

G'day all,

Does anybody have any clues on how to fix/workaround Bug 230053 -
emulators/virtualbox-ose 5.2.16 failed to build?

I've build VBox many times in the past but have just got this error.


In file included from
/usr/ports_build/usr/data/FreeBSD/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.22/src/recompiler/cpu-exec.c:30:

/usr/ports_build/usr/data/FreeBSD/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.22/src/recompiler/target-i386/exec.h:41:38:
error: register 'r14' unsuitable for global register variables on this
target
register struct CPUX86State *env asm(AREG0);
  ^
/usr/ports_build/usr/data/FreeBSD/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.22/src/recompiler/dyngen-exec.h:81:15:
note: expanded from macro 'AREG0'
#define AREG0 "r14"
   ^

Any ideas?

It looks like you built devel/kBuild without GCC option.

Jung-uk Kim


Yep, thanks. That was the problem - all working now.

Thanks again,

    Graham

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Any clues on Bug 230053 - emulators/virtualbox-ose 5.2.16 failed to build?

[Graham Menhennitt]

On 21/11/2018 10:11 am, Jung-uk Kim wrote:

On 18. 11. 20., Graham Menhennitt wrote:

G'day all,

Does anybody have any clues on how to fix/workaround Bug 230053 -
emulators/virtualbox-ose 5.2.16 failed to build?

I've build VBox many times in the past but have just got this error.


In file included from
/usr/ports_build/usr/data/FreeBSD/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.22/src/recompiler/cpu-exec.c:30:

/usr/ports_build/usr/data/FreeBSD/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.22/src/recompiler/target-i386/exec.h:41:38:
error: register 'r14' unsuitable for global register variables on this
target
register struct CPUX86State *env asm(AREG0);
  ^
/usr/ports_build/usr/data/FreeBSD/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.22/src/recompiler/dyngen-exec.h:81:15:
note: expanded from macro 'AREG0'
#define AREG0 "r14"
   ^

Any ideas?

It looks like you built devel/kBuild without GCC option.

Jung-uk Kim



It looks like I did. Not sure how that happened. Rebuilding now.

Thanks,

    Graham

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Any clues on Bug 230053 - emulators/virtualbox-ose 5.2.16 failed to build?

[Graham Menhennitt]

G'day all,

Does anybody have any clues on how to fix/workaround Bug 230053 - 
emulators/virtualbox-ose 5.2.16 failed to build?


I've build VBox many times in the past but have just got this error.


In file included from 
/usr/ports_build/usr/data/FreeBSD/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.22/src/recompiler/cpu-exec.c:30:
/usr/ports_build/usr/data/FreeBSD/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.22/src/recompiler/target-i386/exec.h:41:38: 
error: register 'r14' unsuitable for global register variables on this 
target

register struct CPUX86State *env asm(AREG0);
 ^
/usr/ports_build/usr/data/FreeBSD/ports/emulators/virtualbox-ose/work/VirtualBox-5.2.22/src/recompiler/dyngen-exec.h:81:15: 
note: expanded from macro 'AREG0'

#define AREG0 "r14"
  ^

Any ideas?

Thanks,

    Graham

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: gnucash port won't install: ".../xml-generator.go:No such file or directory" [solved]

[Graham Menhennitt]

On 29/12/2017 07:51, Graham Menhennitt wrote:

Hello all,

I'm attempting to upgrade the finance/gnucash port from 2.6.18 to 
2.6.19 and I'm getting errors on the installation stage. I've read the 
entry in UPDATING which says that I'm building the guile2 flavour by 
default. I could try switching to guile1, but I suspect that just 
delays the problem.


The errors I'm getting are all of the form:

    pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/build-config.go:No 
such file or directory


and there are a hundred or so of them. The full build log is below. 
Does anybody have any clues, please?



Following up my own post...

If I explicitly say "make install FLAVOR=guile2", it works. I thought 
that this would be unnecessary since guile2 is the default, but leaving 
the FLAVOR= bit out causes it to fail.


Graham
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

gnucash port won't install: ".../xml-generator.go:No such file or directory"

[Graham Menhennitt]

Hello all,

I'm attempting to upgrade the finance/gnucash port from 2.6.18 to 2.6.19 
and I'm getting errors on the installation stage. I've read the entry in 
UPDATING which says that I'm building the guile2 flavour by default. I 
could try switching to guile1, but I suspect that just delays the problem.


The errors I'm getting are all of the form:

    pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/build-config.go:No 
such file or directory


and there are a hundred or so of them. The full build log is below. Does 
anybody have any clues, please?


Thanks,

    Graham




# make install
===>  Installing for gnucash-2.6.19
===>  Checking if gnucash already installed
===>   Registering installation for gnucash-2.6.19
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/build-config.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/business-options.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/business-prefs.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/c-interface.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/commodity-table.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/commodity-utilities.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/config-var.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/date-utilities.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/engine-interface.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/engine-utilities.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/fin.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/gnc-menu-extensions.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/gnc-numeric.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/gnucash/app-utils.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/gnucash/business-core.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/gnucash/business-gnome.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/gnucash/core-utils.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/gnucash/engine.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/gnucash/gettext.go:No 
such file or directory
pkg-static: Unable to access file 
/usr/ports_build/usr/data/FreeBSD/ports/finance/gnucash/work-guile2/stage/usr/local/%%GUILE2%%lib/gnucash/scm/ccache/2.0/gnucash/gnc-module.go:No 
such file or directory
pkg-static: Unable to access file 

Re: Thunderbird and UPDATING 20170302

[Graham Menhennitt]

On 09/03/2017 05:09, Andrea Venturoli wrote:

On 03/03/17 19:38, Christoph Moench-Tegeder wrote:


Any interaction with bug 215348 (1)? I'm still using that patch.


Testing revealed that this patch can prevent new profiles from accessing
lightning, which I considered undesirable.


Ok.
I kept that patch and just upgraded: my old profile still works, 
Lightning included, on both my installations.


I didn't try Andriy's suggestion, as, for now, I can live with the 
inability to create new profiles.


I just updated to Thunderbird 45.8.0 via the port and I also have 
Lightning in my profile. Yet I didn't have any problems. And I don't 
have the patch installed. Has this been fixed? If so, should a new entry 
be put into UPDATING (or the existing one removed)?


Graham
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: linker errors for OpenGL functions (solved)

[Graham Menhennitt]

On 07/03/2017 08:38, Graham Menhennitt wrote:

On 6/03/2017 11:29 AM, Kevin Oberman wrote:
On Sat, Mar 4, 2017 at 12:14 PM, Graham Menhennitt 
<gra...@menhennitt.com.au



I've screwed up something on my system. When I try to build the
x11/kde4-workspace port, I get a pile of linker errors. I'm guessing 
that I
just need to reinstall some other OpenGL port, but I can't find out 
which

one. Any clues, please?


I'll try reinstalling some more ports.


Well, I've fixed it by reinstalling a number of ports. I'm not sure 
which one actually did the job, but I've reinstalled:


   graphics/dri

   x11/nvidia-driver

   graphics/qt4-opengl

   graphics/gle

   graphics/prison


Graham

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: linker errors for OpenGL functions

[Graham Menhennitt]

On 6/03/2017 11:29 AM, Kevin Oberman wrote:

On Sat, Mar 4, 2017 at 12:14 PM, Graham Menhennitt <gra...@menhennitt.com.au


I've screwed up something on my system. When I try to build the
x11/kde4-workspace port, I get a pile of linker errors. I'm guessing that I
just need to reinstall some other OpenGL port, but I can't find out which
one. Any clues, please?

Thanks,

 Graham


/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to `glBegin'
c++: error: linker command failed with exit code 1 (use -v to see
invocation)
gmake[4]: *** 
[ksmserver/screenlocker/greeter/CMakeFiles/kscreenlocker_greet.dir/build.make:283:
ksmserver/screenlocker/greeter/kscreenlocker_greet] Error 1
gmake[4]: Leaving directory '/usr/ports_build/usr/data/Fre
eBSD/ports/x11/kde4-workspace/work/.build'
gmake[3]: *** [CMakeFiles/Makefile2:8345: ksmserver/screenlocker/greeter
/CMakeFiles/kscreenlocker_greet.dir/all] Error 2
gmake[3]: *** Waiting for unfinished jobs


Do you have any older versions of llvm installed? OpenGL has issues if
anything older that llvm38 (maybe llvm39) is installed. "pkg delete -f
llvm3?" for each version prior to 3.9 installed. It is quite unlikely that
you will find any dependencies on the old versions. You can use "pkg info
-d llvm3?" to confirm. It is possible that some port or another might need
a re-install, but I have yet to see a report of this.


Hi Kevin,

Thanks for replying. Unfortunately, no, I only have llvm39 installed. 
That's not to say I haven't had other versions installed in the past. In 
fact, I suspect that cleaning up my system is exactly what broke this.


I'll try reinstalling some more ports.

Thanks again,
Graham
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

linker errors for OpenGL functions

[Graham Menhennitt]

G'day all,

I've screwed up something on my system. When I try to build the 
x11/kde4-workspace port, I get a pile of linker errors. I'm guessing 
that I just need to reinstall some other OpenGL port, but I can't find 
out which one. Any clues, please?


Thanks,

Graham


/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to `glBegin'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to `glPopMatrix'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to `glLoadMatrixd'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to 
`glXCreateContext'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to 
`glTexCoordPointer'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to 
`glDeleteTextures'

/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to `glGetError'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to `glTexImage2D'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to `glTexGenfv'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to 
`glCopyTexImage2D'

/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to `glColor4f'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to `glBlendFunc'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to `glDrawArrays'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to 
`glXDestroyContext'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to 
`glXQueryExtension'

/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to `glLoadMatrixf'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to `glIndexi'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to `glBindTexture'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to `glCullFace'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to 
`glPixelTransferi'
/usr/local/lib/qt4/libQtOpenGL.so.4: undefined reference to 
`glXGetClientString'
c++: error: linker command failed with exit code 1 (use -v to see 
invocation)
gmake[4]: *** 
[ksmserver/screenlocker/greeter/CMakeFiles/kscreenlocker_greet.dir/build.make:283: 
ksmserver/screenlocker/greeter/kscreenlocker_greet] Error 1
gmake[4]: Leaving directory 
'/usr/ports_build/usr/data/FreeBSD/ports/x11/kde4-workspace/work/.build'
gmake[3]: *** [CMakeFiles/Makefile2:8345: 
ksmserver/screenlocker/greeter/CMakeFiles/kscreenlocker_greet.dir/all] 
Error 2

gmake[3]: *** Waiting for unfinished jobs

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: VirtualBox port not working with USB

[Graham Menhennitt]

On 26/01/2017 06:41, Hans Petter Selasky wrote:

On 01/25/17 10:00, Graham Menhennitt wrote:

On 25/01/2017 00:43, Hans Petter Selasky wrote:

On 01/24/17 12:03, Graham Menhennitt wrote:

On 24/01/2017 04:19, Alfred Perlstein wrote:

Graham, can you follow what Hans is asking and report back please?



On Jan 23, 2017, at 8:14 AM, Hans Petter Selasky <h...@selasky.org>
wrote:


There hasn't been any big changes in the FreeBSD userspace 
interfaces

used by virtualbox for a while. Maybe you can try to collect output
from "usbdump -i usbusX -f Y -s 65536 > log.txt" where X and Y are
the numbers after ugenX.Y for the device in question. I'll give
virtualbox from FreeBSD ports a spin and see if there is something
obvious broken.






Can you compile VirtualBox with full debugging enabled (make config
and add all debug flags before building) and capture the resulting
debug log(s) and send to me?

There are some debug prints in "USBProxyBackendFreeBSD.cpp" and
"USBProxyDevice-freebsd.cpp" which I need to see and you should see
them too when you add/remove USB devices.


Hans,

I think that this is what you're after. If not, I can have another go.
But it dies pretty quickly so I'm not sure what more I can do.

Thanks,
Graham



Hi Graham,

Can you try to replace the two attached files in 
/usr/ports/...virtualbox-ose/files and re-build. Can someone here 
interacting with the VBOX team make sure these patches gets pushed 
upstream?


--HPS


Thank you very much, Hans. Working for me now.

Thanks,

Graham

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: VirtualBox port not working with USB

[Graham Menhennitt]

On 25/01/2017 00:43, Hans Petter Selasky wrote:

On 01/24/17 12:03, Graham Menhennitt wrote:

On 24/01/2017 04:19, Alfred Perlstein wrote:

Graham, can you follow what Hans is asking and report back please?



On Jan 23, 2017, at 8:14 AM, Hans Petter Selasky <h...@selasky.org>
wrote:


There hasn't been any big changes in the FreeBSD userspace interfaces
used by virtualbox for a while. Maybe you can try to collect output
from "usbdump -i usbusX -f Y -s 65536 > log.txt" where X and Y are
the numbers after ugenX.Y for the device in question. I'll give
virtualbox from FreeBSD ports a spin and see if there is something
obvious broken.






Can you compile VirtualBox with full debugging enabled (make config 
and add all debug flags before building) and capture the resulting 
debug log(s) and send to me?


There are some debug prints in "USBProxyBackendFreeBSD.cpp" and 
"USBProxyDevice-freebsd.cpp" which I need to see and you should see 
them too when you add/remove USB devices. 


Hans,

I think that this is what you're after. If not, I can have another go. 
But it dies pretty quickly so I'm not sure what more I can do.


Thanks,
Graham


Log created: 2017-01-25T08:38:42.439099000Z
Executable: /usr/local/lib/virtualbox/VBoxSVC
Arg[0]: /usr/local/lib/virtualbox/VBoxSVC
Arg[1]: --auto-shutdown

!!Assertion Failed!!
Expression: mUniState == kHostUSBDeviceState_DetachingFromVM || 
(mUniState == kHostUSBDeviceState_UsedByVM && aAbnormal)
Location  : 
/usr/ports_build/usr/data/FreeBSD/ports/emulators/virtualbox-ose/work/VirtualBox-5.1.14/src/VBox/Main/src-server/HostUSBDeviceImpl.cpp(671) 
nsresult HostUSBDevice::i_onDetachFromVM(SessionMachine *, bool, bool *, 
bool)

{EPSON EPSON Scanner} CapturingForVM

!!Assertion Failed!!
Expression: aReason == Uninit::Abnormal
Location  : 
/usr/ports_build/usr/data/FreeBSD/ports/emulators/virtualbox-ose/work/VirtualBox-5.1.14/src/VBox/Main/src-server/MachineImpl.cpp(12749) 
void SessionMachine::uninit(Uninit::Reason)


!!Assertion Failed!!
Expression: SUCCEEDED(rc)
Location  : 
/usr/ports_build/usr/data/FreeBSD/ports/emulators/virtualbox-ose/work/VirtualBox-5.1.14/src/VBox/Main/glue/initterm.cpp(636) 
nsresult com::Shutdown()

COM RC = NS_ERROR_UNEXPECTED (0x8000)
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: VirtualBox port not working with USB

[Graham Menhennitt]

On 24/01/2017 04:19, Alfred Perlstein wrote:

Graham, can you follow what Hans is asking and report back please?



On Jan 23, 2017, at 8:14 AM, Hans Petter Selasky  wrote:


There hasn't been any big changes in the FreeBSD userspace interfaces used by virtualbox for 
a while. Maybe you can try to collect output from "usbdump -i usbusX -f Y -s 65536 > 
log.txt" where X and Y are the numbers after ugenX.Y for the device in question. I'll 
give virtualbox from FreeBSD ports a spin and see if there is something obvious broken.




Alfred,

Thanks for putting me in touch with Hans.



Hans,

Thanks for replying and looking into this.

Unfortunately, there is no USB activity logged with the failing versions 
- please see below.


In both cases, I start VirtualBox, then on the Device->USB menu I try to 
tick Epson Scanner. On version 5.0.26, the box next to that menu item 
appears ticked. On version 5.1.14, it doesn't. Trying to tick it again 
gives the error message that I put in the PR.


Thanks again,

Graham


Firstly:

# dmesg|grep -i epson
ugen2.2:  at usbus2

Then, with version 5.1.14 which fails:

# usbdump -i usbus2 -f 2 -s 65536
^C

0 packets captured
0 packets received by filter
0 packets dropped by kernel
#

Finally, with version 5.0.26 which works correctly:

# usbdump -i usbus2 -f 2 -s 65536
19:55:12.862903 usbus2.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0
19:55:12.863686 usbus2.2 
DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=20,IVAL=0,ERR=0

19:55:12.863708 usbus2.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0
19:55:12.863806 usbus2.2 
DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=12,IVAL=0,ERR=0

19:55:12.964663 usbus2.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0
19:55:12.965599 usbus2.2 
DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=32,IVAL=0,ERR=0

19:55:13.239772 usbus2.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0
19:55:13.240505 usbus2.2 
DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=4,IVAL=0,ERR=0

19:55:13.245722 usbus2.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0
19:55:13.246249 usbus2.2 
DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=28,IVAL=0,ERR=0

19:55:13.251713 usbus2.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0
19:55:13.251999 usbus2.2 
DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=4,IVAL=0,ERR=0

19:55:13.257704 usbus2.2 SUBM-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=8,IVAL=0
19:55:13.258494 usbus2.2 
DONE-CTRL-EP=0080,SPD=HIGH,NFR=2,SLEN=28,IVAL=0,ERR=0

^C
14 packets captured
14 packets received by filter
0 packets dropped by kernel
#

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

VirtualBox port not working with USB

[Graham Menhennitt]

G'day all,

About 6 months ago, the FreeBSD port of VirtualBox was upgraded from 
version 5.0.26 to 5.1.4. The new version didn't work with USB devices 
whereas the old one did. I raised PR 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212845 at the time. 
Since then, the port has followed the releases of VirtualBox up to 
5.1.14 as of last week (thanks, jkim). However, the same USB problem has 
existed for all that time.


I'm having a go at trying to fix it. But I know almost nothing about the 
VirtualBox source code. So, I'd like some help please. Does anybody here 
have any experience with this. Or any clues as to where I should start 
looking.


At the moment I'm just trying to do diffs between the old and new 
versions, but it's a fairly daunting task. I'm also going to try 
building versions 5.0.32 and 5.1.0 (which never had FreeBSD ports) to 
see whether the breakage was in between them (I presume that it was).


Thanks for any help,

Graham

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: What sort of a hog is Ruby?

[Graham Menhennitt]

On 07/10/2016 17:35, Dave Horsfall wrote:
> Looks like I need to upgrade it for security issues; so I tried to compile 
> it from the ports area.
>
> First it blew out my disk space (the "work" sub-directory), so when I 
> rearranged a few things to make more room it blew out my swap space!
>
Not sure what's going on with yours, but mine doesn't show any of those
symptoms. I build it regularly on a relatively low spec box (AMD G-T40E
Processor (1000.02-MHz K8-class CPU) with 4Gb RAM). Which version of
Ruby and which version of FreeBSD?

Graham

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: dependency explosions

[Graham Menhennitt]

Thanks Miroslav,

Cyrus is marked as automatic and I don't understand why that is. But
I've removed it as I only needed its libraries for Dovecot and, as you
pointed out, that isn't necessary any more.

All working!

Thanks for your reply,
Graham

On 06/10/2016 11:23, Miroslav Lachman wrote:
> Graham Menhennitt wrote on 2016/10/06 01:49:
>> Sorry, I just read that UPDATING entry again. Cyrus is only provided to
>> Dovecot if Postfix is present. I do not have Postfix present. So, I
>> think that I do need to install Cyrus explicitly.
>>
>> So, back to my original question, why does "pkg autoremove" want to
>> uninstall Cyrus when I explicitly installed it from the port?
>
> pkg autoremove is working with pkg internal database. If you install
> some ports directly with command "pkg install SomePort", then this
> ports is nor marked as autoamtic. If some port is installed as
> depedency, then it is marked as automatic and if parent port is
> removed, then this automatic port can be deleted by "pkg autoremove"
>
> You can use "pkg query" to check what is marked as automatic
>
> pkg query '%a %n' | sort
>
> You can change this settings by "pkg set" (see man pkg-query example)
>
> EXAMPLES
>  Change a package from automatic to non-automatic, which will prevent
>  autoremove from removing it:
>% pkg set -A 0 perl-5.14
>
>
>
> Why you need cyrus-sasl? Do you use some tools from this package or
> just some libs?
> The Dovecot / Postfix case is that Dovecot have it's own internal SASL
> libs and Postfix from some version have internal support for Dovecots
> SASL and do not need to be build with Cyrus-SASL. But it is not
> related to you if you are not using Postfix. 

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: dependency explosions

[Graham Menhennitt]

Sorry, I just read that UPDATING entry again. Cyrus is only provided to 
Dovecot if Postfix is present. I do not have Postfix present. So, I 
think that I do need to install Cyrus explicitly.


So, back to my original question, why does "pkg autoremove" want to 
uninstall Cyrus when I explicitly installed it from the port?


Thanks,
Graham

On 6/10/2016 10:12 AM, Graham Menhennitt wrote:

Thanks for that, olli.

I didn't understand how I'd missed the fact that Dovecot now included 
Cyrus. So I had a look at /usr/ports/UPDATING. Searching for Dovecot 
shows a mention of it in the entry at 20160228. However, that's 
entitled "AFFECTS: users of mail/postfix", and I don't use Postfix. I 
think that Dovecot should have its own entry in UPDATING for that 
change too.


Graham

On 6/10/2016 9:38 AM, olli hauer wrote:
Postfix in combination with dovecot doesn't require cyrus, since some 
months dovecot support is always provided by postfix.

But i"m sorry and cannot expliain why cyrus is installed on your system
--
send with broken GMX mailer client, sorry for tofu and html scrap
On 06/10/2016, 00:29 Graham Menhennitt <gra...@menhennitt.com.au> wrote:

On 6/10/2016 8:20 AM, Mathieu Arnold wrote:
> Le 05/10/2016 à 22:04, Julian Elischer a écrit :
>> Another thing that might be good woudl be a way to tell ports
"remove
>> all the ports that were just build dependencies".
> pkg autoremove
>

Thanks for that Mathieu - I didn't know about that one.

However...

When I run it, it tells me that it's going to remove my cyrus-SASL
port.
I installed that (via its port) so that I can use SSL/TLS
authentication
on my Dovecot server (installed via the dovecot2 port). So Cyrus
is not
a build dependency of anything - why is it offering to remove it?

Thanks,
Graham
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
"freebsd-ports-unsubscr...@freebsd.org"


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: dependency explosions

[Graham Menhennitt]

Thanks for that, olli.

I didn't understand how I'd missed the fact that Dovecot now included 
Cyrus. So I had a look at /usr/ports/UPDATING. Searching for Dovecot 
shows a mention of it in the entry at 20160228. However, that's entitled 
"AFFECTS: users of mail/postfix", and I don't use Postfix. I think that 
Dovecot should have its own entry in UPDATING for that change too.


Graham

On 6/10/2016 9:38 AM, olli hauer wrote:
Postfix in combination with dovecot doesn't require cyrus, since some 
months dovecot support is always provided by postfix.

But i"m sorry and cannot expliain why cyrus is installed on your system
--
send with broken GMX mailer client, sorry for tofu and html scrap
On 06/10/2016, 00:29 Graham Menhennitt <gra...@menhennitt.com.au> wrote:

On 6/10/2016 8:20 AM, Mathieu Arnold wrote:
> Le 05/10/2016 à 22:04, Julian Elischer a écrit :
>> Another thing that might be good woudl be a way to tell ports
"remove
>> all the ports that were just build dependencies".
> pkg autoremove
>

Thanks for that Mathieu - I didn't know about that one.

However...

When I run it, it tells me that it's going to remove my cyrus-SASL
port.
I installed that (via its port) so that I can use SSL/TLS
authentication
on my Dovecot server (installed via the dovecot2 port). So Cyrus
is not
a build dependency of anything - why is it offering to remove it?

Thanks,
Graham
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
"freebsd-ports-unsubscr...@freebsd.org" 



___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: dependency explosions

[Graham Menhennitt]

On 6/10/2016 8:20 AM, Mathieu Arnold wrote:

Le 05/10/2016 à 22:04, Julian Elischer a écrit :

Another thing that might be good woudl be a way to tell ports "remove
all the ports that were just build dependencies".

pkg autoremove



Thanks for that Mathieu - I didn't know about that one.

However...

When I run it, it tells me that it's going to remove my cyrus-SASL port. 
I installed that (via its port) so that I can use SSL/TLS authentication 
on my Dovecot server (installed via the dovecot2 port). So Cyrus is not 
a build dependency of anything - why is it offering to remove it?


Thanks,
Graham
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: k3b can't find CD drive

[Graham Menhennitt]

On 21/09/2016 23:48, Ivan Klymenko wrote:
> On Wed, 21 Sep 2016 22:35:44 +1000
> Graham Menhennitt <gra...@menhennitt.com.au> wrote:
>
>> Hi all,
>>
>> I'm trying to write a CD using k3b. However, when it starts, it tells
>> me that it can't find a CD drive to work with. Dmesg shows:
>>
>> cd0 at ata0 bus 0 scbus4 target 0 lun 0
>> cd0:  Removable CD-ROM SCSI device
>> cd0: Serial Number NHDL064152WL
>> cd0: 150.000MB/s transfers (SATA, UDMA5, ATAPI 12bytes, PIO
>> 8192bytes) cd0: 0MB (1 2048 byte sectors)
>
> look patch from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210354
Ivan,

Why have you marked the bug as "Closed"? The patch still needs to be
applied.

Graham
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: k3b can't find CD drive

[Graham Menhennitt]

On 21/09/2016 23:48, Ivan Klymenko wrote:
> On Wed, 21 Sep 2016 22:35:44 +1000
> Graham Menhennitt <gra...@menhennitt.com.au> wrote:
>
>> Hi all,
>>
>> I'm trying to write a CD using k3b. However, when it starts, it tells
>> me that it can't find a CD drive to work with. Dmesg shows:
>>
>> cd0 at ata0 bus 0 scbus4 target 0 lun 0
>> cd0:  Removable CD-ROM SCSI device
>> cd0: Serial Number NHDL064152WL
>> cd0: 150.000MB/s transfers (SATA, UDMA5, ATAPI 12bytes, PIO
>> 8192bytes) cd0: 0MB (1 2048 byte sectors)
>>
>> I think I've got all the correct things in my kernel: pass, scb, cd.
>> I'm I'm pretty sure it's not a permissions problem as it happens when
>> I run k3b as root too.
>>
>> This is on a recent 11-stable AMD64 with up to date ports.
>>
> look patch from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210354
Thank you very much Ivan. That fixed it.

Graham
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

k3b can't find CD drive

[Graham Menhennitt]

Hi all,

I'm trying to write a CD using k3b. However, when it starts, it tells me
that it can't find a CD drive to work with. Dmesg shows:

cd0 at ata0 bus 0 scbus4 target 0 lun 0
cd0:  Removable CD-ROM SCSI device
cd0: Serial Number NHDL064152WL
cd0: 150.000MB/s transfers (SATA, UDMA5, ATAPI 12bytes, PIO 8192bytes)
cd0: 0MB (1 2048 byte sectors)

but also has lots of error messages:

(cd0:ata0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00
(cd0:ata0:0:0:0): CAM status: SCSI Status Error
(cd0:ata0:0:0:0): SCSI status: Check Condition
(cd0:ata0:0:0:0): SCSI sense: BLANK CHECK asc:0,0 (No additional
sense information)
(cd0:ata0:0:0:0): Error 28, Unretryable error
(cd0:ata0:0:0:0): cddone: got error 0x1c back

I've followed all the instructions in the port's pkg-message except I
get an error when setting the sysctl:

sysctl hw.ata.atapi_dma=1
sysctl: unknown oid 'hw.ata.atapi_dma'

I think I've got all the correct things in my kernel: pass, scb, cd. I'm
I'm pretty sure it's not a permissions problem as it happens when I run
k3b as root too.

This is on a recent 11-stable AMD64 with up to date ports.

Thanks for any help,

Graham


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: VirtualBox can't attach USB devices

[Graham Menhennitt]

Sorry, I should have mentioned that this is not a permissions problem on 
the USB nodes in /dev. I have followed the handbook's instructions on 
setting the group and permissions.


Graham


On 18/09/2016 4:44 PM, Graham Menhennitt wrote:

Hi all,

I've been using my Epson scanner in Windows XP under VirtualBox for many
years. I recently updated my source and ports to the latest and now I
can't access my scanner. In fact I can't seem to attach any USB devices.
I've tried creating a filter for it under USB Settings, and I've tried
manually connecting it from the Devices->USB menu by clicking its
checkbox. In both cases, it doesn't connect. If I try a second time, I
get a message:

Failed to attach the USB device EPSON Scanner to the virtual machine WinXP.

USB device 'EPSON EPSON Scanner' with UUID
{aa1eba25-05eb-4aed-8e9f-803807dd3bc4} is busy with a previous request.
Please try again later.

Result Code: NS_ERROR_INVALID_ARG (0x80070057)
Component: HostUSBDeviceWrap
Interface: IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89}
Callee: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I've waited for an hour in case it was just taking a long time to
connect - no joy.

This is on FreeBSD 11-Stable (as of today) AMD64, and ports updated as
of today. And I build the kmod with the current kernel source in place.

Does anybody have any clues, please?

Thanks,
 Graham
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

VirtualBox can't attach USB devices

[Graham Menhennitt]

Hi all,

I've been using my Epson scanner in Windows XP under VirtualBox for many
years. I recently updated my source and ports to the latest and now I
can't access my scanner. In fact I can't seem to attach any USB devices.
I've tried creating a filter for it under USB Settings, and I've tried
manually connecting it from the Devices->USB menu by clicking its
checkbox. In both cases, it doesn't connect. If I try a second time, I
get a message:

Failed to attach the USB device EPSON Scanner to the virtual machine WinXP.

USB device 'EPSON EPSON Scanner' with UUID
{aa1eba25-05eb-4aed-8e9f-803807dd3bc4} is busy with a previous request.
Please try again later.

Result Code: NS_ERROR_INVALID_ARG (0x80070057)
Component: HostUSBDeviceWrap
Interface: IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89}
Callee: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I've waited for an hour in case it was just taking a long time to
connect - no joy.

This is on FreeBSD 11-Stable (as of today) AMD64, and ports updated as
of today. And I build the kmod with the current kernel source in place.

Does anybody have any clues, please?

Thanks,
Graham
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: error upgrading graphics/dri port "/usr/local/llvm36/bin/clang: not found"

[Graham Menhennitt]

On 19/01/2016 6:31 AM, Brooks Davis wrote:

On Sun, Jan 17, 2016 at 07:08:14PM +1100, Graham Menhennitt wrote:

Does anybody have any clues, please?

Thanks,
 Graham

root@starker# portupgrade -aWw
[Reading data from pkg(8) ... - 854 packages found - done]
--->  Upgrading 'dri-11.0.7_1,2' to 'dri-11.0.8,2' (graphics/dri)
--->  Building '/usr/ports/graphics/dri'
===>   dri-11.0.8,2 depends on executable: makedepend - found
===>   dri-11.0.8,2 depends on package: libclc>=0.0.r222830 - not found
===>  Building for libclc-0.1.0.20150710
[8/979] LLVM-CC r600--/lib/math/mad.cl.cedar.bc
FAILED: /usr/local/llvm36/bin/clang -MMD -MF
r600--/lib/math/mad.cl.cedar.bc.d -target r600-- -I`dirname
generic/lib/math/mad.cl` -Igeneric/include -fno-builtin
-Dcl_clang_storage_class_specifiers -Dcl_khr_fp64 -Dcles_khr_int64
-D__CLC_INTERNAL -emit-llvm -mcpu=cedar -c -o
r600--/lib/math/mad.cl.cedar.bc generic/lib/math/mad.cl
/bin/sh: /usr/local/llvm36/bin/clang: not found
...

You appear not to have lang/clang36 installed.  I don't know why
portupgrade isn't installing it since it is a BUILD_DEPEND of
graphics/dri, but installing it by hand should work around the problem.

-- Brooks

Indeed, it does fix it. Thanks for your help.

Graham
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

error upgrading graphics/dri port "/usr/local/llvm36/bin/clang: not found"

[Graham Menhennitt]

Does anybody have any clues, please?

Thanks,
Graham

root@starker# uname -a
FreeBSD starker 11.0-CURRENT FreeBSD 11.0-CURRENT #17 r294103: Sun Jan
17 13:26:05 AEDT 2016
gfm@starker:/usr/obj/usr/data/FreeBSD/src_11-Current/sys/starker  amd64
root@starker# ll /usr/local/llvm36/bin
total 22384
-rwxr-xr-x  1 root  wheel277720 Jan  6 19:54 bugpoint
-rwxr-xr-x  1 root  wheel  18292472 Sep 25 07:49 clang-cpp
-rwxr-xr-x  1 root  wheel  7288 Jan  6 19:53 count
-r-xr-xr-x  2 root  wheel220280 Jan  6 19:54 FileCheck
-r-xr-xr-x  4 root  wheel82 Jan  6 19:54 lit
-rwxr-xr-x  1 root  wheel117368 Jan  6 19:54 llc
-rwxr-xr-x  1 root  wheel 96128 Jan  6 19:54 lli
-rwxr-xr-x  1 root  wheel 14648 Jan  6 19:54 lli-child-target
-rwxr-xr-x  1 root  wheel 58200 Jan  6 19:54 llvm-ar
-rwxr-xr-x  1 root  wheel 16960 Jan  6 19:54 llvm-as
-rwxr-xr-x  1 root  wheel 46088 Jan  6 19:54 llvm-bcanalyzer
-rwxr-xr-x  1 root  wheel 91416 Jan  6 19:54 llvm-config
-rwxr-xr-x  1 root  wheel 92552 Jan  6 19:54 llvm-cov
-rwxr-xr-x  1 root  wheel 49200 Jan  6 19:54 llvm-diff
-rwxr-xr-x  1 root  wheel 20432 Jan  6 19:54 llvm-dis
-rwxr-xr-x  1 root  wheel 32992 Jan  6 19:54 llvm-dsymutil
-rwxr-xr-x  1 root  wheel 24888 Jan  6 19:54 llvm-dwarfdump
-rwxr-xr-x  1 root  wheel 33008 Jan  6 19:54 llvm-extract
-rwxr-xr-x  1 root  wheel 24904 Jan  6 19:54 llvm-link
-r-xr-xr-x  4 root  wheel82 Jan  6 19:54 llvm-lit
-rwxr-xr-x  1 root  wheel 74560 Jan  6 19:54 llvm-mc
-rwxr-xr-x  1 root  wheel 18072 Jan  6 19:54 llvm-mcmarkup
-rwxr-xr-x  1 root  wheel 79432 Jan  6 19:54 llvm-nm
-rwxr-xr-x  1 root  wheel244848 Jan  6 19:54 llvm-objdump
-rwxr-xr-x  1 root  wheel 46400 Jan  6 19:54 llvm-profdata
lrwxr-xr-x  1 root  wheel 7 Jan  6 19:54 llvm-ranlib -> llvm-ar
-rwxr-xr-x  1 root  wheel314824 Jan  6 19:54 llvm-readobj
-rwxr-xr-x  1 root  wheel 52520 Jan  6 19:54 llvm-rtdyld
-rwxr-xr-x  1 root  wheel 64744 Jan  6 19:54 llvm-size
-rwxr-xr-x  1 root  wheel 64640 Jan  6 19:54 llvm-stress
-rwxr-xr-x  1 root  wheel 64736 Jan  6 19:54 llvm-symbolizer
-rwxr-xr-x  1 root  wheel   1622424 Jan  6 19:53 llvm-tblgen
-rwxr-xr-x  1 root  wheel 39064 Jan  6 19:54 llvm-vtabledump
-rwxr-xr-x  1 root  wheel 36944 Jan  6 19:54 macho-dump
-rwxr-xr-x  1 root  wheel 41112 Jan  6 19:53 not
-rwxr-xr-x  1 root  wheel 47168 Jan  6 19:54 obj2yaml
-rwxr-xr-x  1 root  wheel302320 Jan  6 19:54 opt
-rwxr-xr-x  1 root  wheel 34264 Jan  6 19:54 verify-uselistorder
-rwxr-xr-x  1 root  wheel 66032 Jan  6 19:54 yaml2obj
root@starker# pkg info|grep llvm
llvm36-3.6.2_2 Low Level Virtual Machine
root@starker# portupgrade -aWw
[Reading data from pkg(8) ... - 854 packages found - done]
--->  Upgrading 'dri-11.0.7_1,2' to 'dri-11.0.8,2' (graphics/dri)
--->  Building '/usr/ports/graphics/dri'
===>   dri-11.0.8,2 depends on executable: makedepend - found
===>   dri-11.0.8,2 depends on package: libclc>=0.0.r222830 - not found
===>  Building for libclc-0.1.0.20150710
[8/979] LLVM-CC r600--/lib/math/mad.cl.cedar.bc
FAILED: /usr/local/llvm36/bin/clang -MMD -MF
r600--/lib/math/mad.cl.cedar.bc.d -target r600-- -I`dirname
generic/lib/math/mad.cl` -Igeneric/include -fno-builtin
-Dcl_clang_storage_class_specifiers -Dcl_khr_fp64 -Dcles_khr_int64
-D__CLC_INTERNAL -emit-llvm -mcpu=cedar -c -o
r600--/lib/math/mad.cl.cedar.bc generic/lib/math/mad.cl
/bin/sh: /usr/local/llvm36/bin/clang: not found
[8/979] LLVM-CC r600--/lib/math/tables.cl.cedar.bc
FAILED: /usr/local/llvm36/bin/clang -MMD -MF
r600--/lib/math/tables.cl.cedar.bc.d -target r600-- -I`dirname
generic/lib/math/tables.cl` -Igeneric/include -fno-builtin
-Dcl_clang_storage_class_specifiers -Dcl_khr_fp64 -Dcles_khr_int64
-D__CLC_INTERNAL -emit-llvm -mcpu=cedar -c -o
r600--/lib/math/tables.cl.cedar.bc generic/lib/math/tables.cl
/bin/sh: /usr/local/llvm36/bin/clang: not found
...
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

portupgrade fails possibly due to py27-asn1 rename to py-pyasn1

[Graham Menhennitt]

Hi all,

I updated my ports collection the other day and ran portupgrade. It
fails on the devel/py-pyasn1 port with the error:

===>  Installing for py27-pyasn1-0.1.9
===>   py27-pyasn1-0.1.9 depends on package: py27-setuptools27>0 - found
===>   py27-pyasn1-0.1.9 depends on file: /usr/local/bin/python2.7 - found
===>  Checking if py27-pyasn1 already installed
===>   Registering installation for py27-pyasn1-0.1.9 as automatic
Installing py27-pyasn1-0.1.9...
pkg-static: py27-pyasn1-0.1.9 conflicts with py27-asn1-0.1.8,1 (installs
files into the same place).  Problematic file:
/usr/local/lib/python2.7/site-packages/pyasn1/__init__.py
*** Error code 70

Stop.

I suspect it's because this port was recently renamed from
devel/py27-asn1 (see
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204567). I can't see
any message in UPDATING that's relevant.

Any clues please?

Thanks,
Graham
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"