Starcraft and Diablo 2 players rejoice, for the evil which plagues the
wine-kthread binary (i.e. makes it hang at 100% CPU load) has been identified
by the http://bsdforen.de code monkeys in their never ending slave labour. It
is named libcups and weather this has to be resolved in wine or cups
Current FreeBSD problem reports
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including experimental
development code and obsolete releases.
Bugs can be in one of several states:
o - open
A problem report has bee
On 11/27/06, [LoN]Kamikaze <[EMAIL PROTECTED]> wrote:
Starcraft and Diablo 2 players rejoice, for the evil which plagues the
wine-kthread binary (i.e. makes it hang at 100% CPU load) has been identified
by the http://bsdforen.de code monkeys in their never ending slave labour. It
is named lib
Hi mi!
I found a problem that icu don't reflect PTHREAD_LIBS=ANY(like -lthr).
Please check following patch.
Index: Makefile
===
RCS file: /home/ncvs/ports/devel/icu/Makefile,v
retrieving revision 1.24
diff -u -r1.24 M
Hi delphij!
I found a problem that openldap23-server doesn't reflect
PTHREAD_LIBS=ANY (like -lthr). Please check following patch.
Index: Makefile
===
RCS file: /home/ncvs/ports/net/openldap23-server/Makefile,v
retrie
Clint Olsen writes:
> FreeBSD belle.0lsen.net 5.5-STABLE FreeBSD 5.5-STABLE #1: Mon Oct 23
> 13:04:36 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BELLE i386
FreeBSD 7.0-CURRENT #0: Tue Nov 14 17:38:15 EST 2006 i386
Port was re-built from current source on November 22.
As Clint, you seem to be building without X11 option.
Looks like there was a thinko in the last commit so it builds without GUI if
you do not run 'make config' again for the new port revision to have
WITH_X11=yes set.
Sorry, going to submit a PR for this.
On Monday 27 November 2006 15:10, Robe
On Monday 27 November 2006 08:27, Norikatsu Shigemura wrote:
= Hi mi!
=
= I found a problem that icu don't reflect PTHREAD_LIBS=ANY(like -lthr).
= Please check following patch.
Thanks, I'll try it... Do you need it to be thread-aware though? It is built
by default without threads at
On Monday 27 November 2006 10:59, Norikatsu Shigemura wrote:
= 1. PTHREAD_LIBS=-lthr
= So I removed libpthread.*, I'm testing.
=
= 2. WITHOUT_LIBPTHREAD=yes >> /etc/src.conf and make world
= ru@ committed this way. So I can do it.
= But we can only
On Mon, 27 Nov 2006 10:32:17 -0500
Mikhail Teterin <[EMAIL PROTECTED]> wrote:
> On Monday 27 November 2006 08:27, Norikatsu Shigemura wrote:
> = Hi mi!
> = I found a problem that icu don't reflect PTHREAD_LIBS=ANY(like -lthr).
> = Please check following patch.
> Thanks, I'll try it... Do yo
Hi,
VjAGRA_ip_$1,78
CjALiS_tf_$3,00
LEVjTRA_hn_$3,33
www [dot] rx44 [dot] info
_
A quick grrr-grrr reassured me. So I did not have to keep track of
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
Informativa ai s= ensi dell'articolo 13 del codice privacy per
richiesta consenso.
Gentili Signore & Signori,
Le Vinali di Fiume Veneto (Friuli) propone = la fornitura diretta di
Grandi Vini Italiani.
Le chiediamo quindi il= suo consenso preventivo ad informarla su
Have any of you started getting the below errors with fuzzyocr since the
port updated?
I did have this working manually previously, but now the port has been
updated, and my procmail.log is full of these. The corrupt image line
isn't in all of them, but most of the time it is there. I tried
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming Convention
John Jetmore wrote:
> I am the author of the swaks smtp testing tool. The port in FreeBSD is a
> couple of releases behind.
Done.
> Is there an email address I could add to my
> announce list to help keep the port up to date? Sorry for the email to
> ports@ but I couldn't find a more specific
On Mon, Nov 27, 2006 at 07:04:18PM +, [EMAIL PROTECTED] wrote:
> ** The following ports have a version number that sorts before a previous one
> **
>
> For many package tools to work correctly, it is of utmost importance that
> version numbers of a port form a monotonic increasing sequence
On Mon, Nov 27, 2006 at 11:26:46AM -0800, Brian wrote:
>
> Have any of you started getting the below errors with fuzzyocr since the
> port updated?
>
> I did have this working manually previously, but now the port has been
> updated, and my procmail.log is full of these. The corrupt image line
Hi,
Just an FYI, but Zend Optimizer 3.0.2 is not compatible with PHP 5.2.x.
However, Zend just today released version 3.2 of Zend Optimizer which is now
compatible with PHP 5.2.
Brian
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/
Let's suppose I have a list of tarballs
(e.g. foobar-1.23.456.tar.gz). How do I tell which port each file
belongs to? "pkg_info" only lists the end results.
Robert Huff
___
freebsd-ports@freebsd.org mailing lis
Shaun Amott wrote:
On Mon, Nov 27, 2006 at 11:26:46AM -0800, Brian wrote:
Have any of you started getting the below errors with fuzzyocr since the
port updated?
I did have this working manually previously, but now the port has been
updated, and my procmail.log is full of these. The corrup
I'm trying to make a port of the latest Blender with the SCons build.
The scons command in the do-build target in bsd.scons.mk is expanded in:
/usr/bin/env /usr/local/bin/scons \
CCFLAGS="-O2 -fno-strict-aliasing -pipe" \
CXXFLAGS="-O2 -fno-strict-aliasing -pipe" ...
Which gives an error:
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming Convention
> I'm trying to make a port of the latest Blender with the SCons build.
> The scons command in the do-build target in bsd.scons.mk is expanded in:
Yes, I've had this lovely discussion before. Blender has gone through many
iterations of bad scons behavior, at one point it used to split the args so
FIne. Are there any links to howtos explaining how to go about the
pertinent forensics? Much of the literature on strace and the kernel
debugger seem to be documented by persons suffering from asperger
syndrome.
Basically I load the module and the emulated winXP croaks when the
logo starts fadi
Robert Huff wrote:
> Let's suppose I have a list of tarballs
> (e.g. foobar-1.23.456.tar.gz). How do I tell which port each file
> belongs to? "pkg_info" only lists the end results.
The correct answer is, "not easily." You can look at the code for
sysutils/portmaster to get an idea of how
SOURCE: 6.2 PRERELEASE (Nov 20th)
ports: updated 11/27/2006 11pm EST
security/wpa_supplicant
make -DWITH_STATIC_SUPPLICANT install clean
gmake[2]: Leaving directory
`/usr/ports/net/libdnet/work/libdnet-1.11/test/dnet'
gmake[2]: Entering directory `/usr/ports/net/libdnet/work/libdnet-1.11/test'
g
Norikatsu Shigemura wrote:
> 3. libpthread.so.2 -> libthr.so.2 in /etc/libmap.conf IS TOO BAD
> I don't think this approch is good, believe that I'll get
> unstable environment.
I've been using that for over a month, and haven't had a single
problem. I've made no other mod
On Mon, Nov 27, 2006 at 05:02:53PM -0500, Robert Huff wrote:
>
> Let's suppose I have a list of tarballs
> (e.g. foobar-1.23.456.tar.gz). How do I tell which port each file
> belongs to? "pkg_info" only lists the end results.
This information is not compiled in any convenient form. You w
On Mon, Nov 27, 2006 at 11:28:18PM +, [EMAIL PROTECTED] wrote:
> ** The following ports have a version number that sorts before a previous one
> **
>
> For many package tools to work correctly, it is of utmost importance that
> version numbers of a port form a monotonic increasing sequence
Shaun Amott wrote:
On Mon, Nov 27, 2006 at 02:40:27PM -0800, Brian wrote:
Shaun Amott wrote:
On Mon, Nov 27, 2006 at 11:26:46AM -0800, Brian wrote:
Have any of you started getting the below errors with fuzzyocr since the
port updated?
I did have this working manually previou
On Mon, Nov 27, 2006 at 02:40:27PM -0800, Brian wrote:
>
> Shaun Amott wrote:
> >On Mon, Nov 27, 2006 at 11:26:46AM -0800, Brian wrote:
> >
> >>Have any of you started getting the below errors with fuzzyocr since the
> >>port updated?
> >>
> >>I did have this working manually previously, but no
On 11/28/06, Michael S <[EMAIL PROTECTED]> wrote:
SOURCE: 6.2 PRERELEASE (Nov 20th)
ports: updated 11/27/2006 11pm EST
security/wpa_supplicant
make -DWITH_STATIC_SUPPLICANT install clean
gmake[2]: Leaving directory
gmake[1]: Nothing to be done for `all-am'.
gmake[1]: Leaving directory `/usr
On Nov 27, 2006, at 8:43 AM, Kris Kennaway wrote:
FYI; can you please investigate and/or report to the developers? If
you are already aware of this problem but do not yet have a fix,
please mark the port BROKEN in the appropriate case, so that users do
not unexpectedly encounter it.
See http:
On Mon, Nov 27, 2006 at 11:29:30PM -0800, Wes Peters wrote:
>
> On Nov 27, 2006, at 8:43 AM, Kris Kennaway wrote:
>
> >FYI; can you please investigate and/or report to the developers? If
> >you are already aware of this problem but do not yet have a fix,
> >please mark the port BROKEN in the app
34 matches
Mail list logo
