[QAT] r333283: 2x leftovers, 2x success

[Ports-QAT]

- Unbreak build on 10.x and -CURRENT
- Use a modern GCC toolchain to unbreak the build on 8.x
- Force 32-bit mode on i386
- Enhance default OPTIONs for a better usability of the port

Supported by:   John Van Sickle 
-

  Build ID:  20131109122200-10978
  Job owner: m...@freebsd.org
  Buildtime: 13 minutes
  Enddate:   Sat, 09 Nov 2013 12:35:17 GMT

  Revision:  r333283
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=333283

-

Port:multimedia/libav 9.10_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20131109122200-10978-224020/libav-9.10_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20131109122200-10978-224021/libav-9.10_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20131109122200-10978-224022/libav-9.10_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~m...@freebsd.org/20131109122200-10978-224023/libav-9.10_1.log


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

Re: Anyone looked at making a port for https://www.eff.org/https-everywhere ?

[Alexey Dokuchaev]

On Thu, Nov 07, 2013 at 02:34:00PM +0100, Julian H. Stacey wrote:
> Has anyone looked at making a ports wrapper for
> https://www.eff.org/https-everywhere ?
> 
> Sources: https://www.eff.org/https-everywhere/development
> 
> PS on current/ports, grep https-everywhere shows nothing,
> grep www.eff.org shows just security/switzerland/, port creator
> Alexey Dokuchaev  added to CC.

Oh, that's a blast from the past. :)  Frankly I already forgot why I decided
to port it, probably because I needed it back in those days.  I'm afraid I
cannot say anything about https-everywhere as a whole.

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

Re: [pkg-fall...@freebsd.org: [REL - head-amd64-default][textproc/multimarkdown] Failed for multimarkdown-4.3.2 in checksum]

[Jimmy Kelley]

On Fri, Nov 08, 2013 at 09:55:00AM -0500, Adam Weinberger wrote:
> Hi, I'm still having trouble with this. Can anybody offer me some advice
> here? During which build stages may my port dial out? When "make
> checksum" is run independently of "make fetch", it begins by wiping out
> ${WRKDIR}.
> 
> Can I dial out during do-build on the package cluster?
> 
> # Adam
> 
> 
> --
> Adam Weinberger
> ad...@adamw.org
> http://www.adamw.org

> Date: Fri, 8 Nov 2013 05:47:29 GMT
> From: pkg-fall...@freebsd.org
> To: ad...@freebsd.org
> Cc: pkg-fall...@freebsd.org
> Subject: [REL - head-amd64-default][textproc/multimarkdown] Failed for
>  multimarkdown-4.3.2 in checksum
> 
> You are receiving this mail as a port that you maintain
> is failing to build on the FreeBSD package build server.
> Please investigate the failure and submit a PR to fix
> build.
> 
  

Hi Adam,

   I've been working on a port for the latest version of Eclipse, which will
