On Mon, Jan 7, 2013 at 12:49 PM, Adam Vande More wrote:
> On Mon, Jan 7, 2013 at 12:53 PM, John Marino wrote:
>
>>
>> Here's the issue I think some folks have:
>>
>> "Outdated": debatable. If outdated means a newer release is available,
>> then yes. If "outdated" means it outlived its usefulnes
On Mon, Jan 7, 2013 at 12:53 PM, John Marino wrote:
>
> Here's the issue I think some folks have:
>
> "Outdated": debatable. If outdated means a newer release is available,
> then yes. If "outdated" means it outlived its usefulness, I'd say no. This
> term seems subjectively used here.
>
> "pro
I have a clang-only world (no gcc42) and want to use gcc46 for port building.
I have ccache and distcc installed. In /etc/make.conf I have:
CC:=${CC:C,^gcc46,/usr/local/libexec/ccache/world/gcc46,1}
CXX:=${CXX:C,^g\+\+\46,/usr/local/libexec/ccache/world/g++46,1}
This used to work correctly but do
devel/gobject-introspection [0.10.8_3]: gcc46 error python2.7 (and may
be other versions of py) headers detection.
GCC 4.2 (default) - fine.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe
On 1/7/2013 19:47, awarecons wrote:
deskutils/superkaramba[4.84.4]: karamba.cpp, meter.cpp ... : multiple
errors 'too few args'
with clang3.1, gcc46 - fine.
___
Shouldn't all these notices be introduced in a PR rather than serially
on a mail list?
On 1/7/2013 19:40, Beat Gaetzi wrote:
On 01/07/13 15:22, Mikhail T. wrote:
Once again a working port (no build errors) is scheduled for deletion on
the grounds of simply being "unmaintained".
QT 3.3.8 was released in 2007 and KDE 3.5.10 in 2008 and both are no
longer maintained upstream nor in
deskutils/superkaramba[4.84.4]: karamba.cpp, meter.cpp ... : multiple
errors 'too few args'
with clang3.1, gcc46 - fine.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "
On 01/07/13 15:22, Mikhail T. wrote:
> On 07.01.2013 03:33, freebsd-ports-requ...@freebsd.org wrote:
>> portname: accessibility/kdeaccessibility description:
>> Accessibility applications for KDE maintainer:po...@freebsd.org
>> deprecated because: Depends on QT3; unmaintained expiration
On 1/7/2013 18:55, awarecons wrote:
Thank you.
As you could notice from the lines (...gcc46 -fpic -DPIC -O2 -pipe
-march=pentium4 -mtune=pentium4...) it raised, when compiling for i386
arch and, yes, it's not on amd64 platform, but i386.
Right, sorry about that. I caught the error after I se
Thank you.
As you could notice from the lines (...gcc46 -fpic -DPIC -O2 -pipe
-march=pentium4 -mtune=pentium4...) it raised, when compiling for i386
arch and, yes, it's not on amd64 platform, but i386.
2013/1/7 John Marino :
> On 1/7/2013 14:06, awarecons wrote:
>
>> libmng_chunk_descr.So: In fun
Right you are - that is perl & python GNU PThread issue.
To avoid extra-coitus moved to non-GNU PThread version of perl & python.
Guess the case needs a person or couple even to dig&repair to-and-fro... ;7
2013/1/7 Marcus von Appen :
> On, Mon Jan 07, 2013, awarecons wrote:
>
>> uname: FreeBSD 9
multimedia/vlc [2.0.5_3]: needs PortAudio2.0 dependence in port
Makefile, if chosen one (absents).
Silent usage of gcc46 for plugins compilation (causes vlc-cache
plugin`s cache generation to fail, when another CC is used generally
in /etc/make.conf: clang or gcc48, for e.g.) and quite strange sil
On, Mon Jan 07, 2013, awarecons wrote:
> uname: FreeBSD 9.0-RELEASE
>
> How to reproduce:
>
> compile, guess any 5.[12-16], perl with GNU PThread support and try,
> for e.g., portmaster x11/kde4 or x11/gnome2 with maximum ports
> involved/chosen (to enlarge test coverage). Try to use clang, gcc 4.
uname: FreeBSD 9.0-RELEASE
How to reproduce:
compile, guess any 5.[12-16], perl with GNU PThread support and try,
for e.g., portmaster x11/kde4 or x11/gnome2 with maximum ports
involved/chosen (to enlarge test coverage). Try to use clang, gcc 4.2
(default) and 4.6.3 (gcc 4.7&4.8 seem to be excess
On 01/07/13 15:43, John Marino wrote:
I don't normally agree with Mikhail's rants to save old ports, but in
the case of KDE-3, I am inclined to share his view.
Are KDE-3 ports causing any problems? I don't know if KDE-3 is still be
developed upstream, but if it's not it doesn't really need muc
Quoting "Mikhail T." :
On 07.01.2013 09:54, Kimmo Paasiala wrote:
Are you willing to step up as the maintainer of the KDE3 ports? Or
anyone else reading this? The situation with ports like KDE3 is that
they are lots of work to keep up in shape and if no one wants to
maintain them they succumb t
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
On 1/7/2013 16:04, Mikhail T. wrote:
On 07.01.2013 09:54, Kimmo Paasiala wrote:
Are you willing to step up as the maintainer of the KDE3 ports? Or
anyone else reading this? The situation with ports like KDE3 is that
they are lots of work to keep up in shape and if no one wants to
maintain them t
On 07.01.2013 09:54, Kimmo Paasiala wrote:
Are you willing to step up as the maintainer of the KDE3 ports? Or
anyone else reading this? The situation with ports like KDE3 is that
they are lots of work to keep up in shape and if no one wants to
maintain them they succumb to what is called "bitrot"
On Mon, Jan 7, 2013 at 4:43 PM, John Marino wrote:
> On 1/7/2013 15:22, Mikhail T. wrote:
>>
>> On 07.01.2013 03:33, freebsd-ports-requ...@freebsd.org wrote:
>>>
>>> portname: accessibility/kdeaccessibility
>>> description: Accessibility applications for KDE
>>> maintainer:po...@freebsd.org
>>> de
On 07.01.2013 09:41, David Demelier wrote:
Because Qt3 is old and KDE3 will completely disappear.
This is exactly the sentiment I find disagreeable -- that simply being
"old" is enough to condemn a perfectly functional piece of software.
Maybe, it is because of my own age, that I am -- in the
On 1/7/2013 15:22, Mikhail T. wrote:
On 07.01.2013 03:33, freebsd-ports-requ...@freebsd.org wrote:
portname: accessibility/kdeaccessibility
description: Accessibility applications for KDE
maintainer:po...@freebsd.org
deprecated because: Depends on QT3; unmaintained
expiration date: 2013-07-01
bu
Because Qt3 is old and KDE3 will completely disappear. It the same goal for
GNOME 2 (not for now because GNOME 3 is not yet available) but GNOME 2 will
ne probably replaced by MATE.
I think you should look at trinity. It is a fork of KDE3 and is in
development to be ported to Qt4 :)
http://mate-d
On 1/7/2013 14:06, awarecons wrote:
libmng_chunk_descr.So: In function `mng_pplt_entries':
libmng_chunk_descr.c:(.text+0x1f41): undefined reference to
`__stack_chk_fail_local'
libmng_pixels.So: In function `.L1180':
libmng_pixels.c:(.text+0xa1da): undefined reference to `__stack_chk_fail_local'
On 07.01.2013 03:33, freebsd-ports-requ...@freebsd.org wrote:
portname: accessibility/kdeaccessibility
description:Accessibility applications for KDE
maintainer:po...@freebsd.org
deprecated because: Depends on QT3; unmaintained
expiration date:2013-07-01
build errors:
gcc 4.6.3:
gcc46 -fpic -DPIC -O2 -pipe -march=pentium4 -mtune=pentium4
-Wl,-rpath=/usr/local/lib/gcc46 -fno-strict-aliasing -march=pentium4
-mtune=pentium4 -I/usr/local/include -DMNG_OPTIMIZE_CHUNKINITFREE
-DMNG_OPTIMIZE_OBJCLEANUP -DMNG_OPTIMIZE_CHUNKASSIGN
-DMNG_OPTIMIZE_CHUNKREADER -std=gnu99 -
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .)
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsol
On 6 Jan 2013, at 20:38, Erik Cederstrand wrote:
> You can't seriously blame LLVM for making progress. If ports rely on a
> specific version of LLVM, it would be far better to create devel/llvm31,
> devel/llvm32 etc.
Well, I can (and, even with my LLVM committer hat on, do) blame LLVM for not
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 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
31 matches
Mail list logo
