devel/linux-js update for FreeBSD 8.0

2009-12-20 Thread Martin Laabs

Hi,

does someone has started updating the linux-js port for the new USB 
interface in the kernel? I'm trying it at the moment and do not want to do 
work twice.


Greetings,
 Martin L.

PS: I'm not subscribed to the ports mailing list - so please also reply 
directly.


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


status of x11-drivers/input-wacom

2009-12-20 Thread Frank Staals

Hey everyone,

Does anyone know of there is someone working on updating the input-wacom 
driver ? The current port is broken on FreeBSD >= 8 and outdated. It 
would be a shame if the driver realy dies; without the absolute 
positioning the pen-tablets are not as usefull as they could be. I'm 
don't have enough experiance in C to try and fix it myself, but I will 
do what I can to help.


--

- Frank
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


port print/ghostscript8 fails to build on ia64, sparc64

2009-12-20 Thread Anton Shterenlikht
===>  Building for ghostscript8-8.70
/bin/mkdir -p /usr/ports/print/ghostscript8/work/ghostscript-8.70/obj
/bin/mkdir -p /usr/ports/print/ghostscript8/work/ghostscript-8.70/bin
/bin/mkdir -p 
/usr/ports/print/ghostscript8/work/ghostscript-8.70/freetype/include
/bin/ln -s -f /usr/local/include/ft2build.h  
/usr/ports/print/ghostscript8/work/ghostscript-8.70/freetype/include/ft2build.h
/bin/ln -s -f /usr/local/include/freetype2/freetype  
/usr/ports/print/ghostscript8/work/ghostscript-8.70/freetype/include/freetype
/bin/mkdir -p /usr/ports/print/ghostscript8/work/ghostscript-8.70/freetype/objs
/bin/ln -s -f /usr/local/lib/libfreetype.so  
/usr/ports/print/ghostscript8/work/ghostscript-8.70/freetype/objs/freetype214MT_D.so
/bin/mv 
/usr/ports/print/ghostscript8/work/ghostscript-8.70/base/write_t[12].[ch]  
/usr/ports/print/ghostscript8/work/ghostscript-8.70/base/wrfont.[ch]  
/usr/ports/print/ghostscript8/work/ghostscript-8.70/psi
mv: rename 
/usr/ports/print/ghostscript8/work/ghostscript-8.70/base/write_t[12].[ch] to 
/usr/ports/print/ghostscript8/work/ghostscript-8.70/psi/write_t[12].[ch]: No 
such file or directory
mv: rename /usr/ports/print/ghostscript8/work/ghostscript-8.70/base/wrfont.[ch] 
to /usr/ports/print/ghostscript8/work/ghostscript-8.70/psi/wrfont.[ch]: No such 
file or directory
*** Error code 1

Stop in /usr/ports/print/ghostscript8.
*** 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-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: status of x11-drivers/input-wacom

2009-12-20 Thread Jerry
On Sun, 20 Dec 2009 12:38:05 +0100
Frank Staals  articulated:

> Hey everyone,
> 
> Does anyone know of there is someone working on updating the
> input-wacom driver ? The current port is broken on FreeBSD >= 8 and
> outdated. It would be a shame if the driver realy dies; without the
> absolute positioning the pen-tablets are not as usefull as they could
> be. I'm don't have enough experiance in C to try and fix it myself,
> but I will do what I can to help.

Did you try to contact the port maintainer?

kamik...@bsdforen.de

-- 
Jerry
ges...@yahoo.com

|===
|===
|===
|===
|

Remember: Silly is a state of Mind, Stupid is a way of Life.

Dave Butler

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


Attempted upgrade of ghostscript8-8.64_7 -> ghostscript-8.70 failed

2009-12-20 Thread David Wolfskill
This was under stable/6; it may be relevant to note that as I have 4
slices configured on my laptop's disk, each of which is bootable
(stable/6, stable/7, stable/8, & head), /usr/ports is actually a symlink
from each of those slices to a file system that is mountable regardless
of which slice is booted.

The fetch eventually ompleted; the build started, but ended thus:

...
checking for strerror... yes
checking for strrchr... yes
checking for strspn... yes
checking for strstr... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating cups/pstopxl
config.status: creating cups/pstoraster
===>  Building for ghostscript8-8.70
/bin/ln -s -f 
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/epag-3.09/gdevepag.c 
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/base
/bin/mkdir -p /bkp/ports/print/ghostscript8/work/ghostscript-8.70/obj
/bin/mkdir -p /bkp/ports/print/ghostscript8/work/ghostscript-8.70/bin
/bin/mkdir -p 
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/freetype/include
/bin/ln -s -f /usr/local/include/ft2build.h  
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/freetype/include/ft2build.h
/bin/ln -s -f /usr/local/include/freetype2/freetype  
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/freetype/include/freetype
/bin/mkdir -p /bkp/ports/print/ghostscript8/work/ghostscript-8.70/freetype/objs
/bin/ln -s -f /usr/local/lib/libfreetype.so  
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/freetype/objs/freetype214MT_D.so
/bin/mv 
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/write_t[12].[ch]  
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/wrfont.[ch]  
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/psi
mv: rename 
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/write_t[12].[ch] to 
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/psi/write_t[12].[ch]: No 
such file or directory
mv: rename /bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/wrfont.[ch] 
to /bkp/ports/print/ghostscript8/work/ghostscript-8.70/psi/wrfont.[ch]: No such 
file or directory
*** Error code 1

Stop in /bkp/ports/print/ghostscript8.
*** Error code 1

Stop in /bkp/ports/print/ghostscript8.

===>>> make failed for print/ghostscript8
===>>> Aborting update

===>>> Update for ghostscript8-8.64_7 failed
===>>> Aborting update


As a reality check:

g1-119(6.4-S)[4] ls -lT 
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/write*
ls: No match.
g1-119(6.4-S)[5] 

(Though I note that /bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/
does seem to be populated with several other files.)

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


pgp7pC29oEmSA.pgp
Description: PGP signature


Re: devel/linux-js update for FreeBSD 8.0

2009-12-20 Thread Jerry
On Sun, 20 Dec 2009 12:39:48 +0100
Martin Laabs  articulated:

> Hi,
> 
> does someone has started updating the linux-js port for the new USB 
> interface in the kernel? I'm trying it at the moment and do not want
> to do work twice.
> 
> Greetings,
>   Martin L.
> 
> PS: I'm not subscribed to the ports mailing list - so please also
> reply directly.

