Doug Barton writes:
> I've been experimenting with the idea of using gcc 4.5.1 as my "ports
> compiler" and ran into this problem:
> CCCMD = /usr/local/bin/gcc45 -DPERL_CORE -c
> -DAPPLLIB_EXP="/usr/local/lib/perl5/5.10.1/BSDPAN" -DHAS_FPSETMASK
> -DHAS_FLOATINGPOINT_H -DDEBUGGING -fno-strict-al
FreeBSD-PRERELEASE 8.1 amd64
Since the release of "libassuan-2.0.0", I have not been able to update
or reinstall "security/GPA". All of the other ports appear to build
fine.
I tried removing the old "libassuan-1-1.0.5" ports; however, when
attempting to rebuld the 'GPA' port, it only appears to w
I'm wondering why it installs samba 3.0 instead of the latest
release in the samba 3 branch like other ports do.
Regards
--
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and i
Am 19.06.2010 15:41, schrieb Lasse Collin:
> Perhaps FreeBSD provides a good working way to limit the amount of
> memory that a process actually can use. I don't see such a way e.g. in
> Linux, so having some method in the application to limit memory usage is
> definitely nice. It's even more u
x11-wm/e16utils, which was previously failing is OK after this commit.
Thanks for fixing it!
A description of the testing process can be found here:
http://T32.TecNik93.com/FreeBSD/QA-Tindy/
Thanks for your work on making FreeBSD better,
--
QAT - your friendly neighborhood Daemon,
preparing a
On 2010-06-20 Matthias Andree wrote:
> Am 19.06.2010 15:41, schrieb Lasse Collin:
> > Perhaps FreeBSD provides a good working way to limit the amount of
> > memory that a process actually can use. I don't see such a way e.g.
> > in Linux, so having some method in the application to limit memory
> >
On Sunday, June 20, 2010 06:55:52 you wrote:
> FreeBSD-PRERELEASE 8.1 amd64
>
> Since the release of "libassuan-2.0.0", I have not been able to update
> or reinstall "security/GPA". All of the other ports appear to build
> fine.
>
> I tried removing the old "libassuan-1-1.0.5" ports; however, whe
On Sun, 20 Jun 2010 18:23:03 +0300
Lasse Collin wrote:
> On 2010-06-20 Matthias Andree wrote:
> > Am 19.06.2010 15:41, schrieb Lasse Collin:
> > > Perhaps FreeBSD provides a good working way to limit the amount of
> > > memory that a process actually can use. I don't see such a way
> > > e.g. in
On Sun, 20 Jun 2010 12:30:37 -0400
"Jason E. Hale" wrote:
> On Sunday, June 20, 2010 06:55:52 you wrote:
> > FreeBSD-PRERELEASE 8.1 amd64
> >
> > Since the release of "libassuan-2.0.0", I have not been able to
> > update or reinstall "security/GPA". All of the other ports appear
> > to build fin
x11/xlupe, which was previously failing is OK after this commit.
Thanks for fixing it!
A description of the testing process can be found here:
http://T32.TecNik93.com/FreeBSD/QA-Tindy/
Thanks for your work on making FreeBSD better,
--
QAT - your friendly neighborhood Daemon,
preparing a heck
Max,
What about this one. I was trying to do a 'make install' on
kdebase4-workspace and it's erroring. I did not find anything in
UPDATING around this.
-Troy
[ 69%] Built target krunner_shell
[ 69%] Built target krunner_solid_automoc
[ 69%] Built target krunner_solid
[ 69%] Built target
devel/chrpath, which was previously failing is OK after this commit.
Thanks for fixing it!
A description of the testing process can be found here:
http://T32.TecNik93.com/FreeBSD/QA-Tindy/
Thanks for your work on making FreeBSD better,
--
QAT - your friendly neighborhood Daemon,
preparing a h
On Sun, 20 Jun 2010 20:08:19 +0300
Ion-Mihai Tetcu articulated:
[snip]
> Only slush, not full freeze.
> If your patches fix a problem, they will go in.
I filed a PR, so perhaps it will get fixed in the near future.
http://www.freebsd.org/cgi/query-pr.cgi?pr=148016
--
Jerry ✌
freebsd-ports.u.
(Just to clarify, this is my personal opinion, with a certain focus of
getting ports, i. e. automated source code builds for FreeBSD, going. I
am not speaking on behalf of FreeBSD.)
Am 20.06.2010 17:23, schrieb Lasse Collin:
> I have only one computer with over 512 MiB RAM (this has 8 GiB). Thus
Good day!
I (still) have a trouble in using deskutils/gtg after gnome update,
but i was able to make it work partially (it was new intel video
driver issue). So, new problem is appear when i try to select some menu
item - it crashes with:
"""
/libexec/ld-elf.so.1:
/usr/local/lib/python2.6/si
On 2010-06-20 Ion-Mihai Tetcu wrote:
> Personally I'd suggest keeping the option to limit the memory, but as
> an option, not as default.
OK.
> One thing I would really love to see going away is the default to
> delete the archive on decompression.
Being somewhat compatible with gzip and bzip2 c
21.06.2010 00:37, Ruslan Mahmatkhanov пишет:
Good day!
I (still) have a trouble in using deskutils/gtg after gnome update,
but i was able to make it work partially (it was new intel video
driver issue). So, new problem is appear when i try to select some menu
item - it crashes with:
"""
/libex
On Sun, 20 Jun 2010 12:44:20 -0500, Troy wrote:
> Max,
>
> What about this one. I was trying to do a 'make install' on
> kdebase4-workspace and it's erroring. I did not find anything in
> UPDATING around this.
It seems you have kdelibs4 package corrupted (you can check that with
'pkg_info -g')
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
lini...@freebsd.org writes:
Hello,
> PR number: 87397
> PR title: [patch] incorrect use of PAPERSIZE make variable in some
> ports
> category: print
> portname: lpr-wrapper
> submitter: ga...@zahemszky.hu
> arrival date: 2005-10-13 20:40:18
>
25 matches
Mail list logo
