Re: 11.0-RC1 unsupported by ports?

[Bernd Walter]

On Wed, Jan 25, 2017 at 07:20:45AM +0100, Kurt Jaeger wrote:
> Hi!
> 
> > [61]cnc# make install
> > /!\ ERROR: /!\
> > 
> > Ports Collection support for your FreeBSD version has ended, and no ports 
> > are
> > guaranteed to build on this system. Please upgrade to a supported release.
> > 
> > No support will be provided if you silence this message by defining
> > ALLOW_UNSUPPORTED_SYSTEM.
> 
> 11.0-RC1 was superseded by 11.0-REL, so while that message is a bit
> drastic, there's a point to it.

With that argument only the latest version would be supported.
That said, it is a release candidate and as such one could argue that
there never had been any official support at all.
In that case however the message is wrong, because when a support has
ended it implies that there was support.

The check in the code is this one:
.if (${OPSYS} == FreeBSD && (${OSVERSION} < 1003000 || (${OSVERSION} >= 110 
&& ${OSVERSION} < 1100122))) || \
(${OPSYS} == DragonFly && ${DFLYVERSION} < 400400)

It is not about RC as such, it is explicitly about 11.0-RC.
My OSVERSION is 1100121.
So obviously support starts with the first release.
Fair enough, but then the message is still wrong unless it was supported.

-- 
B.Walter  http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
___
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: 11.0-RC1 unsupported by ports?

[Kurt Jaeger]

Hi!

> [61]cnc# make install
> /!\ ERROR: /!\
> 
> Ports Collection support for your FreeBSD version has ended, and no ports are
> guaranteed to build on this system. Please upgrade to a supported release.
> 
> No support will be provided if you silence this message by defining
> ALLOW_UNSUPPORTED_SYSTEM.

11.0-RC1 was superseded by 11.0-REL, so while that message is a bit
drastic, there's a point to it.

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
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"

11.0-RC1 unsupported by ports?

[Bernd Walter]

[61]cnc# make install
/!\ ERROR: /!\

Ports Collection support for your FreeBSD version has ended, and no ports are
guaranteed to build on this system. Please upgrade to a supported release.

No support will be provided if you silence this message by defining
ALLOW_UNSUPPORTED_SYSTEM.

*** Error code 1

Stop.
make[1]: stopped in /usr/ports/misc/raspberrypi-userland
*** Error code 1

Stop.
make: stopped in /usr/ports/misc/raspberrypi-userland
Exit 1
[62]cnc# uname -a
FreeBSD cnc.cicely.de 11.0-RC1 FreeBSD 11.0-RC1 #0 r303979: Fri Aug 12 17:12:13 
UTC 2016 r...@releng2.nyi.freebsd.org:/usr/obj/arm.armv6/usr/src/sys/RPI2  
arm


-- 
B.Walter  http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
___
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: net-mgmt/prometheus update to 1.5.0, comitter requested

[Kurt Jaeger]

Hi!

> Could I get a committer to apply my latest update patch for
> net-mgmt/prometheus?
> Patch is available here:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216411

Done.

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
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: unable to build java in poudriere

[Ultima]

Sorry Julian but your details are kind of vague. Are you on head? I'm not
sure when my last build for openjdk7 or 8 were but I have them built in my
repo. Is there enough memory on the system building it? or is it limited?
that is usually the culprit for the openjdk ports.

I ask if you were on head because I know java was broken for sometime in
January but was fixed, or at least r312388 is working.

On Tue, Jan 24, 2017 at 8:56 PM, Julian Elischer  wrote:

> from he log file:  (see below)
>
> This dies almost immediately.
> Do we need to prime the build with an older java? (e.g. the bootstrap pkg)?
> If so why does  poudriere not do this?
> I actually want jdk8 but iti insists on building 7 first, which fails.
> Since I don't care about 7 I can prime the pump by downloading a 7 pkg but
> should all this be automatic somehow?
>
> Log:
>
> 
> 
> # Entering langtools for target(s) all #
> 
>
> (cd  ./langtools/make && \
>   gmake JDK_TOPDIR=/wrkdirs/usr/ports/java/openjdk7/work/openjdk/jdk
> JDK_MAKE_SHARED_DIR=/wrkdirs/usr/ports/java/openjdk7/work/openjdk/jdk/make/common/shared
> EXTERNALSANITYCONTROL=true SOURCE_LANGUAGE_VERSION=7 TARGET_CLASS_VERSION=7
> MILESTONE=fcs BUILD_NUMBER=b01 JDK_BUILD_NUMBER=b01
> FULL_VERSION=1.7.0_111-b01 PREVIOUS_JDK_VERSION=1.6. JDK_VERSION=1.7.0_111
> JDK_MKTG_VERSION=7 JDK_MAJOR_VERSION=1 JDK_MINOR_VERSION=7
> JDK_MICRO_VERSION=0_111 PREVIOUS_MAJOR_VERSION=1 PREVIOUS_MINOR_VERSION=6
> PREVIOUS_MICRO_VERSION= PAX_COMMAND=/usr/sbin/paxmark.sh
> PAX_COMMAND_ARGS="-vm" ARCH_DATA_MODEL=64 COOKED_BUILD_NUMBER=1
> ANT_HOME="/wrkdirs/usr/ports/java/openjdk7/work/apache-ant-1.9.7"
> ALT_OUTPUTDIR=/wrkdirs/usr/ports/java/openjdk7/work/openjdk/build/bsd-amd64/langtools
> ALT_BOOTDIR=/usr/local/bootstrap-openjdk all)
> gmake[3]: Entering directory '/wrkdirs/usr/ports/java/openj
> dk7/work/openjdk/langtools/make'
> JAVA_HOME=/usr/local/bootstrap-openjdk ANT_OPTS=-Djava.io.tmpdir='/wr
> kdirs/usr/ports/java/openjdk7/work/openjdk/build/bsd-amd64/langtools/build/ant-tmp'
> /wrkdirs/usr/ports/java/openjdk7/work/apache-ant-1.9.7/bin/ant
> -diagnostics > /wrkdirs/usr/ports/java/openjdk7/work/openjdk/build/bsd-
> amd64/langtools/build/ant-diagnostics.log ; \
>   JAVA_HOME=/usr/local/bootstrap-openjdk ANT_OPTS=-Djava.io.tmpdir='/wr
> kdirs/usr/ports/java/openjdk7/work/openjdk/build/bsd-amd64/langtools/build/ant-tmp'
> /wrkdirs/usr/ports/java/openjdk7/work/apache-ant-1.9.7/bin/ant -version
> >> /wrkdirs/usr/ports/java/openjdk7/work/openjdk/build/bsd-
> amd64/langtools/build/ant-diagnostics.log
> Could not create the Java virtual machine.
> Could not create the Java virtual machine.
> gmake[3]: *** [Makefile:196: /wrkdirs/usr/ports/java/openjd
> k7/work/openjdk/build/bsd-amd64/langtools/build/ant-diagnostics.log]
> Error 1
> gmake[3]: Leaving directory '/wrkdirs/usr/ports/java/openj
> dk7/work/openjdk/langtools/make'
> gmake[2]: *** [make/langtools-rules.gmk:39: langtools-build] Error 2
> gmake[2]: Leaving directory '/wrkdirs/usr/ports/java/openj
> dk7/work/openjdk'
> gmake[1]: *** [Makefile:251: build_product_image] Error 2
> gmake[1]: Leaving directory '/wrkdirs/usr/ports/java/openj
> dk7/work/openjdk'
> *** Error code 1
>
>
> ___
> 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"