OK, jylef...@freebsd.org is listed in the 'pkg-descr' file, although
apparently he no longer maintains the port. You might try contacting
them anyway.

-- 
Jerry
ges...@yahoo.com

|===
|===
|===
|===
|

The Ancient Doctrine of Mind Over Matter:

"I don't mind... and you don't matter." As revealed to reporter G.
Rivera by Swami Havabanana

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


Re: Attempted upgrade of ghostscript8-8.64_7 -> ghostscript-8.70 failed

2009-12-20 Thread Anton Shterenlikht
On Sun, Dec 20, 2009 at 05:18:40AM -0800, David Wolfskill wrote:
> This was under stable/6; it may be relevant to note that as I have 4
> slices configured on my laptop's disk, each of which is bootable
> (stable/6, stable/7, stable/8, & head), /usr/ports is actually a symlink
> from each of those slices to a file system that is mountable regardless
> of which slice is booted.
> 
> The fetch eventually ompleted; the build started, but ended thus:
> 
> ...
> checking for strerror... yes
> checking for strrchr... yes
> checking for strspn... yes
> checking for strstr... yes
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating cups/pstopxl
> config.status: creating cups/pstoraster
> ===>  Building for ghostscript8-8.70
> /bin/ln -s -f 
> /bkp/ports/print/ghostscript8/work/ghostscript-8.70/epag-3.09/gdevepag.c 
> /bkp/ports/print/ghostscript8/work/ghostscript-8.70/base
> /bin/mkdir -p /bkp/ports/print/ghostscript8/work/ghostscript-8.70/obj
> /bin/mkdir -p /bkp/ports/print/ghostscript8/work/ghostscript-8.70/bin
> /bin/mkdir -p 
> /bkp/ports/print/ghostscript8/work/ghostscript-8.70/freetype/include
> /bin/ln -s -f /usr/local/include/ft2build.h  
> /bkp/ports/print/ghostscript8/work/ghostscript-8.70/freetype/include/ft2build.h
> /bin/ln -s -f /usr/local/include/freetype2/freetype  
> /bkp/ports/print/ghostscript8/work/ghostscript-8.70/freetype/include/freetype
> /bin/mkdir -p 
> /bkp/ports/print/ghostscript8/work/ghostscript-8.70/freetype/objs
> /bin/ln -s -f /usr/local/lib/libfreetype.so  
> /bkp/ports/print/ghostscript8/work/ghostscript-8.70/freetype/objs/freetype214MT_D.so
> /bin/mv 
> /bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/write_t[12].[ch]  
> /bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/wrfont.[ch]  
> /bkp/ports/print/ghostscript8/work/ghostscript-8.70/psi
> mv: rename 
> /bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/write_t[12].[ch] to 
> /bkp/ports/print/ghostscript8/work/ghostscript-8.70/psi/write_t[12].[ch]: No 
> such file or directory
> mv: rename 
> /bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/wrfont.[ch] to 
> /bkp/ports/print/ghostscript8/work/ghostscript-8.70/psi/wrfont.[ch]: No such 
> file or directory
> *** Error code 1
> 
> Stop in /bkp/ports/print/ghostscript8.
> *** Error code 1
> 
> Stop in /bkp/ports/print/ghostscript8.
> 
> ===>>> make failed for print/ghostscript8
> ===>>> Aborting update
> 
> ===>>> Update for ghostscript8-8.64_7 failed
> ===>>> Aborting update
> 
> 
> As a reality check:
> 
> g1-119(6.4-S)[4] ls -lT 
> /bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/write*
> ls: No match.
> g1-119(6.4-S)[5] 
> 
> (Though I note that /bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/
> does seem to be populated with several other files.)

is this i386?

I reported this already for sparc and ia64:
http://lists.freebsd.org/pipermail/freebsd-ports/2009-December/058432.html

-- 
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-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Attempted upgrade of ghostscript8-8.64_7 -> ghostscript-8.70 failed

2009-12-20 Thread David Wolfskill
On Sun, Dec 20, 2009 at 01:27:31PM +, Anton Shterenlikht wrote:
> ...
> > (Though I note that 
> > /bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/
> > does seem to be populated with several other files.)
> 
> is this i386?

Aye

> I reported this already for sparc and ia64:
> http://lists.freebsd.org/pipermail/freebsd-ports/2009-December/058432.html

Ah, yes -- I reall you did... (sorry; I glanced at the note for ia64
and made a silly assumption -- and I know what *that* means).

> ...

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


pgpbzXQU9xFOx.pgp
Description: PGP signature


Re: status of x11-drivers/input-wacom

2009-12-20 Thread Dominic Fandrey
Frank Staals wrote:
> Hey everyone,
> 
> Does anyone know of there is someone working on updating the input-wacom
> driver ? The current port is broken on FreeBSD >= 8 and outdated. It
> would be a shame if the driver realy dies; without the absolute
> positioning the pen-tablets are not as usefull as they could be. I'm
> don't have enough experiance in C to try and fix it myself, but I will
> do what I can to help.
> 

The developer (Bartosz) told me he'd get back to work on the driver around
Christmas.

-- 
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 in e-mail? 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Attempted upgrade of ghostscript8-8.64_7 -> ghostscript-8.70 failed

2009-12-20 Thread Gary Jennejohn
On Sun, 20 Dec 2009 05:32:38 -0800
David Wolfskill  wrote:

> On Sun, Dec 20, 2009 at 01:27:31PM +, Anton Shterenlikht wrote:
> > ...
> > > (Though I note that 
> > > /bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/
> > > does seem to be populated with several other files.)
> > 
> > is this i386?
> 
> Aye
> 
> > I reported this already for sparc and ia64:
> > http://lists.freebsd.org/pipermail/freebsd-ports/2009-December/058432.html
> 
> Ah, yes -- I reall you did... (sorry; I glanced at the note for ia64
> and made a silly assumption -- and I know what *that* means).
> 
> > ...
> 

I just updated this using "make deinstall reinstall clean" on AMD64
9-CURRENT without any errors:
drwxr-xr-x  2 root  wheel  512 Dec 20 11:08 ghostscript8-8.70

---
Gary Jennejohn
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: status of x11-drivers/input-wacom

2009-12-20 Thread Frank Staals

Dominic Fandrey wrote:

Frank Staals wrote:
  

Hey everyone,

