On 12/07/2019 12:04, Po-Chuan Hsieh wrote:
> It builds successfully on FreeBSD.
> I've add devel/pecl-ds in r506449.
Great stuff. Thanks.
--
Oliver Schönrock
signature.asc
Description: OpenPGP digital signature
Hello PECL port maintainers
There is a appealing "newish" pecl php extension, which addresses some
of php's long standing shortcomings in well defined data structures
replacing the ubiquitous "array()".
Efficient data structures for PHP 7, provided as an alternative to the
array
bump? still broken for me... now under DEFAULT_VERSIONS+= php=7.2
On 03/12/17 12:16, Oliver Schonrock wrote:
> I think it's just a path issue:
>
> [root@epsilon php-xapian]# cat /etc/make.conf
> DEFAULT_VERSIONS+= php=7.1
>
> [root@epsilon php-xapian]# make reinstall
> ===
On 12/12/17 10:26, Oliver Schonrock wrote:
> I will wait for that libargon2 patch to be committed to svn.ports and
> then retest on the "haswell" poudriere server to see if I can get it to
> build "sandybridge" (and bdver3) compat binaries
Rebuilt after por
On 12/12/17 10:26, Oliver Schonrock wrote:
> It seems that this file has the
> answer:
>
> /usr/src/share/mk/bsd.cpu.mk
>
...
>
> So I should be able to put CPUTYPE=sandybridge into /etc/make.conf
> and...happy days? No more nasty surprises?
Actually I a
On 12/12/17 00:29, Oliver Schonrock wrote:
>> Well, maybe. From your mail, though, it looks like you did that
>> testing by rebuilding/installing the ports _on the local machine_,
>> rather than rebuilding in poudriere. If the poudriere box was
>> building binaries with
On 11/12/17 23:41, Matthew D. Fuller wrote:
> On Mon, Dec 11, 2017 at 11:32:08PM + I heard the voice of
> Oliver Schonrock, and lo! it spake thus:
>> and it solves my issue as well. Don't think the CPUTYPE stuff comes
>> into it.
> Well, maybe. From your mail, though,
On 11/12/17 23:28, Matthew D. Fuller wrote:
>> pkg check --dependencies reports problem.
> This seems the separate issue already being convered.
>
>
and it solves my issue as well. All tested just waiting for commit of
this ports tree:
On 11/12/17 02:30, Christopher Hall wrote:
>> Error: /usr/local/bin/php is linked to /usr/local/lib/libargon2.so
>> which does not have a SONAME. security/libargon2 needs to be fixed.
>>
>> I would say that this is the cause of the problem. So at first
>> Christopher - the maintainer of
On 08/12/17 12:33, Torsten Zuehlsdorff wrote:
>
>> 1. In the worst case (when built on remote poudriere) php72 crashes when
>> using the PASSWORD_ARGON2I algo for password_hash. pkg check
>> --dependencies reports problem.
>>
>> 2. On a separate machine. When building from local ports,
>>
I am having some trouble with the libargon2 dependency for lang/php72
Summary, for full details see below:
1. In the worst case (when built on remote poudriere) php72 crashes when
using the PASSWORD_ARGON2I algo for password_hash. pkg check
--dependencies reports problem.
2. On a separate
I think it's just a path issue:
[root@epsilon php-xapian]# cat /etc/make.conf
DEFAULT_VERSIONS+= php=7.1
[root@epsilon php-xapian]# make reinstall
===> Installing for php-xapian-1.4.5
===> php-xapian-1.4.5 depends on file:
/usr/local/include/php/main/php.h - found
===> php-xapian-1.4.5
On 01/12/17 23:17, Jonathan Chen wrote:
> www/node is what gets installed as a dependancy when installing
> www/npm. There is an expectation that they will behave well together.
I agree, but to be honest, that's the least of your problems with
front-end js stuff which changes every 5 minutes ;-)
On 01/12/17 22:46, Jonathan Chen wrote:
> Currently, with npm-5.4.2_2, I'm getting:
do you really need node9? that is what you are getting by installing
www/node.
I had more luck with "www/npm-node8" which is a combination of the two
that actually works OK together?
--
Oliver Schönrock
On 01/12/17 18:46, Jan Beich wrote:
> Only builds from "Type: package" are uploaded to pkg.freebsd.org.
> Packages are built on the *oldest* supported release for a given branch.
> Until a day ago packages for 11.* were built on 11.0 which has Clang 3.8
> in base. The next build should happen on
On 01/12/17 17:54, Jan Beich wrote:
> Why do you use 12.0-CURRENT packages on 11.1-RELEASE?
>
> http://beefy12.nyi.freebsd.org/data/head-amd64-default/p455158_s326378/logs/node8-8.9.1_1.log
> contains 'llvm_version': '5.0',
>
>
I have not dived down this deep into the ports => pkg build system
before, so excuse me if I get this wrong.
TLDR;
-
I suspect that the package I get from beefy12 in this build:
https://pkg-status.freebsd.org/builds/default:default:head-amd64:p455158_s326378:beefy12
was built in a jail
On 10/07/17 19:51, Sunpoet Po-Chuan Hsieh wrote:
> Since our default php is still 5.6, there are only official packages
> for php 5.6.
>
> However, we'll have flavored packages in the near future.
> It is said to support multiple python versions.
> I believe packages for non-default php versions
On 10/07/17 13:57, Oliver Schonrock wrote:
> Is that because the repo binary packages assume php56 and there are no
> php71 configured binary packages available, ie would need to "make" from
> source?
"make'ing" from source certainly seems to compile and run:
>
On 10/07/17 13:19, Oliver Schonrock wrote:
> Am I interpreting that correctly, or can it already build against php7?
> If not, what is needed before that can work?
Looks like there is something there driving the correct config for the
bindings package depending on the installed PHP_VER
On 09/12/16 07:21, Sunpoet Po-Chuan Hsieh wrote:
> Yes, I'm working on xapian 1.4.1. But I encountered some build failure
> on xapian-bindings. Hope it could be fixed this weekend.
It seems that Xapian 1.4.4 is now stably in ports. So is xapian-bindings
1.4.4.
It seems from here:
On Fri Dec 9 07:21:57 UTC 2016 Sunpoet Po-Chuan Hsieh sunpoet at
freebsd.org wrote:
> Yes, I'm working on xapian 1.4.1. But I encountered some build
> failure on xapian-bindings. Hope it could be fixed this weekend.
Any update on this?
Thanks
--
Oliver Schönrock
signature.asc
Description:
Hi There
I have been waiting for SWIG to gain php7 support so that
xapian-bindings can too. Looks like SWIG is now there, and the xapian
guys have included a php7 compiliation option on xapian master branch:
https://lists.xapian.org/pipermail/xapian-discuss/2016-November/009444.html
I tried to
Hi Alex
Now that php7 is released: http://php.net/ , the task of creating the
new FreeBSD ports for it, is on our plate.
I wonder what plans you have for this, or how far along your are?
I have been compiling php from ports for 14 years starting with version
php4.3 on FreeBSD 5.3, I think. Many
Having issue compiling/running www/lighttpd with openssl_from_ports
details are here:
http://redmine.lighttpd.net/issues/2534
Not sure which end needs to change: Freebsd lighty port, openssl port or
lighty?
--
Oliver Schonrock
___
freebsd-ports
On Tuesday 20 Jul 2010 00:14:47 Chris Rees wrote:
I'll have a look on Thursday for you.
that's great, thanks chris.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
Hi Olivier
It seems there is a new stable version of sympa 6.0.05 which has been out for
a while and v6.1 is already in beta2.
This is just a polite prompt to enquire if you will be updating the FreeBSD
port. I tried myself for an hour but ran out of skills (none of the old
patches apply and
?
--
Oliver Schonrock
___
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
Hi Alex
On Thursday 05 Nov 2009 15:39:20 Oliver Schonrock wrote:
You are probably aware of the discussion
here:http://forums.freebsd.org/showthread.php?t=5132
Do you plan to create a php53 set of ports or just update the php5 set?
How far have you got?
Obviously since then we have had
Hi
Hopefully a useful reminder...
http://pecl.php.net/package/APC/3.0.15
has been out for a couple of months and contains significant bug fixes
over 3.0.14.
I have hacked the current port with the following:
[EMAIL PROTECTED] diff -u distinfo distinfo.orig
--- distinfoMon Nov 19
30 matches
Mail list logo
