Nabble - freebsd-gnome

Re: x11/gnome2 fails in pulseaudio on -CURRENT from 2009/11/19

2009-11-21T08:02:31Z

On Sat, 2009-11-21 at 10:42 +0800, Alexander Logvinov wrote:

> Hello!
>
> On 21.11.2009 01:42 Nick Evans wrote:
> > [rtstutter-rtstutter.o] Error 1 gmake[3]: Leaving directory
> > `/usr/ports/audio/pulseaudio/work/pulseaudio-0.9.19/src' gmake[2]:
> > *** [all] Error 2 gmake[2]: Leaving directory
> > `/usr/ports/audio/pulseaudio/work/pulseaudio-0.9.19/src' gmake[1]:
> > *** [all-recursive] Error 1 gmake[1]: Leaving directory
> > `/usr/ports/audio/pulseaudio/work/pulseaudio-0.9.19' gmake: *** [all]
> Please try this:
> http://people.freebsd.org/~avl/patches/pulse-patch-configure

I may have missed something being so busy, but why are we removing
detection of this function? Is there not a more tactical fix to this
build problem?

Joe

>
--
PGP Key : http://www.marcuscom.com/pgp.asc

signature.asc (203 bytes) Download Attachment

FreeBSD ports that you maintain which are currently marked broken

2009-11-20T23:28:26Z

Dear FreeBSD port maintainer:

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 problem is that recent versions
of -CURRENT include gcc4.2, which is much stricter than older versions.
The next most common problem is that compiles succeed on the i386
architecture (e.g. the common Intel PC), but fail on one or more
of the other architectures due to assumptions about things such as
size of various types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments. The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

One more note: on occasion, there are transient build errors seen
on the build farm. Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The errors are listed below. In the case where the same problem
exists on more than one build environment, the URL points to the
latest errorlog for that type. (By 'build environment' here we
mean 'combination of 6.x/7.x/-current with target architecture'.)

(Note: the dates are included to help you to gauge whether or not
the error still applies to the latest version. The program
that generates this report is not yet able to determine this
automatically.)

portname: databases/libgda4-jdbc
broken because: does not configure
build errors: none.
overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=libgda4-jdbc

If these errors are ones that you are already aware of, please
accept our apologies and ignore this message. On the other hand, if
you no longer wish to maintain this port (or ports), please reply
with a message stating that, and accept our thanks for your efforts
in the past.

Every effort has been made to make sure that these error reports
really do correspond to a port that you maintain. However, due to
the fact that this is an automated process, it may indeed generate
false matches. If one of these errors fits that description,
please forward this email to the author of this software, Mark
Linimon <linimon@...>, so that he can attempt to fix the
problem in the future.

Thanks for your efforts to help improve FreeBSD.
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: x11/gnome2 fails in pulseaudio on -CURRENT from 2009/11/19

2009-11-20T18:42:27Z

Hello!

On 21.11.2009 01:42 Nick Evans wrote:
> [rtstutter-rtstutter.o] Error 1 gmake[3]: Leaving directory
> `/usr/ports/audio/pulseaudio/work/pulseaudio-0.9.19/src' gmake[2]:
> *** [all] Error 2 gmake[2]: Leaving directory
> `/usr/ports/audio/pulseaudio/work/pulseaudio-0.9.19/src' gmake[1]:
> *** [all-recursive] Error 1 gmake[1]: Leaving directory
> `/usr/ports/audio/pulseaudio/work/pulseaudio-0.9.19' gmake: *** [all]
Please try this:
http://people.freebsd.org/~avl/patches/pulse-patch-configure

--
Best regards,
Alexander

_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

x11/gnome2 fails in pulseaudio on -CURRENT from 2009/11/19

2009-11-20T09:42:09Z