Does anyone know of there is someone working on updating the input-wacom
driver ? The current port is broken on FreeBSD >= 8 and outdated. It
would be a shame if the driver realy dies; without the absolute
positioning the pen-tablets are not as usefull as they could be. I'm
don't have enough experiance in C to try and fix it myself, but I will
do what I can to help.



The developer (Bartosz) told me he'd get back to work on the driver around
Christmas.
  

That is good news :)

--

- Frank

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


Re: Attempted upgrade of ghostscript8-8.64_7 -> ghostscript-8.70 failed

2009-12-20 Thread Rainer Hurling

On 20.12.2009 14:18 (UTC+1), David Wolfskill wrote:

This was under stable/6; it may be relevant to note that as I have 4
slices configured on my laptop's disk, each of which is bootable
(stable/6, stable/7, stable/8,&  head), /usr/ports is actually a symlink
from each of those slices to a file system that is mountable regardless
of which slice is booted.

The fetch eventually ompleted; the build started, but ended thus:

...
checking for strerror... yes
checking for strrchr... yes
checking for strspn... yes
checking for strstr... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating cups/pstopxl
config.status: creating cups/pstoraster
===>   Building for ghostscript8-8.70
/bin/ln -s -f 
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/epag-3.09/gdevepag.c 
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/base
/bin/mkdir -p /bkp/ports/print/ghostscript8/work/ghostscript-8.70/obj
/bin/mkdir -p /bkp/ports/print/ghostscript8/work/ghostscript-8.70/bin
/bin/mkdir -p 
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/freetype/include
/bin/ln -s -f /usr/local/include/ft2build.h  
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/freetype/include/ft2build.h
/bin/ln -s -f /usr/local/include/freetype2/freetype  
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/freetype/include/freetype
/bin/mkdir -p /bkp/ports/print/ghostscript8/work/ghostscript-8.70/freetype/objs
/bin/ln -s -f /usr/local/lib/libfreetype.so  
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/freetype/objs/freetype214MT_D.so
/bin/mv 
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/write_t[12].[ch]  
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/wrfont.[ch]  
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/psi
mv: rename 
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/write_t[12].[ch] to 
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/psi/write_t[12].[ch]: No 
such file or directory
mv: rename /bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/wrfont.[ch] 
to /bkp/ports/print/ghostscript8/work/ghostscript-8.70/psi/wrfont.[ch]: No such 
file or directory
*** Error code 1

Stop in /bkp/ports/print/ghostscript8.
*** Error code 1

Stop in /bkp/ports/print/ghostscript8.

===>>>  make failed for print/ghostscript8
===>>>  Aborting update

===>>>  Update for ghostscript8-8.64_7 failed
===>>>  Aborting update


For me this occurs on i386 and amd64, both 9.0-CURRENT. Commenting out 
lines 249-251 of print/ghostscript8/Makefile seems to help:


249,251c249,251
<   ${MV} ${WRKSRC}/base/write_t[12].[ch] \
<   ${WRKSRC}/base/wrfont.[ch] \
<   ${WRKSRC}/psi
---
> # ${MV} ${WRKSRC}/base/write_t[12].[ch] \
> # ${WRKSRC}/base/wrfont.[ch] \
> # ${WRKSRC}/psi

---
A second issue is with Makefile option

  [ ] FT_BRIDGEFreeType bridge

If I choose this option [X] the build breaks with following messages:

cc  -DHAVE_MKSTEMP -DHAVE_HYPOT   -DHAVE_FONTCONFIG -O2 -pipe 
-fno-strict-aliasing -fPIC -DUPD_SIGNAL=0 -I. -I/usr/ports/prin 
/ghostscript8/work/ghostscript-8.70/jasper/src/libjasper/include 
-I/usr/local/include/libpng -I/usr/local/include  -Wall -Wst 
ict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes 
-Wwrite-strings -Wno-strict-aliasing -Wdeclaration-after-s atement 
-fno-builtin -fno-common -DHAVE_STDINT_H -DGX_COLOR_INDEX_TYPE="unsigned 
long int" -O2 -pipe -fno-strict-aliasing -DU E_LIBICONV_GNU 
-DUSE_LIBPAPER -DGS_DEVS_SHARED 
-DGS_DEVS_SHARED_DIR=\"/usr/local/lib/ghostscript/8.70\" -I./psi 
-I./obj/../so bj -I./obj/../soobj -I./base   -o ./obj/../soobj/fapi_ft.o 
-c ./psi/fapi_ft.c

In file included from ./psi/fapi_ft.c:32:
/usr/local/include/ft2build.h:56:38: error: freetype/config/ftheader.h: 
No such file or directory

[..snip..]

Thanks in advance for any help,
Rainer Hurling



As a reality check:

g1-119(6.4-S)[4] ls -lT 
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/write*
ls: No match.
g1-119(6.4-S)[5]

(Though I note that /bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/
does seem to be populated with several other files.)

Peace,
david

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


[HEADS UP] Experimental 3D HW accel support for Radeon HD 2xxx, 3xxx and 4xxx, 2nd!

2009-12-20 Thread Norikatsu Shigemura
Hi everyone!

On Sat, 5 Dec 2009 10:42:43 +0900
Norikatsu Shigemura  wrote:
>   I'm ready to update ports related Mesa3D to 7.6 base, graphics/dri,
>   graphics/libGL*, graphics/libglut, graphics/mesa-demos and
>   graphics/libdrm.  Please see also my attached patch file.  I'll
>   update these as soon as tomorrow.

Reworking for 7.6.1-rc4.  Please test attached patch.

1st:
portupgrade -f libdrm  after apply this patch.

2nd:
others are portupgrade OK:-).

