Hi,
With Mulberry from ports I see the following error when I run it:
mulberry: error while loading shared libraries: /usr/lib/librt.so.1: ELF
file OS ABI invalid
The OS version is quite fresh:
FreeBSD 7.0-CURRENT #0: Tue Aug 28
Anyone have an idea how to fix?
Thanks,
Per olof
__
Hello,
I noticed that after upgrading spamassassin to the latest (in ports)
version, manual whitelist is somehow broken.
In previous version spamassassin detects without a problem forged "From"
headers and even with "whitelist_from [EMAIL PROTECTED]"
mails that are spam got caught.
With the l
By the way, can we separate the port into -server, -client and -agent,
so that the package cluster will be able to build that at the moment?
ok, I'll think about your proposal
/Vladimir Ermakov
___
freebsd-ports@freebsd.org mailing list
http://l
Hi,
I've made a patch for postfix submitted in pr
(http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/110678) the 16 April
2007.
The maintainer ask it to be committed the 3 august 2007, and it is
still not committed, Is there a reason ? Have I done something wrong ?
Or is it the normal proc
Stefan Lambrev wrote:
Hello,
I noticed that after upgrading spamassassin to the latest (in ports)
version, manual whitelist is somehow broken.
In previous version spamassassin detects without a problem forged "From"
headers and even with "whitelist_from [EMAIL PROTECTED]"
mails that are spam
Hello,
John Marshall wrote:
Stefan Lambrev wrote:
Hello,
I noticed that after upgrading spamassassin to the latest (in ports)
version, manual whitelist is somehow broken.
In previous version spamassassin detects without a problem forged
"From" headers and even with "whitelist_from [EMAIL PRO
Hi,
I'm using ntop 3.3 with FreeBSD 6.2-STABLE , I use it mostely to monitor
netflow flows from cisco routers. After a few seconds ntop stops answering
and the browser is in the state "waiting".
This repeats all the time. Where is the problem and what can I do to make
ntop more useful for me ?
On Thu, Aug 30, 2007 at 10:41:09AM +0200, Baptiste Daroussin wrote:
> I've made a patch for postfix submitted in pr
> (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/110678) the 16 April
> 2007.
> The maintainer ask it to be committed the 3 august 2007, and it is still
> not committed, Is ther
Yes it has been committed few minutes after I sent my email, I haven't
been patient enough :)
Quoting Jeremy Chadwick <[EMAIL PROTECTED]>:
On Thu, Aug 30, 2007 at 10:41:09AM +0200, Baptiste Daroussin wrote:
I've made a patch for postfix submitted in pr
(http://www.freebsd.org/cgi/query-pr.cg
Edwin Groothuis wrote:
I have rewritten the logic part of the GNATS Auto Assign Tool a
little bit, to make it easier for me to add people who have requests
for PRs related to ports. If you have access to freefall.freebsd.org,
have a look at /hub/g/hubgnats/gnats-aa/incoming-PRs/bin/lookups.txt.
Sorry for long delay...
Alex Dupre wrote:
Stefan Lambrev wrote:
After upgrade from openssh from 4.5 to 4.6 I'm unable to login using
password authentication.
This a challenge-response problem. I'll fix this now...
Neither with RSA keys.
Works to me with fixes in challenge-response... see
On Aug 30, 2007, at 4:40 AM, Timur I. Bakeyev wrote:
Which threading libraries do you use? I remember having similar
problem with
libthr.so enabled in libmap.conf. As soon as I tried:
[java]
libpthread.so libpthread.so
libpthread.so.2 libpthread.so.2
All pr
On Aug 29, 2007, at 10:27 PM, Greg Lewis wrote:
FreeBSD 6.1/amd64 inside a jail.
Builds fine for me on 6.2/amd64 (but outside of a jail).
The hs_error*mumble*.log might provide some clues.
Timur figured it out: it was the threading library from libmap.conf.
Switching to libpthread allow
On Aug 30, 2007, at 4:40 AM, Timur I. Bakeyev wrote:
Which threading libraries do you use? I remember having similar
problem with
libthr.so enabled in libmap.conf. As soon as I tried:
[java]
libpthread.so libpthread.so
libpthread.so.2 libpthread.so.2
All pr
[EMAIL PROTECTED] writes:
>> pkg_add PathToPackage
>>
> i already try that one, but got problems with dependencies.
> pkg_add don't want install dependencies, so i must install dependences one
> by one.
According to "man 1 pkg_add" you need the PKG_PATH variable.
_
On Wed, 2007-08-29 at 23:38 +0200, Patrick Hurrelmann wrote:
> On Mon, 20 Aug 2007 01:16:53 -0400
> "Robert C. Noland III" <[EMAIL PROTECTED]> wrote:
>
> > On Mon, 2007-08-20 at 02:59 +0530, Subhro wrote:
> > > Hello,
> > >
> > > I have compiled the FreeBSD port for compiz 0.5.0 and experiencing
Today it muine that won't build, but it always something.
And make readmes are still broken.
--
Lars Eighner
http://www.larseighner.com/index.html
8800 N IH35 APT 1191 AUSTIN TX 78753-5266
___
freebsd-ports@freebsd.org mailing list
http://lists.freebs
Lars Eighner wrote:
Today it muine that won't build, but it always something.
And make readmes are still broken.
Yes, of course.
Kris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe,
Hello Robert,
Yes I have also noted that compiz is segfaulting. I have asked this in
#compiz-fusion in freenode. They also didn't have much clue. Maybe a
dump would be more useful?
Also you can commit it in the current state mentioning in pkg-message
about the crash?
Subhro
On 8/30/07, Robert
Hi,
I just saw that the version of this port is obsolete, maybe
you could update it.
Right now version 0.6.1 is up-to-date.
And as I typed "whereis tracker", i got an audio tool back, this metatracker is
also named tracker, maybe it would help to just rename it to metatracker or
something, bec
On Thu, Aug 30, 2007 at 11:02:25PM +0200, r3inforce wrote:
> Hi,
>
> I just saw that the version of this port is obsolete, maybe
> you could update it.
>
> Right now version 0.6.1 is up-to-date.
>
> And as I typed "whereis tracker", i got an audio tool back, this metatracker
> is also named tra
I just checked the diffs. It is the removal of the processor specific
flags that broke the build.
In addition, it's probably more compatible with future builds to
specify the --disable-server --disable-graphics command line options
on the configure command line rather than to edit the Makefile.am
Hi Rene,
Just getting back from vacation, so am just seeing this now.
The major issue seems to be with the vectorized stuff. If you look at
the file client/Makefile.am, you will see some specific compile
options for different files. For example, analyzeFuncs_sse.cpp needs
to be compiled with th
23 matches
Mail list logo
