Hi Mav,
Sorry for disturbing!
We are using libpdel.
In our souce code, structs_xml_input is called with STRUCTS_XML_LOOSE which
means unrecognised xml tags will be ignored.
We are doing some tests about this.
The xml file we are using is as follows and corresponding structs_type
structs_field
This is due to the September 19 change r304506 to lang/tcl86
/usr/ports/lang/tcl-modules# make
===> License BSD accepted by the user
===> Extracting for tcl-modules-8.5.12_2
=> SHA256 Checksum OK for tcl8.5.12-src.tar.gz.
===> Patching for tcl-modules-8.5.12_2
===> Applying extra patch /usr/po
On Sat, 22 Sep 2012 12:47:31 +0200, Andrea Venturoli said:
> Hello.
> What are the plans for emacs23?
> It is marked as vulnerable now, but emacs24 is almost unusable (1)...
> bye & Thanks
> av.
> (1) I'm mainly referring to gdb integration: in case anyone is
> interested, I can describe
Naram Qashat wrote on 22.09.2012 05:15:
graphics/autotrace has been updated to OptionsNG, but there is a check
of .if ${PORT_OPTIONS:MSETUIDMING} while the Option for it is just MING,
not SETUIDMING. Really minor, but if anyone is using this port with
that option, they would be in a bit of a pic
On Sunday, September 23, 2012 08:52:05 Jonathan Chen wrote:
> Hi,
>
> Now that www/linux-flashpluginwrapper has disappeared from the ports
> tree, how do I connect the linux-f10-flashplugin onto my web browsers?
> Is there any documentation on how to do this?
>
> Cheers.
Use www/nspluginwrapper.
On 23/09/2012 08:52, Jonathan Chen wrote:
Hi,
Now that www/linux-flashpluginwrapper has disappeared from the ports
tree, how do I connect the linux-f10-flashplugin onto my web browsers?
Is there any documentation on how to do this?
Never mind. www/nspluginwrapper is the correct one to use. Sor
Hi,
Now that www/linux-flashpluginwrapper has disappeared from the ports
tree, how do I connect the linux-f10-flashplugin onto my web browsers?
Is there any documentation on how to do this?
Cheers.
--
Jonathan Chen
--
If y
On Sat, 22 Sep 2012 18:56:22 +0100
Chris Rees articulated:
> On 22 September 2012 15:22, Jerry wrote:
> > On Sat, 22 Sep 2012 08:43:29 -0400
> > Steve Wills articulated:
> >
> >> Please see the 20120908 entry in /usr/ports/UPDATING.
> >
> > Been there, done that, doesn't make any difference. My q
On Sat, 22 Sep 2012 18:56:22 +0100, Chris Rees wrote:
> This patch is untested, but if you really have successfully linked
> kdenetwork with libotr-4.0.0 then it should work no problem.
>
> Please let us know.
kdenetwork doesn't support libotr-4.0.0
Max
__
On 22 September 2012 15:22, Jerry wrote:
> On Sat, 22 Sep 2012 08:43:29 -0400
> Steve Wills articulated:
>
>> Please see the 20120908 entry in /usr/ports/UPDATING.
>
> Been there, done that, doesn't make any difference. My question is why
> should I have to delete the never version "libotr-4.0.0"
W dniu 2012-09-22 19:38, Bernhard Fröhlich pisze:
On Sa., 22. Sep. 2012 18:54:08 CEST, Marek Salwerowicz wrote:
Hi,
W dniu 2012-09-20 08:02, Bernhard Fröhlich pisze:
Bernhard on behalf of the new VirtualBox on FreeBSD Team!
What happened with '--vnc' option of VBoxHeadless?
s14% VBoxHeadle
On Sa., 22. Sep. 2012 18:54:08 CEST, Marek Salwerowicz wrote:
> Hi,
>
> W dniu 2012-09-20 08:02, Bernhard Fröhlich pisze:
> > Bernhard on behalf of the new VirtualBox on FreeBSD Team!
> What happened with '--vnc' option of VBoxHeadless?
>
> s14% VBoxHeadless --startvm test1 --vnc --vncport 5100
On Wed, Sep 19, 2012 at 04:55:49PM +0700, Alexey Dokuchaev wrote:
> Hi there,
>
> I am calling for testers to help me make weighted decision about updating
> the port to 304.43. If, for some reason, 304.43 does not work for you,
> tell me how does version 295.75 feel.
Thanks everyone giving back
On Sat, Sep 22, 2012 at 05:55:32PM +0100, Chris Rees wrote:
> ...
> > Eh; I grabbed the message & exercised "svn patch" for now. :-}
> >
> > Thanks again!
>
> Yeah, thing is I made a mistake in the correction!
>
> You'll need to remove the files/ from the EXTRA_PATCHES line.
OK; I can cope. :-}
On 22 September 2012 17:51, David Wolfskill wrote:
> On Sat, Sep 22, 2012 at 05:42:11PM +0100, Chris Rees wrote:
>> ...
>> > * Dependency of lang/tcl75 on lang/tcl86/files/patch-uk-locale was
>> > added in r303095 | mi | 2012-08-24 10:16:37 -0700 (Fri, 24 Aug 2012)
>> > (which also added the f
Hi,
W dniu 2012-09-20 08:02, Bernhard Fröhlich pisze:
Bernhard on behalf of the new VirtualBox on FreeBSD Team!
What happened with '--vnc' option of VBoxHeadless?
s14% VBoxHeadless --startvm test1 --vnc --vncport 5100 --width 800
--height 600
Oracle VM VirtualBox Headless Interface 4.2.0_OSE
On Sat, Sep 22, 2012 at 05:42:11PM +0100, Chris Rees wrote:
> ...
> > * Dependency of lang/tcl75 on lang/tcl86/files/patch-uk-locale was
> > added in r303095 | mi | 2012-08-24 10:16:37 -0700 (Fri, 24 Aug 2012)
> > (which also added the file itself).
> >
> > * The file was removed in r304506 | g
___
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"
On 22 September 2012 16:39, David Wolfskill wrote:
> A port I'm trrying to install (in the process of re-installing all ports
> on my work desktop) has lang/tcl85 as a dependency.
>
> No problem; I have already performed this exercise on my laptop, so I
> know it works.
>
> But then I hit:
>
> ===
A port I'm trrying to install (in the process of re-installing all ports
on my work desktop) has lang/tcl85 as a dependency.
No problem; I have already performed this exercise on my laptop, so I
know it works.
But then I hit:
===>>> Port directory: /usr/ports/lang/tcl85
===>>> Starting check fo
On 22 September 2012 11:04, Erwin Lansing wrote:
> INDEX build failed with errors:
> Generating INDEX-7 - please wait.. Done.
> make_index: jai-imageio-1.0_2: no entry for /usr/ports/www/linuxpluginwrapper
this was fixed already.
--
Eitan Adler
___
fr
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: jai-imageio-1.0_2: no entry for /usr/ports/www/linuxpluginwrapper
Committers on the hook:
bsam cs culot eadler lwhsu mm rm
Most recent CVS update was:
U databases/mydumper/Makefile
U databases/mydumper/pkg-descr
On Sat, 22 Sep 2012 08:43:29 -0400
Steve Wills articulated:
> Please see the 20120908 entry in /usr/ports/UPDATING.
Been there, done that, doesn't make any difference. My question is why
should I have to delete the never version "libotr-4.0.0" which
"kdenetwork-4.8.4_1" is currently linked agains
On Sat, 22 Sep 2012, Kurt Jaeger wrote:
Inkskape build without problem (gcc) on FreeBSD 9.1 RC1 but when I ran it I
got:
Shared object "libpcre.so.0" not found, required by "liblqr-1.so.3"
locate libpcre.so shows:
/compat/linux/lib/libpcre.so.0
/compat/linux/lib/libpcre.so.0.0.1
/usr/local/lib
On Sat, Sep 22, 2012 at 1:47 PM, Andrea Venturoli wrote:
> Hello.
>
> What are the plans for emacs23?
> It is marked as vulnerable now, but emacs24 is almost unusable (1)...
>
> bye & Thanks
> av.
>
> (1) I'm mainly referring to gdb integration: in case anyone is interested, I
> can descr
In file included from ./ImfChromaticities.h:47:0,
from ImfChromaticities.cpp:43:
/usr/local/include/OpenEXR/ImathMatrix.h: In instantiation of
'Imath::Matrix44::Matrix44() [with T = float]':
ImfChromaticities.cpp:110:17: required from here
/usr/local/include/OpenEXR/ImathMatrix.h
Please see the 20120908 entry in /usr/ports/UPDATING.
Steve
On 09/22/12 08:39, Jerry wrote:
This probably belongs on ; however, I thought I
would start here first.
FreeBSD 8.3-STABLE
The build fails with this message:
===> kdenetwork-4.8.4_2 depends on shared library: otr.4 - not found
==
Jerry wrote on 22.09.2012 16:39:
This probably belongs on ; however, I thought I
would start here first.
FreeBSD 8.3-STABLE
The build fails with this message:
===> kdenetwork-4.8.4_2 depends on shared library: otr.4 - not found
===>Verifying install for otr.4 in /usr/ports/security/libo
This probably belongs on ; however, I thought I
would start here first.
FreeBSD 8.3-STABLE
The build fails with this message:
===> kdenetwork-4.8.4_2 depends on shared library: otr.4 - not found
===>Verifying install for otr.4 in /usr/ports/security/libotr3
===> libotr-3.2.1 conflicts w
On Saturday 22 September 2012 05:52:19 Ruslan Mahmatkhanov wrote:
> ajtiM wrote on 22.09.2012 14:37:
> > Hi!
> >
> > Inkskape build without problem (gcc) on FreeBSD 9.1 RC1 but when I ran it
> > I got:
> > Shared object "libpcre.so.0" not found, required by "liblqr-1.so.3"
> >
> > locate libpcre.
Hello.
I've got Horde 4 installed; this is my situation:
# pkg_info | grep horde
horde-4.0.15Horde Application Framework
horde-content-1.0.3 Horde tagging application
horde-imp-5.0.23Horde web based webmail system
horde-ingo-2.0.9Horde email filter rules manager
horde-kronolith-
Hello.
What are the plans for emacs23?
It is marked as vulnerable now, but emacs24 is almost unusable (1)...
bye & Thanks
av.
(1) I'm mainly referring to gdb integration: in case anyone is
interested, I can describe some of the problems.
__
Hi!
> Inkskape build without problem (gcc) on FreeBSD 9.1 RC1 but when I ran it I
> got:
> Shared object "libpcre.so.0" not found, required by "liblqr-1.so.3"
>
> locate libpcre.so shows:
>
> /compat/linux/lib/libpcre.so.0
> /compat/linux/lib/libpcre.so.0.0.1
> /usr/local/lib/libpcre.so
> /usr/
ajtiM wrote on 22.09.2012 14:37:
Hi!
Inkskape build without problem (gcc) on FreeBSD 9.1 RC1 but when I ran it I
got:
Shared object "libpcre.so.0" not found, required by "liblqr-1.so.3"
locate libpcre.so shows:
/compat/linux/lib/libpcre.so.0
/compat/linux/lib/libpcre.so.0.0.1
/usr/local/lib/li
Hi!
Inkskape build without problem (gcc) on FreeBSD 9.1 RC1 but when I ran it I
got:
Shared object "libpcre.so.0" not found, required by "liblqr-1.so.3"
locate libpcre.so shows:
/compat/linux/lib/libpcre.so.0
/compat/linux/lib/libpcre.so.0.0.1
/usr/local/lib/libpcre.so
/usr/local/lib/libpcre.so
Hello,
There is a known segfault in mail/dovecot2-pigeonhole released with
Dovecot 2.1.8 which is what we have in ports at the moment.
The segfault makes it very near impossible to edit sieve scripts with a
managesieve client which does syntax validation (like the Thunderbird
plugin does). The p
36 matches
Mail list logo
