date:20170202

===> $1 depends on executable: $1 - not found

2017-02-02 Thread Karli Sjöberg

Hello!

(Sent this mail out yesterday but saw that our exchange server had
base64 encoded it, so trying again with my gmail account.)

This is concerning PR 212420. I want to test making new ports for
rubygems sinatra, rack-protection and mustermann, where the existing
ports have lower versions, and I´d like to have them with a higher
version number. Kind of like 'ruby22' vs. 'ruby23'.

I have taken copies of the existing ports, modified them to match the
new versions and made sure to edit to size and hash in their 'distinfo'
files.

'rubygem-mustermann1' and 'rubygem-rack-protection2' (as I have called
them) both build OK but 'rubygem-sinatra2' does not, and I can´t figure
out what the problem is. This is what the error looks like building
with poudriere:
===
===>   rubygem-sinatra2-2.0.0.beta2 depends on package: rubygem-
rack>=2.0 - not found
===>   Installing existing package /packages/All/rubygem-rack-
2.0.1,3.txz
[release103amd64-default-job-01] Installing rubygem-rack-2.0.1,3...
[release103amd64-default-job-01] Extracting rubygem-rack-2.0.1,3:
.. done
===>   rubygem-sinatra2-2.0.0.beta2 depends on package: rubygem-
rack>=2.0 - found
===>   Returning to build of rubygem-sinatra2-2.0.0.beta2
===>   rubygem-sinatra2-2.0.0.beta2 depends on executable: rubygem-
rack-protection2 - not found
===>   Installing existing package /packages/All/rubygem-rack-
protection2-2.0.0.beta2.txz
[release103amd64-default-job-01] Installing rubygem-rack-protection2-
2.0.0.beta2...
[release103amd64-default-job-01] Extracting rubygem-rack-protection2-
2.0.0.beta2: .. done
===>   rubygem-sinatra2-2.0.0.beta2 depends on executable: rubygem-
rack-protection2 - not found
*** Error code 1

Stop.

This is what my 'rubygem-sinatra2' Makefile looks like:
##
PORTNAME=   sinatra
PORTVERSION=2.0.0.beta2
CATEGORIES= www rubygems
MASTER_SITES=   RG
PKGNAMESUFFIX=  2

MAINTAINER= r...@freebsd.org
COMMENT=Classy web development framework in ruby

LICENSE=MIT
LICENSE_FILE=   ${WRKSRC}/LICENSE

RUN_DEPENDS=rubygem-rack>=2.0:www/rubygem-rack \
rubygem-rack-protection2:www/rubygem-rack-protection2 \
mustermann:devel/rubygem-mustermann1 \
rubygem-tilt>=2.0:devel/rubygem-tilt

NO_ARCH=yes
USE_RUBY=   yes
USES=   gem

.include 
##

The other ports are made in a similar fashion. This is my first attempt
at making ports so please excuse my ignorance, but I believe I have
studied how other "suffix" packages look like, "rubygem-rack1{4,5,6}
e.g. and it feels like this should work. I have tried several different
formats to it's RUN_DEPENDS, like:
rubygem-rack-protection2:www/rubygem-rack-protection2
rubygem-rack-protection:www/rubygem-rack-protection2
rack-protection2:www/rubygem-rack-protection2
rack-protection:www/rubygem-rack-protection2

The error is always the same.

What am I missing here? Why does it find and install the package I´ve
made, and still won´t accept it´s there?

PS. Please make sure to CC me directly as I´m not registered to this
list.

Best Regards
Karli Sjöberg
___
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"

TLC required for PR 216599

2017-02-02 Thread Martin Waschbüsch via freebsd-ports

Hi there,

could a committer please provide TLC for the mentioned PR?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216599

Thanks a lot,

Martin
___
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: Recent update to lang/php70 and lang/php71

2017-02-02 Thread Adam Weinberger