CC rtstutter-rtstutter.o
tests/rtstutter.c: In function 'work':
tests/rtstutter.c:47: error: 'cpu_set_t' undeclared (first use in this
function) tests/rtstutter.c:47: error: (Each undeclared identifier is
reported only once tests/rtstutter.c:47: error: for each function it
appears in.) tests/rtstutter.c:47: error: expected ';' before 'mask'
tests/rtstutter.c:49: warning: ISO C90 forbids mixed declarations and
code tests/rtstutter.c:58: warning: implicit declaration of function
'CPU_ZERO' tests/rtstutter.c:58: error: 'mask' undeclared (first use
in this function) tests/rtstutter.c:59: warning: implicit declaration
of function 'CPU_SET' tests/rtstutter.c:60: warning: implicit
declaration of function 'pthread_setaffinity_np' gmake[3]: ***
[rtstutter-rtstutter.o] Error 1 gmake[3]: Leaving directory
`/usr/ports/audio/pulseaudio/work/pulseaudio-0.9.19/src' gmake[2]:
*** [all] Error 2 gmake[2]: Leaving directory
`/usr/ports/audio/pulseaudio/work/pulseaudio-0.9.19/src' gmake[1]:
*** [all-recursive] Error 1 gmake[1]: Leaving directory
`/usr/ports/audio/pulseaudio/work/pulseaudio-0.9.19' gmake: *** [all]
Error 2 *** Error code 1

Stop in /usr/ports/audio/pulseaudio.
*** Error code 1

Stop in /usr/ports/audio/pulseaudio.
*** Error code 1
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: [PATCH] Fix security/nss for ia64

2009-11-20T02:23:22Z

On Fri, Nov 20, 2009 at 12:59:16PM +0900, Alexander Nedotsukov wrote:
>
> Yes.
> On Thu, 19 Nov 2009 19:51:25 -0800, Marcel Moolenaar <xcllnt@...>
> wrote:
> > All,
> >
> > The attached patch fixes the build for ia64.
> > Ok for me to commit?

Marcel, well done!

--
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: [PATCH] Fix security/nss for ia64

2009-11-19T19:59:16Z

Yes.
On Thu, 19 Nov 2009 19:51:25 -0800, Marcel Moolenaar <xcllnt@...>
wrote:
> All,
>
> The attached patch fixes the build for ia64.
> Ok for me to commit?
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

[PATCH] Fix security/nss for ia64

2009-11-19T19:51:25Z

All,

The attached patch fixes the build for ia64.
Ok for me to commit?

--
Marcel Moolenaar
xcllnt@...

_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

nss.diff (1K) Download Attachment

Native Firefox 3.5 and Flash10

2009-11-19T13:05:25Z

I am running a Fresh install of amd64 FreeBSD 8.0 RC3
when running firefox It locks up for a moment then is fine then when I
load a new page it locks up again.
here is the error I get in the console when running native firefox 3.5

what do I have to rebuild inorder to fix this?

Sam Fourman Jr.

[sfourman@Sam ~]$ firefox3
Gtk-Message: Failed to load module "canberra-gtk-module":
libcanberra-gtk-module.so: cannot open shared object file: No such
file or directory
Gtk-Message: Failed to load module "gnomebreakpad":
libgnomebreakpad.so: cannot open shared object file: No such file or
directory
Gtk-Message: Failed to load module "canberra-gtk-module":
libcanberra-gtk-module.so: cannot open shared object file: No such
file or directory
Gtk-Message: Failed to load module "gnomebreakpad":
libgnomebreakpad.so: cannot open shared object file: No such file or
directory
*** NSPlugin Wrapper *** ERROR: NPP_New() wait for reply: Message timeout
Gtk-Message: Failed to load module "canberra-gtk-module":
libcanberra-gtk-module.so: cannot open shared object file: No such
file or directory
Gtk-Message: Failed to load module "gnomebreakpad":
libgnomebreakpad.so: cannot open shared object file: No such file or
directory
Gtk-Message: Failed to load module "canberra-gtk-module":
libcanberra-gtk-module.so: cannot open shared object file: No such
file or directory
Gtk-Message: Failed to load module "gnomebreakpad":
libgnomebreakpad.so: cannot open shared object file: No such file or
directory

Sam# uname -a
FreeBSD Sam.PuffyBSD.Com 8.0-RC3 FreeBSD 8.0-RC3 #0: Wed Nov 18
22:22:44 UTC 2009 root@:/usr/obj/usr/src/sys/WORKSTATION amd64

Sam# pkg_info -xI linux
linux-f10-atk-1.24.0 Accessibility Toolkit, Linux/i386 binary (Linux Fedora 10)
linux-f10-cairo-1.8.0 Vector graphics library Cairo (Linux Fedora 10)
linux-f10-curl-7.19.6 The command line tool for transferring files
with URL synta
linux-f10-cyrus-sasl2-2.1.22 RFC 2222 SASL (Simple Authentication and
Security Layer) (L
linux-f10-expat-2.0.1 Linux/i386 binary port of Expat XML-parsing
library (Linux
linux-f10-flashplugin-10.0r32 Adobe Flash Player NPAPI Plugin
linux-f10-fontconfig-2.6.0 An XML-based font configuration API for X
Windows (Linux Fe
linux-f10-gtk2-2.14.7 GTK+ library, version 2.X (Linux Fedora 10)
linux-f10-hicolor-icon-theme-0.5 A high-color icon theme shell from
the FreeDesktop project
linux-f10-jpeg-6b RPM of the JPEG lib (Linux Fedora 10)
linux-f10-libssh2-0.18 The library implementing the SSH2 protocol
(Linux Fedora 10
linux-f10-nspr-4.7.6 Netscape Portable Runtime (Linux Fedora 10)
linux-f10-nss-3.12.2.0 Network Security Services (Linux Fedora 10)
linux-f10-openldap-2.4.12_1 Lightweight Directory Access Protocol
libraries (Linux Fedo
linux-f10-openssl-0.9.8g The OpenSSL toolkit (Linux Fedora 10)
linux-f10-pango-1.22.3 The pango library (Linux Fedora 10)
linux-f10-png-1.2.37 RPM of the PNG lib (Linux Fedora 10)
linux-f10-sqlite3-3.5.9_1 The library that implements an embeddable
SQL database engi
linux-f10-tiff-3.8.2 The TIFF library, Linux/i386 binary (Linux Fedora 10)
linux-f10-xorg-libs-7.4_1 Xorg libraries (Linux Fedora 10)
linux-firefox-3.0.15,1 Web browser based on the browser portion of Mozilla
linux_base-f10-10_2 Base set of packages needed in Linux mode for i386/amd64 (L
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: [FreeBSD] Gedit Plugin issued the following error

2009-11-19T00:39:22Z

Sorry I forgot the attachment.

Best regards,
Daniele.

2009/11/19 Daniele Mazzotti <kappei84@...>

> Dear maintainer,
>
> I am writing to report an error related to gedit. I have installed both
> gedit and gedit plugins on my freebsd 7.2 box but I cannot get the last one
> to work. I have compiled the plugin module with python support.
> Enclosed with the email is a trace of the error and the list of installed
> python packages. As you can see I am using python 2.6 as python version. The
> error is due to the following actions:
>
> 1. open gedit;
> 2. go to edit -> preferences -> plugins;
> 3. try to load code comment, latex plugin (
> http://live.gnome.org/Gedit/LaTeXPlugin) and embed terminal.
>
> I wait forward to receive from you,
>
> regards,
>
> Daniele
>

_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

output (3K) Download Attachment

[FreeBSD] Gedit Plugin issued the following error

2009-11-19T00:35:29Z

Dear maintainer,

I am writing to report an error related to gedit. I have installed both
gedit and gedit plugins on my freebsd 7.2 box but I cannot get the last one
to work. I have compiled the plugin module with python support.
Enclosed with the email is a trace of the error and the list of installed
python packages. As you can see I am using python 2.6 as python version. The
error is due to the following actions:

1. open gedit;
2. go to edit -> preferences -> plugins;
3. try to load code comment, latex plugin (
http://live.gnome.org/Gedit/LaTeXPlugin) and embed terminal.

I wait forward to receive from you,

regards,

Daniele
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: sysutils/libcdio provides no cdio_paranoia.0 for ports/devel/gvfs

2009-11-17T07:44:00Z

Hi TÄ±lman Linneweh & Koop Mast,

Reference:
> From: Koop Mast <kwm@...>
> Date: Mon, 16 Nov 2009 14:47:21 +0100
> Message-id: <1258379241.48450.7.camel@...>

Koop Mast wrote:

> On Mon, 2009-11-16 at 10:51 +0100, Týlman Linneweh wrote:
> > Hello Julian!
> >
> > (CC: devel/gvfs maintainer added)
> >
> > Thanks for reporting this issue.
> >
> > On Nov 15, 2009, at 22:51 , Julian H. Stacey wrote:
> > > int would be welcome please with sysutils/libcdio, Paranoia stuff seems
> > > broken, but I'm not clear what's intended, hence mail rather than a send-pr.
> > >
> > > ===> gvfs-1.2.1 depends on shared library: cdio_paranoia.0 - not found
> > > ===> Verifying install for cdio_paranoia.0 in \
> > > /usr/ports/sysutils/libcdio
> > > ===> Returning to build of gvfs-1.2.1
> > > Error: shared library "cdio_paranoia.0" does not exist
> > > /usr/ports/devel/gvfs ; make
> > > ===> gvfs-1.2.1 depends on shared library: cdio_paranoia.0 - not found
> > > ===> Verifying install for cdio_paranoia.0 in \
> > > /usr/ports/sysutils/libcdio
> > > ===> Returning to build of gvfs-1.2.1
> > > Error: shared library "cdio_paranoia.0" does not exist
> >
> > There are two easy possible solutions.
> > a) make gvfs depend on libcdio.so instead of the non-default cdio_paranoia.0 library
> > b) Change libcdio to install cdio_paranoia.0 by default.
> >
> > Question to gnome@ - Does gvfs really need the cdio_paranoia library, or is this just a bug
> > in the port Makefile and it is ok with the libcdio library?
>
> a) The configure script of the gvfs port checks for cdio_paranoia
> library. It needs it for the cdda backend.
> b) libcdio already got a option for paranoia support and it is default
> to on.
>
> Julian you can do two things now. Either you disable the cdda backend in
> gvfs with the WITH_CDDA option. Or build libcdio with paranoia support.
>
> -Koop

OK Thanks, I'll try both (but not at same time :-) ...
I've not tried just yet as another big compile running.

I'd request one of the 2 ports be changed please, so that
by default, without changing either default options,
the 2 Makefiles are compatible when called from above, eg from
/usr/ports/net-mgmt/etherape

Cheers,
Julian
--
Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Mail plain text not quoted-printable, HTML or Base64: http://asciiribbon.org
Vote For Smoke Free Bavarian Pubs Restaurants http://berklix.org/~jhs/nim/
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: port security/nss fails to build on ia64 - assembler trouble

2009-11-17T07:06:34Z

On Mon, Nov 16, 2009 at 10:36:50AM -0800, Marcel Moolenaar wrote:
> .OBJ/include -I../../../../dist/public/nss -I../../../../dist/private/nss -Impi -Iecl -O -fPIC -ansi -Wall -Wno-switch -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -DSHLIB_SUFFIX=\"so.1\" -DSHLIB_PREFIX=\"lib\" -DSHLIB_VERSION=\"3\" -DSOFTOKEN_SHLIB_VERSION=\"3\" -DRIJNDAEL_INCLUDE_TABLES -UDEBUG -DNDEBUG -D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -DNSS_X86_OR_X64 -DNSS_X86 -DMP_API_COMPATIBLE -I../../../../dist/FreeBSD9.0_OPT.OBJ/include -I../../../../dist/public/nss -I../../../../dist/private/nss -Impi -Iecl sha_fast.c
>
> I ran into this as well. I thought I fixed this.
> Can you update your ports tree and try again. In
> the mean time I'll see what happened to my fix.

no, still the same:

cc -o FreeBSD9.0_OPT.OBJ/FreeBSD_SINGLE_SHLIB/sha_fast.o -c -O2 -pipe -I/usr/local/include/nspr -L/usr/local/lib -fno-strict-aliasing -O -fPIC -ansi -Wall -Wno-switch -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -UDEBUG -DNDEBUG -D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -I../../dist/FreeBSD9.0_OPT.OBJ/include -I../../dist/public/ -I../../dist/private/ -O -fPIC -ansi -Wall -Wno-switch -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -UDEBUG -DNDEBUG -D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -I../../../dist/FreeBSD9.0_OPT.OBJ/include -I../../../dist/public/ -I../../../dist/private/ -O -fPIC -ansi -Wall -Wno-switch -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -DSHLIB_SUFFIX=\"so.1\" -DSHLIB_PREFIX=\"lib\" -DSHLIB_VERSION=\"3\" -DSOFTOKEN_SHLIB_VERSION=\"3\" -DRIJNDAEL_INCLUDE_TABLES -UDEBUG -DNDEBUG -D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -DNSS_X86_OR_X64 -DNSS_X86 -DMP_API_COMPATIBLE -I../../../../dist/FreeBSD9.0_OPT.OBJ/include -I../../../../dist/public/nss -I../../../../dist/private/nss -Impi -Iecl -O -fPIC -ansi -Wall -Wno-switch -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -DSHLIB_SUFFIX=\"so.1\" -DSHLIB_PREFIX=\"lib\" -DSHLIB_VERSION=\"3\" -DSOFTOKEN_SHLIB_VERSION=\"3\" -DRIJNDAEL_INCLUDE_TABLES -UDEBUG -DNDEBUG -D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -DNSS_X86_OR_X64 -DNSS_X86 -DMP_API_COMPATIBLE -I../../../../dist/FreeBSD9.0_OPT.OBJ/include -I../../../../dist/public/nss -I../../../../dist/private/nss -Impi -Iecl sha_fast.c
{standard input}: Assembler messages:
{standard input}:63: Error: Unknown opcode `bswap r14'
{standard input}:98: Error: Unknown opcode `bswap r14'
{standard input}:135: Error: Unknown opcode `bswap r14'
{standard input}:171: Error: Unknown opcode `bswap r14'
{standard input}:207: Error: Unknown opcode `bswap r14'
{standard input}:243: Error: Unknown opcode `bswap r14'
{standard input}:278: Error: Unknown opcode `bswap r14'
{standard input}:315: Error: Unknown opcode `bswap r14'
{standard input}:351: Error: Unknown opcode `bswap r14'
{standard input}:387: Error: Unknown opcode `bswap r14'
{standard input}:423: Error: Unknown opcode `bswap r14'
{standard input}:459: Error: Unknown opcode `bswap r14'
{standard input}:495: Error: Unknown opcode `bswap r14'
{standard input}:531: Error: Unknown opcode `bswap r14'
{standard input}:567: Error: Unknown opcode `bswap r14'
{standard input}:603: Error: Unknown opcode `bswap r14'
{standard input}:3585: Error: Unknown opcode `bswap r14'
{standard input}:3591: Error: Unknown opcode `bswap r35'
{standard input}:3605: Error: Unknown opcode `bswap r14'
{standard input}:3615: Error: Unknown opcode `bswap r14'
{standard input}:3625: Error: Unknown opcode `bswap r14'
{standard input}:3635: Error: Unknown opcode `bswap r14'
{standard input}:3645: Error: Unknown opcode `bswap r14'
gmake[3]: *** [FreeBSD9.0_OPT.OBJ/FreeBSD_SINGLE_SHLIB/sha_fast.o] Error 1
gmake[3]: Leaving directory `/usr/ports/security/nss/work/nss-3.12.4/mozilla/security/nss/lib/freebl'
gmake[2]: *** [libs] Error 2

--
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: port security/nss fails to build on ia64 - assembler trouble

2009-11-16T10:36:50Z

On Nov 16, 2009, at 9:06 AM, Anton Shterenlikht wrote:

> [a port build failure report]
>
> on ia64, kern.osreldate: 900002, while trying to build port
> security/nss I get:
>
> gmake[2]: Leaving directory `/usr/ports/security/nss/work/nss-3.12.4/mozilla/security/nss/lib/util'
> cd freebl; gmake libs
> gmake[2]: Entering directory `/usr/ports/security/nss/work/nss-3.12.4/mozilla/security/nss/lib/freebl'
> ../../../coreconf/nsinstall/FreeBSD9.0_OPT.OBJ/nsinstall -R -m 664 FreeBSD9.0_OPT.OBJ/libfreebl.a ../../../../dist/FreeBSD9.0_OPT.OBJ/lib
> gmake FREEBL_CHILD_BUILD=1 \
> OBJDIR=FreeBSD9.0_OPT.OBJ/FreeBSD_SINGLE_SHLIB libs
> gmake[3]: Entering directory `/usr/ports/security/nss/work/nss-3.12.4/mozilla/security/nss/lib/freebl'
> cc -o FreeBSD9.0_OPT.OBJ/FreeBSD_SINGLE_SHLIB/sha_fast.o -c -O2 -pipe -I/usr/local/include/nspr -L/usr/local/lib -fno-strict-aliasing -O -fPIC -ansi -Wall -Wno-switch -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -UDEBUG -DNDEBUG -D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -I../../dist/FreeBSD9.0_OPT.OBJ/include -I../../dist/public/ -I../../dist/private/ -O -fPIC -ansi -Wall -Wno-switch -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -UDEBUG -DNDEBUG -D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -I../../../dist/FreeBSD9.0_OPT.OBJ/include -I../../../dist/public/ -I../../../dist/private/ -O -fPIC -ansi -Wall -Wno-switch -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -DSHLIB_SUFFIX=\"so.1\" -DSHLIB_PREFIX=\"lib\" -DSHLIB_VERSION=\"3\" -DSOFTOKEN_SHLIB_VERSION=\"3\" -DRIJNDAEL_INCLUDE_TABLES -UDEBUG -DNDEBUG -D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -DNSS_X86_OR_X64 -DNSS_X86 -DMP_API_COMPATIBLE -I../../../../dist/FreeBSD9.0_OPT.OBJ/include -I../../../../dist/public/nss -I../../../../dist/private/nss -Impi -Iecl -O -fPIC -ansi -Wall -Wno-switch -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -DSHLIB_SUFFIX=\"so.1\" -DSHLIB_PREFIX=\"lib\" -DSHLIB_VERSION=\"3\" -DSOFTOKEN_SHLIB_VERSION=\"3\" -DRIJNDAEL_INCLUDE_TABLES -UDEBUG -DNDEBUG -D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -DNSS_X86_OR_X64 -DNSS_X86 -DMP_API_COMPATIBLE -I../../../../dist/FreeBSD9.0_OPT.OBJ/include -I../../../../dist/public/nss -I../../../../dist/private/nss -Impi -Iecl sha_fast.c