Changing:
libradeon no longer installed.
WRKSRC, DISTFILES, MESAVERSION are support 'rc', but all 'rc's
are same version:).
Index: dri/distinfo
===
RCS file: /home/ncvs/ports/graphics/dri/distinfo,v
retrieving revision 1.17
diff -u -r1.17 distinfo
--- dri/distinfo24 Jun 2009 01:15:07 -  1.17
+++ dri/distinfo5 Dec 2009 00:59:36 -
@@ -1,3 +1,3 @@
-MD5 (MesaLib-7.4.4.tar.bz2) = b66528d314c574dccbe0ed963cac5e93
-SHA256 (MesaLib-7.4.4.tar.bz2) = 
eaf73d7a3a2dc959ddc0753abaa18160c64bec00b35bf4a0c96040b2072918ec
-SIZE (MesaLib-7.4.4.tar.bz2) = 3375615
+MD5 (MesaLib-7.6.tar.bz2) = 8c75f90cd0303cfac9e4b6d54f6759ca
+SHA256 (MesaLib-7.6.tar.bz2) = 
782a7b2810b1c466b3a994eba96485b59b47cc1120c0caa24de1aecf1e013830
+SIZE (MesaLib-7.6.tar.bz2) = 4866983
Index: dri/pkg-plist
===
RCS file: /home/ncvs/ports/graphics/dri/pkg-plist,v
retrieving revision 1.11
diff -u -r1.11 pkg-plist
--- dri/pkg-plist   24 Jan 2009 18:13:00 -  1.11
+++ dri/pkg-plist   5 Dec 2009 00:59:36 -
@@ -7,6 +7,7 @@
 lib/dri/r128_dri.so
 lib/dri/r200_dri.so
 lib/dri/r300_dri.so
+lib/dri/r600_dri.so
 lib/dri/radeon_dri.so
 lib/dri/savage_dri.so
 lib/dri/sis_dri.so
Index: dri/files/patch-configure
===
RCS file: dri/files/patch-configure
diff -N dri/files/patch-configure
--- dri/files/patch-configure   10 Apr 2009 18:00:47 -  1.1
+++ /dev/null   1 Jan 1970 00:00:00 -
@@ -1,11 +0,0 @@
 configure.orig 2009-03-28 00:59:46.0 +
-+++ configure  2009-04-05 11:53:44.0 +
-@@ -5739,7 +5739,7 @@
- ;;
- *freebsd* | dragonfly*)
- case "$host_cpu" in
--i*86|x86_64) default_driver="dri";;
-+i*86|x86_64|powerpc*|sparc*) default_driver="dri";;
- esac
- ;;
- esac
Index: libGL/bsd.mesalib.mk
===
RCS file: /home/ncvs/ports/graphics/libGL/bsd.mesalib.mk,v
retrieving revision 1.15
diff -u -r1.15 bsd.mesalib.mk
--- libGL/bsd.mesalib.mk22 Aug 2009 00:22:54 -  1.15
+++ libGL/bsd.mesalib.mk5 Dec 2009 00:59:36 -
@@ -17,7 +17,7 @@
 # $FreeBSD: ports/graphics/libGL/bsd.mesalib.mk,v 1.15 2009/08/22 00:22:54 
amdmi3 Exp $
 #
 
-MESAVERSION=   7.4.4
+MESAVERSION=   7.6
 MASTER_SITES?= SF/mesa3d/MesaLib/${PORTVERSION}:mesa \

ftp://ftp.fu-berlin.de/pub/unix/X11/graphics/Mesa/:mesa,glut,demos
 MASTER_SITE_SUBDIR=mesa3d
@@ -32,6 +32,7 @@
 
 CONFIGURE_ENV= CPPFLAGS=-I${LOCALBASE}/include \
LDFLAGS=-L${LOCALBASE}/lib
+CONFIGURE_ARGS=--disable-gallium
 
 ALL_TARGET=default
 
Index: libGL/distinfo
===
RCS file: /home/ncvs/ports/graphics/libGL/distinfo,v
retrieving revision 1.11
diff -u -r1.11 distinfo
--- libGL/distinfo  24 Jun 2009 01:15:06 -  1.11
+++ libGL/distinfo  5 Dec 2009 00:59:36 -
@@ -1,3 +1,3 @@
-MD5 (MesaLib-7.4.4.tar.bz2) = b66528d314c574dccbe0ed963cac5e93
-SHA256 (MesaLib-7.4.4.tar.bz2) = 
eaf73d7a3a2dc959ddc0753abaa18160c64bec00b35bf4a0c96040b2072918ec
-SIZE (MesaLib-7.4.4.tar.bz2) = 3375615
+MD5 (MesaLib-7.6.tar.bz2) = 8c75f90cd0303cfac9e4b6d54f6759ca
+SHA256 (MesaLib-7.6.tar.bz2) = 
782a7b2810b1c466b3a994eba96485b59b47cc1120c0caa24de1aecf1e013830
+SIZE (MesaLib-7.6.tar.bz2) = 4866983
Index: libGL/pkg-plist
===
RCS file: /home/ncvs/ports/graphics/libGL/pkg-plist,v
retrieving revision 1.3
diff -u -r1.3 pkg-plist
--- libGL/pkg-plist 25 Jan 2009 02:00:47 -  1.3
+++ libGL/pkg-plist 5 Dec 2009 00:59:36 -
@@ -1,17 +1,18 @@
 include/GL/dmesa.h
 include/GL/ggimesa.h
-include/GL/gl_mangle.h
 include/GL/gl.h
+include/GL/gl_mangle.h
 include/GL/glext.h
 include/GL/glfbdev.h
-include/GL/glx_mangle.h
 include/GL/glx.h
+include/GL/glx_mangle.h
 include/GL/glxext.h
 include/GL/mesa_wgl.h
 include/GL/mglmesa.h
 include/GL/osmesa.h
 include/GL/svgamesa.h
 include/GL/vms_x_fix.h
+include/GL/wglext.h
 include/GL/wmesa.h
 lib/libGL.so
 lib/libGL.so.1
Index: libGL/files/patch-configure
===
RCS file: libGL/files/patch-configure
diff -N libGL/files/patch-configure
--- libGL/files/patch-configure 

Re: devel/linux-js update for FreeBSD 8.0

2009-12-20 Thread Mark Linimon
On Sun, Dec 20, 2009 at 08:25:08AM -0500, Jerry wrote:
> OK, jylef...@freebsd.org is listed in the 'pkg-descr' file, although
> apparently he no longer maintains the port. You might try contacting
> them anyway.

Jean-Yves has not been active for over 2 years now.

(This is kind of why I don't like the entries in pkg-descr; they
just become stale.)

mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Fwd: Re: FreeBSD Port: argouml-0.28.1 - .desktop file

2009-12-20 Thread Rene Ladan

Hi list,

per suggestion of the original poster, I added a desktop entry to the 
Makefile of devel/argouml.  Installing the port fails because the 
resulting pkg-plist is incorrect.  The patch seems correct according to 
the Porters Handbook ( 
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/using-x11.html#DESKTOP-ENTRIES 
), but maybe I've made a mistake.  I'm also not sure if fetching the 
icon file from a jar archive is supported, it could be added manually.


 Original Message 
