I am unable to update ports tree using ssubversion, where I was consistently
successful until now, because of a supposedly missing file:
root@amelia4:/BETA1/usr/ports # svn up .
Updating '.':
Ux11/i3lock/Makefile
Ux11/xpyb/Makefile
Ux11/mate-applets/Makefile
svn: E02: Can't open
Is it necessary for the installed FreeBSD to be in sync with the src tree for
ports to build successfully?
I might update the src tree to see what is happening but not do the buildworld
and buildkernel every time. Could that hurt for building ports? Or do I worry
needlessly?
On 20 April 2014 23:41, Thomas Mueller mueller6...@bellsouth.net wrote:
Is it necessary for the installed FreeBSD to be in sync with the src tree for
ports to build successfully?
I might update the src tree to see what is happening but not do the
buildworld and buildkernel every time.
Thomas Mueller wrote on 21.04.2014 10:41:
Is it necessary for the installed FreeBSD to be in sync with the src tree for
ports to build successfully?
I might update the src tree to see what is happening but not do the buildworld
and buildkernel every time. Could that hurt for building ports?
This is a problem which I think is happening at many places within the
ports tree, but often isn't being recognised.
Say a port uses liba and libz. Liba is a common, say graphics library port.
It is a required port, and installs in /usr/local/include/liba.h and
usr/local/lib/liba.so . Libz is
- Fix plist to have proper 'rmdir DIR' ordering.
Pkgng will not detect the directory otherwise. This was due to
incorrectly advise in the check-stagedir.sh script, fixed in
r351587
With hat: portmgr
-
Build ID:
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
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
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
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
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,
+--On 20 avril 2014 20:10:39 -0400 Robert Huff roberth...@rcn.com wrote:
| Is there a authoritative list of those ports know to not build with
| clang 3.2/3.4?
No, but you can grep for USE_GCC in the ports tree to find that out.
--
Mathieu Arnold
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,
(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
On 04/21/2014 04:58 AM, Mathieu Arnold wrote:
+--On 20 avril 2014 20:10:39 -0400 Robert Huff roberth...@rcn.com wrote:
| Is there a authoritative list of those ports know to not build with
| clang 3.2/3.4?
No, but you can grep for USE_GCC in the ports tree to find that out.
Maybe you
I did not test this commit. I was fixing improper ordering in @unexec
lines.
If you see your port in here, please fix it.
Thanks,
Bryan
On 2014-04-21 03:22, Ports-QAT wrote:
- Fix plist to have proper 'rmdir DIR' ordering.
Pkgng will not detect the directory otherwise. This was due to
On Mon, 21 Apr 2014 11:58:58 +0200
Mathieu Arnold m...@freebsd.org wrote:
+--On 20 avril 2014 20:10:39 -0400 Robert Huff roberth...@rcn.com wrote:
| Is there a authoritative list of those ports know to not build with
| clang 3.2/3.4?
No, but you can grep for USE_GCC in the ports tree to
+--On 21 avril 2014 17:56:45 +0200 Matthieu Volat ma...@alkumuna.eu wrote:
| On Mon, 21 Apr 2014 11:58:58 +0200
| Mathieu Arnold m...@freebsd.org wrote:
|
| +--On 20 avril 2014 20:10:39 -0400 Robert Huff roberth...@rcn.com
| wrote:
| |Is there a authoritative list of those ports know to not
+--On 21 avril 2014 13:46:54 + Montgomery-Smith, Stephen
step...@missouri.edu wrote:
| On 04/21/2014 04:58 AM, Mathieu Arnold wrote:
| +--On 20 avril 2014 20:10:39 -0400 Robert Huff roberth...@rcn.com
| wrote:
| |Is there a authoritative list of those ports know to not build with
| | clang
В Mon, 21 Apr 2014 11:30:56 +0200
Niclas Zeising zeis...@freebsd.org пишет:
On 04/20/14 19:05, Ivan Klymenko wrote:
Hi all.
You are tired of frequent friezes xorg server?
Are you bored messages in /var/log/Xorg.0.log:
...
[mi] EQ overflowing. Additional events will be discarded
On 21 Apr 2014, at 18:30, Mathieu Arnold m...@freebsd.org wrote:
+--On 21 avril 2014 13:46:54 + Montgomery-Smith, Stephen
step...@missouri.edu wrote:
| On 04/21/2014 04:58 AM, Mathieu Arnold wrote:
| +--On 20 avril 2014 20:10:39 -0400 Robert Huff roberth...@rcn.com
| wrote:
| | Is there
On Mon, Apr 21, 2014 at 02:31:12PM -0400, John Baldwin wrote:
On Thursday, April 17, 2014 2:50:01 pm Konstantin Belousov wrote:
The following reply was made to PR amd64/188699; it has been noted by GNATS.
From: Konstantin Belousov kostik...@gmail.com
To: John Allman free...@hugme.org
+1
Only www/opera should actually need libmap entry, rest of the
pkg_libchk output sohuld be rebuilt.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/libfreetype-so-9-errors-tp5905087p5905460.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
On Sun, 20 Apr 2014, Beeblebrox wrote:
Use sysutils/libchk and 'pkg which' to find the port that is linked
against the old library and needs rebuild.
Irrelevant - full poudriere run means I am re-building all ports from a full
list of ports installed on the system. Also, the UPDATING entry
Hi all,
I have ported a new upstream snapshot of mplayer and mencoder.
The tarball with drop-in replacements for both ports can be found here:
http://people.freebsd.org/~riggs/m20140421.tar.xz
The following things have changed compared to the current version in
svn head:
- Sync with upstream
These ports are no longer used or cared for.
Horia Racoviceanu ho...@racoviceanu.com wishes to maintain these ports
with my help.
misc/lxde-common
- Bump PORTREVISION
- Pass maintainership to ho...@racoviceanu.com
misc/xdg-menu
- Change Makefile header, use my name and @FreeBSD.org email
-
On Monday, April 21, 2014 3:51:33 pm Konstantin Belousov wrote:
On Mon, Apr 21, 2014 at 02:31:12PM -0400, John Baldwin wrote:
On Thursday, April 17, 2014 2:50:01 pm Konstantin Belousov wrote:
The following reply was made to PR amd64/188699; it has been noted by
GNATS.
From:
On Mon, Apr 21, 2014 at 05:23:04PM -0400, John Baldwin wrote:
On Monday, April 21, 2014 3:51:33 pm Konstantin Belousov wrote:
On Mon, Apr 21, 2014 at 02:31:12PM -0400, John Baldwin wrote:
On Thursday, April 17, 2014 2:50:01 pm Konstantin Belousov wrote:
The following reply was made to PR
On 2014-04-21 16:40, Konstantin Belousov wrote:
On Mon, Apr 21, 2014 at 05:23:04PM -0400, John Baldwin wrote:
On Monday, April 21, 2014 3:51:33 pm Konstantin Belousov wrote:
On Mon, Apr 21, 2014 at 02:31:12PM -0400, John Baldwin wrote:
On Thursday, April 17, 2014 2:50:01 pm Konstantin
On 21/04/14 21:51, Konstantin Belousov wrote:
On Mon, Apr 21, 2014 at 02:31:12PM -0400, John Baldwin wrote:
On Thursday, April 17, 2014 2:50:01 pm Konstantin Belousov wrote:
The following reply was made to PR amd64/188699; it has been noted by GNATS.
From: Konstantin Belousov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2014-04-21 17:46:32 -0400, Bryan Drewery wrote:
On 2014-04-21 16:40, Konstantin Belousov wrote:
On Mon, Apr 21, 2014 at 05:23:04PM -0400, John Baldwin wrote:
On Monday, April 21, 2014 3:51:33 pm Konstantin Belousov
wrote:
On Mon, Apr 21, 2014
On Mon, Apr 21, 2014 at 11:52:59PM +0200, Emanuel Haupt wrote:
On 21/04/14 21:51, Konstantin Belousov wrote:
On Mon, Apr 21, 2014 at 02:31:12PM -0400, John Baldwin wrote:
On Thursday, April 17, 2014 2:50:01 pm Konstantin Belousov wrote:
The following reply was made to PR amd64/188699; it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2014-04-21 18:00:30 -0400, Jung-uk Kim wrote:
2014년 4월 21일 18:00, Jung-uk Kim 쓴 글: On 2014-04-21 17:46:32
- -0400, Bryan Drewery wrote:
On 2014-04-21 16:40, Konstantin Belousov wrote:
On Mon, Apr 21, 2014 at 05:23:04PM -0400, John Baldwin wrote:
With respect to the missing libxcb.so.2: try re-building open-motif.
This updated libXm, which made a large number of these vanish.
Robert Huff
___
freebsd-ports@freebsd.org mailing list
print/xfce4-print builds normally on 9.2-R with default config,
but build fails when port is configured with --enable-cups rather
than --enable-bsdlpr.
STDERR attached.
--
c...@sdf.org
SDF Public Access UNIX System - http://sdf.org
--
cups.c: In function
On 21/04/2014 1:41 AM, Mathieu Arnold wrote:
Hi,
+--On 20 avril 2014 11:18:35 -0400 Chris Ross cross+free...@distal.com
wrote:
|
| The pkg-message in dns/bind910 (actually, bind9*) includes text about
| setting up a chroot environment, and configuring rdns. At the end, it
| says:
|
On 22 April 2014 09:41, Cary c...@sdf.org wrote:
print/xfce4-print builds normally on 9.2-R with default config,
but build fails when port is configured with --enable-cups rather
than --enable-bsdlpr.
STDERR attached.
Could we have a little more information? The command lines for that
On Tue, Apr 22, 2014 at 10:30:37AM +1000, Robert Backhaus wrote:
On 22 April 2014 09:41, Cary c...@sdf.org wrote:
print/xfce4-print builds normally on 9.2-R with default config,
but build fails when port is configured with --enable-cups rather
than --enable-bsdlpr.
STDERR attached.
On 22 April 2014 11:09, Cary c...@sdf.org wrote:
On Tue, Apr 22, 2014 at 10:30:37AM +1000, Robert Backhaus wrote:
On 22 April 2014 09:41, Cary c...@sdf.org wrote:
print/xfce4-print builds normally on 9.2-R with default config,
but build fails when port is configured with --enable-cups
On Tue, Apr 22, 2014 at 12:16:34PM +1000, Robert Backhaus wrote:
Thanks. First thing to do is rebuild and reinstall print/cups-client . That
port installs the file that includes the typedef that it is complaining
about. My programming skills are very low, especially when it comes to the
40 matches
Mail list logo