I ran into this as well. I thought I fixed this.
Can you update your ports tree and try again. In
the mean time I'll see what happened to my fix.

FYI,

--
Marcel Moolenaar
xcllnt@...

_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

port security/nss fails to build on ia64 - assembler trouble

2009-11-16T09:06:54Z

[a port build failure report]

on ia64, kern.osreldate: 900002, while trying to build port
security/nss I get:

gmake[2]: Leaving directory `/usr/ports/security/nss/work/nss-3.12.4/mozilla/security/nss/lib/util'
cd freebl; gmake libs
gmake[2]: Entering directory `/usr/ports/security/nss/work/nss-3.12.4/mozilla/security/nss/lib/freebl'
../../../coreconf/nsinstall/FreeBSD9.0_OPT.OBJ/nsinstall -R -m 664 FreeBSD9.0_OPT.OBJ/libfreebl.a ../../../../dist/FreeBSD9.0_OPT.OBJ/lib
gmake FREEBL_CHILD_BUILD=1 \
OBJDIR=FreeBSD9.0_OPT.OBJ/FreeBSD_SINGLE_SHLIB libs
gmake[3]: Entering directory `/usr/ports/security/nss/work/nss-3.12.4/mozilla/security/nss/lib/freebl'
cc -o FreeBSD9.0_OPT.OBJ/FreeBSD_SINGLE_SHLIB/sha_fast.o -c -O2 -pipe -I/usr/local/include/nspr -L/usr/local/lib -fno-strict-aliasing -O -fPIC -ansi -Wall -Wno-switch -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -UDEBUG -DNDEBUG -D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -I../../dist/FreeBSD9.0_OPT.OBJ/include -I../../dist/public/ -I../../dist/private/ -O -fPIC -ansi -Wall -Wno-switch -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -UDEBUG -DNDEBUG -D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -I../../../dist/FreeBSD9.0_OPT.OBJ/include -I../../../dist/public/ -I../../../dist/private/ -O -fPIC -ansi -Wall -Wno-switch -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -DSHLIB_SUFFIX=\"so.1\" -DSHLIB_PREFIX=\"lib\" -DSHLIB_VERSION=\"3\" -DSOFTOKEN_SHLIB_VERSION=\"3\" -DRIJNDAEL_INCLUDE_TABLES -UDEBUG -DNDEBUG -D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -DNSS_X86_OR_X64 -DNSS_X86 -DMP_API_COMPATIBLE -I../../../../dist/FreeBSD9.0_OPT.OBJ/include -I../../../../dist/public/nss -I../../../../dist/private/nss -Impi -Iecl -O -fPIC -ansi -Wall -Wno-switch -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -DSHLIB_SUFFIX=\"so.1\" -DSHLIB_PREFIX=\"lib\" -DSHLIB_VERSION=\"3\" -DSOFTOKEN_SHLIB_VERSION=\"3\" -DRIJNDAEL_INCLUDE_TABLES -UDEBUG -DNDEBUG -D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -DNSS_X86_OR_X64 -DNSS_X86 -DMP_API_COMPATIBLE -I../../../../dist/FreeBSD9.0_OPT.OBJ/include -I../../../../dist/public/nss -I../../../../dist/private/nss -Impi -Iecl sha_fast.c
{standard input}: Assembler messages:
{standard input}:63: Error: Unknown opcode `bswap r14'
{standard input}:98: Error: Unknown opcode `bswap r14'
{standard input}:135: Error: Unknown opcode `bswap r14'
{standard input}:171: Error: Unknown opcode `bswap r14'
{standard input}:207: Error: Unknown opcode `bswap r14'
{standard input}:243: Error: Unknown opcode `bswap r14'
{standard input}:278: Error: Unknown opcode `bswap r14'
{standard input}:315: Error: Unknown opcode `bswap r14'
{standard input}:351: Error: Unknown opcode `bswap r14'
{standard input}:387: Error: Unknown opcode `bswap r14'
{standard input}:423: Error: Unknown opcode `bswap r14'
{standard input}:459: Error: Unknown opcode `bswap r14'
{standard input}:495: Error: Unknown opcode `bswap r14'
{standard input}:531: Error: Unknown opcode `bswap r14'
{standard input}:567: Error: Unknown opcode `bswap r14'
{standard input}:603: Error: Unknown opcode `bswap r14'
{standard input}:3585: Error: Unknown opcode `bswap r14'
{standard input}:3591: Error: Unknown opcode `bswap r35'
{standard input}:3605: Error: Unknown opcode `bswap r14'
{standard input}:3615: Error: Unknown opcode `bswap r14'
{standard input}:3625: Error: Unknown opcode `bswap r14'
{standard input}:3635: Error: Unknown opcode `bswap r14'
{standard input}:3645: Error: Unknown opcode `bswap r14'
gmake[3]: *** [FreeBSD9.0_OPT.OBJ/FreeBSD_SINGLE_SHLIB/sha_fast.o] Error 1
gmake[3]: Leaving directory `/usr/ports/security/nss/work/nss-3.12.4/mozilla/security/nss/lib/freebl'
gmake[2]: *** [libs] Error 2
gmake[2]: Leaving directory `/usr/ports/security/nss/work/nss-3.12.4/mozilla/security/nss/lib/freebl'
gmake[1]: *** [libs] Error 2
gmake[1]: Leaving directory `/usr/ports/security/nss/work/nss-3.12.4/mozilla/security/nss/lib'
gmake: *** [libs] Error 2
*** Error code 1

Stop in /usr/ports/security/nss.
*** Error code 1

--
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: sysutils/libcdio provides no cdio_paranoia.0 for ports/devel/gvfs

2009-11-16T05:47:21Z

On Mon, 2009-11-16 at 10:51 +0100, Tılman Linneweh wrote:

> Hello Julian!
>
> (CC: devel/gvfs maintainer added)
>
> Thanks for reporting this issue.
>
> On Nov 15, 2009, at 22:51 , Julian H. Stacey wrote:
> > int would be welcome please with sysutils/libcdio, Paranoia stuff seems
> > broken, but I'm not clear what's intended, hence mail rather than a send-pr.
> >
> > ===> gvfs-1.2.1 depends on shared library: cdio_paranoia.0 - not found
> > ===> Verifying install for cdio_paranoia.0 in \
> > /usr/ports/sysutils/libcdio
> > ===> Returning to build of gvfs-1.2.1
> > Error: shared library "cdio_paranoia.0" does not exist
> > /usr/ports/devel/gvfs ; make
> > ===> gvfs-1.2.1 depends on shared library: cdio_paranoia.0 - not found
> > ===> Verifying install for cdio_paranoia.0 in \
> > /usr/ports/sysutils/libcdio
> > ===> Returning to build of gvfs-1.2.1
> > Error: shared library "cdio_paranoia.0" does not exist
>
> There are two easy possible solutions.
> a) make gvfs depend on libcdio.so instead of the non-default cdio_paranoia.0 library
> b) Change libcdio to install cdio_paranoia.0 by default.
>
> Question to gnome@ - Does gvfs really need the cdio_paranoia library, or is this just a bug
> in the port Makefile and it is ok with the libcdio library?

a) The configure script of the gvfs port checks for cdio_paranoia
library. It needs it for the cdda backend.
b) libcdio already got a option for paranoia support and it is default
to on.

Julian you can do two things now. Either you disable the cdda backend in
gvfs with the WITH_CDDA option. Or build libcdio with paranoia support.

-Koop

> regards
> arved_______________________________________________
> freebsd-ports@... mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@..."
>

_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Current problem reports assigned to gnome@FreeBSD.org

2009-11-16T03:07:13Z

Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

S Tracker Resp. Description
--------------------------------------------------------------------------------
o ports/140563 gnome net/avahi-app doesn't build - depends on missing "gnom
o ports/140543 gnome x11/xcb issue prevents pidgin & xchat ports from compi
o ports/140533 gnome bsd.gnome.mk - mtree may get parameters w/o space
o ports/140216 gnome [patch] devel/nspr does not check POLLHUP in PR_Connec
o ports/140097 gnome update to devel/json-glib
o ports/139972 gnome sysutils/hal / devel/dbus does not automount media
p ports/139941 gnome [PATCH] Add missing dependency to graphics/evince
p ports/139160 gnome update port: devel/dbus This fixes dbus on systems u
a ports/138872 gnome www/epiphany doesn't work when WITH_GECKO=libxul
f ports/137368 gnome x11-toolkits/libwnck: add menu option to configure dep
s ports/137367 gnome net/libproxy: add menu option to configure dependence
s ports/136967 gnome security/seahorse-plugins 2.26.2_1 + GPG = fail
p ports/136676 gnome x11/gnome2: hald/GNOME (I guess) (re) mounted /usr and
f ports/136435 gnome security/gnome-keyring + hald prevents umount of usb d
p ports/134737 gnome Update www/webkit-gtk2 to 1.1.7
f ports/134536 gnome [patch] graphics/gimp: Gimp 2.6.6 fails to open URI's
a ports/134361 gnome devel/gvfs ports with smbclient support doesn't pass a
f ports/134358 gnome x11/gnome2: trackerd uses up all of the cpu
o ports/132304 gnome ports/devel/dbus misses /var/db/dbus/machine-id in dis

19 problems total.

_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: sysutils/libcdio provides no cdio_paranoia.0 for ports/devel/gvfs

2009-11-16T01:51:39Z

Hello Julian!

(CC: devel/gvfs maintainer added)

Thanks for reporting this issue.

On Nov 15, 2009, at 22:51 , Julian H. Stacey wrote:

> int would be welcome please with sysutils/libcdio, Paranoia stuff seems
> broken, but I'm not clear what's intended, hence mail rather than a send-pr.
>
> ===> gvfs-1.2.1 depends on shared library: cdio_paranoia.0 - not found
> ===> Verifying install for cdio_paranoia.0 in \
> /usr/ports/sysutils/libcdio
> ===> Returning to build of gvfs-1.2.1
> Error: shared library "cdio_paranoia.0" does not exist
> /usr/ports/devel/gvfs ; make
> ===> gvfs-1.2.1 depends on shared library: cdio_paranoia.0 - not found
> ===> Verifying install for cdio_paranoia.0 in \
> /usr/ports/sysutils/libcdio
> ===> Returning to build of gvfs-1.2.1
> Error: shared library "cdio_paranoia.0" does not exist

There are two easy possible solutions.
a) make gvfs depend on libcdio.so instead of the non-default cdio_paranoia.0 library
b) Change libcdio to install cdio_paranoia.0 by default.

Question to gnome@ - Does gvfs really need the cdio_paranoia library, or is this just a bug
in the port Makefile and it is ok with the libcdio library?

regards
arved_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: ports/140563: net/avahi-app doesn't build - depends on missing "gnome-config"

2009-11-14T18:50:12Z

Synopsis: net/avahi-app doesn't build - depends on missing "gnome-config"

Responsible-Changed-From-To: freebsd-ports-bugs->gnome
Responsible-Changed-By: edwin
Responsible-Changed-When: Sun Nov 15 02:50:11 UTC 2009
Responsible-Changed-Why:
Over to maintainer (via the GNATS Auto Assign Tool)

http://www.freebsd.org/cgi/query-pr.cgi?pr=140563
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

port build error -- avahi-app

2009-11-14T18:41:18Z

Greetings,

I'm trying to build a port called "gthumb" and that is failing because
several of the prerequsites failed to build properly. One of these
is something called "avahi-app". I have no idea what this is, and
since I'm really just trying to build gthumb, I don't really care.
I just want to get it built.

Anyway, the build of avahi-app is dying during configuration as follows:

...
checking for pkg-config... /usr/local/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GLIB20... yes
checking for GOBJECT... yes
checking for DBUS... yes
Error: Couldn't determine the version of your D-Bus package.
This is probably an error in this script, please report it
along with the following information:
Base D-Buss version =''
DBUS_VERSION_MAJOR='0'
DBUS_VERSION_MINOR='0'
DBUS_VERSION_MICRO='0'
===> Script "configure" failed unexpectedly.
...

I there by any chance a simple/known fix for this?

I have no idea what D-Bus even is, let alone why it's version number is
unknown to the configure for avahi-app.

Any help appreciated.
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: ports/140543: x11/xcb issue prevents pidgin & xchat ports from compiling (on 7.2 + portsnap run at 00:00 14-Nov-2009)

2009-11-13T21:24:46Z

Old Synopsis: XCB issue prevents pidgin & xchat ports from compiling (on 7.2 + portsnap run at 00:00 14-Nov-2009)
New Synopsis: x11/xcb issue prevents pidgin & xchat ports from compiling (on 7.2 + portsnap run at 00:00 14-Nov-2009)

Responsible-Changed-From-To: freebsd-ports-bugs->gnome
Responsible-Changed-By: linimon
Responsible-Changed-When: Sat Nov 14 05:21:36 UTC 2009
Responsible-Changed-Why:
Looks like perhaps a problem in some gnome dependencies?

http://www.freebsd.org/cgi/query-pr.cgi?pr=140543
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: ports/140533: bsd.gnome.mk - mtree may get parameters w/o space

2009-11-13T07:40:22Z

Synopsis: bsd.gnome.mk - mtree may get parameters w/o space

Responsible-Changed-From-To: freebsd-ports-bugs->gnome
Responsible-Changed-By: edwin
Responsible-Changed-When: Fri Nov 13 15:40:21 UTC 2009
Responsible-Changed-Why:
bsd.gnome.mk is gnome territory (via the GNATS Auto Assign Tool)

http://www.freebsd.org/cgi/query-pr.cgi?pr=140533
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

security/nss self-test failures

2009-11-10T11:48:28Z

Hello!

Simply running `make test' after building nss is not any longer possible
due to bit rot. I'm somewhat disappointed, that far from fixing the
problems detected by the tests, the test-target itself was allowed to
deteriorate... In my not so humble opinion (of the person, who created
that target in the first place), it should be invoked by whoever
upgrades the port at least once to make sure, the upgrade does not
introduce new problems...