> On 2 Feb, 2017, at 7:39, Torsten Zuehlsdorff  wrote:
> 
> On 02.02.2017 15:37, Jim Ohlstein wrote:
>> Hello,
>> 
>> On 02/02/2017 04:35 AM, Torsten Zuehlsdorff wrote:
>>> Hello Jim,
>>> 
 Could not this semantic change have waited for a new version? It forced
 a rebuild of ALL PHP extensions for no reason. They all had a dependency
 on devel/pcre via the main port as it was.
>>> 
>>> Did you use poudriere?
>> 
>> Yes
>> 
>>> 
>>> It wasn't meant to force a rebuild. There was no PORTREVISION bump nor a
>>> new dependency. But poudriere detect a new one, so i would say its a
>>> poudriere bug. Or am i wrong?
>> 
>> Looks like a direct dependency was added. Here's a sample output from a
>> jail that runs PHP70:
>> 
>> Installed packages to be REINSTALLED:
>>[output]
> 
> Yes, it look like, but it wasn't. That's the patch:
> https://svnweb.freebsd.org/ports/head/lang/php71/Makefile?r1=433046=433045=433046
>  
> 
> 
> Only one line was moved more upwards. Nothing more. This shouldn't have 
> caused such a detection.


It’s not, though, because before it was protected within 
!defined(PKGNAMESUFFIX). Previously, only php itself brought in the pcre 
dependency; now all the extensions bring it in too.

# Adam


—
Adam Weinberger
ad...@adamw.org
http://www.adamw.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"

===> $1 depends on executable: $1 - not found

2017-02-02 Thread Karli Sjöberg

Hello!

This is concerning PR 212420. I want to test making new ports for
rubygems sinatra, rack-protection and mustermann, where the existing
ports have lower versions, and I´d like to have them with a higher
version number. Kind of like 'ruby22' vs. 'ruby23'.

I have taken copies of the existing ports, modified them to match the
new versions and made sure to edit to size and hash in their 'distinfo'
files.

'rubygem-mustermann1' and 'rubygem-rack-protection2' (as I have called
them) both build OK but 'rubygem-sinatra2' does not, and I can´t figure
out what the problem is. This is what the error looks like building
with poudriere:
===
===>   rubygem-sinatra2-2.0.0.beta2 depends on package: rubygem-rack>=2.0 - not 
found
===>   Installing existing package /packages/All/rubygem-rack-2.0.1,3.txz
[release103amd64-default-job-01] Installing rubygem-rack-2.0.1,3...
[release103amd64-default-job-01] Extracting rubygem-rack-2.0.1,3: .. 
done
===>   rubygem-sinatra2-2.0.0.beta2 depends on package: rubygem-rack>=2.0 - 
found
===>   Returning to build of rubygem-sinatra2-2.0.0.beta2
===>   rubygem-sinatra2-2.0.0.beta2 depends on executable: 
rubygem-rack-protection2 - not found
===>   Installing existing package 
/packages/All/rubygem-rack-protection2-2.0.0.beta2.txz
[release103amd64-default-job-01] Installing 
rubygem-rack-protection2-2.0.0.beta2...
[release103amd64-default-job-01] Extracting 
rubygem-rack-protection2-2.0.0.beta2: .. done
===>   rubygem-sinatra2-2.0.0.beta2 depends on executable: 
rubygem-rack-protection2 - not found
*** Error code 1

Stop.

This is what my 'rubygem-sinatra2' Makefile looks like:
##
PORTNAME=   sinatra
PORTVERSION=2.0.0.beta2
CATEGORIES= www rubygems
MASTER_SITES=   RG
PKGNAMESUFFIX=  2

MAINTAINER= r...@freebsd.org
COMMENT=Classy web development framework in ruby

LICENSE=MIT
LICENSE_FILE=   ${WRKSRC}/LICENSE

RUN_DEPENDS=rubygem-rack>=2.0:www/rubygem-rack \
rubygem-rack-protection2:www/rubygem-rack-protection2 \
mustermann:devel/rubygem-mustermann1 \
rubygem-tilt>=2.0:devel/rubygem-tilt

NO_ARCH=yes
USE_RUBY=   yes
USES=   gem

.include 
##