Subject: Re: FreeBSD Port: argouml-0.28.1 - .desktop file
Date: Tue, 15 Dec 2009 21:40:07 +0100
From: Rene Ladan 
To: army.of.root <>

2009/12/15 army.of.root <>:

I just created a .desktop file for this Port for it to be listed in the gnome
menus. The last, commented, line shows the place where an icon can be found. -
As .jar files are actually just renamed .zip . The Icon= needs to be
filled in, and maybe the Version=[..] also.

It would be very nice if you could integrate this into the port.

Thanks in advance !

best regards


/usr/local/share/applications/argo-uml.desktop:

[Desktop Entry]
Version=0.28.1
Name=ArgoUML Editor
Comment=Create advanced UML Diagrams
Exec=/usr/local/bin/argouml
Terminal=false
Type=Application
Icon=
Categories=Application;Development;Building;Java;
StartupNotify=false
GenericName=

# /usr/local/share/argouml/argouml.jar:/org/argouml/Images/ArgoIcon32x32.png


I created the attached patch, but the install phase fails because the
desktop file is installed to the wrong location (see also the
generated PLIST file).  This is the way described in the Porters
Handbook...

Maybe someone at ports@ knows?

Regards,
René



PLIST.mktmp
Description: Binary data


argouml.diff
Description: Binary data
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Attempted upgrade of ghostscript8-8.64_7 -> ghostscript-8.70 failed

2009-12-20 Thread Hiroki Sato
David Wolfskill  wrote
  in <20091220133238.gr...@bunrab.catwhisker.org>:

da> On Sun, Dec 20, 2009 at 01:27:31PM +, Anton Shterenlikht wrote:
da> > ...
da> > > (Though I note that 
/bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/
da> > > does seem to be populated with several other files.)
da> >
da> > is this i386?
da>
da> Aye
da>
da> > I reported this already for sparc and ia64:
da> > http://lists.freebsd.org/pipermail/freebsd-ports/2009-December/058432.html
da>
da> Ah, yes -- I reall you did... (sorry; I glanced at the note for ia64
da> and made a silly assumption -- and I know what *that* means).

 Fixed just now.  This build error occurred only when WITH_FT_BRIDGE
 was enabled regardless of the platform.

-- Hiroki


pgpI8AZITeXef.pgp
Description: PGP signature


Re: devel/linux-js update for FreeBSD 8.0

2009-12-20 Thread Jerry
On Sun, 20 Dec 2009 10:14:19 -0600
Mark Linimon  articulated:

> On Sun, Dec 20, 2009 at 08:25:08AM -0500, Jerry wrote:
> > OK, jylef...@freebsd.org is listed in the 'pkg-descr' file, although
> > apparently he no longer maintains the port. You might try contacting
> > them anyway.
> 
> Jean-Yves has not been active for over 2 years now.
> 
> (This is kind of why I don't like the entries in pkg-descr; they
> just become stale.)

Yes, it would seem like it is time to do a little house cleaning.

-- 
Jerry
ges...@yahoo.com

|===
|===
|===
|===
|

Today's weirdness is tomorrow's reason why.

Hunter S. Thompson

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


Re: portmaster-with-package-support release candidate available for testing / pkg_add: illegal option -- -

2009-12-20 Thread Miroslav Lachman

Doug Barton wrote:

Miroslav Lachman wrote:

I don't know if it is well known / documented somewhere in portmaster,
but after debugging, I realized that pkg_add on FreeBSD 6.3 has no long
options


This is why all of the ports tools should be in the ports tree. :)

I just added the fix to the svn version of portmaster, if you can
confirm that it works I'll add it to the port immediately. I was not
aware of this issue, and apparently you're the first person to test
package support on a release this old. Thank you, both for the testing
and the bug report.


It is not working - pkg_add on 6.3 has no option for "Install the 
package without fetching and installing dependencies". I mean, there is 
no long nor short option for this, so this portmaster's functionality 
cannot be easily ported to 6.3. That's why I suggest to disable packages 
support on FreeBSD =< 6.3 as it cannot work this way. pkg_add will 
always install dependencies on this old version.


6.3 pkg_add options
usage: pkg_add [-vInrfRMSK]
7.2 pkg_add options
usage: pkg_add [-viInfFrRMSK]

According to man pkg_add on 6.4, there are needed options
http://www.freebsd.org/cgi/man.cgi?query=pkg_add&apropos=0&sektion=0&manpath=FreeBSD+6.4-RELEASE&format=html

But not on 6.3
http://www.freebsd.org/cgi/man.cgi?query=pkg_add&apropos=0&sektion=0&manpath=FreeBSD+6.3-RELEASE&format=html

I think you don't need to spend a lot of time to solve this for 6.3 as 
it's Estimated EoL is January 31, 2010 ;)


Maybe something like this can be enough:

if [ ! `uname -r | egrep -q "^(5|6\.[0-3])"` ]; then
echo "Packages options are not supported on your OS version"
exit
fi


And one question - is it really mandatory to use
--local-packagedir=/usr/ports/packages if I want to install locally
available packages from standard path /usr/local/packages/All?


Yes.


Shouldn't it be default behavior?


IMO, no. I think that the vast majority of FreeBSD users just want to
be able to fetch packages and have them installed.


Without --local-packagedir portmaster is trying to fetch it from FTP:
"Package and/or archive not found at:
http://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.3-release/lang/";
and doesn't look at the local directory:
"There is no valid package to install, building port instead"


This is the desired behavior.


OK, I can live with it. :) I was asking it because somebody can use NFS 
mounted /usr/ports from build machine and then all packages are located 
in /usr/local/packages/All and packages should be installed from this 
location only (not fetched from FreeBSD FTP).


Is there a simple way to disable fetching packages from remote site and 
use local packages only? (something better than fake PACKAGEROOT?)


Anyway, thank you for packages support in portmaster! Now I am waiting 
for "more general scripting hooks such as BEFOREDEINSTALL and 
AFTERINSTALL" and then portmaster will have all features I need! :o)


Miroslav Lachman
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: [HEADS UP] Experimental 3D HW accel support for Radeon HD 2xxx, 3xxx and 4xxx, 2nd!

