The mysql server 5.0.37 built from ports with default configuration
is too slow, I found I must put --disable-profiling into Makefile's
CONFIGURE_ARGS to bring it back to normal performance.
Regards,
David Xu
___
freebsd-ports@freebsd.org mailing list
On Wed, Jun 13, 2007 at 03:17:44PM +0800, David Xu wrote:
> The mysql server 5.0.37 built from ports with default configuration
> is too slow, I found I must put --disable-profiling into Makefile's
> CONFIGURE_ARGS to bring it back to normal performance.
Yeah, that made me very confused too. I f
Quoting Gabor Tjong A Hung <[EMAIL PROTECTED]> (from Tue, 12
Jun 2007 17:26:35 +0200):
As it is now some ports don't even have OPTIONS, and you need to define
variables to "define" your options. I don't really understand why this is
done this way, but this is equally annoying.
First there wh
Kris Kennaway wrote:
On Wed, Jun 13, 2007 at 03:17:44PM +0800, David Xu wrote:
The mysql server 5.0.37 built from ports with default configuration
is too slow, I found I must put --disable-profiling into Makefile's
CONFIGURE_ARGS to bring it back to normal performance.
Yeah, that made me ve
On Wednesday 13 June 2007 00:36:58 Alexander Leidinger wrote:
> Quoting Gabor Tjong A Hung <[EMAIL PROTECTED]> (from Tue, 12
>
> Jun 2007 17:26:35 +0200):
> > As it is now some ports don't even have OPTIONS, and you need to define
> > variables to "define" your options. I don't really understand wh
On Fri, 01 Jun 2007 14:48:13 +0200
Thomas Spreng <[EMAIL PROTECTED]> wrote:
> Thomas Spreng wrote:
> > Hi,
> >
> > Duane Hill wrote:
> >> From the stand point of a fresh FBSD 6.2 install, rdesktop 1.5.0
> >> works fine here using xorg 7.2. I just logged into an XP pro and
> >> 2000 server without
>> If I apply the patch (which I attached in one of my earlier posts)
>> everything runs fine, regardless what color depth is used.
>
> Kind of new to path...please help me, how do I apply it?
as I have mentioned in the message containing the patch. The following
procedure should do the trick (u
compiling on:
# uname -a
FreeBSD ___ 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May 7 04:15:57 UTC
2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP amd64
2 -L/usr/local/lib -L/usr/local/lib/db42 -rpath /usr/local/lib -o
libsvn_ra_dav-1.la commit.lo fetch.lo file_revs.lo log.lo merge
Do you have kerberos installed for the base system?
hp010# ls /usr/lib/libgss*
/usr/lib/libgssapi.a/usr/lib/libgssapi_krb5.so
/usr/lib/libgssapi.so /usr/lib/libgssapi_krb5.so.8
/usr/lib/libgssapi.so.8 /usr/lib/libgssapi_krb5_p.a
/usr/lib/libgssapi_krb5.a /usr/l
On Jun 13, 2007, at 3:36 AM, Alexander Leidinger wrote:
First there where no OPTIONS, then OPTIONS was introduced. If you
feel annoyed by those ports which are not converted yet to OPTIONS
(because nobody felt annoyed enough to convert them), feel free to
submit patches for them.
persona
Vivek Khera wrote:
>
> On Jun 13, 2007, at 3:36 AM, Alexander Leidinger wrote:
>
>> First there where no OPTIONS, then OPTIONS was introduced. If you feel
>> annoyed by those ports which are not converted yet to OPTIONS (because
>> nobody felt annoyed enough to convert them), feel free to submit
On Wed, 13 Jun 2007, Vivek Khera wrote:
On Jun 13, 2007, at 3:36 AM, Alexander Leidinger wrote:
First there where no OPTIONS, then OPTIONS was introduced. If you
feel annoyed by those ports which are not converted yet to OPTIONS
(because nobody felt annoyed enough to convert them), feel free t
Alex Dupre wrote:
> [LoN]Kamikaze ha scritto:
>> Make update is broken on my system. Due to the removal of
>> PORTSNAP_UPDATE it
>> now complains about a missing PORTSSUPFILE (SUP_UPDATE is defined for
>> updating
>> /usr/src) instead of using portsnap.
>
> I've already notified portmgr and propos
On Wednesday 13 June 2007 07:24:23 Scot Hetzel wrote:
> On 6/13/07, David Southwell <[EMAIL PROTECTED]> wrote:
> > compiling on:
> > # uname -a
> > FreeBSD ___ 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May 7 04:15:57
> > UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP amd64
> >
> >
>
[LoN]Kamikaze wrote:
> It still seems not to be fixed and I cannot find the PR either. Can you give
> me
> the number?
I didn't open a PR, I contacted directly who proposed/committed that
change and portmgr. But after a couple of mail exchanges nobody took a
final decision (i.e. I'm still waiting
On Wed, Jun 13, 2007 at 06:47:41PM +0200, Alex Dupre wrote:
> [LoN]Kamikaze wrote:
> > It still seems not to be fixed and I cannot find the PR either. Can you
> > give me
> > the number?
>
> I didn't open a PR, I contacted directly who proposed/committed that
> change and portmgr. But after a cou
On 6/13/07, David Southwell <[EMAIL PROTECTED]> wrote:
here is what I have:
[EMAIL PROTECTED] /usr/bin]# ls -l /usr/lib/libgss*
-r--r--r-- 1 root wheel 141960 Feb 27 10:24 /usr/lib/libgssapi.a
lrwxr-xr-x 1 root wheel 14 Mar 23 07:59 /usr/lib/libgssapi.so ->
libgssapi.so.8
-r--r--r-- 1
Erwin Lansing wrote:
> On Wed, Jun 13, 2007 at 06:47:41PM +0200, Alex Dupre wrote:
>> [LoN]Kamikaze wrote:
>>> It still seems not to be fixed and I cannot find the PR either. Can you
>>> give me
>>> the number?
>> I didn't open a PR, I contacted directly who proposed/committed that
>> change and p
Hello,
does someone else see this as well? :
I now need to set SAL_IGNOREXERRORS=true in order to correctly
run openoffice.org (June 11 world & ports x86-stable).
Otherwise it will almost immediately quit after lauch; gdb
does not learn me more than 'Program exited with code 0116.'
I worked OK
Arno J. Klaassen wrote:
> Hello,
>
> does someone else see this as well? :
>
> I now need to set SAL_IGNOREXERRORS=true in order to correctly
> run openoffice.org (June 11 world & ports x86-stable).
> Otherwise it will almost immediately quit after lauch; gdb
> does not learn me more than 'Progr
2007/6/9, Benjamin Lutz <[EMAIL PROTECTED]>:
On Saturday 09 June 2007 18:36, David Southwell wrote:
> Hi
>
> Would it be possible , when a port has options, to ask porters if
> they would consider the merits/demerits of adding:
>
> 1. An ./options-descr file in the port directory that describes
Erwin Lansing wrote:
> As I described earlier, SUP_UPDATE, CVS_UPDATE and PORTSNAP_UPDATE are
> mutually exclusive and cannot be used at the same time. That it worked
> before was an artifact which has been fixed. That is doesn't work
> anymore means the designed behaviour finally has been fixed
I use FreeBSD on a lot of mailservers in combination with postfix.
When i compile on FreeBSD 5 i see messages like:
cc -DHAS_PCRE -I/usr/local/include -O -pipe -I. -DFREEBSD5 -c format_tv.c
On FreeBSD 6 they look like :
cc -DHAS_PCRE -I/usr/local/include -O2 -fno-strict-aliasing -pipe -I.
-DFR
On 6/13/07, Johan Hendriks <[EMAIL PROTECTED]> wrote:
I use FreeBSD on a lot of mailservers in combination with postfix.
When i compile on FreeBSD 5 i see messages like:
cc -DHAS_PCRE -I/usr/local/include -O -pipe -I. -DFREEBSD5 -c format_tv.c
On FreeBSD 6 they look like :
cc -DHAS_PCRE -I/usr/
Hi,
I'm getting a checksum error for this update. I think there may be a fault
in the install script.
Kind regards
Claus Krogsgaard
smime.p7s
Description: S/MIME cryptographic signature
Any suggestions on how to cross compile ports?
Also, when using PREFIX, how common are issues with it being
different with what it was compiled on versus where it is being ran
on?
I am looking at how to go about building them on one machine and then
running them on another machine of a different
On Wed, Jun 13, 2007 at 06:35:10PM -0400, Z.C.B. wrote:
> Any suggestions on how to cross compile ports?
It's almost entirely unsupported by the individual ports.
Kris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/
On Wed, 13 Jun 2007 19:11:41 -0400
Kris Kennaway <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 13, 2007 at 06:35:10PM -0400, Z.C.B. wrote:
> > Any suggestions on how to cross compile ports?
>
> It's almost entirely unsupported by the individual ports.
So ones best option is qemu?
28 matches
Mail list logo