The other ports are made in a similar fashion. This is my first attempt
at making ports so please excuse my ignorance, but I believe I have
studied how other "suffix" packages look like, "rubygem-rack1{4,5,6}
e.g. and it feels like this should work. I have tried several different
formats to it's RUN_DEPENDS, like:
rubygem-rack-protection2:www/rubygem-rack-protection2
rubygem-rack-protection:www/rubygem-rack-protection2
rack-protection2:www/rubygem-rack-protection2
rack-protection:www/rubygem-rack-protection2

The error is always the same.

What am I missing here? Why does it find and install the package I´ve
made, and still won´t accept it´s there?

Best Regards
Karli Sjöberg
___
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: phantomjs build failure system/compiler not supported.

2017-02-02 Thread Johan Hendriks



Op 01/02/2017 om 16:56 schreef Volodymyr Kostyrko:
> Johan Hendriks wrote:
>> Hello I try to build grafana3 which has phantomjs as a dependency, but i
>> get a system compiler error.
>
> Yeah, grafana is getting the hype.
>
> I think gcc++49 line at files/patch-src_qt_qtbase_configure is causing
> the breakage:
>
> Index: files/patch-src_qt_qtbase_configure
> ===
> --- files/patch-src_qt_qtbase_configure (revision 432991)
> +++ files/patch-src_qt_qtbase_configure (working copy)
> @@ -8,7 +8,7 @@
>
>   # find out which awk we want to use, prefer gawk, then nawk, then
> regular awk
>   AWK=
> -@@ -2791,11 +2792,19 @@ if [ -z "$PLATFORM" ]; then
> +@@ -2791,11 +2792,18 @@ if [ -z "$PLATFORM" ]; then
>ULTRIX:*)
>   PLATFORM=ultrix-g++
>   ;;
> @@ -25,11 +25,10 @@
>  +type g++   >/dev/null && PLATFORM=freebsd-g++
>  +type g++46 >/dev/null && PLATFORM=freebsd-g++46
>  +type g++48 >/dev/null && PLATFORM=freebsd-g++48
> -+type g++49 >/dev/null && PLATFORM=freebsd-g++49
>   ;;
>OpenBSD:*)
>   PLATFORM=openbsd-g++
> -@@ -6359,7 +6368,7 @@ case "$XPLATFORM" in
> +@@ -6358,7 +6367,7 @@ case "$XPLATFORM" in
> ;;
>   *-g++*)
> # Check gcc's version
>
Hello, thanks for your answer.
I changed the file to the following, but the error remains.

--- src/qt/qtbase/configure.orig2015-12-12 12:58:05 UTC
+++ src/qt/qtbase/configure
@@ -51,6 +51,7 @@ mactests="$relpath/config.tests/mac"
 WHICH="$unixtests/which.test"

 PERL=`$WHICH perl 2>/dev/null`
+export CXX=${CXX}

 # find out which awk we want to use, prefer gawk, then nawk, then
regular awk
 AWK=
@@ -2791,11 +2792,18 @@ if [ -z "$PLATFORM" ]; then
  ULTRIX:*)
 PLATFORM=ultrix-g++
 ;;
+# FreeBSD:10.[0-9]*)
+#echo "=== ($UNAME_RELEASE) ==="
+#PLATFORM=freebsd-clang
+#;;
  FreeBSD:*)
-PLATFORM=freebsd-g++
+PLATFORM=freebsd-clang
 PLATFORM_NOTES="
 - Also available for FreeBSD: freebsd-icc
 "
+type g++   >/dev/null && PLATFORM=freebsd-g++
+type g++46 >/dev/null && PLATFORM=freebsd-g++46
+type g++48 >/dev/null && PLATFORM=freebsd-g++48
 ;;
  OpenBSD:*)
 PLATFORM=openbsd-g++
@@ -6358,7 +6367,7 @@ case "$XPLATFORM" in
;;
 *-g++*)
# Check gcc's version
-   case "$(${QMAKE_CONF_COMPILER} -dumpversion)" in
+   case "$(${TEST_COMPILER} -dumpversion)" in
4*|3.4*)
;;
 3.3*)