2009-12-20 Thread Norikatsu Shigemura
On Mon, 21 Dec 2009 00:34:22 +0900
Norikatsu Shigemura  wrote:
> > I'm ready to update ports related Mesa3D to 7.6 base, graphics/dri,
> > graphics/libGL*, graphics/libglut, graphics/mesa-demos and
> > graphics/libdrm.  Please see also my attached patch file.  I'll
> > update these as soon as tomorrow.
>   Reworking for 7.6.1-rc4.  Please test attached patch.

I confirmed that 2 *my* issue was fixed:

1. bluish coloring
   Because of Depth Color = 16, so I change Depth Color to 24.
   Fix this issue.

2. Too heavy FlightGear
   I always enable LIBGL_ALWAYS_INDIRECT environment.  It's
   required by compiz.  But many OpenGL applications are not
   comfortably.  glxgears's frames bump up to 2600FPS from
   1600FPS by disable LIBGL_ALWAYS_INDIRECT.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Attempted upgrade of ghostscript8-8.64_7 -> ghostscript-8.70 failed

2009-12-20 Thread Anton Shterenlikht
On Mon, Dec 21, 2009 at 02:06:39AM +0900, Hiroki Sato wrote:
> David Wolfskill  wrote
>   in <20091220133238.gr...@bunrab.catwhisker.org>:
> 
> da> On Sun, Dec 20, 2009 at 01:27:31PM +, Anton Shterenlikht wrote:
> da> > ...
> da> > > (Though I note that 
> /bkp/ports/print/ghostscript8/work/ghostscript-8.70/base/
> da> > > does seem to be populated with several other files.)
> da> >
> da> > is this i386?
> da>
> da> Aye
> da>
> da> > I reported this already for sparc and ia64:
> da> > 
> http://lists.freebsd.org/pipermail/freebsd-ports/2009-December/058432.html
> da>
> da> Ah, yes -- I reall you did... (sorry; I glanced at the note for ia64
> da> and made a silly assumption -- and I know what *that* means).
> 
>  Fixed just now.  This build error occurred only when WITH_FT_BRIDGE
>  was enabled regardless of the platform.

many thanks!

-- 
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-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: portmaster-with-package-support release candidate available for testing / pkg_add: illegal option -- -

2009-12-20 Thread Doug Barton
Miroslav Lachman wrote:
> It is not working - pkg_add on 6.3 has no option for "Install the
> package without fetching and installing dependencies". I mean, there is
> no long nor short option for this, so this portmaster's functionality
> cannot be easily ported to 6.3. That's why I suggest to disable packages
> support on FreeBSD =< 6.3 as it cannot work this way. pkg_add will
> always install dependencies on this old version.

Well that sucks. You're right, I'll have to add a warning for this
issue. Thanks again for letting me know.

> I think you don't need to spend a lot of time to solve this for 6.3 as
> it's Estimated EoL is January 31, 2010 ;)

Yeah, if only all FreeBSD users upgraded before the version they are
using went EOL. :)

> OK, I can live with it. :) I was asking it because somebody can use NFS
> mounted /usr/ports from build machine and then all packages are located
> in /usr/local/packages/All and packages should be installed from this
> location only (not fetched from FreeBSD FTP).

I added support for --local-packagedir to accommodate just this kind
of configuration, but I still hold that it will be the exception
rather than the rule, and that portmaster should be optimized for the
majority of users.

> Is there a simple way to disable fetching packages from remote site and
> use local packages only? (something better than fake PACKAGEROOT?)

Well I have --always-fetch now, I suppose I should add --never-fetch.
That's QED.

> Anyway, thank you for packages support in portmaster! Now I am waiting
> for "more general scripting hooks such as BEFOREDEINSTALL and
> AFTERINSTALL" and then portmaster will have all features I need! :o)

So help me line up support to get that feature done. :)


Doug

-- 

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

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


Re: devel/linux-js update for FreeBSD 8.0

2009-12-20 Thread Doug Barton
Mark Linimon wrote:
> (This is kind of why I don't like the entries in pkg-descr; they
> just become stale.)

Yes, especially if the person who resets MAINTAINER does not also
update the pkg-descr. :)


Doug

-- 

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

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


freebsd-oc-en

2009-12-20 Thread ajtiM
Hi!

I did try to update port from the subject and I got:


Error: /undefinedfilename in --file--   
 
Operand stack:  
 
   (/usr/ports/misc/freebsd-doc-en/work/doc/en_US.ISO8859-1/articles/building-
products/../../../share/images/articles/building-products/freebsd-
branches.eps)   (r)   
Execution stack:
 
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --
nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --
nostringval--   false   1   %stopped_push   1862   1   3   %oparray_pop   1861  
 
1   3   %oparray_pop   1845   1   3   %oparray_pop   1739   1   3   
%oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   
--nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --
nostringval--   --nostringval-- 
   
Dictionary stack:   
 
   --dict:1155/1684(ro)(G)--   --dict:0/20(G)--   --dict:77/200(L)--   --
dict:10/25(L)-- 
Current allocation mode is local
 
Last OS error: 2
 
Current file position is 8177   
 
GPL Ghostscript 8.70: Unrecoverable error, exit code 1  
 
*** Error code 1
 
Error: /undefinedfilename in --file--   
 
Operand stack:  
 
   (/usr/ports/misc/freebsd-doc-en/work/doc/en_US.ISO8859-1/articles/building-
products/../../../share/images/articles/building-products/freebsd-
organization.eps)   (r)   
Execution stack:
 
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --
nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --
nostringval--   false   1   %stopped_push   1862   1   3   %oparray_pop   1861  
 
1   3   %oparray_pop   1845   1   3   %oparray_pop   1739   1   3   
%oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --nostringval--   
--nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --
nostringval--   --nostringval-- 
   
Dictionary stack:   
 
   --dict:1155/1684(ro)(G)--   --dict:0/20(G)--   --dict:77/200(L)--   --
dict:10/25(L)-- 
Current allocation mode is local
 
Last OS error: 2
Current file position is 8177
GPL Ghostscript 8.70: Unrecoverable error, exit code 1
*** Error code 1
2 errors
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 1

Stop in /usr/ports/misc/freebsd-doc-en.
*** Error code 1

Stop in /usr/ports/misc/freebsd-doc-en.

===>>> make failed for misc/freebsd-doc-en
===>>> Aborting update

===>>> Update for en-freebsd-doc-20091126 failed
===>>> Aborting update

Mitja