unable to build java in poudriere

[Julian Elischer]

from he log file:  (see below)

This dies almost immediately.
Do we need to prime the build with an older java? (e.g. the bootstrap 
pkg)?

If so why does  poudriere not do this?
I actually want jdk8 but iti insists on building 7 first, which fails.
Since I don't care about 7 I can prime the pump by downloading a 7 pkg 
but should all this be automatic somehow?


Log:



# Entering langtools for target(s) all #


(cd  ./langtools/make && \
  gmake JDK_TOPDIR=/wrkdirs/usr/ports/java/openjdk7/work/openjdk/jdk 
JDK_MAKE_SHARED_DIR=/wrkdirs/usr/ports/java/openjdk7/work/openjdk/jdk/make/common/shared 
EXTERNALSANITYCONTROL=true SOURCE_LANGUAGE_VERSION=7 
TARGET_CLASS_VERSION=7 MILESTONE=fcs BUILD_NUMBER=b01 
JDK_BUILD_NUMBER=b01 FULL_VERSION=1.7.0_111-b01 
PREVIOUS_JDK_VERSION=1.6. JDK_VERSION=1.7.0_111 JDK_MKTG_VERSION=7 
JDK_MAJOR_VERSION=1 JDK_MINOR_VERSION=7 JDK_MICRO_VERSION=0_111 
PREVIOUS_MAJOR_VERSION=1 PREVIOUS_MINOR_VERSION=6 
PREVIOUS_MICRO_VERSION= PAX_COMMAND=/usr/sbin/paxmark.sh 
PAX_COMMAND_ARGS="-vm" ARCH_DATA_MODEL=64 COOKED_BUILD_NUMBER=1 
ANT_HOME="/wrkdirs/usr/ports/java/openjdk7/work/apache-ant-1.9.7" 
ALT_OUTPUTDIR=/wrkdirs/usr/ports/java/openjdk7/work/openjdk/build/bsd-amd64/langtools 
ALT_BOOTDIR=/usr/local/bootstrap-openjdk all)
gmake[3]: Entering directory 
'/wrkdirs/usr/ports/java/openjdk7/work/openjdk/langtools/make'
JAVA_HOME=/usr/local/bootstrap-openjdk 
ANT_OPTS=-Djava.io.tmpdir='/wrkdirs/usr/ports/java/openjdk7/work/openjdk/build/bsd-amd64/langtools/build/ant-tmp' 
/wrkdirs/usr/ports/java/openjdk7/work/apache-ant-1.9.7/bin/ant 
-diagnostics > 
/wrkdirs/usr/ports/java/openjdk7/work/openjdk/build/bsd-amd64/langtools/build/ant-diagnostics.log 
; \
  JAVA_HOME=/usr/local/bootstrap-openjdk 
ANT_OPTS=-Djava.io.tmpdir='/wrkdirs/usr/ports/java/openjdk7/work/openjdk/build/bsd-amd64/langtools/build/ant-tmp' 
/wrkdirs/usr/ports/java/openjdk7/work/apache-ant-1.9.7/bin/ant 
-version >> 
/wrkdirs/usr/ports/java/openjdk7/work/openjdk/build/bsd-amd64/langtools/build/ant-diagnostics.log

Could not create the Java virtual machine.
Could not create the Java virtual machine.
gmake[3]: *** [Makefile:196: 
/wrkdirs/usr/ports/java/openjdk7/work/openjdk/build/bsd-amd64/langtools/build/ant-diagnostics.log] 
Error 1
gmake[3]: Leaving directory 
'/wrkdirs/usr/ports/java/openjdk7/work/openjdk/langtools/make'

gmake[2]: *** [make/langtools-rules.gmk:39: langtools-build] Error 2
gmake[2]: Leaving directory 
'/wrkdirs/usr/ports/java/openjdk7/work/openjdk'

gmake[1]: *** [Makefile:251: build_product_image] Error 2
gmake[1]: Leaving directory 
'/wrkdirs/usr/ports/java/openjdk7/work/openjdk'

*** Error code 1


___
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: devel/cargo build failure

[Don Zavitz]

On 1/24/2017 4:20 PM, Fernando Herrero Carrón wrote:

El 24 ene. 2017 9:18 p. m., "Mathieu Arnold"  escribió:

Le 24/01/2017 à 20:27, Fernando Herrero Carrón a écrit :


El 24 ene. 2017 6:57 p. m., "Mathieu Arnold" > escribió:

 Le 24/01/2017 à 18:47, David Wolfskill a écrit :
 > On Tue, Jan 24, 2017 at 06:33:29PM +0100, Mathieu Arnold wrote:
 >> Le 24/01/2017 à 16:52, Bob Willcox a écrit :
 >>> When trying to build devel/cargo I get this error:
 >>>
 >>> /xports/Mk/Scripts/checksum.sh: cannot open
 2016-11-02/cargo-nightly-x86_64-unknown-freebsd.tar.gz: No such
 file or directory
 >>> *** Error code 2
 >>>
 >>> Stop.
 >>> make: stopped in /xports/devel/cargo
 >>>
 >>> Anyone have any ideas why and what I can do to overcome it?
 >> Ok, so, the port changed the directory this file is fetched in,
 to fix
 >> the problem, you'll need to remove the
 >> cargo-nightly-x86_64-unknown-freebsd.tar.gz from
 /usr/ports/distfiles
 >> (or whereever your distfiles are)
 >> 
 > Thanks -- that worked for me.

 So, I opened PR #216442 to see if the code that made this problem was
 legacy or not, an exp-run will tell :-)

 --
 Mathieu Arnold


Wow, cool to see more people doing rust on freebsd, count me in!


I have no idea what rust is, but sure.


http://www.freshports.org/devel/cargo:

Cargo is Rust's Package Manager. Cargo downloads your Rust project's
dependencies and compiles your project.
___
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"


I ran into this issue, removing 
cargo-nightly-x86_64-unknown-freebsd.tar.gz from /usr/ports/distfiles 
fixed it for me...


www/firefox pulls this in, didn't know firefox used rust?
___
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 Port: emacs25-25.1,3

[Joel F Rodriguez]

Hi,

 

I completed a FREEBSD upgrade to 10.3-release and about midway through the 3
day process I lost emacs.

 

I've rebuilt everything, but I still get this error:

 

gmake[4]: Leaving directory '/usr/ports/editors/emacs/work/emacs-25.1/lisp'

./temacs --batch --load loadup bootstrap

gmake[3]: *** [Makefile:737: bootstrap-emacs] Segmentation fault (core
dumped)

gmake[3]: Leaving directory '/usr/ports/editors/emacs/work/emacs-25.1/src'

gmake[2]: *** [Makefile:398: src] Error 2

gmake[2]: Leaving directory '/usr/ports/editors/emacs/work/emacs-25.1'

===> Compilation failed unexpectedly.

Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to

the maintainer.

*** Error code 1

 

I've seen a few posts about this, but no solutions.

 

Please advise.

 

Thanks.

 

Joel Rodriguez

Gossamer Computer Services

___
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: devel/cargo build failure

[Fernando Herrero Carrón]

El 24 ene. 2017 9:18 p. m., "Mathieu Arnold"  escribió:

Le 24/01/2017 à 20:27, Fernando Herrero Carrón a écrit :
>
>
> El 24 ene. 2017 6:57 p. m., "Mathieu Arnold"  > escribió:
>
> Le 24/01/2017 à 18:47, David Wolfskill a écrit :
> > On Tue, Jan 24, 2017 at 06:33:29PM +0100, Mathieu Arnold wrote:
> >> Le 24/01/2017 à 16:52, Bob Willcox a écrit :
> >>> When trying to build devel/cargo I get this error:
> >>>
> >>> /xports/Mk/Scripts/checksum.sh: cannot open
> 2016-11-02/cargo-nightly-x86_64-unknown-freebsd.tar.gz: No such
> file or directory
> >>> *** Error code 2
> >>>
> >>> Stop.
> >>> make: stopped in /xports/devel/cargo
> >>>
> >>> Anyone have any ideas why and what I can do to overcome it?
> >> Ok, so, the port changed the directory this file is fetched in,
> to fix
> >> the problem, you'll need to remove the
> >> cargo-nightly-x86_64-unknown-freebsd.tar.gz from
> /usr/ports/distfiles
> >> (or whereever your distfiles are)
> >> 
> > Thanks -- that worked for me.
>
> So, I opened PR #216442 to see if the code that made this problem was
> legacy or not, an exp-run will tell :-)
>
> --
> Mathieu Arnold
>
>
> Wow, cool to see more people doing rust on freebsd, count me in!


I have no idea what rust is, but sure.


http://www.freshports.org/devel/cargo:

Cargo is Rust's Package Manager. Cargo downloads your Rust project's
dependencies and compiles your project.
___
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: devel/cargo build failure

[Mathieu Arnold]

Le 24/01/2017 à 20:27, Fernando Herrero Carrón a écrit :
>
>
> El 24 ene. 2017 6:57 p. m., "Mathieu Arnold"  > escribió:
>
> Le 24/01/2017 à 18:47, David Wolfskill a écrit :
> > On Tue, Jan 24, 2017 at 06:33:29PM +0100, Mathieu Arnold wrote:
> >> Le 24/01/2017 à 16:52, Bob Willcox a écrit :
> >>> When trying to build devel/cargo I get this error:
> >>>
> >>> /xports/Mk/Scripts/checksum.sh: cannot open
> 2016-11-02/cargo-nightly-x86_64-unknown-freebsd.tar.gz: No such
> file or directory
> >>> *** Error code 2
> >>>
> >>> Stop.
> >>> make: stopped in /xports/devel/cargo
> >>>
> >>> Anyone have any ideas why and what I can do to overcome it?
> >> Ok, so, the port changed the directory this file is fetched in,
> to fix
> >> the problem, you'll need to remove the
> >> cargo-nightly-x86_64-unknown-freebsd.tar.gz from
> /usr/ports/distfiles
> >> (or whereever your distfiles are)
> >> 
> > Thanks -- that worked for me.
>
> So, I opened PR #216442 to see if the code that made this problem was
> legacy or not, an exp-run will tell :-)
>
> --
> Mathieu Arnold
>
>
> Wow, cool to see more people doing rust on freebsd, count me in!