That's the least, that should be expected, really -- especially, in
preparation for a major release like 8.0...

Here is the simple fix for the target itself:

http://aldan.algebra.com/~mi/nss-test-target-fix.patch

Indeed, there are still some tests failing -- and not uniformly so,
which is troubling.

FreeBSD-7.2-STABLE/amd64: 8 failures
http://aldan.algebra.com/~mi/tmp/aldan-nss-results.html
FreeBSD-7.0-STABLE/i386: 248 failures
http://aldan.algebra.com/~mi/tmp/symbion-nss-results.html

I'll try to bring this up with the NSS developers... But if we claim to
support releases as far back as 6.x, we'll need to account for all
failures :( beginning with those, still present in the latest 8.x and
7.x releases... Yours,

-mi

_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: [marcuscom] gnome 2.28 + linux apps = SIGSEGV ?

2009-11-10T05:36:40Z

On Tue, 10 Nov 2009 08:19:09 +0800 Denise H. G. wrote:
> On 2009/11/06 at 18:11, Boris Samorodov <bsam@...> wrote:
> >
> > Hello List, I faced a problem with 9-CURRENT and 8-STABLE:
> >http://lists.freebsd.org/pipermail/freebsd-current/2009-November/013061.html
> >
> > Both systems use gnome-2.28 from marcuscom. Can anybody use acroread8
> >with gnome-2.28? (I'm not sure but seems that skype and
> >linux-realplayer get SIGSEGV as well.) Other 8-STABLE system with gnome
> >from current ports tree works fine.

> Hi, there seems to be a trick to get linux acroread running. Just use
> sysctl(8) to turn 'security.bsd.map_at_zero' from '0' to '1'. It works
> for me, at least. I'm using 8.0-RC2 amd64.

I think that the latest 8-STABLE doesn't need this trick. But my
problem was with incompatible fontconfig from marcuscom gnome-2.28.

--
WBR, Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: upgrading NSPR to 4.8.2

2009-11-10T05:21:18Z

On Mon, 09 Nov 2009 18:04:54 -0600, Mikhail T. <mi+thun@...>
wrote:

> Jeremy Messenger написав(ла):
>> Because, your attach has turned into message body rather than attach a
>> file. There is no way I (or we are) am going to copy and paste as it
>> won't work to get apply clean. See here:
>>
>> http://lists.freebsd.org/pipermail/freebsd-gnome/2009-November/023324.html
>>
>
> I don't understand... My message was text/plain. You should be able to
> just feed it to patch(1) straight -- it will skip the beginning of the
> e-mail and get right to the patches... Save the message from your Opera
> to a /tmp/nspr-update.diff and feed it to patch...
>
> Just in case, I placed it online too for your convenience:
>
> cd /usr/ports/devel/nspr
> fetch -o - http://aldan.algebra.com/~mi/nspr-4.8.2-update.diff.bz2 |
> bzcat | patch -p
>
>> I don't think the 'regression-test: test' will be include in the ports
>> tree, because it causes pointyhat/tinderbox hang if I remember it
>> correct. Should be in the commit history, I believe.
>
> That should not be happening any more (under 7.2), and when it did, it
> was an indication of a bug (in 7.0)...

We still support FreeBSD 6.x. Let's hold on regression-test until after
FreeBSD 8.0 released. The nspr doesn't need to be shoot pointyhat down
during the thaw.

>> I think most of us are busy at the moment. It looks like if it works
>> great w/ Firefox 3/libxul by build and run time. Then it can be
>> commit. From what I read in the release note and I don't think it
>> breaks anything, but never know (hate when it happens :-)).
>
> So, do you need me to do anything else? Or can I commit it on my own,
> since I am not that busy?

