OpenSSL port ASM removal

2016-09-18 Thread Franco Fichtner
Hi all,

ASM support for OpenSSL is missing from the port now,
which is kind of unfortunate for two reasons:

(a) FreeBSD base (at least for i386 and amd64) has it.

(b) ASM is required for AESNI to work last time I checked.

Why was it removed? It's not clear from the commit message.

LibreSSL port has had the assembler bits turned on a
while back by default, too.


Thanks,
Franco
___
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

2016-09-18 Thread Sergey Dyatko
+1. I have USB token and windows xp on vbox, after lattest vbox update I
can't use this usb key on vm :(

2016-09-19 9:25 GMT+03:00 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"
>
___
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

2016-09-18 Thread 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

2016-09-18 Thread 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: New port maintainer

2016-09-18 Thread Thomas Zander
On Sun, Sep 18, 2016 at 11:05:45AM +0200, Carsten Larsen wrote:
> Any committers who could take a look at this port:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=20

Sure, on it.

Best regards
Riggs


signature.asc
Description: PGP signature


Re: FreeBSD Port: neovim-0.1.4_2

2016-09-18 Thread gor
On 17/09/16 23:58:54 EEST, Christopher Deluca wrote:
> Hello,
> 
> Thanks for maintaining the FreeBSD Neovim port!
> 
> Just wondering if/when it will be upgraded to 0.1.5?
> 
> Thanks!

Hi!

Update alredy waiting one of commiters for review and commit.

See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212233

Regards.

-- 
Oleg Gushchenkov aka gor
___
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"


New port maintainer

2016-09-18 Thread Carsten Larsen

Any committers who could take a look at this port:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=20

___
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: Problems with fetching from GitHub using GH_TAGNAME= hash

2016-09-18 Thread Carsten Larsen

Den 18-09-2016 kl. 09:29 skrev Olivier Duchateau:

On Sat, 17 Sep 2016 22:40:27 -0700
Kevin Oberman  wrote:


I an attempting to write a port for multimedia/mp4vs which has moved from
Google Code to GitHub. I tried specifying GH_TAGNAME= 6fda22f, but instead
of fetching mp4v2-Release-MP4v2-3.0.1.1.tar.gz, it tries to fetch
mp4v2-Release-MP4v2-3.0.1.1_GH0.tar.gz. (Note added "_GH0".)

I have no idea where this is coming from an have no experience with porting
where GitHub is the distfile repo.


Tarball is correct, despite "_GH0", I think it's GitHub, which adds this 
keyword on the fly, when we fetch tarball.



My Makefile contains:
USE_GITHUB= yes
GH_ACCOUNT= TechSmith
GH_PROJECT= mp4v2
GH_TAGNAME= 6fda22f


Here, GH_PROJECT= is not necessary, because by default it re-uses PORTNAME (see 
Mk/bsd.sites.mk).



Any idea what I need to change?


The port should fetch from:
https://codeload.github.com/TechSmith/mp4v2/tar.gz/6fda22f

Which seems to work fine.



Thanks,
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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"





--

Kind regards
Carsten Larsen
___
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: Problems with fetching from GitHub using GH_TAGNAME= hash

2016-09-18 Thread Olivier Duchateau
On Sat, 17 Sep 2016 22:40:27 -0700
Kevin Oberman  wrote:

> I an attempting to write a port for multimedia/mp4vs which has moved from
> Google Code to GitHub. I tried specifying GH_TAGNAME= 6fda22f, but instead
> of fetching mp4v2-Release-MP4v2-3.0.1.1.tar.gz, it tries to fetch
> mp4v2-Release-MP4v2-3.0.1.1_GH0.tar.gz. (Note added "_GH0".)
> 
> I have no idea where this is coming from an have no experience with porting
> where GitHub is the distfile repo.

Tarball is correct, despite "_GH0", I think it's GitHub, which adds this 
keyword on the fly, when we fetch tarball.

> 
> My Makefile contains:
> USE_GITHUB= yes
> GH_ACCOUNT= TechSmith
> GH_PROJECT= mp4v2
> GH_TAGNAME= 6fda22f

Here, GH_PROJECT= is not necessary, because by default it re-uses PORTNAME (see 
Mk/bsd.sites.mk). 

> 
> Any idea what I need to change?
> 
> Thanks,
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> ___
> 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"


-- 
olivier
___
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"