http://redbubble.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Attempted upgrade of ghostscript8-8.64_7 -> ghostscript-8.70 failed

2009-12-20 Thread Jamie Griffin
On Mon, Dec 21, 2009 at 02:06:39AM +0900, Hiroki Sato wrote:
 
>  Fixed just now.  This build error occurred only when WITH_FT_BRIDGE
>  was enabled regardless of the platform.
 
I'm still not able to build this. I've updated my ports tree which
hasn't helped. Is there anything else I can do to get it to build? 

 
Jamie


pgpSCKka0TnzA.pgp
Description: PGP signature


Re: Attempted upgrade of ghostscript8-8.64_7 -> ghostscript-8.70 failed

2009-12-20 Thread Anton Shterenlikht
On Mon, Dec 21, 2009 at 12:54:42AM +, Jamie Griffin wrote:
> On Mon, Dec 21, 2009 at 02:06:39AM +0900, Hiroki Sato wrote:
>  
> >  Fixed just now.  This build error occurred only when WITH_FT_BRIDGE
> >  was enabled regardless of the platform.
>  
> I'm still not able to build this. I've updated my ports tree which
> hasn't helped. Is there anything else I can do to get it to build? 

I just used the usual

portmaster --force-config -Bd ghost

no problems on ia64 or sparc64.

If you don't use portmaster, I'd do

cd /usr/ports/print/ghostscript8
make distclean
make rmconfig
make

-- 
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-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Attempted upgrade of ghostscript8-8.64_7 -> ghostscript-8.70 failed

2009-12-20 Thread David Wolfskill
On Mon, Dec 21, 2009 at 12:54:42AM +, Jamie Griffin wrote:
> On Mon, Dec 21, 2009 at 02:06:39AM +0900, Hiroki Sato wrote:
>  
> >  Fixed just now.  This build error occurred only when WITH_FT_BRIDGE
> >  was enabled regardless of the platform.
>  
> I'm still not able to build this. I've updated my ports tree which
> hasn't helped. Is there anything else I can do to get it to build? 

I hand-applied the patch in question; re-running portmaster after that
allowed the upgrade to succeed in my case.

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


pgpQQrthMdroP.pgp
Description: PGP signature


Re: Attempted upgrade of ghostscript8-8.64_7 -> ghostscript-8.70 failed

2009-12-20 Thread Hiroki Sato
Jamie Griffin  wrote
  in <20091221005442.ga54...@bsdbox.koderize.com>:

jg> On Mon, Dec 21, 2009 at 02:06:39AM +0900, Hiroki Sato wrote:
jg>
jg> >  Fixed just now.  This build error occurred only when WITH_FT_BRIDGE
jg> >  was enabled regardless of the platform.
jg>
jg> I'm still not able to build this. I've updated my ports tree which
jg> hasn't helped. Is there anything else I can do to get it to build?

 If you are still suffering from the build failure, please send me
 privately the error log and output of "make showconfig".

-- Hiroki


pgpupQEMBmB1h.pgp
Description: PGP signature


Re: Attempted upgrade of ghostscript8-8.64_7 -> ghostscript-8.70 failed

2009-12-20 Thread Jamie Griffin
On Mon, Dec 21, 2009 at 12:57:50AM +, Anton Shterenlikht wrote:
 
> cd /usr/ports/print/ghostscript8
> make distclean
> make rmconfig
> make
 
This did the trick. Oddly, though, I did do this about an hour ago and
it still failed but, and probably completely coincidental, I rebooted
and gave it another go and it worked. Weird. 

Anyway, thanks for the advice guys.
 
Jamie


pgpraqp43AJIy.pgp
Description: PGP signature


Re: port devel/gobject-introspection fails to build on sparc

2009-12-20 Thread Anton Shterenlikht
On Fri, Dec 18, 2009 at 01:40:58PM +, Anton Shterenlikht wrote:
> On Fri, Dec 18, 2009 at 03:17:40PM +0300, Andrew Belashov wrote:
> > Hi, Anton!
> > 
> > Anton Shterenlikht wrote:
> > > on FreeBSD 9.0-CURRENT sparc64
> > > port devel/gobject-introspection fails to build:
> > > 
> > > 
> > > Making all in gir
> > > gmake[2]: Entering directory 
> > > `/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.6.6/gir'
> > > ../tools/g-ir-compiler --includedir=.  GLib-2.0.gir -o GLib-2.0.typelib
> > > gmake[2]: *** [GLib-2.0.typelib] Illegal instruction: 4 (core dumped)
> > > gmake[2]: Leaving directory 
> > > `/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.6.6/gir'
> > > gmake[1]: *** [all-recursive] Error 1

just to say that the same error is present in 0.6.7

-- 
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-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


FreeBSD unmaintained ports which are currently marked broken

2009-12-20 Thread linimon
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:   audio/audacious-crossfade
broken because: Does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=audacious-crossfade


portname:   audio/ccaudio
broken because: Does not build with libtool 2.2.
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ccaudio


portname:   audio/py-libmpdclient
broken because: does not build
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/py26-libmpdclient-0.10.0.log
 (_Aug_23_08:38:53_UTC_2009)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=py-libmpdclient


portname:   chinese/gbk2uni
broken because: does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=gbk2uni


portname:   chinese/iiimf-le-xcin
broken because: does not build
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/zh-iiimf-le-xcin-0.1.7_5.log
 (_Aug_23_08:39:47_UTC_2009)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=iiimf-le-xcin


portname:   comms/asmodem
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=asmodem


portname:   comms/ltmdm
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=ltmdm


portname:   comms/yawmppp
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=yawmppp


portname:   devel/ace+tao
broken because: Does not compile on FreeBSD >= 7.0
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ace%2Btao


portname:   devel/adabindx
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=adabindx


portname:   devel/agide
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=agide


portname:   devel/asis
broken because: Does not build after gpl 2009 update to lang/gnat
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=asis


portname:   devel/callgrind
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=callgrind


portname:   devel/fampp
broken because: FAM system mismatch: gamin is installed, while desired
FAM system is fam
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=fampp


portname:   devel/florist
broken because: Does not build after gpl 2009 update to lang/gnat
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=florist


portname: 

FreeBSD ports which are currently marked broken

2009-12-20 Thread linimon
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:   audio/audacious-crossfade
broken because: Does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=audacious-crossfade


portname:   audio/ccaudio
broken because: Does not build with libtool 2.2.
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ccaudio