Is it that I am on FreeBSD 11-STABLE?
It did build on a FreeBSD 11.0 server and that did install without a
problem. This is a 11.0 poudriere jail running on the 11-stable host.

regards
Johan Hendriks


___
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: Recent update to lang/php70 and lang/php71

2017-02-02 Thread Torsten Zuehlsdorff


On 02.02.2017 15:37, Jim Ohlstein wrote:

Hello,

On 02/02/2017 04:35 AM, Torsten Zuehlsdorff wrote:

Hello Jim,


Could not this semantic change have waited for a new version? It forced
a rebuild of ALL PHP extensions for no reason. They all had a dependency
on devel/pcre via the main port as it was.


Did you use poudriere?


Yes



It wasn't meant to force a rebuild. There was no PORTREVISION bump nor a
new dependency. But poudriere detect a new one, so i would say its a
poudriere bug. Or am i wrong?


Looks like a direct dependency was added. Here's a sample output from a
jail that runs PHP70:

Installed packages to be REINSTALLED:
[output]


Yes, it look like, but it wasn't. That's the patch:
https://svnweb.freebsd.org/ports/head/lang/php71/Makefile?r1=433046=433045=433046

Only one line was moved more upwards. Nothing more. This shouldn't have 
caused such a detection.


Greetings,
Torsten
___
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: Recent update to lang/php70 and lang/php71

2017-02-02 Thread Jim Ohlstein


Hello,

On 02/02/2017 04:35 AM, Torsten Zuehlsdorff wrote:

Hello Jim,


Could not this semantic change have waited for a new version? It forced
a rebuild of ALL PHP extensions for no reason. They all had a dependency
on devel/pcre via the main port as it was.


Did you use poudriere?


Yes



It wasn't meant to force a rebuild. There was no PORTREVISION bump nor a
new dependency. But poudriere detect a new one, so i would say its a
poudriere bug. Or am i wrong?


Looks like a direct dependency was added. Here's a sample output from a 
jail that runs PHP70:


Installed packages to be REINSTALLED:
php70-zlib-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-zip-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-xsl-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-xmlwriter-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-xmlreader-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-xml-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-wddx-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-sqlite3-7.0.15 [poudriere-php70] (direct dependency changed: pcre)
php70-simplexml-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-session-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-posix-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-pdo_sqlite-7.0.15 [poudriere-php70] (direct dependency changed: 
pcre)
php70-pdo_mysql-7.0.15 [poudriere-php70] (direct dependency changed: 
pcre)
php70-pdo-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-openssl-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-mbstring-7.0.15 [poudriere-php70] (direct dependency changed: 
pcre)
php70-json-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-iconv-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-hash-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-filter-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-fileinfo-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-exif-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-dom-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-curl-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-ctype-7.0.15 [poudriere-php70] (direct dependency added: pcre)
php70-bz2-7.0.15 [poudriere-php70] (direct dependency added: pcre)



--
Jim Ohlstein
___
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: Recent update to lang/php70 and lang/php71

2017-02-02 Thread Torsten Zuehlsdorff


Hello Jim,


Could not this semantic change have waited for a new version? It forced
a rebuild of ALL PHP extensions for no reason. They all had a dependency
on devel/pcre via the main port as it was.


Did you use poudriere?

It wasn't meant to force a rebuild. There was no PORTREVISION bump nor a 
new dependency. But poudriere detect a new one, so i would say its a 
poudriere bug. Or am i wrong?


Sorry for the rebuild - this wasn't intended. :/

Greetings,
Torsten
___
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"

===> $1 depends on executable: $1 - not found

TLC required for PR 216599

Re: Recent update to lang/php70 and lang/php71

===> $1 depends on executable: $1 - not found

Re: phantomjs build failure system/compiler not supported.

Re: Recent update to lang/php70 and lang/php71

Re: Recent update to lang/php70 and lang/php71

Re: Recent update to lang/php70 and lang/php71

8 matches

Site Navigation

Mail list logo

Footer information