I have no idea what rust is, but sure.


-- 
Mathieu Arnold




signature.asc
Description: OpenPGP digital signature

Re: CFT upgrade to xorg 1.18.4 and newer intel/ati DDX

[Pete Wright]

On 01/24/2017 11:26, Matthieu Volat wrote:

On Tue, 24 Jan 2017 11:12:56 -0800
Pete Wright  wrote:


On 01/24/2017 00:55, Matthieu Volat wrote:

On Tue, 24 Jan 2017 00:55:16 +0100
Baptiste Daroussin  wrote:


Hi all,

This is a call for testing for newer Xorg along with newer drivers: intel and
ati.

The patch against the head ports: https://people.freebsd.org/~bapt/newxorg.diff

Note that you would need to rebuild all the xf86-* packages to work with that
newer xorg (hence the bump of the revision)

Do not expect newer gpu supported as this is not the kernel part.

If you experience any issue with intel or radeon driver please try to use the
new modesetting driver provided by xorg directly (note that fedora and debian
recommands to use that new driver instead of the ati/intel one)

To use that driver:

cat /usr/local/etc/xorg.conf.d/modesetting.conf
Section "Device"
  Identifier "Card0"
  Driver "modesetting"
EndSection

You need to first load the kms driver eiter via loader.conf or manually via
kldload

Best regards,
Bapt of behalf of the X11 team

Looks good with x11/nvidia driver!

Hi Matthieu - did you run into any issues building components from
x11-drivers?  specifically i'm running into this error when attempting
to build x11-drivers/xf86-input-mouse x11-drivers/xf86-video-vesa (among
others):

from vesa build log:

checking if DPMSExtension is defined... yes
checking for XORG... no
configure: error: Package requirements (xorg-server >= 1.6 xproto
fontsproto  randrproto renderproto xextproto) were not met:

Package dri3proto was not found in the pkg-config search path.
Perhaps you should add the directory containing `dri3proto.pc'
to the PKG_CONFIG_PATH environment variable
Package 'dri3proto', required by 'xorg-server', not found


Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.


It's odd because xorg-server built fine as did dri3proto - so I'm not
sure why its not being picked up by poudriere when i attempt to build
these packages.

Cheers!
-pete


Hmm, I did not have the issue when I rebuilt ports, but you're right: it seems 
that dri3proto should be added to ${PORTSDIR}/Mk/bsd.xorg.mk line 61 USE_XORG 
flags...

I think I missed the problem since xorg-server must have brought the dependancy that was 
not removed from my system until I ran "pkg autoremove".


hey thanks for getting back to me, and teaching me a bit more about our 
ports infrastructure :)


that def seemed to fix 'er up - here is a diff:

$ diff -u bsd.xorg.mk.bak bsd.xorg.mk
--- bsd.xorg.mk.bak 2017-01-24 11:27:44.998639000 -0800
+++ bsd.xorg.mk 2017-01-24 11:28:16.089046000 -0800
@@ -59,8 +59,8 @@

 . if ${XORG_CAT} == "driver"
 USE_XORG+= xorg-server xproto randrproto xi renderproto xextproto \
-   inputproto kbproto fontsproto videoproto dri2proto 
xf86driproto \
-   presentproto glproto xineramaproto resourceproto 
scrnsaverproto
+   inputproto kbproto fontsproto videoproto dri2proto 
dri3proto xf86driproto \
+   presentproto glproto xineramaproto resourceproto 
scrnsaverproto

 # work around a llvm bug on i386, llvm bug #15806
 # reproduced with clang 3.2 (current release) and 3.1
 .  if ${ARCH} == i386


Cheers!
-pete
___
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: devel/cargo build failure

[Fernando Herrero Carrón]

El 24 ene. 2017 6:57 p. m., "Mathieu Arnold"  escribió:

Le 24/01/2017 à 18:47, David Wolfskill a écrit :
> On Tue, Jan 24, 2017 at 06:33:29PM +0100, Mathieu Arnold wrote:
>> Le 24/01/2017 à 16:52, Bob Willcox a écrit :
>>> When trying to build devel/cargo I get this error:
>>>
>>> /xports/Mk/Scripts/checksum.sh: cannot open
2016-11-02/cargo-nightly-x86_64-unknown-freebsd.tar.gz: No such file or
directory
>>> *** Error code 2
>>>
>>> Stop.
>>> make: stopped in /xports/devel/cargo
>>>
>>> Anyone have any ideas why and what I can do to overcome it?
>> Ok, so, the port changed the directory this file is fetched in, to fix
>> the problem, you'll need to remove the
>> cargo-nightly-x86_64-unknown-freebsd.tar.gz from /usr/ports/distfiles
>> (or whereever your distfiles are)
>> 
> Thanks -- that worked for me.

So, I opened PR #216442 to see if the code that made this problem was
legacy or not, an exp-run will tell :-)

--
Mathieu Arnold


Wow, cool to see more people doing rust on freebsd, count me in!

Fernando
___
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: FreeBSD Port: libsoxr-0.1.2.20160529_2

[Thomas Zander]

On 24 January 2017 at 11:39, Microsoft Roaming
 wrote:

> This causes a « circular dependency » between ffmpeg and libsoxr

Yes, we know that in this case it is possible to have this dependency
by choosing the wrong options. The default options, however, are
selected such that this does not happen.

Riggs
___
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: CFT upgrade to xorg 1.18.4 and newer intel/ati DDX

[Matthieu Volat]

On Tue, 24 Jan 2017 11:12:56 -0800
Pete Wright  wrote:

> On 01/24/2017 00:55, Matthieu Volat wrote:
> > On Tue, 24 Jan 2017 00:55:16 +0100
> > Baptiste Daroussin  wrote:
> >
> >> Hi all,
> >>
> >> This is a call for testing for newer Xorg along with newer drivers: intel 
> >> and
> >> ati.
> >>
> >> The patch against the head ports: 
> >> https://people.freebsd.org/~bapt/newxorg.diff
> >>
> >> Note that you would need to rebuild all the xf86-* packages to work with 
> >> that
> >> newer xorg (hence the bump of the revision)
> >>
> >> Do not expect newer gpu supported as this is not the kernel part.
> >>
> >> If you experience any issue with intel or radeon driver please try to use 
> >> the
> >> new modesetting driver provided by xorg directly (note that fedora and 
> >> debian
> >> recommands to use that new driver instead of the ati/intel one)
> >>
> >> To use that driver:
> >>
> >> cat /usr/local/etc/xorg.conf.d/modesetting.conf
> >> Section "Device"
> >>  Identifier "Card0"
> >>  Driver "modesetting"
> >> EndSection
> >>
> >> You need to first load the kms driver eiter via loader.conf or manually via
> >> kldload
> >>
> >> Best regards,
> >> Bapt of behalf of the X11 team
> > Looks good with x11/nvidia driver!
> 
> Hi Matthieu - did you run into any issues building components from 
> x11-drivers?  specifically i'm running into this error when attempting 
> to build x11-drivers/xf86-input-mouse x11-drivers/xf86-video-vesa (among 
> others):
> 
> from vesa build log:
> 
> checking if DPMSExtension is defined... yes
> checking for XORG... no
> configure: error: Package requirements (xorg-server >= 1.6 xproto 
> fontsproto  randrproto renderproto xextproto) were not met:
> 
> Package dri3proto was not found in the pkg-config search path.
> Perhaps you should add the directory containing `dri3proto.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'dri3proto', required by 'xorg-server', not found
> 
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> 
> It's odd because xorg-server built fine as did dri3proto - so I'm not 
> sure why its not being picked up by poudriere when i attempt to build 
> these packages.
> 
> Cheers!
> -pete
> 