portname:   audio/dino
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=dino


portname:   audio/ecamegapedal
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ecamegapedal


portname:   audio/ecawave
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ecawave


portname:   audio/emu10kx
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=emu10kx


portname:   audio/gmpc-mserver
broken because: fails to build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gmpc-mserver


portname:   audio/py-libmpdclient
broken because: does not build
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/py26-libmpdclient-0.10.0.log
 (_Aug_23_08:38:53_UTC_2009)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=py-libmpdclient


portname:   biology/dotter
broken because: checksum mismatch
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20091209110328/dotter-20021204.log.bz2
 (_Nov_19_12:11:51_UTC_2009)
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/dotter-20021204.log
 (_Aug_17_05:33:45_UTC_2009)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=biology&portname=dotter


portname:   cad/alliance
broken because: incomplete plist
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20091207233526/alliance-5.0.20090901_1.log.bz2
 (_Dec__9_09:38:12_UTC_2009)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=alliance


portname:   chinese/gbk2uni
broken because: does not fetch
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=gbk2uni


portname:   chinese/iiimf-le-xcin
broken because: does not build
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/zh-iiimf-le-xcin-0.1.7_5.log
 (_Aug_23_08:39:47_UTC_2009)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=iiimf-le-xcin


portname:   comms/asmodem
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=asmodem


portname:   comms/hcfmdm
broken because: Does not compile at 7.x or higher
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portover

FreeBSD unmaintained ports which are currently scheduled for deletion

2009-12-20 Thread linimon
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 the existing port.  In some cases,
ports are marked for removal because they fail to build and install
correctly from their sources, or otherwise fail in operation.

The ports, and the reason and date that they have been scheduled
for removal, are listed below.  If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports will be deleted.



portname:   audio/ccaudio
description:C++ class framework for manipulating audio files
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 4 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ccaudio


portname:   audio/py-libmpdclient
description:Python bindings for libmpdclient
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 3 months
expiration date:2010-01-08
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/py26-libmpdclient-0.10.0.log
 (_Aug_23_08:38:53_UTC_2009)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=py-libmpdclient


portname:   chinese/gbk2uni
description:TeX applet used to generate correct Chinese PDF
bookmarks
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 6 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=gbk2uni


portname:   chinese/iiimf-le-xcin
description:IIIMF xcin language engine, a traditional Chinese
input method
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 3 months
expiration date:2010-01-08
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/zh-iiimf-le-xcin-0.1.7_5.log
 (_Aug_23_08:39:47_UTC_2009)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=iiimf-le-xcin


portname:   devel/adabindx
description:An Ada-binding to the X Window System and *tif
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 3 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=adabindx


portname:   devel/agide
description:A-A-P GUI IDE: a framework for software development
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 6 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=agide


portname:   devel/asis
description:GNAT implementation of the Ada Semantic Interface
Specification
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 3 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=asis


portname:   devel/callgrind
description:Valgrind skin for cache simulation and call tracing
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: Included in devel/valgrind
expiration date:2009-10-30
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=callgrind


portname:   devel/florist
description:FSU implementation of POSIX.5, the POSIX Ada binding
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 3 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=florist


portname:   editors/xml2rfc-xxe
description:An xml2rfc configuration for XMLMind XML Editor
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 4 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=editors&portname=xml2rfc-xxe


portname:   graphics/gephex
description:Software-based interactive video-effect system
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken fo

FreeBSD ports which are currently scheduled for deletion

2009-12-20 Thread linimon
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 the existing port.  In some cases,
ports are marked for removal because they fail to build and install
correctly from their sources, or otherwise fail in operation.

The ports, and the reason and date that they have been scheduled
for removal, are listed below.  If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports will be deleted.



portname:   audio/ccaudio
description:C++ class framework for manipulating audio files
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 4 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ccaudio


portname:   audio/dino
description:A pattern-based MIDI sequencer
maintainer: tr...@freebsd.org
status: BROKEN
deprecated because: has been broken for 7 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=dino


portname:   audio/py-libmpdclient
description:Python bindings for libmpdclient
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 3 months
expiration date:2010-01-08
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/py26-libmpdclient-0.10.0.log
 (_Aug_23_08:38:53_UTC_2009)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=py-libmpdclient


portname:   chinese/gbk2uni
description:TeX applet used to generate correct Chinese PDF
bookmarks
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 6 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=gbk2uni


portname:   chinese/iiimf-le-xcin
description:IIIMF xcin language engine, a traditional Chinese
input method
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 3 months
expiration date:2010-01-08
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/zh-iiimf-le-xcin-0.1.7_5.log
 (_Aug_23_08:39:47_UTC_2009)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=iiimf-le-xcin


portname:   devel/adabindx
description:An Ada-binding to the X Window System and *tif
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 3 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=adabindx


portname:   devel/agide
description:A-A-P GUI IDE: a framework for software development
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 6 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=agide


portname:   devel/asis
description:GNAT implementation of the Ada Semantic Interface
Specification
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 3 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=asis


portname:   devel/asis-gpl
description:An Ada ASIS implementation including the Data
Decomposition Annex
maintainer: john_m_coo...@yahoo.com
status: BROKEN
deprecated because: has been broken for 3 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=asis-gpl


portname:   devel/aunit
description:AUnit is an adaption of the Java JUnit unit test
framework
maintainer: john_m_coo...@yahoo.com
status: BROKEN
deprecated because: has been broken for 3 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=aunit


portname:   devel/callgrind
description:Valgrind skin for cache simulation and call tracing
maintainer: po...@freebsd.org
status: BROKEN

FreeBSD unmaintained ports which are currently marked forbidden

2009-12-20 Thread linimon
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, including errors seen on the build farm,
is included below.

portname:   misc/compat3x
forbidden because:  FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath  - not
fixed / no lib available
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


FreeBSD ports which are currently marked forbidden

2009-12-20 Thread linimon
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, including errors seen on the build farm,
is included below.

portname:   databases/gnats
forbidden because:  Security issues
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats


portname:   misc/compat3x
forbidden because:  FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath  - not
fixed / no lib available
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x


portname:   www/firefox
forbidden because:  too many security issues 

http://www.vuxml.org/freebsd/922d2398-9e2d-11de-a998-0030843d3802.html


http://www.vuxml.org/freebsd/49e8f2ee-8147-11de-a994-0030843d3802.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=firefox
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"