El 24 jun. 2016 8:16 a. m., "Fernando Apesteguía" <
fernando.apesteg...@gmail.com> escribió:
>
> One of my ports is written in C++. It links agains libc++ that is in
> base (/usr/src/contrib/libc++). The port still builds fine and works
> but the QA scripts show an error complaining about the execu
Hi Jan and Torsten,
Thanks a lot for your help.
I will try it later after taking a break. As I lack knowledge on C/C++, I
spent a month to retry many ways on FreeBSD 10/11. I feel tried.
Fortunately, I got some clues.
During this month, I also learnt a lot on FreeBSD. As least I can build and
in
On Fri, Jun 24, 2016 at 10:25 AM, Fernando Herrero Carrón
wrote:
>
> El 24 jun. 2016 8:16 a. m., "Fernando Apesteguía"
> escribió:
>>
>> One of my ports is written in C++. It links agains libc++ that is in
>> base (/usr/src/contrib/libc++). The port still builds fine and works
>> but the QA scrip
Yuri writes:
> I have two port options: GUI NLS.
>
> I would like to have USES=gettext only when both GUI and NLS are "on".
>
> If it was only one option, say NLS, NLS_USES=gettext would work.
>
> But what about the two options case? Is there any magic to do this
> without .include ?
Depends on
El 24 jun. 2016 4:23 p. m., "Fernando Apesteguía" <
fernando.apesteg...@gmail.com> escribió:
>
> On Fri, Jun 24, 2016 at 10:25 AM, Fernando Herrero Carrón
> wrote:
> >
> > El 24 jun. 2016 8:16 a. m., "Fernando Apesteguía"
> > escribió:
> >>
> >> One of my ports is written in C++. It links agains
On 06/23/2016 14:54, Fernando Herrero Carrón wrote:
Could you please elaborate on the reasons why you want to do that? I don't
see how that particular combination of options would introduce a dependence
that neither of them alone would.
In this particular case, as I figured, this isn't actually
El 24 jun. 2016 9:36 p. m., "Yuri" escribió:
>
> On 06/23/2016 14:54, Fernando Herrero Carrón wrote:
>>
>> Could you please elaborate on the reasons why you want to do that? I
don't
>> see how that particular combination of options would introduce a
dependence
>> that neither of them alone would.
On 06/23/2016 14:26, Yuri wrote:
But what about the two options case? Is there any magic to do this
without .include ?
This isn't currently possible. But I think it makes sense to implement
the double option case, because it is very easy to do this.
Yuri
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210533:
-Solution
Add this line
CONFIGURE_ARGS= --without-libva
to libvcnserver/Makefile
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubs
Hi!
I like to update libvncserver 0.9.10 on FreeBSD 10.3-RELEASE (amd64)
and I got an error:
In file included from rfbproto.c:2406:
./h264.c:253:108: error: too few arguments to function call, expected
8, have 6
va_status = vaCreateSurfaces(va_dpy, width, height,
VA_RT_FORMAT_YUV420, SURFACE_
10 matches
Mail list logo