Hmm, I did not have the issue when I rebuilt ports, but you're right: it seems 
that dri3proto should be added to ${PORTSDIR}/Mk/bsd.xorg.mk line 61 USE_XORG 
flags...

I think I missed the problem since xorg-server must have brought the dependancy 
that was not removed from my system until I ran "pkg autoremove".

-- Matthieu Volat


pgpvzoParoOMW.pgp
Description: OpenPGP digital signature

net-mgmt/prometheus update to 1.5.0, comitter requested

[Jev Björsell]

Hi All,

Could I get a committer to apply my latest update patch for
net-mgmt/prometheus?
Patch is available here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216411

Thanks so much,
-Jev
___
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: CFT upgrade to xorg 1.18.4 and newer intel/ati DDX

[Pete Wright]

On 01/24/2017 00:55, Matthieu Volat wrote:

On Tue, 24 Jan 2017 00:55:16 +0100
Baptiste Daroussin  wrote:


Hi all,

This is a call for testing for newer Xorg along with newer drivers: intel and
ati.

The patch against the head ports: https://people.freebsd.org/~bapt/newxorg.diff

Note that you would need to rebuild all the xf86-* packages to work with that
newer xorg (hence the bump of the revision)

Do not expect newer gpu supported as this is not the kernel part.

If you experience any issue with intel or radeon driver please try to use the
new modesetting driver provided by xorg directly (note that fedora and debian
recommands to use that new driver instead of the ati/intel one)

To use that driver:

cat /usr/local/etc/xorg.conf.d/modesetting.conf
Section "Device"
 Identifier "Card0"
 Driver "modesetting"
EndSection

You need to first load the kms driver eiter via loader.conf or manually via
kldload

Best regards,
Bapt of behalf of the X11 team

Looks good with x11/nvidia driver!


Hi Matthieu - did you run into any issues building components from 
x11-drivers?  specifically i'm running into this error when attempting 
to build x11-drivers/xf86-input-mouse x11-drivers/xf86-video-vesa (among 
others):


from vesa build log:

checking if DPMSExtension is defined... yes
checking for XORG... no
configure: error: Package requirements (xorg-server >= 1.6 xproto 
fontsproto  randrproto renderproto xextproto) were not met:


Package dri3proto was not found in the pkg-config search path.
Perhaps you should add the directory containing `dri3proto.pc'
to the PKG_CONFIG_PATH environment variable
Package 'dri3proto', required by 'xorg-server', not found


Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.


It's odd because xorg-server built fine as did dri3proto - so I'm not 
sure why its not being picked up by poudriere when i attempt to build 
these packages.


Cheers!
-pete

___
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: portmaster showstopper

[Walter Schwarzenfeld]

It is not the port if it already exists. It is the reference in 
x11-drivers/xorg-driver/Makefile.

BUt this should be fixed with this update
https://svnweb.freebsd.org/ports/head/x11-drivers/xorg-drivers/Makefile?r1=432203=432202=432203
___
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"

net-im/prosody update commit request

[Christian Schwarz]

net-im/prosody is at version 0.9.10 and thus two patch versions behind
upstream [0]

There has been a patch in Bugzilla but the maintainer does not respond:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214487

Could someone please commit this?

Thanks,

  Christian

[0] https://prosody.im/doc/release/0.9.12


___
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: FreeBSD Port: mkvtoolnix-9.7.1

[Walter Schwarzenfeld]

I have made a PR with a possible solution
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216445
___
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"

Committer needed to unbreak graphics/llpp

[Tobias Kortkamp]

Hi,

the recent update to mupdf 1.10a broke graphics/llpp.  Can someone
commit the update from https://bugs.freebsd.org/216158 to unbreak it?

Thanks!
___
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: devel/cargo build failure

[Mathieu Arnold]

Le 24/01/2017 à 18:47, David Wolfskill a écrit :
> On Tue, Jan 24, 2017 at 06:33:29PM +0100, Mathieu Arnold wrote:
>> Le 24/01/2017 à 16:52, Bob Willcox a écrit :
>>> When trying to build devel/cargo I get this error:
>>>
>>> /xports/Mk/Scripts/checksum.sh: cannot open 
>>> 2016-11-02/cargo-nightly-x86_64-unknown-freebsd.tar.gz: No such file or 
>>> directory
>>> *** Error code 2
>>>
>>> Stop.
>>> make: stopped in /xports/devel/cargo
>>>
>>> Anyone have any ideas why and what I can do to overcome it?
>> Ok, so, the port changed the directory this file is fetched in, to fix
>> the problem, you'll need to remove the
>> cargo-nightly-x86_64-unknown-freebsd.tar.gz from /usr/ports/distfiles
>> (or whereever your distfiles are)
>> 
> Thanks -- that worked for me.

So, I opened PR #216442 to see if the code that made this problem was
legacy or not, an exp-run will tell :-)

-- 
Mathieu Arnold




signature.asc
Description: OpenPGP digital signature

Re: devel/cargo build failure

[Bob Willcox]

On Tue, Jan 24, 2017 at 09:47:56AM -0800, David Wolfskill wrote:
> On Tue, Jan 24, 2017 at 06:33:29PM +0100, Mathieu Arnold wrote:
> > Le 24/01/2017 à 16:52, Bob Willcox a écrit :
> > > When trying to build devel/cargo I get this error:
> > >
> > > /xports/Mk/Scripts/checksum.sh: cannot open 
> > > 2016-11-02/cargo-nightly-x86_64-unknown-freebsd.tar.gz: No such file or 
> > > directory
> > > *** Error code 2
> > >
> > > Stop.
> > > make: stopped in /xports/devel/cargo
> > >
> > > Anyone have any ideas why and what I can do to overcome it?
> > 
> > Ok, so, the port changed the directory this file is fetched in, to fix
> > the problem, you'll need to remove the
> > cargo-nightly-x86_64-unknown-freebsd.tar.gz from /usr/ports/distfiles
> > (or whereever your distfiles are)
> > 
> 
> Thanks -- that worked for me.

Yep, that fixed it for me as well...thanks.


-- 
Bob Willcox| There's nothing very mysterious about you, except that
b...@immure.com | nobody really knows your origin, purpose, or destination.
Austin, TX |
___
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: devel/cargo build failure

[David Wolfskill]

On Tue, Jan 24, 2017 at 06:33:29PM +0100, Mathieu Arnold wrote:
> Le 24/01/2017 à 16:52, Bob Willcox a écrit :
> > When trying to build devel/cargo I get this error:
> >
> > /xports/Mk/Scripts/checksum.sh: cannot open 
> > 2016-11-02/cargo-nightly-x86_64-unknown-freebsd.tar.gz: No such file or 
> > directory
> > *** Error code 2
> >
> > Stop.
> > make: stopped in /xports/devel/cargo
> >
> > Anyone have any ideas why and what I can do to overcome it?
> 
> Ok, so, the port changed the directory this file is fetched in, to fix
> the problem, you'll need to remove the
> cargo-nightly-x86_64-unknown-freebsd.tar.gz from /usr/ports/distfiles
> (or whereever your distfiles are)
> 

Thanks -- that worked for me.

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
How could one possibly "respect" a misogynist, racist, bullying con-man??!?

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: devel/cargo build failure

[Mathieu Arnold]

Le 24/01/2017 à 16:52, Bob Willcox a écrit :
> When trying to build devel/cargo I get this error:
>
> /xports/Mk/Scripts/checksum.sh: cannot open 
> 2016-11-02/cargo-nightly-x86_64-unknown-freebsd.tar.gz: No such file or 
> directory
> *** Error code 2
>
> Stop.
> make: stopped in /xports/devel/cargo
>
> Anyone have any ideas why and what I can do to overcome it?


Ok, so, the port changed the directory this file is fetched in, to fix
the problem, you'll need to remove the
cargo-nightly-x86_64-unknown-freebsd.tar.gz from /usr/ports/distfiles
(or whereever your distfiles are)


-- 
Mathieu Arnold




signature.asc
Description: OpenPGP digital signature

Re: devel/cargo build failure

[Mathieu Arnold]

Le 24/01/2017 à 16:52, Bob Willcox a écrit :
> When trying to build devel/cargo I get this error:
>
> /xports/Mk/Scripts/checksum.sh: cannot open 
> 2016-11-02/cargo-nightly-x86_64-unknown-freebsd.tar.gz: No such file or 
> directory
> *** Error code 2
>
> Stop.
> make: stopped in /xports/devel/cargo
>
> Anyone have any ideas why and what I can do to overcome it?

The port must be doing something stupid, I'll have a look.


-- 
Mathieu Arnold




signature.asc
Description: OpenPGP digital signature

Re: devel/cargo build failure

[David Wolfskill]

On Tue, Jan 24, 2017 at 09:52:41AM -0600, Bob Willcox wrote:
> When trying to build devel/cargo I get this error:
> 
> /xports/Mk/Scripts/checksum.sh: cannot open 
> 2016-11-02/cargo-nightly-x86_64-unknown-freebsd.tar.gz: No such file or 
> directory
> *** Error code 2
> 
> Stop.
> make: stopped in /xports/devel/cargo
> 
> Anyone have any ideas why and what I can do to overcome it?
> 
> Thanks,
> Bob
> 

No actual suggestion, but I'll confirm that I experienced the same
failure (with a ports working copy @r432320).

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
How could one possibly "respect" a misogynist, racist, bullying con-man??!?

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

devel/cargo build failure

[Bob Willcox]

When trying to build devel/cargo I get this error:

/xports/Mk/Scripts/checksum.sh: cannot open 
2016-11-02/cargo-nightly-x86_64-unknown-freebsd.tar.gz: No such file or 
directory
*** Error code 2

Stop.
make: stopped in /xports/devel/cargo

Anyone have any ideas why and what I can do to overcome it?

Thanks,
Bob

-- 
Bob Willcox| There's nothing very mysterious about you, except that
b...@immure.com | nobody really knows your origin, purpose, or destination.
Austin, TX |
___
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

[Hans Petter Selasky]

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 
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.





Hi Graham,

Looking at the differences between VirtualBOX 5.0.26 and 5.1.14, I see 
the USB proxy backend for FreeBSD was rewritten:


Have a look here:

VirtualBox-5.1.14/src/VBox/Main/src-server/freebsd/USBProxyBackendFreeBSD.cpp

Which was previously:

./work/VirtualBox-5.0.26/src/VBox/Main/src-server/freebsd/USBProxyServiceFreeBSD.cpp

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.


--HPS
___
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: Mumble in pkg

[Christian Schwarz]

On Mon, Jan 23, 2017 at 10:33:26PM +0100, Greg Byshenk wrote:
> Ok, so I think what's going on here is that:
> 
> The pkg version of mumble uses the default system OpenSSL, but
> you've installed the OpenSSL port (via the package). This means
> that the port builds fine - using the non-system OpenSSL that 
> you've installed. But the pkg conflicts, because it wants the
> system OpenSSL -- and /usr/local/lib/* is found first.
> 
> There are probably other ways to fix this, but the easiest is
> to either a) remove the OpenSSL pkg, or b) build mumble as a
> port.
> 
> [Corrections welcome if I have something wrong.]

Shouldn't ports migrate away from using base's OpenSSL?

I would consider reporting this as a bug to the port maintainer...

--
Christian
___
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: portmaster showstopper

[abi]

24.01.2017 16:00, The Doctor пишет:


Getting

===>>> The x11-drivers/xf86-video-fbdev port has been deleted: Linux only driver
===>>> Aborting update

on portmaster -a .


What do I need to stop this from happening?

Probably, delete this package from your system :) fbdev shouldn't work 
on FreeBSD at all


___
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: portmaster showstopper

[Tommy Scheunemann]

Hi,

the quick and dirty way:

pkg remove xf86-video-fbdev

If pkg complains about dependencies, that will be removed as well, note 
them and then:


pkg remove -f xf86-video-fbdev

then reinstall the dependencies (was here the xorg meta-port and 
xorg-video-drivers meta port), then give portmaster another try.


Good luck

On Tue, 24 Jan 2017, The Doctor wrote:




Getting

===>>> The x11-drivers/xf86-video-fbdev port has been deleted: Linux only driver
===>>> Aborting update

on portmaster -a .


What do I need to stop this from happening?

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

portmaster showstopper

[The Doctor]

Getting

===>>> The x11-drivers/xf86-video-fbdev port has been deleted: Linux only driver
===>>> Aborting update

on portmaster -a .


What do I need to stop this from happening?

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! 
http://www.fullyfollow.me/rootnl2k  Look at Psalms 14 and 53 on Atheism
Birthdate 29 Jan 1969 Redhill Surrey England
___
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: FreeBSD Port: mythtv-0.27.5.20150616_1

[Walter Schwarzenfeld]

change   --dvb-path="${LOCALBASE}/include to 
--dvb-path="${LOCALBASE}/include/libdvbv5" in the mythtv Makefile.

*
(There is an PR trying update mythtv to 
28.7https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216237)



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

Nieuwe vacatures voor verkoper 2017-01-24

[alert]

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

Re: FreeBSD Port: chromaprint-1.3.1_1

[Jason E. Hale]

On Tue, Jan 24, 2017 at 5:36 AM, Microsoft Roaming
 wrote:
>
> Chromaprint fails to build when chromaprint build option is activated in
> ffmpeg meta port.
>
> It seems that Chromaprint is requesting an injustified dependency,  so
> trying to build ffmpeg metaport first if non present.
>
> This causes a « circular dependency » between ffmpeg and chromaprint
>

Yes, this is a known issue. See
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208877.
Currently, the ffmpeg port is marked BROKEN if the CHROMAPRINT option
is selected, so you shouldn't be seeing circular dependency problems
unless you specifically removed the BROKEN line. Working around it
would be complicated and is more of an issue for the ffmpeg
maintainer. While the chromaprint library itself can use other fft
libraries, they are not ideal for speed and licensing issues. Plus,
the included fpcalc tool can only use ffmpeg. Do you really need this
functionality for something?

-Jason
___
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 Port: ffmpeg-3.2.2_3,1

[Microsoft Roaming]

Hello,

ffmpeg chromaprint build option is broken.
It fails to build with last chromaprint revision

There is also a bug that I have previously notified to chromaprint port 
maintener as there is at this moment a circular dependency between ffmpeg and 
chromaprint.

Same problem for libsoxr port when SOXR build option is activated except that 
when libsoxr is already installed, ffmpeg can build just after

Testing environment

FreBSD 11 AMD64

Regards,

David

Provenance : Courrier pour 
Windows 10

___
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 Port: libsoxr-0.1.2.20160529_2

[Microsoft Roaming]

Hello,

libsoxr fails to build when SOXR build option is activated in ffmpeg meta port.
It seems that libsoxr is requesting an injustified dependency,  so trying to 
build ffmpeg metaport first if non present.

This causes a « circular dependency » between ffmpeg and libsoxr

Same problem occurs with chromaprint

Testing environment


FreeBSD 11 AMD64

Regards,

David


Provenance : Courrier pour 
Windows 10

___
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 Port: chromaprint-1.3.1_1

[Microsoft Roaming]

Hello,

Chromaprint fails to build when chromaprint build option is activated in ffmpeg 
meta port.
It seems that Chromaprint is requesting an injustified dependency,  so trying 
to build ffmpeg metaport first if non present.

This causes a « circular dependency » between ffmpeg and chromaprint

Same problem occurs with libsoxr

Testing environment


FreeBSD 11 AMD64

Regards,

David

Provenance : Courrier pour 
Windows 10

___
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 Port: mkvtoolnix-9.7.1

[Microsoft Roaming]

Hello,

Mkvtoolnix fails to build when pugixml port is installed
It seems that mkvtoolnix uses the based version of pugixml, unfortunately  
/ftp/filezilla uses port version of pugixml
Could you patch mkvtoolnix either to make be able to use the port version when 
installed or either to force use of base version (preferable)

Testing environment when bug coccurs :

FreeBSD 11 AMD64
FreeBSD 10.3 AMD64 and I386


Regards,

David

Provenance : Courrier pour 
Windows 10

___
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 Port: mythtv-0.27.5.20150616_1

[Microsoft Roaming]

Hello All,

Mythtv doesn’t build when ffmpeg meta port is installed
One must force deinstall ffmpeg metaport, install mythtv, and reinstall 
thereafter ffmpeg meta port

This bug is persistent since few years now… under FreeBSD 9, 10, 11 so I am 
quite sure this is a real bug

This doesn’t seem to affect mythtv-frontend port.

I don’t understand why this has not been fixed since.

Regards

David

Provenance : Courrier pour 
Windows 10

___
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: CFT upgrade to xorg 1.18.4 and newer intel/ati DDX

[Baptiste Daroussin]

On Tue, Jan 24, 2017 at 09:55:55AM +0100, Matthieu Volat wrote:
> On Tue, 24 Jan 2017 00:55:16 +0100
> Baptiste Daroussin  wrote:
> 
> > Hi all,
> > 
> > This is a call for testing for newer Xorg along with newer drivers: intel 
> > and
> > ati.
> > 
> > The patch against the head ports: 
> > https://people.freebsd.org/~bapt/newxorg.diff
> > 
> > Note that you would need to rebuild all the xf86-* packages to work with 
> > that
> > newer xorg (hence the bump of the revision)
> > 
> > Do not expect newer gpu supported as this is not the kernel part.
> > 
> > If you experience any issue with intel or radeon driver please try to use 
> > the
> > new modesetting driver provided by xorg directly (note that fedora and 
> > debian
> > recommands to use that new driver instead of the ati/intel one)
> > 
> > To use that driver:
> > 
> > cat /usr/local/etc/xorg.conf.d/modesetting.conf
> > Section "Device"
> > Identifier "Card0"
> > Driver "modesetting"
> > EndSection
> > 
> > You need to first load the kms driver eiter via loader.conf or manually via
> > kldload
> > 
> > Best regards,
> > Bapt of behalf of the X11 team
> 
> Looks good with x11/nvidia driver!
> 
> In related matters, I noticed that parts of the stack (libclc) require/use 
> llvm 3.9 while the main body (mesa related ports) still use llvm 3.7. I 
> cherry picked very few changes from mesa 12.0 and 13.0 and was able to build 
> graphics/libEGL and graphics/dri with llvm 3.9 too:
> 
> https://gist.githubusercontent.com/mazhe/e094ac71ae25d40d46fd49510311204e/raw/aca8404c14693a3779d618c3c920a97a7fb620fb/ports_mesa_llvm39.diff
> 
> As a nvidia driver user, I guess most of mesa is shortcutted in my config, 
> but maybe that would be of interest to other people? 

An update of mesa will come just after. just want to go step by step

I already have a diff which goes to 3.9 and upgrade to 13.0

but step by step, first xorg.

Thanks for the report and testing with nvidia

Best regards,
Bapt


signature.asc
Description: PGP signature

Manuscript submission invitation for Volume 6, Issue1, 2017

[Editor IJLRST]

___
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: CFT upgrade to xorg 1.18.4 and newer intel/ati DDX

[Matthieu Volat]

On Tue, 24 Jan 2017 00:55:16 +0100
Baptiste Daroussin  wrote:

> Hi all,
> 
> This is a call for testing for newer Xorg along with newer drivers: intel and
> ati.
> 
> The patch against the head ports: 
> https://people.freebsd.org/~bapt/newxorg.diff
> 
> Note that you would need to rebuild all the xf86-* packages to work with that
> newer xorg (hence the bump of the revision)
> 
> Do not expect newer gpu supported as this is not the kernel part.
> 
> If you experience any issue with intel or radeon driver please try to use the
> new modesetting driver provided by xorg directly (note that fedora and debian
> recommands to use that new driver instead of the ati/intel one)
> 
> To use that driver:
> 
> cat /usr/local/etc/xorg.conf.d/modesetting.conf
> Section "Device"
> Identifier "Card0"
> Driver "modesetting"
> EndSection
> 
> You need to first load the kms driver eiter via loader.conf or manually via
> kldload
> 
> Best regards,
> Bapt of behalf of the X11 team

Looks good with x11/nvidia driver!

In related matters, I noticed that parts of the stack (libclc) require/use llvm 
3.9 while the main body (mesa related ports) still use llvm 3.7. I cherry 
picked very few changes from mesa 12.0 and 13.0 and was able to build 
graphics/libEGL and graphics/dri with llvm 3.9 too:

https://gist.githubusercontent.com/mazhe/e094ac71ae25d40d46fd49510311204e/raw/aca8404c14693a3779d618c3c920a97a7fb620fb/ports_mesa_llvm39.diff

As a nvidia driver user, I guess most of mesa is shortcutted in my config, but 
maybe that would be of interest to other people? 

-- Matthieu Volat


pgp5FEqJW1j_t.pgp
Description: OpenPGP digital signature