You have the approve to commit it as long as it has been tested and
without that regression-test patch. After FreeBSD 8.0 released, one of us
can enable that regression-test and see how it goes.

Cheers,
Mezz

> -mi

--
mezz7@... - mezz@...
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gnome@...
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: [marcuscom] gnome 2.28 + linux apps = SIGSEGV ?

2009-11-09T16:19:09Z

On 2009/11/06 at 18:11, Boris Samorodov <bsam@...> wrote:
>
> Hello List, I faced a problem with 9-CURRENT and 8-STABLE:
>http://lists.freebsd.org/pipermail/freebsd-current/2009-November/013061.html
>
> Both systems use gnome-2.28 from marcuscom. Can anybody use acroread8
>with gnome-2.28? (I'm not sure but seems that skype and
>linux-realplayer get SIGSEGV as well.) Other 8-STABLE system with gnome
>from current ports tree works fine.
>

Hi, there seems to be a trick to get linux acroread running. Just use
sysctl(8) to turn 'security.bsd.map_at_zero' from '0' to '1'. It works
for me, at least. I'm using 8.0-RC2 amd64.

good luck.

--
(dhg) darcsis |aT| gmail |DoT| COM
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: upgrading NSPR to 4.8.2

2009-11-09T16:04:54Z

Jeremy Messenger написав(ла):
> Because, your attach has turned into message body rather than attach a
> file. There is no way I (or we are) am going to copy and paste as it
> won't work to get apply clean. See here:
>
> http://lists.freebsd.org/pipermail/freebsd-gnome/2009-November/023324.html
>
I don't understand... My message was text/plain. You should be able to
just feed it to patch(1) straight -- it will skip the beginning of the
e-mail and get right to the patches... Save the message from your Opera
to a /tmp/nspr-update.diff and feed it to patch...

