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. One common problem is
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. One common problem is
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 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
Can a committer commit the patch attached to this PR
so I don't get more pkg-fallout messages?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198312
Thanks!
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail
In article <54f64bbc.4060...@gmail.com> you write:
>Yeah! I was able to setup qemu-devel(ver 2.20) to use existing qcow2
>images from linux. Sort of...
>
>The biggest pain I had was getting networking to play along. No matter
>what settings, modules or otherwise I tried, I could not get the VM
>
I still haven't fixed it.
But I haven't had enough free time to try other options.
Anton
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
One of my ports (devel/gcc-arm-embedded) doesn't produce much output
on build (output is redirected to log files), but takes severa hours
to be built.
Looks like pkg building cluster doesn't like such behavior.
Could I notify build cluster (pou
You can increase the max_execution_time in /usr/local/share/common.sh
(default 3600 seconds). There are individual timeout values for extract,
install, package and deinstall. These are the maximum values for each stage
(with or without output being produced).
But more likely, you need to look at t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193528
Many packages still don't build with clang (in part because Linux didn't
adopt it as much as FreeBSD did), and at the same time they are changing
code to be c++11.
As a result, many such packages can't be updated any more.
In two days I
On 03/07/15 16:14, Yuri wrote:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193528
Many packages still don't build with clang (in part because Linux didn't
adopt it as much as FreeBSD did), and at the same time they are changing
code to be c++11.
As a result, many such packages can't be u
powerpc64 context (more details are listed later):
$ freebsd-version -ku; uname -a
10.1-STABLE
10.1-STABLE
FreeBSD FBSDG5S0 10.1-STABLE FreeBSD 10.1-STABLE #0 r279507M: Fri Mar 6
23:08:59 PST 2015 root@FBSDG5S0:/usr/obj/usr/src/sys/GENERIC64vtsc powerpc
Ports Revision 380683 via svnlite up
On 03/07/2015 21:28, Russell L. Carter wrote:
I would like to understand better the problem here, because I use c++11
features heavily with lang/gcc49 on a daily basis with zero problems.
No, gcc-4.9.3 fails in the same way. Specific missing feature: std::snprintf
error: 'snprintf' is not a m
powerpc64 context (more details are listed much later):
$ freebsd-version -ku; uname -a
10.1-STABLE
10.1-STABLE
FreeBSD FBSDG5S0 10.1-STABLE FreeBSD 10.1-STABLE #0 r279507M: Fri Mar 6
23:08:59 PST 2015 root@FBSDG5S0:/usr/obj/usr/src/sys/GENERIC64vtsc powerpc
Ports Revision 380683 via svnli
15 matches
Mail list logo