have to clone the eclipse git repo along with a bunch of submodules as you are
doing with the multimarkdown port.  I will tell you that what has to be
pulled down is HUGH, and it really was a pain to wait for that fetch to happen
when I wanted to clean and rebuild because of some build error.  What I ended
up doing is have the fetch  phase pull the git repo down into the DISTDIR area
("git clone" if it's not there, "git update" if it is already there" ), and
then have the extract phase copy the stuff in DISTDIR over to WRKSRC where
it can be patched and built; a "clean" copy is always left in DISTDIR, just
like the tarballs of other ports.

This might sound like overkill (it's 2+Gb per copy of the git repo), but
for eclipse it's necessary because the build process needs the repo history
for timestamp info, and it really does speed things up (and will for future
port updates).

Perhaps this might help with the multimarkdown port...

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

[QAT] r333297: 4x leftovers

[Ports-QAT]

devel/thrift-cpp: C++ interface to Thrift

WWW: http://thrift.apache.org/

PR: ports/183060
Submitted by:   Valery Komarov 
-

  Build ID:  20131109151200-28105
  Job owner: w...@freebsd.org
  Buildtime: 8 minutes
  Enddate:   Sat, 09 Nov 2013 15:19:55 GMT

  Revision:  r333297
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=333297

-

Port:devel/thrift-cpp 0.9.1,1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109151200-28105-224080/thrift-cpp-0.9.1,1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109151200-28105-224081/thrift-cpp-0.9.1,1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109151200-28105-224082/thrift-cpp-0.9.1,1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109151200-28105-224083/thrift-cpp-0.9.1,1.log


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

Re: ports default version system

[Florian Smeets]

On 09/11/13 05:42, Eitan Adler wrote:
> On Fri, Nov 8, 2013 at 9:34 PM, Allan Jude  wrote:
>> Attached is a proposed patch for Mk/bsd.default-versions.mk

I had a quick look at the PHP and MySQL parts and they look sane to me,
but don't take this as an Approved by, as I'm sure ale want's to have a
look at it, too. :)

> DEFAULT_VERSIONS is a really poorly thought out API which is hard to
> read, hard to parse, and makes make -V far less useful.  It pushes
> parsing logic into every single consumer.

Why do we have to discuss this in a thread that just extends the usage
of the feature, and not the original commit/discussion? Please don't
hijack this thread.

Florian



signature.asc
Description: OpenPGP digital signature

[QAT] r333298: 4x leftovers

[Ports-QAT]

devel/thrift-c_glib: C glib interface to Thrift

WWW: http://thrift.apache.org/

PR: ports/183057
Submitted by:   Valery Komarov 
-

  Build ID:  20131109152001-13016
  Job owner: w...@freebsd.org
  Buildtime: 16 minutes
  Enddate:   Sat, 09 Nov 2013 15:36:04 GMT

  Revision:  r333298
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=333298

-

Port:devel/thrift-c_glib 0.9.1,1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109152001-13016-224084/thrift-c_glib-0.9.1,1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109152001-13016-224085/thrift-c_glib-0.9.1,1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109152001-13016-224086/thrift-c_glib-0.9.1,1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109152001-13016-224087/thrift-c_glib-0.9.1,1.log


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

Re: ports default version system

[Mark Felder]

On Nov 8, 2013, at 20:34, Allan Jude  wrote:

> and change the default version of php from lang/php5 to lang/php53

Wouldn't that need to be set to lang/php54 as default?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD Port: node-0.8.14 on NAS4Free

[Michael Herrmann]

Hello,

I use NAS4Free as my personal server and I would like to run node.js on it. I 
tried pkg_add -r node and got node version 0.8.14.

But instead of the prompt I get: FATAL ERROR: v8::Context::New() V8 is no 
longer usable

I tried the same on a FreeBSD (virtual) machine and it runs fine. Googling gave 
some hint regarding memory usage, but after transfering
ulimit from FreeBSD to NAS4Free it gave:

$ ulimit -v
unlimited

Now I have no more idea what I can do. Do you perhaps have any idea?

regards
 Michael

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

Re: ports default version system

[Allan Jude]

On 2013-11-09 11:00, Mark Felder wrote:
> On Nov 8, 2013, at 20:34, Allan Jude  wrote:
>
>> and change the default version of php from lang/php5 to lang/php53
> Wouldn't that need to be set to lang/php54 as default?
The port for php 5.4 is called lang/php5 

confusingly, the default port for php is always lang/php5, and every
other version is lang/php53 or lang/php55 etc. so when the default gets
bumped, php 5.4 will become lang/php54 and php5.5 will change from
lang/php55 to lang/php5

-- 
Allan Jude




signature.asc
Description: OpenPGP digital signature

Re: ports default version system

[Mark Felder]

On Nov 9, 2013, at 11:09, Allan Jude  wrote:

> On 2013-11-09 11:00, Mark Felder wrote:
>> On Nov 8, 2013, at 20:34, Allan Jude  wrote:
>> 
>>> and change the default version of php from lang/php5 to lang/php53
>> Wouldn't that need to be set to lang/php54 as default?
> The port for php 5.4 is called lang/php5 
> 
> confusingly, the default port for php is always lang/php5, and every
> other version is lang/php53 or lang/php55 etc. so when the default gets
> bumped, php 5.4 will become lang/php54 and php5.5 will change from
> lang/php55 to lang/php5
> 

Maybe this should be coordinated with the move of lang/php5 to lang/php54 then? 
PHP 5.3 is EOL as of March and only receives critical security fixes now. It 
would also unexpectedly downgrade existing users to 5.3 in some scenarios.

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

Re: ports default version system

[Florian Smeets]

On 09/11/13 18:14, Mark Felder wrote:
> 
> On Nov 9, 2013, at 11:09, Allan Jude  wrote:
> 
>> On 2013-11-09 11:00, Mark Felder wrote:
>>> On Nov 8, 2013, at 20:34, Allan Jude 
>>> wrote:
>>> 
 and change the default version of php from lang/php5 to
 lang/php53
>>> Wouldn't that need to be set to lang/php54 as default?
>> The port for php 5.4 is called lang/php5
>> 
>> confusingly, the default port for php is always lang/php5, and
>> every other version is lang/php53 or lang/php55 etc. so when the
>> default gets bumped, php 5.4 will become lang/php54 and php5.5 will
>> change from lang/php55 to lang/php5

No. lang/php5 will die, see r321684 and
http://lists.freebsd.org/pipermail/freebsd-ports/2013-July/084714.html

>> 
> 
> Maybe this should be coordinated with the move of lang/php5 to
> lang/php54 then? PHP 5.3 is EOL as of March and only receives
> critical security fixes now. It would also unexpectedly downgrade
> existing users to 5.3 in some scenarios.
> 

I think you misunderstood what Alan said, as did I on my first read of
the email.

> Users can specify in /etc/make.conf
>
> DEFAULT_VERSIONS= perl5=5.18 ruby=2.0 php=5.3 mysql=55p
>
> and change the default version of php from lang/php5 to lang/php53

On reading this a second time it became clear to me that he is not
suggesting changing the default PHP to 5.3, it was merely an example
what users can do if they build their own packages.

Florian



signature.asc
Description: OpenPGP digital signature

Re: ports default version system

[Mark Felder]

On Nov 9, 2013, at 11:47, Florian Smeets  wrote:

> On reading this a second time it became clear to me that he is not
> suggesting changing the default PHP to 5.3, it was merely an example
> what users can do if they build their own packages.

Yep. My mistake!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

[QAT] r333306: 15x depend (fetch in devel/json-c), 4x depend_object, 1x fetch, 34x success, 2x leftovers

[Ports-QAT]

devel/json-c: update to 0.11

- Update to 0.11
- Bump revision of dependent ports
- Fix pkg-plist [1]

PR: ports/182958
Submitted by:   zi, wg [1]
Approved by:maintainer (timeout)
-

  Build ID:  20131109155800-43812
  Job owner: w...@freebsd.org
  Buildtime: 2 hours
  Enddate:   Sat, 09 Nov 2013 17:58:25 GMT

  Revision:  r06
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=06

-

Port:audio/pianobar 2013.09.15_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   DEPEND (FETCH IN DEVEL/JSON-C)
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224112/json-c-0.11.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   DEPEND (FETCH IN DEVEL/JSON-C)
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224113/json-c-0.11.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224114/pianobar-2013.09.15_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224115/pianobar-2013.09.15_1.log

-

Port:databases/postgis20 2.0.2_4

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   DEPEND (FETCH IN DEVEL/JSON-C)
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224116/json-c-0.11.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224117/postgis-2.0.2_4.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224118/postgis-2.0.2_4.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224119/postgis-2.0.2_4.log

-

Port:databases/postgis21 2.1.0_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   DEPEND (FETCH IN DEVEL/JSON-C)
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224120/json-c-0.11.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224121/postgis-2.1.0_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224122/postgis-2.1.0_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224123/postgis-2.1.0_1.log

-

Port:devel/json-c 0.11

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   FETCH
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224124/json-c-0.11.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224125/json-c-0.11.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224126/json-c-0.11.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224127/json-c-0.11.log

-

Port:graphics/mypaint 1.1.0_2

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   DEPEND (FETCH IN DEVEL/JSON-C)
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224128/json-c-0.11.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   DEPEND (FETCH IN DEVEL/JSON-C)
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224129/json-c-0.11.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224130/mypaint-1.1.0_2.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224131/mypaint-1.1.0_2.log

-

Port:net/grive 0.2.0_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131109155800-43812-224132/grive-0.2.0_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https:/

DEFAULT_VERSIONS vs DEFAULT_${PORT}_VERSION

[Eitan Adler]

[ apologies to users of threaded mail clients]

On Sat, Nov 9, 2013 at 4:21 AM, Florian Smeets  wrote:
>> DEFAULT_VERSIONS is a really poorly thought out API which is hard to
>> read, hard to parse, and makes make -V far less useful.  It pushes
>> parsing logic into every single consumer.
>
> Why do we have to discuss this in a thread that just extends the usage
> of the feature, and not the original commit/discussion?

I was discussing this #bsdports and was asked to reply on the mailing lists.

In any case since DEFAULT_VERSIONS isn't widely used now would be a
good time to fix it.


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

continued graphics/opencv-core problems

[Chess Griffin]

For about 2-3 weeks now, I have continued to run into problems with 
opencv-core not building on my 9.2-RELEASE poudriere box that uses 
clang.  I reported it here:


http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/183238

This problem prevents me from building multimedia/ffmpeg which in turn 
causes a bunch of issues with other ports, including audacious-plugins.


Has anyone else run into this or have a solution?  Thanks in advance.

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

[QAT] r333331: 4x leftovers

[Ports-QAT]

Forgot to commit this port in the previous USES=kmod conversion.
-

  Build ID:  20131109192200-41444
  Job owner: r...@freebsd.org
  Buildtime: 41 minutes
  Enddate:   Sat, 09 Nov 2013 20:02:42 GMT

  Revision:  r31
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=31

-

Port:emulators/virtualbox-ose-kmod-legacy 4.1.24

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~r...@freebsd.org/20131109192200-41444-224308/virtualbox-ose-kmod-legacy-4.1.24.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~r...@freebsd.org/20131109192200-41444-224309/virtualbox-ose-kmod-legacy-4.1.24.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~r...@freebsd.org/20131109192200-41444-224310/virtualbox-ose-kmod-legacy-4.1.24.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~r...@freebsd.org/20131109192200-41444-224311/virtualbox-ose-kmod-legacy-4.1.24.log


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

Re: [QAT] r333331: 4x leftovers

[René Ladan]

2013/11/9 Ports-QAT :
> Forgot to commit this port in the previous USES=kmod conversion.
> -
>
>   Build ID:  20131109192200-41444
>   Job owner: r...@freebsd.org
>   Buildtime: 41 minutes
>   Enddate:   Sat, 09 Nov 2013 20:02:42 GMT
>
>   Revision:  r31
>   Repository:
> https://svnweb.freebsd.org/ports?view=revision&revision=31
>
This is about QAT noticing /boot/modules gone missing after
deinstalling the package, should this be added to mtree?

> -
>
> Port:emulators/virtualbox-ose-kmod-legacy 4.1.24
>
>   Buildgroup: 8.4-QAT/amd64
>   Buildstatus:   LEFTOVERS
>   Log: 
> https://qat.redports.org//~r...@freebsd.org/20131109192200-41444-224308/virtualbox-ose-kmod-legacy-4.1.24.log
>
>   Buildgroup: 8.4-QAT/i386
>   Buildstatus:   LEFTOVERS
>   Log: 
> https://qat.redports.org//~r...@freebsd.org/20131109192200-41444-224309/virtualbox-ose-kmod-legacy-4.1.24.log
>
>   Buildgroup: 9.2-QAT/amd64
>   Buildstatus:   LEFTOVERS
>   Log: 
> https://qat.redports.org//~r...@freebsd.org/20131109192200-41444-224310/virtualbox-ose-kmod-legacy-4.1.24.log
>
>   Buildgroup: 9.2-QAT/i386
>   Buildstatus:   LEFTOVERS
>   Log: 
> https://qat.redports.org//~r...@freebsd.org/20131109192200-41444-224311/virtualbox-ose-kmod-legacy-4.1.24.log
>
>
> --
> Buildarchive URL: 
> redports 

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

Re: continued graphics/opencv-core problems

[Thierry Thomas]

Le sam  9 nov 13 à 21:00:51 +0100, Chess Griffin 
 écrivait :
> For about 2-3 weeks now, I have continued to run into problems with 
> opencv-core not building on my 9.2-RELEASE poudriere box that uses 
> clang.  I reported it here:
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/183238
> 
> This problem prevents me from building multimedia/ffmpeg which in turn 
> causes a bunch of issues with other ports, including audacious-plugins.
> 
> Has anyone else run into this or have a solution?  Thanks in advance.

As I need it for my ports, I has just been rebuilt in poudriere, and
everything is fine.

Full log available at


Is your poudriere's ports tree up-to-date?
-- 
Th. Thomas.


pgpH3XNxVw6Hl.pgp
Description: PGP signature

Re: continued graphics/opencv-core problems

[Jason E. Hale]

On Saturday, November 09, 2013 15:00:51 Chess Griffin wrote:
> For about 2-3 weeks now, I have continued to run into problems with
> opencv-core not building on my 9.2-RELEASE poudriere box that uses
> clang.  I reported it here:
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/183238
> 
> This problem prevents me from building multimedia/ffmpeg which in turn
> causes a bunch of issues with other ports, including audacious-plugins.
> 
> Has anyone else run into this or have a solution?  Thanks in advance.

Sorry for my silence on the matter.  I have been extremely busy lately.  The 
problem seems to be that you don't have libc++ installed.  At the moment, if 
you wish to build with clang, the port must link to libc++.  Otherwise, I 
suggest building with gcc (still the default compiler on 9.2).

I do plan to address this in the next update which should hopefully be soon.  
I just have a few more bugs to work out.

-- 
Jason E. Hale - jhale@
FreeBSD Ports Committer
KDE/FreeBSD Team
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Unable to "make clean"

[Jerry]

This is a brand new on me. I tried to build the latest firefox port but
it failed. I then tried to do a "make clean", but it failed also. I
could not even manually remove the work directory. I finally went down
the path until I reached
"/usr/ports/www/firefox/work/mozilla-release/browser/base/content/test".
I can not even get a true listing of the directory. This is the output
when I attempt to do so:

ls: blockPluginHard.xml: Input/output error
ls: browser_addKeywordSearch.js: Input/output error
ls: browser_addon_bar.js: Input/output error
ls: browser_bug386835.js: Input/output error
ls: browser_bug419612.js: Input/output error
ls: browser_bug424101.js: Input/output error
ls: browser_bug455852.js: Input/output error
ls: browser_bug462673.js: Input/output error
ls: browser_bug533232.js: Input/output error
ls: browser_bug550565.js: Input/output error
ls: browser_bug553455.js: Input/output error
ls: browser_bug559991.js: Input/output error
ls: browser_bug575830.js: Input/output error
ls: browser_bug581242.js: Input/output error
ls: browser_bug590206.js: Input/output error
ls: browser_bug599325.js: Input/output error
ls: browser_bug734076.js: Input/output error
ls: browser_bug735471.js: Input/output error
ls: browser_getshortcutoruri.js: Input/output error
ls: browser_minimize.js: Input/output error
ls: browser_pageInfo.js: Input/output error
ls: browser_pluginCrashCommentAndURL.js: Input/output error
ls: browser_pluginplaypreview.js: Input/output error
ls: browser_plugins_added_dynamically.js: Input/output error
ls: browser_popupNotification.js: Input/output error
ls: browser_private_browsing_window.js: Input/output error
ls: browser_sanitize-sitepermissions.js: Input/output error
ls: browser_scope.js: Input/output error
ls: browser_tab_dragdrop2_frame1.xul: Input/output error
ls: browser_visibleTabs_bookmarkAllTabs.js: Input/output error
ls: browser_zbug569342.js: Input/output error
ls: file_fullscreen-window-open.html: Input/output error
ls: gZipOfflineChild.cacheManifest: Input/output error
ls: gZipOfflineChild_uncompressed.html: Input/output error
ls: offlineChild.html: Input/output error
ls: offlineChild2.cacheManifest: Input/output error
ls: offlineEvent.cacheManifest^headers^: Input/output error
ls: page_style_sample.html: Input/output error
ls: plugin_bug820497.html: Input/output error
ls: plugin_test2.html: Input/output error
ls: print_postdata.sjs: Input/output error
ls: social: Input/output error
ls: title_test.svg: Input/output error
total 14

I have never ran into this before. How do I clean up this mess so I can
attempt to build the port? I am unable to manually delete any of the
files.

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__

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

Re: Unable to "make clean"

[Matthew Seaman]

On 09/11/2013 23:02, Jerry wrote:
> I have never ran into this before. How do I clean up this mess so I can
> attempt to build the port? I am unable to manually delete any of the
> files.

Unmount the partition and run fsck over it.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey




signature.asc
Description: OpenPGP digital signature

full documentation for all @'s in pkg-plist

[Aryeh Friedman]

Where would I find a complete list of @'s allowed in pkg-plist and
hopefully an explination of each one? (the porter's handbook is incomplete)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: full documentation for all @'s in pkg-plist

[Julien Laffaye]

On 11/10/2013 12:47 AM, Aryeh Friedman wrote:

Where would I find a complete list of @'s allowed in pkg-plist and
hopefully an explination of each one? (the porter's handbook is incomplete)



In the manpage pkg_create(1).
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

opvp support seems broken in ghostscript port

[Perry Hutchison]

Has anyone been able to use the opvp support in ghostscript?

It works fine displaying to the screen, but when I specify
-sDEVICE=opvp I get

   Unable to open the initial device, quitting.

If I also specify -dINITDEBUG=1 (which turns on debug output in the
initialization file, gs_init.ps) I get a lot of messages showing
progress through the initialization process -- none of which seem
to have anything to do with device choice, nor to be much different
from what INITDEBUG produces when displaying to the screen -- until

  END FONTS 219 2605656 1227805 1417680 125870 true 1166 4 <0>
  Unrecoverable error: unknownerror in setdevice
  Operand stack:
  --nostringval--

which is not a whole lot more informative than the original message.
(When displaying to the screen, the next line after "END FONTS ..."
is "END DEVICE ...")

Is there any way to turn on debug or tracing, or otherwise get more
detail, re what is going on in setdevice and exactly what failed?

So far I haven't found anything particularly helpful using Google.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: continued graphics/opencv-core problems

[Chess Griffin]

On 09.11.2013 17:44, Jason E. Hale wrote:

On Saturday, November 09, 2013 15:00:51 Chess Griffin wrote:


Has anyone else run into this or have a solution?  Thanks in advance.


@Thierry - thank you for your reply - yes, my ports tree is up to date.  
It updates via cron every night and then I also manually update before 
trying opencv-core again




Sorry for my silence on the matter.  I have been extremely busy lately. 
 The
problem seems to be that you don't have libc++ installed.  At the 
moment, if
you wish to build with clang, the port must link to libc++.  Otherwise, 
I

suggest building with gcc (still the default compiler on 9.2).

I do plan to address this in the next update which should hopefully be 
soon.

I just have a few more bugs to work out.


@jhale - thanks also.  I figured you were working on it but I just 
thought I'd check for an interim fix in the meantime.  But to your 
point, you are correct in that I don't have libc++ installed.  If that's 
the one from ports, I see it is marked IGNORE but I have not tried 
overriding that and building anyway.  Maybe I'll just go ahead and let 
it build with gcc for the time being.


Thanks to all who replied!

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

Re: how to tell pkg-list not to deinstall/overwrite certain files

[Aryeh Friedman]

Thanks the stuff worked there but it is not clear how to handle user dirs
(don't nuke dirs withi user data for example we create /usr/local/vms and
it should not be erased on deinstall)


On Fri, Nov 8, 2013 at 6:13 AM, Tijl Coosemans  wrote:

> On Fri, 8 Nov 2013 05:23:47 -0500 Aryeh Friedman wrote:
> > Forgot to mention the solution should if at all possible be 100%
> pkg-plist
> > based because our internal build system is not make
> >
> > On Fri, Nov 8, 2013 at 5:21 AM, Aryeh Friedman  >wrote:
> >> I am doing a lot of inter-machine testing of a private port (will be
> >> released soon as a actual port) but need to tell "make deinstall" not to
> >> delete a certain file... how do we do this?... background one thing we
> are
> >> testing is the ability to upgrade the port (privately) and it must not
> nuke
> >> our settings file on the test machines because the default config
> provided
> >> by our port is inappropriate for how we have things configured (it is
> >> correct for 99.9% of everyone else though).
> >>
> >> Namely we need:
> >>
> >> 1. Do not delete  /usr/local/etc/petitecloud/settings on deinstall
> >> 2. Do not overwrite it with a new version on install (if present else
> >> install it)
>
> Basically you have to install the file as settings.sample and add some
> pkg-plist magic.  It's explained in more detail here:
>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/plist-config.html
>
> Note that with staging you don't need the post-install part, only the
> pkg-plist part.
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

[QAT] r333366: 4x leftovers

[Ports-QAT]

- Fix build with USE_GCC on head
-

  Build ID:  20131110060800-32464
  Job owner: w...@freebsd.org
  Buildtime: 6 minutes
  Enddate:   Sun, 10 Nov 2013 06:14:04 GMT

  Revision:  r66
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=66

-

Port:security/py-pycryptopp 0.5.29

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131110060800-32464-224456/py27-pycryptopp-0.5.29.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131110060800-32464-224457/py27-pycryptopp-0.5.29.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131110060800-32464-224458/py27-pycryptopp-0.5.29.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~w...@freebsd.org/20131110060800-32464-224459/py27-pycryptopp-0.5.29.log


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

Re: continued graphics/opencv-core problems

[Kurt Jaeger]

Hi!

> > For about 2-3 weeks now, I have continued to run into problems with 
> > opencv-core not building on my 9.2-RELEASE poudriere box that uses 
> > clang.
> 
> As I need it for my ports, I has just been rebuilt in poudriere, and
> everything is fine.

Thanks for the pointer to the poudriere process. I used it to
build opencv-core and this worked (I have disk space at /serv):

  cd /usr/local/etc
  cp poudriere.conf.sample poudriere.conf
  vi poudriere.conf


--- poudriere.conf.sample   2013-10-29 23:28:55.0 +0100
+++ poudriere.conf  2013-11-09 22:05:01.0 +0100
@@ -13,7 +13,7 @@
 
 ### NO ZFS
 # To not use ZFS, define NO_ZFS=yes
-#NO_ZFS=yes
+NO_ZFS=yes
 
 # root of the poudriere zfs filesystem, by default /poudriere
 # ZROOTFS=/poudriere
@@ -26,7 +26,7 @@
 #
 # Also not that every protocols supported by fetch(1) are supported here, even
 # file:///
-FREEBSD_HOST=_PROTO_://_CHANGE_THIS_
+FREEBSD_HOST=ftp://ftp.freebsd.org
 
 # By default the jails have no /etc/resolv.conf, you will need to set
 # REVOLV_CONF to a file on your hosts system that will be copied has
@@ -35,7 +35,7 @@
 RESOLV_CONF=/etc/resolv.conf
 
 # The directory where poudriere will store jails and ports
-BASEFS=/usr/local/poudriere
+BASEFS=/serv/poudriere
 
 # The directory where the jail will store the packages and logs
 # by default a zfs filesystem will be created and set to
@@ -62,7 +62,7 @@
 # all   - Run the entire build in memory, including builder jails.
 # yes   - Only enables tmpfs(5) for wrkdir
 # EXAMPLE: USE_TMPFS="wrkdir data"
-USE_TMPFS=yes
+USE_TMPFS=
 
 # If set the given directory will be used for the distfiles this allow the 
share
 # the distfiles between jails and ports tree
@@ -76,7 +76,7 @@
 # mirror (default: svn0.us-west.FreeBSD.org)
 # The full mirror list is available here:
 # http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/svn-mirrors.html
-#SVN_HOST=svn0.us-west.FreeBSD.org
+SVN_HOST=mysvn-host
 
 # Automatic OPTION change detection
 # When bulk building packages, compare the options from kept packages to

  mkdir /serv/poudriere
  poudriere jail -c -v 9.2-RELEASE -a amd64 -j 92amd64
  poudriere ports -c
  echo 'graphics/opencv-core' > ~/pkglist
  poudriere bulk -f ~/pkglist -j 92amd64

This build the package in /serv/poudriere/data/packages/92amd64-default/All/
and I replaced my not upgradable one via:

pkg_delete -f opencv-core-2.3.1_7
pkg_add opencv-core-2.3.1_9.tbz

Very nice! I'll start to use poudriere for other problems that
come up from time to time!

-- 
p...@opsec.eu+49 171 3101372 7 years to go !
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"