Just in case, I placed it online too for your convenience:

cd /usr/ports/devel/nspr
fetch -o - http://aldan.algebra.com/~mi/nspr-4.8.2-update.diff.bz2 |
bzcat | patch -p

> I don't think the 'regression-test: test' will be include in the ports
> tree, because it causes pointyhat/tinderbox hang if I remember it
> correct. Should be in the commit history, I believe.
That should not be happening any more (under 7.2), and when it did, it
was an indication of a bug (in 7.0)...
> I think most of us are busy at the moment. It looks like if it works
> great w/ Firefox 3/libxul by build and run time. Then it can be
> commit. From what I read in the release note and I don't think it
> breaks anything, but never know (hate when it happens :-)).
So, do you need me to do anything else? Or can I commit it on my own,
since I am not that busy?

-mi

_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: upgrading NSPR to 4.8.2

2009-11-09T15:33:37Z

On Mon, 09 Nov 2009 15:14:05 -0600, Mikhail T. <mi+thun@...>
wrote:

> Denise H. G. написав(ла):
>> Hi Mikhail
>>
>> consider using send-pr or sending the problem report via the web
>> interface, which is a more efficient way and will attract more
>> attention.
>
> I really do believe, that e-mailing the port-maintainer is the quickest
> and the surest way of getting a port's issue addressed. Unless the
> particular maintainer is absent, of course :-) in which case any
> ports-committer (such as myself) can fix the problem themselves, after a
> reasonable "maintainer timeout".
>
> Even if I were to submit a PR (what's "web interface" anyway?), it would
> just be assigned to ``gnome''... Why waste time and effort?

Because, your attach has turned into message body rather than attach a
file. There is no way I (or we are) am going to copy and paste as it won't
work to get apply clean. See here:

http://lists.freebsd.org/pipermail/freebsd-gnome/2009-November/023324.html

I don't think the 'regression-test: test' will be include in the ports
tree, because it causes pointyhat/tinderbox hang if I remember it correct.
Should be in the commit history, I believe.

> Joe, do you need more information, or is my update being tested on your
> famous cluster already? I was hoping, this would be done over the
> weekend...

I think most of us are busy at the moment. It looks like if it works great
w/ Firefox 3/libxul by build and run time. Then it can be commit. From
what I read in the release note and I don't think it breaks anything, but
never know (hate when it happens :-)).

> BTW, I sent our collection of little fixes to Mozilla -- maybe, we'll be
> able to remove some of the hunks next time:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=527006

Thanks!

Cheers,
Mezz

> Thanks! Yours,
>
> -mi

--
mezz7@... - mezz@...
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gnome@...
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: upgrading NSPR to 4.8.2

2009-11-09T13:14:05Z

Denise H. G. написав(ла):
> Hi Mikhail
>
> consider using send-pr or sending the problem report via the web
> interface, which is a more efficient way and will attract more
> attention.

I really do believe, that e-mailing the port-maintainer is the quickest
and the surest way of getting a port's issue addressed. Unless the
particular maintainer is absent, of course :-) in which case any
ports-committer (such as myself) can fix the problem themselves, after a
reasonable "maintainer timeout".

Even if I were to submit a PR (what's "web interface" anyway?), it would
just be assigned to ``gnome''... Why waste time and effort?

Joe, do you need more information, or is my update being tested on your
famous cluster already? I was hoping, this would be done over the weekend...

BTW, I sent our collection of little fixes to Mozilla -- maybe, we'll be
able to remove some of the hunks next time:

https://bugzilla.mozilla.org/show_bug.cgi?id=527006

Thanks! Yours,

-mi
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: libxslt port build problem

2009-11-09T11:16:30Z

Kevin Oberman wrote:

>> Apparently there are one or two old versions knocking around:
>>
>> ted# /opt/xml2/bin/xml2-config --version
>> 2.7.3
>> ted# /usr/bin/xml2-config --version
>> 2.6.23
>> ted# /scripts/cpan_sandbox/x86_64/xml2-config --version
>> 2.6.23
>> ted# /root/installd/scripts/cpan_sandbox/x86_64/xml2-config --version
>> 2.6.23
>> ted# /usr/local/bin/xml2-config --version
>> 2.7.6
>>
>> The old versions must have either been installed from some other source
>> or not deleted properly by the ports during upgrade. What's the best way
>> to clean them up as I assume its best to only have the one version running!
>>
>
> Something rather odd has bitten your system. Thee is no reason that any
> port would install files on /usr/bin. It looks to me like someone
> installed libxml2 from place other than ports and it spattered stuff in
> odd places.
>
> /opt is a place several Unix-like systems install things. I know Solaris
> does. The /root/installd and /scripts locations, I don't know
> about. Since all are showing 2.6.23, all were probably done at the same
> time.
>
> One scheme would be to take the output of 'pkg_info -L libxml2-2.7.6 and
> look for these files outside of /usr/local/. Time consuming, but could
> be scripted fairly easily. Any of these files outside of /usr/local or
> /usr/ports should be deleted.
>
> Batter still would be to re-install world AFTER deleting the contents of
> /usr/bin, /usr/include and /usr/lib and manually deleting
> /etc/xml2Conf.sh if it is there. (Note that you will probably be unable
> to run 'make installworld' after blowing away these directories, so you
> will need to re-install them from another system. possibly a live
> CD. I'll admit to never having tried this, though.
>

Thanks for the info, I'm starting to figure some of this out.
It looks like the 2.6.23 files were built when the OS was installed from
the timestamps on the files
I'm running some scripts to find all the offending files, checked the
list and then removed them.
I've also dug up some 2.7.2 files that seem to be linked to Apache so a
full house clean, reinstall the port and now libxslt will build and upgrade.
Many thanks.
Colin.
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: libxslt port build problem

2009-11-09T09:26:52Z

> Date: Mon, 09 Nov 2009 09:15:52 +0000
> From: Colin <colin@...>
> Sender: owner-freebsd-gnome@...
>
> Kevin Oberman wrote:
> >> Date: Sun, 08 Nov 2009 18:19:05 +0000
> >> From: Colin <colin@...>
> >> Sender: owner-freebsd-gnome@...
> >>
> >> Kevin Oberman wrote:
> >>
> >>>> Date: Sun, 08 Nov 2009 11:59:16 +0000
> >>>> From: Colin <colin@...>
> >>>> Sender: owner-freebsd-gnome@...
> >>>>
> >>>> Hi,
> >>>> I've been unable to upgrade libxslt for a while on my installation of
> >>>> FreeBSD 7.0-RELEASE-p12
> >>>> It always tells me the following:
> >>>>
> >>>> checking for libxml libraries >= 2.6.27... configure: error: Version
> >>>> 2.6.23 found. You need at least libxml2 2.6.27 for this version of libxslt
> >>>>
> >>>> I can find no information on where it is getting the information that
> >>>> 2.6.23 is installed because pkg_info shows only libxml2-2.7.6 (the
> >>>> current port) as installed.
> >>>>
> >>>> I don't really know anything about libxml2 so I assume there's some
> >>>> leftover bits from an old version somewhere..can you point me in the
> >>>> right direction to clean it up?
> >>>>
> >>>>
> >>> Just 'portupgrade -f libxml2' should do the trick. (Or what every tool
> >>> you would use to force the re-installation of a port). Then upgrade
> >>> libxslt. At least this has worked for me.
> >>>
> >>>
> >> Thanks for the reply Kevin,
> >> I have already done a full rebuild including recompiling libxml
> >> however I didn't use portupgrade. I've just tried the way you say and
> >> that has unfortunately not made any difference.
> >>
> >> Oh and as a side note, are there any archived for this list? The
> >> FreeBSD Gnome page lists freebsd-gnome and has a search box that
> >> points to a Russian site but I was wondering if there's a browseable
> >> archive?
> >>
> >
> > Rats. This has always worked for me.
> >
> > The configure script, at about line 15800, does the check by issuing the
> > command 'xml2-config --version'. It should be using the xml2-config in
> > /usr/local/bin, but it does several operations to determine exactly what
> > command to use, so something might be causing it to use an old one.
> >
> > First, try entering '/usr/local/bin/xml2-config --version'. If that
> > reports the correct version, try 'locate xml2-config' to see if there is
> > another xml2-config on the system.
> >
> > Archives are found a number of places, but the official one is
> > http://www.freebsd.org/community/mailinglists.html
> >
> Apparently there are one or two old versions knocking around:
>
> ted# /opt/xml2/bin/xml2-config --version
> 2.7.3
> ted# /usr/bin/xml2-config --version
> 2.6.23
> ted# /scripts/cpan_sandbox/x86_64/xml2-config --version
> 2.6.23
> ted# /root/installd/scripts/cpan_sandbox/x86_64/xml2-config --version
> 2.6.23
> ted# /usr/local/bin/xml2-config --version
> 2.7.6
>
> The old versions must have either been installed from some other source
> or not deleted properly by the ports during upgrade. What's the best way
> to clean them up as I assume its best to only have the one version running!

Something rather odd has bitten your system. Thee is no reason that any
port would install files on /usr/bin. It looks to me like someone
installed libxml2 from place other than ports and it spattered stuff in
odd places.

/opt is a place several Unix-like systems install things. I know Solaris
does. The /root/installd and /scripts locations, I don't know
about. Since all are showing 2.6.23, all were probably done at the same
time.

One scheme would be to take the output of 'pkg_info -L libxml2-2.7.6 and
look for these files outside of /usr/local/. Time consuming, but could
be scripted fairly easily. Any of these files outside of /usr/local or
/usr/ports should be deleted.

Batter still would be to re-install world AFTER deleting the contents of
/usr/bin, /usr/include and /usr/lib and manually deleting
/etc/xml2Conf.sh if it is there. (Note that you will probably be unable
to run 'make installworld' after blowing away these directories, so you
will need to re-install them from another system. possibly a live
CD. I'll admit to never having tried this, though.
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@... Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: greeter application is missing[?!] is this the gnome login?

2009-11-09T06:31:14Z

On 2007/10/29, Gary Kline <kline@...> wrote:
>
> Lines: 21
> Well, I managed to hose my gnome config *thoroughly*. Can
> anybody clue me in how to set things right?
>
> /home is now where /usr/home was before. I have a dummy
> acccolunt that when I typr (as root) kdm, KDE starts up.
> But trying gdm (or automating this in /etc/rc.conf) gets me
> nowhere. I deleted ~/.gnome2 thinking that itwould be rebuilt on

There might be a need to change the HOME value in your $HOME/.profile.
It might be the problem, I think, since you moved your home directory
from /usr/home to /home.

--

(dhg) darcsis |aT| gmail |DoT| COM
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Current problem reports assigned to gnome@FreeBSD.org

2009-11-09T03:07:15Z

Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

S Tracker Resp. Description
--------------------------------------------------------------------------------
o ports/140216 gnome [patch] devel/nspr does not check POLLHUP in PR_Connec
o ports/140097 gnome update to devel/json-glib
o ports/139972 gnome sysutils/hal / devel/dbus does not automount media
p ports/139941 gnome [PATCH] Add missing dependency to graphics/evince
p ports/139160 gnome update port: devel/dbus This fixes dbus on systems u
a ports/138872 gnome www/epiphany doesn't work when WITH_GECKO=libxul
f ports/137368 gnome x11-toolkits/libwnck: add menu option to configure dep
s ports/137367 gnome net/libproxy: add menu option to configure dependence
s ports/136967 gnome security/seahorse-plugins 2.26.2_1 + GPG = fail
p ports/136676 gnome x11/gnome2: hald/GNOME (I guess) (re) mounted /usr and
f ports/136435 gnome security/gnome-keyring + hald prevents umount of usb d
p ports/134737 gnome Update www/webkit-gtk2 to 1.1.7
f ports/134536 gnome [patch] graphics/gimp: Gimp 2.6.6 fails to open URI's
a ports/134361 gnome devel/gvfs ports with smbclient support doesn't pass a
f ports/134358 gnome x11/gnome2: trackerd uses up all of the cpu
o ports/132304 gnome ports/devel/dbus misses /var/db/dbus/machine-id in dis

16 problems total.

_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: libxslt port build problem

2009-11-09T01:15:52Z

Kevin Oberman wrote:

>> Date: Sun, 08 Nov 2009 18:19:05 +0000
>> From: Colin <colin@...>
>> Sender: owner-freebsd-gnome@...
>>
>> Kevin Oberman wrote:
>>
>>>> Date: Sun, 08 Nov 2009 11:59:16 +0000
>>>> From: Colin <colin@...>
>>>> Sender: owner-freebsd-gnome@...
>>>>
>>>> Hi,
>>>> I've been unable to upgrade libxslt for a while on my installation of
>>>> FreeBSD 7.0-RELEASE-p12
>>>> It always tells me the following:
>>>>
>>>> checking for libxml libraries >= 2.6.27... configure: error: Version
>>>> 2.6.23 found. You need at least libxml2 2.6.27 for this version of libxslt
>>>>
>>>> I can find no information on where it is getting the information that
>>>> 2.6.23 is installed because pkg_info shows only libxml2-2.7.6 (the
>>>> current port) as installed.
>>>>
>>>> I don't really know anything about libxml2 so I assume there's some
>>>> leftover bits from an old version somewhere..can you point me in the
>>>> right direction to clean it up?
>>>>
>>>>
>>> Just 'portupgrade -f libxml2' should do the trick. (Or what every tool
>>> you would use to force the re-installation of a port). Then upgrade
>>> libxslt. At least this has worked for me.
>>>
>>>
>> Thanks for the reply Kevin,
>> I have already done a full rebuild including recompiling libxml
>> however I didn't use portupgrade. I've just tried the way you say and
>> that has unfortunately not made any difference.
>>
>> Oh and as a side note, are there any archived for this list? The
>> FreeBSD Gnome page lists freebsd-gnome and has a search box that
>> points to a Russian site but I was wondering if there's a browseable
>> archive?
>>
>
> Rats. This has always worked for me.
>
> The configure script, at about line 15800, does the check by issuing the
> command 'xml2-config --version'. It should be using the xml2-config in
> /usr/local/bin, but it does several operations to determine exactly what
> command to use, so something might be causing it to use an old one.
>
> First, try entering '/usr/local/bin/xml2-config --version'. If that
> reports the correct version, try 'locate xml2-config' to see if there is
> another xml2-config on the system.
>
> Archives are found a number of places, but the official one is
> http://www.freebsd.org/community/mailinglists.html
>

Apparently there are one or two old versions knocking around:

ted# /opt/xml2/bin/xml2-config --version
2.7.3
ted# /usr/bin/xml2-config --version
2.6.23
ted# /scripts/cpan_sandbox/x86_64/xml2-config --version
2.6.23
ted# /root/installd/scripts/cpan_sandbox/x86_64/xml2-config --version
2.6.23
ted# /usr/local/bin/xml2-config --version
2.7.6

The old versions must have either been installed from some other source
or not deleted properly by the ports during upgrade. What's the best way
to clean them up as I assume its best to only have the one version running!
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: libxslt port build problem

2009-11-08T21:37:11Z

> Date: Sun, 08 Nov 2009 18:19:05 +0000
> From: Colin <colin@...>
> Sender: owner-freebsd-gnome@...
>
> Kevin Oberman wrote:
> >> Date: Sun, 08 Nov 2009 11:59:16 +0000
> >> From: Colin <colin@...>
> >> Sender: owner-freebsd-gnome@...
> >>
> >> Hi,
> >> I've been unable to upgrade libxslt for a while on my installation of
> >> FreeBSD 7.0-RELEASE-p12
> >> It always tells me the following:
> >>
> >> checking for libxml libraries >= 2.6.27... configure: error: Version
> >> 2.6.23 found. You need at least libxml2 2.6.27 for this version of libxslt
> >>
> >> I can find no information on where it is getting the information that
> >> 2.6.23 is installed because pkg_info shows only libxml2-2.7.6 (the
> >> current port) as installed.
> >>
> >> I don't really know anything about libxml2 so I assume there's some
> >> leftover bits from an old version somewhere..can you point me in the
> >> right direction to clean it up?
> >>
> >
> > Just 'portupgrade -f libxml2' should do the trick. (Or what every tool
> > you would use to force the re-installation of a port). Then upgrade
> > libxslt. At least this has worked for me.
> >
> Thanks for the reply Kevin,
> I have already done a full rebuild including recompiling libxml
> however I didn't use portupgrade. I've just tried the way you say and
> that has unfortunately not made any difference.
>
> Oh and as a side note, are there any archived for this list? The
> FreeBSD Gnome page lists freebsd-gnome and has a search box that
> points to a Russian site but I was wondering if there's a browseable
> archive?

Rats. This has always worked for me.

The configure script, at about line 15800, does the check by issuing the
command 'xml2-config --version'. It should be using the xml2-config in
/usr/local/bin, but it does several operations to determine exactly what
command to use, so something might be causing it to use an old one.

First, try entering '/usr/local/bin/xml2-config --version'. If that
reports the correct version, try 'locate xml2-config' to see if there is
another xml2-config on the system.

Archives are found a number of places, but the official one is
http://www.freebsd.org/community/mailinglists.html
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@... Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

Re: libxslt port build problem

2009-11-08T21:35:24Z

On Sun, 08 Nov 2009 18:19:05 +0000, Colin <colin@...>
wrote:

> Kevin Oberman wrote:
>>> Date: Sun, 08 Nov 2009 11:59:16 +0000
>>> From: Colin <colin@...>
>>> Sender: owner-freebsd-gnome@...
>>>
>>> Hi,
>>> I've been unable to upgrade libxslt for a while on my installation of
>>> FreeBSD 7.0-RELEASE-p12
>>> It always tells me the following:
>>>
>>> checking for libxml libraries >= 2.6.27... configure: error: Version
>>> 2.6.23 found. You need at least libxml2 2.6.27 for this version of
>>> libxslt
>>>
>>> I can find no information on where it is getting the information that
>>> 2.6.23 is installed because pkg_info shows only libxml2-2.7.6 (the
>>> current port) as installed.
>>>
>>> I don't really know anything about libxml2 so I assume there's some
>>> leftover bits from an old version somewhere..can you point me in the
>>> right direction to clean it up?
>>>
>>
>> Just 'portupgrade -f libxml2' should do the trick. (Or what every tool
>> you would use to force the re-installation of a port). Then upgrade
>> libxslt. At least this has worked for me.
>>
> Thanks for the reply Kevin,
> I have already done a full rebuild including recompiling libxml however

I
> didn't use portupgrade. I've just tried the way you say and that has
> unfortunately not made any difference.
Show me output of pkg-config libxml-2.0 --modversion, please.

> Oh and as a side note, are there any archived for this list?
http://lists.freebsd.org/pipermail/freebsd-gnome/

> The FreeBSD Gnome page lists freebsd-gnome and has a search box that
> points to a Russian site but I was wondering if there's a browseable
> archive?
>
> Cheers,
> Colin.
>
> _______________________________________________
> freebsd-gnome@... mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
> To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."

_______________________________________________
freebsd-gnome@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@..."