Re: print/cups-base 1.2.0_2 and locally connected printer

2006-07-01 Thread David MAREC
Le lundi 26 juin 2006 04:18, Rick Voland a écrit :

> It seems to be a permissions thing.

I have the same problem running FreeBSD 6.1.
A few weeks ago, «cups» stopped printing through local ports while  «lpd» 
dæmon was still working.
( maybe, as soon as i removed cups-lpr from the system )

> Now, I can print to the parallel port.  I didn't have to do this with
> print/cups-base 1.1.23.0_9.

Setting «rw» permissions to group and others to that device allows «cupsd » 
to work through local ports.
Setting «rw» permissions to group only, does'nt.

Is there new device policies defined by cups ?

-- 
David Marec www.diablotins.org
http://david.marec.free.fr  www.fr.freebsd.org/fr
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


[SDL-1.2.14] Build fails on the libvlg checking

2010-01-31 Thread David Marec
Hello,


Trying to update SDL1.2 librairies, the build failed on the following errors:


/usr/bin/ld: skipping incompatible /usr/lib/libvgl.so when searching for -lvgl
/usr/bin/ld: skipping incompatible /usr/lib/libvgl.a when searching for -lvgl
/usr/bin/ld: skipping incompatible /usr/lib/libvgl.so when searching for -lvgl
/usr/bin/ld: skipping incompatible /usr/lib/libvgl.a when searching for -lvgl
/usr/bin/ld: skipping incompatible /usr/lib/libvgl.so when searching for -lvgl
/usr/bin/ld: skipping incompatible /usr/lib/libvgl.a when searching for -lvgl
/usr/bin/ld: cannot find -lvgl

Running:
david:~>uname  -p -r
8.0-STABLE amd64


Any idea to get rid of this ?



-- 
david Marec: http://www.diablotins.org
___
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: [SDL-1.2.14] Build fails on the libvlg checking

2010-01-31 Thread David Marec
Le dimanche 31 janvier 2010 14:27:19, Marcus von Appen a écrit :

> /usr/lib/libvgl.* should not be available on RELENG_8, amd64 - instead
> it should reside in /usr/lib32 only. Did you upgrade from i386 to amd64
> or did you manually link the libvgl.* to /usr/lib?

Neither of them.

The system is amd64 from the begining.


> If so, please remove them or run make config and disable the VGL knob
> (or add 'WITHOUT_VGL=true' to the make invocation).

That s what i did.
But, if, for example, svgalib is tagged "i386 only", svgl is not.

btw, should i remove these libs ?


___
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: [SDL-1.2.14] Build fails on the libvlg checking

2010-01-31 Thread David Marec

Le dimanche 31 janvier 2010 17:40:22, Marcus von Appen a écrit :

> > > If so, please remove them or run make config and disable the VGL knob
> > > (or add 'WITHOUT_VGL=true' to the make invocation).
> >
> > That s what i did.
> 
> And it still does not work for you?

Sorry, i missed to precise that the build was successful with VGL disabled.

> > But, if, for example, svgalib is tagged "i386 only", svgl is not.
> 
> If I manually link libvgl.* from /usr/lib32 to /usr/lib and rebuild SDL
> with VGL enabled, anything links properly. I am not sure, what's wrong
> on your side. 

I don't actually know why  libvgl* are located in /usr/lib instead of 
/usr/lib32, on my side.

> > btw, should i remove these libs ?

I mean, move them to the right place.

> 
> I do not recommend to do that manually. Which shared library versions of
> libvgl are installed (output of find /usr/lib -name "*vgl*") on your
> side?

david:~>find /usr/lib -name "*vgl*"
/usr/lib/libvgl.a
/usr/lib/libvgl.so
/usr/lib/libvgl_p.a

> Did you ever run make delete-old or make delete-old-libs after updating
> the system?

I have just ran these libs deletion tools and the VGL option has disapeared 
from the SDL12 knob.



btw, i don't really need libvgl  at this time.

Thanks.

___
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"


[Libmpdclient] upate failed on doxygen call

2010-01-31 Thread David Marec
Hi,


I tryied to update libmpdclient-2.1 and the build failed on the following 
errors:

/usr/local/bin/doxygen 
Doxyfile not found and no input file specified!
Doxygen version 1.6.2
Copyright Dimitri van Heesch 1997-2008


Any clue to solve this issue ?


Regards,
-- 
David Marec
http://www.diablotins.org
___
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: [Libmpdclient] upate failed on doxygen call

2010-02-01 Thread David Marec

HI,

Le 01/02/2010 18:17, Martin Wilke a écrit :

I tryied to update libmpdclient-2.1 and the build failed on the
following errors:

/usr/local/bin/doxygen
Doxyfile not found and no input file specified!
Doxygen version 1.6.2
Copyright Dimitri van Heesch 1997-2008


add USE_GMAKE=yes to your makefile
this should be save


Thanks for the tip.
The update has completed successfully.


Regards,
--
David Marec http://user.lamaiziere.net/david/Site
FreeBSD: http://www.freebsd.org/fr/ http://www.diablotins.org/
___
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"


DosBox upgrade failed.

2010-05-30 Thread David Marec
Hi all, 


I got the following issue, upgrading Dosbox to the 0.74 release:

===
Making all in core_dynrec
g++44 -DHAVE_CONFIG_H -I. -I../..   -I../../include -I/usr/local/include -
I/usr/local/include/SDL -I/usr/local/include -D_GNU_SOURCE=1 -D_REENTRANT  -O2 
-pipe -march=native -fno-strict-aliasing -MT callback.o -MD -MP -MF 
.deps/callback.Tpo -c -o callback.o callback.cpp
mv -f .deps/callback.Tpo .deps/callback.Po
g++44 -DHAVE_CONFIG_H -I. -I../..   -I../../include -I/usr/local/include -
I/usr/local/include/SDL -I/usr/local/include -D_GNU_SOURCE=1 -D_REENTRANT  -O2 
-pipe -march=native -fno-strict-aliasing -MT cpu.o -MD -MP -MF .deps/cpu.Tpo -
c -o cpu.o cpu.cpp
In file included from cpu.cpp:29:
../../include/setup.h:247: error: 'FILE' has not been declared
../../include/setup.h:280: error: 'FILE' has not been declared
../../include/setup.h:315: error: 'FILE' has not been declared
*** Error code 1

Stop in /usr/ports/emulators/dosbox/work/dosbox-0.74/src/cpu.
*** Error code 1

Stop in /usr/ports/emulators/dosbox/work/dosbox-0.74/src/cpu.
*** Error code 1

Stop in /usr/ports/emulators/dosbox/work/dosbox-0.74/src.
*** Error code 1

Stop in /usr/ports/emulators/dosbox/work/dosbox-0.74.
*** Error code 1

Stop in /usr/ports/emulators/dosbox/work/dosbox-0.74.
*** Error code 1

Stop in /usr/ports/emulators/dosbox.

===>>> make failed for emulators/dosbox
===>>> Aborting update

===>>> Update for dosbox-0.73_1 failed
===>>> Aborting update
===

Any idea to solve this ?
___
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: DosBox upgrade failed.

2010-05-30 Thread David Marec
Le dimanche 30 mai 2010 12:21:13, Alex Kozlov a écrit :
> On Sun, May 30, 2010 at 10:58:42AM +0200, David Marec wrote:
> > I got the following issue, upgrading Dosbox to the 0.74 release:
> > 
> > ===
> > Making all in core_dynrec
> > g++44 -DHAVE_CONFIG_H -I. -I../..   -I../../include -I/usr/local/include
> > - I/usr/local/include/SDL -I/usr/local/include -D_GNU_SOURCE=1
> > -D_REENTRANT  -O2 -pipe -march=native -fno-strict-aliasing -MT
> > callback.o -MD -MP -MF .deps/callback.Tpo -c -o callback.o callback.cpp
> > mv -f .deps/callback.Tpo .deps/callback.Po
> > g++44 -DHAVE_CONFIG_H -I. -I../..   -I../../include -I/usr/local/include
> > - I/usr/local/include/SDL -I/usr/local/include -D_GNU_SOURCE=1
> > -D_REENTRANT  -O2 -pipe -march=native -fno-strict-aliasing -MT cpu.o -MD
> > -MP -MF .deps/cpu.Tpo - c -o cpu.o cpu.cpp
> > In file included from cpu.cpp:29:
> > ../../include/setup.h:247: error: 'FILE' has not been declared
> > ../../include/setup.h:280: error: 'FILE' has not been declared
> > ../../include/setup.h:315: error: 'FILE' has not been declared
> > *** Error code 1
> > Any idea to solve this ?
> 
> Try to add 'include ', if it's not help, use base gcc (4.2.1)
> instead of lang/gcc44.

My bad. I did not pay attention that gcc4 was installed buy another port.

As Gcc4 knobs were still activated in /etc/make.conf:
- .if exists(/usr/local/bin/gcc44) -
Gcc4 was the the default compiler.

disabling it did the trick.

Thanks.


___
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"


GCC44 upgrade fails

2010-10-30 Thread David Marec
Hello,


On my FreeBSD8-Stable box,
the last GCC44.6 attempt to update fails on the following errors:
<<
libtool: compile:  /usr/ports/lang/gcc44/work/build/./gcc/gfortran - 
B/usr/ports/lang/gcc44/work/build/./gcc/ -B/usr/local/x86_64-portbld-
freebsd8.1/bin/ -B/usr/local/x86_64-portbld-freebsd8.1/lib/ -isystem 
/usr/local/x86_64-portbld-freebsd8.1/include -isystem /usr/local/x86_64-
portbld-freebsd8.1/sys-include -DHAVE_CONFIG_H -I. -
I../.././../gcc-4.4-20101026/libgfortran -I. -
iquote../.././../gcc-4.4-20101026/libgfortran/io -
I../.././../gcc-4.4-20101026/libgfortran/../gcc -
I../.././../gcc-4.4-20101026/libgfortran/../gcc/config -I../.././gcc -
D_GNU_SOURCE -I . -Wall -Werror -fimplicit-none -fno-repack-arrays -fno-
underscoring -fallow-leading-underscore -g -c 
../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90  -o 
.libs/_abs_c4.o
../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1:

\xD4\x8A\x01\x08\x04\x1E\xD7\xD9\x8A\x01\x08\x05\xA7\xEE\x7F\xF2
 1
Error: Invalid character in name at (1)
../.././../gcc-4.4-20101026/libgfortran/generated/_abs_c4.F90:1.1:

[...] 

gmake[3]: quittant le répertoire « /usr/ports/lang/gcc44/work/build/x86_64-
portbld-freebsd8.1/libgfortran »
gmake[2]: *** [all] Erreur 2
gmake[2]: quittant le répertoire « /usr/ports/lang/gcc44/work/build/x86_64-
portbld-freebsd8.1/libgfortran »
gmake[1]: *** [all-target-libgfortran] Erreur 2
gmake[1]: quittant le répertoire « /usr/ports/lang/gcc44/work/build »
gmake: *** [bootstrap-lean] Erreur 2
>>

Any idea is welcome...

___
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"


[9.0 RC1] Unable to build Image Magik and glib-20

2011-11-11 Thread David Marec

hi mates,

I get build-failures  while i try to update the following ports, with 
the help of portmaster:


* devel/glib20

config.status: executing glib/glibconfig.h commands
config.status: executing chmod-scripts commands
===>  Building for glib-2.28.8_2
make  all-recursive
make: illegal option -- -
usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
[-d flags] [-E variable] [-f makefile] [-I directory]
[-j max_jobs] [-m directory] [-V variable]
[variable=value] [target ...]
gmake: *** [all] Erreur 2
*** Error code 1

Stop in /usr/ports/devel/glib20.
*** Error code 1

Stop in /usr/ports/devel/glib20.

===>>> make failed for devel/glib20
===>>> Aborting update
---

*graphics/ImageMagik

===>  Building for ImageMagick-6.7.3.4
/bin/sh ./config/mkinstalldirs . ltdl/
cp ./ltdl/argz_.h ltdl/argz.h-t
mv ltdl/argz.h-t ltdl/argz.h
make  all-am
make: illegal option -- -
usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
[-d flags] [-E variable] [-f makefile] [-I directory]
[-j max_jobs] [-m directory] [-V variable]
[variable=value] [target ...]
gmake: *** [all] Erreur 2
*** Error code 1

Stop in /usr/ports/graphics/ImageMagick.
*** Error code 1

Stop in /usr/ports/graphics/ImageMagick.

===>>> make failed for graphics/ImageMagick
===>>> Aborting update

===>>> Update for graphics/ImageMagick failed
===>>> Aborting update





'Sounds like there is something missing or outdated in ports/Mk ?


Thanks in advance.

--
David Marec, mailto:david.ma...@davenulle.org
http://user.lamaiziere.net/david/Site
http://www.diablotins.org/
___
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: Recent ports removal

2011-11-11 Thread David Marec

Le 11.11.2011 11:07, Dmitry Marakasov a écrit :


Why don't we take out Gnome and KDE then? I don't use it.


Cause,  there is  still guys that are ready to maintain them, and, 
futhermore, some stuff in the ports tree that depend on them ?



--
David Marec, mailto:david.ma...@davenulle.org
http://user.lamaiziere.net/david/Site
http://www.diablotins.org/
___
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"


[9 RC][AMD64] ImageMagick failed to pass 'exceptions' self-test

2011-12-10 Thread David Marec

mates,

After the build, the ImageMagick  port does not pass the 'exceptions' test:


>
=
   ImageMagick 6.7.3: ./test-suite.log
=

1 of 48 tests failed.

.. contents:: :depth: 2


FAIL: Magick++/tests/exceptions.sh (exit: 139)
==

Segmentation fault (core dumped)
<---


A logfile and a 'warnings' file have been uploaded there:
http://user.lamaiziere.net/david/bsd/ImageMagick.log
http://user.lamaiziere.net/david/bsd/ImageMagick.warnings


I also tried to use CLANG with the same result.

I didn't find more explanations and/or log files regarding this issue.



--
David Marec, mailto:david.ma...@davenulle.org
http://user.lamaiziere.net/david/Site
http://www.diablotins.org/
___
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"


Assault_cube, do not run

2011-04-09 Thread David Marec

Hi guys,


I tried to run the new release of "games/assaultcube", but the game fails
to start on the following error:

<->
david:/<1>ports/games/assaultcube>assaultcube_client &
[1] 8336
david:/<1>ports/games/assaultcube>Using existing ~/.assaultcube directory.
Using home directory: ~/.assaultcube
current locale: fr_FR.ISO8859-15
init: sdl
init: net
init: world
init: video: sdl
init: video: mode
init: video: misc
init: gl
Renderer: GeForce 6150SE nForce 430/PCI/SSE2 (NVIDIA Corporation)
Driver: 2.1.2 NVIDIA 270.18
init: console
cannot find default font definitions ()

[1]Sortie 1assaultcube_client
<-->

What does "default font definitions" means ?

-- 
Cordialement,
-- 
David Marec: http://user.lamaiziere.net/david/Site/
http://www.freebsd.org/fr/ http://www.diablotins.org/



___
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"


[linux-nx-client] session failed.

2007-11-01 Thread David Marec
hello,

i am trying to take the control of an ubuntu box on an nxserveur, using 
linux-nx-client running on FreeBSD 6.3
( http://www.nomachine.org )

But each attempt fails with the message:
 
»x
NXPROXY - Version 2.1.0

Copyright (C) 2001, 2006 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Proxy running in client mode with pid '1373'.
Session: Starting session at 'Thu Nov  1 09:26:30 2007'.
Info: Connecting to remote host '192.168.0.2:5008'.
Info: Connection to remote proxy '192.168.0.2:5008' established.
Warning: Connected to remote NXPROXY version 3.0.0 with local version 2.1.0.
Warning: Consider checking http://www.nomachine.com/ for updates.
Info: Synchronizing local and remote caches.
Info: Handshaking with remote proxy completed.
Info: Using LAN link parameters 1536/24/1/0.
Info: Using image streaming parameters 50/128/1024KB/6144/768.
Info: Using image cache parameters 1/1/32768KB.
Info: Using pack method '16m-jpeg-9' with session 'unix-gnome'.
Info: Using product 'LFE/None/LFEN/None'.
Info: Not using NX delta compression.
Info: Not using ZLIB data compression.
Info: Not using ZLIB stream compression.
Info: Not using persistent cache.
Info: Using remote server '192.168.0.2:5008'.
Info: Listening for font server connections on port '11008'.
Session: Session started at 'Thu Nov  1 09:26:31 2007'.
Error: Failed to set TCP_NODELAY flag on FD#14 to 1. Error is 22 'Invalid 
argument'.
Info: Established X server connection.
Session: Terminating session at 'Thu Nov  1 09:26:31 2007'.
Info: End of NX transport requested by signal '15'.
»x

Any idea ?

Regards
-- 
David Marec www.diablotins.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD Port: nvidia-driver-169.12

2008-03-07 Thread David Marec
Laurent,

> I think I've found the problem :)
>
> In "/usr/local/lib/xorg/modules/extensions", there was "libglx.so" and "
> libglx.so.1". I rename the "libglx.so" in "libglx.so.old" and
> "libglx.so.1"
> in "libglx.so".


Beware of Xorg updates; While updating, Xorg overwrites these modules.

You have to rebuild nvidia driver following any Xorg updates.

-- 
Les pixels au peuple.

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


Upgrade fails with enlightenment

2008-03-16 Thread David Marec
FreeBSD-istes,

following the 20080312 notice of /usr/ports/UPDATNG

i removed the enlightenment core and others e-stuff from my FB7 box.

But, re-building e17 fails on the following step:

[quote]--
Package openssl was not found in the pkg-config search path.
Perhaps you should add the directory containing `openssl.pc'
to the PKG_CONFIG_PATH environment variable
Package 'openssl', required by 'ecore-con', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables E_CFLAGS
and E_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

===>  Script "configure" failed unexpectedly.

[/quote]--

Do i need to install openSSL from the port tree, while it is available from 
the freebSD world ?


-- 
http://www.diablotins.org/
http://www.arcadehits.net/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


QT4 upgrade fails

2008-03-16 Thread David Marec
FreeBsd-istes,


I tried to upgrade ports on my FB7 box, but, 
QT4 fails to build on the following error:

-[Quote]
widgets/qcombobox.cpp: In member function 'virtual void 
QComboBoxPrivateContainer::resizeEvent(QResizeEvent*)':
widgets/qcombobox.cpp:351: error: 'SH_Menu_Mask' is not a member of 'QStyle'
*** Error code 1

Stop 
in /usr/ports/x11-toolkits/qt4-gui/work/qt-x11-opensource-src-4.3.4/src/gui.
*** Error code 1

Stop in /usr/ports/x11-toolkits/qt4-gui.
*** Error code 1
<---[quote]


any idea to solve this issue ?

-- 
http://www.diablotins.org/
http://www.arcadehits.net/

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


Re: QT4 upgrade fails

2008-03-17 Thread David Marec
Le Sunday 16 March 2008 22:33:47 Alex Dupre, vous avez écrit :
> David Marec wrote:
> > any idea to solve this issue ?
>
> Try disabling CUPS support in qt4-gui.


Thanks, this port is up to date, now.

-- 
http://www.diablotins.org/
http://www.arcadehits.net/


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


Re: Upgrade fails with enlightenment

2008-03-17 Thread David Marec
Le Monday 17 March 2008 00:07:35 Stanislav Sedov, vous avez écrit :

>>following the 20080312 notice of /usr/ports/UPDATNG
>> 
>> i removed the enlightenment core and others e-stuff from my FB7 box.
>> 
>> But, re-building e17 fails on the following step:
>>[...]
> Which e17 port report this? You're not required to install openssl port,
> e17 uses the base one.



E17 itself:

[quote]>
===>  Configuring for enlightenment-0.16.999.042,2
checking build system type... i386-portbld-freebsd7.0
checking host system type... i386-portbld-freebsd7.0
checking for gcc... cc
checking for C compiler default output file name... a.out
[Snip]
checking pkg-config is at least version 0.9.0... yes
checking for E... gnome-config: not found
configure: error: Package requirements (
  evas
  ecore
  ecore-evas
  ecore-file
  ecore-ipc
  ecore-con
  ecore-job
  ecore-imf
  ecore-imf-evas
  edje
  eet
  embryo
  efreet
  efreet-mime
) were not met:

Package openssl was not found in the pkg-config search path.
<-[quote]---


May be one of the dependencies above requires the port-based OpenSSL, switched 
on by a configure  option ?

I will check out the dependencies about this.

-- 
http://www.diablotins.org/
http://www.arcadehits.net/

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


Re: Upgrade fails with enlightenment

2008-03-17 Thread David Marec
Le Monday 17 March 2008 22:08:52 David Marec, vous avez écrit :
> configure: error: Package requirements (
>   evas
>   ecore
>   ecore-evas
>   ecore-file
>   ecore-ipc
>   ecore-con
>   ecore-job
>   ecore-imf
>   ecore-imf-evas
>   edje
>   eet
>   embryo
>   efreet
>   efreet-mime
> ) were not met:
>
> Package openssl was not found in the pkg-config search path.
> <-[quote]---
>
>
> May be one of the dependencies above requires the port-based OpenSSL,
> switched on by a configure  option ?
>
> I will check out the dependencies about this.


-[quote]--->
===>   Registering installation for enlightenment-0.16.999.042,2
===>  Cleaning for ecore-ipc-0.9.9.042_1
===>  Cleaning for ecore-con-0.9.9.042_1
===>  Cleaning for enlightenment-0.16.999.042,2
<-[quote]---

I had to disable OpenSSL for the two e-core ports above to build E17.



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


Battle for wesnoth

2018-07-03 Thread David Marec

Hello,


Some days ago, the port games/wesnoth was removed from my poudriere 
builds, because of boost libraries mismatches I guess.


So that, I decided to port a newer version of the game (1.14.%) to 
FreeBSD. If the port "works for me", it 'be better to provide a 
port-tree compliant installation.


If I'm running FreeBSD for years, it's the first time I am writing a 
Makefile for the port tree.


Thanks to the porters-handbook, (and the original wesnoth Makefile)
I was able to write a Makefile and provides a couple of patches.
One can find the files below:
https://gitlab.com/TurtleCrazy/wesnoth_1_14_freebsd

Now, as a beginner, I have some questions regarding the Makefile to be 
included in the port tree.


First, the CMake file provides one option to disable the installation of 
the game itself.
This might be use to run game servers only. It also avoid the 
installation of SDL2 libs.
This option was not defined on the previous port, so I wonder if there 
is a need for it.



It could be done by adding  the following lines:

GAME_DESC=The game client
GAME_CMAKE_OFF=-DENABLE_GAME=off
GAME_USE_SDL= image2 mixer2 net2 ttf2 sdl2



Second, the pkg-plist is missing. - what makes poudriere testport to 
fail. -


I did not find suitable information in the handbook that explains
how to fill it. Any clue may be helpful.


Next, some sets of options requires additional boost libraries.
as
* unit_test_framework
* iostreams program_options regex system thread random

The Makefile need some reworks to allow fine-grained  dependencies


Finally, what about the entry name in the port tree ?



Feel free to correct the code, moreover: be "-pedantic".

regards,

--
David Marec
https://lapinbilly.eu/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: sqlite3 update to 3.31.0 breaks firefox and thunderbird

2020-01-27 Thread David Marec

Le 27/01/2020 à 06:06, Tobias C. Berner a écrit :


This should likely be added to firefox:
https://hg.mozilla.org/try/rev/8d7104bac33729b4da67954b07fb08371df39bd8




Finally, it sounds that the sqlite team will do review their API to 
ensure backward compatibility.


https://www.sqlite.org/src/info/34ab760689fd493e

:
>> It turns out that some important 3rd-party software does 
questionable >> pointer manipulations on those filenames that depend on 
that legacy >> layout. Technically, this is a misuse of SQLite by the 
3rd-party

>> software, but we want to avoid unnecessary breakage

Thanks, even if I think they are in a way being too soft in this case.


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


Re: xorg upgrade issue

2009-04-08 Thread David Marec
Le Wednesday 08 April 2009 19:20:28 Robert Noland, vous avez écrit :

> balrog% setxkbmap de
> Couldn't interpret _XKB_RULES_NAMES property
> Use defaults: rules - 'xorg' model - 'pc105' layout - 'us'
> balrog% setxkbmap us
> balrog% setxkbmap de
> balrog% setxkbmap us
> balrog% setxkbmap de
> Try setting to us then de.  Not sure why that seemed to work, but the

david:~$ setxkbmap us
Couldn't interpret _XKB_RULES_NAMES property
Use defaults: rules - 'xorg' model - 'pc105' layout - 'us'
Error loading new keyboard description
david:~$ setxkbmap fr
Couldn't interpret _XKB_RULES_NAMES property
Use defaults: rules - 'xorg' model - 'pc105' layout - 'us'
Error loading new keyboard description
david:~$ setxkbmap us
Couldn't interpret _XKB_RULES_NAMES property
Use defaults: rules - 'xorg' model - 'pc105' layout - 'us'
Error loading new keyboard description
david:~$ setxkbmap fr
Couldn't interpret _XKB_RULES_NAMES property
Use defaults: rules - 'xorg' model - 'pc105' layout - 'us'
Error loading new keyboard description

> error went away for me...  

No change here.

> and my keys do strange things when set to 
> 'de'. ;)

Strange behavior here too, using the default set.

-- 
http://david.marec.free.fr/
http://www.freebsd.org/fr/  http://www.diablotins.org/
___
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: xorg upgrade issue

2009-04-08 Thread David Marec
Le Wednesday 08 April 2009 23:00:46 Dominic Fandrey, vous avez écrit :

> The same here, the error prevails.

The last upgrade of xkeyboard-config solve the issue.


-- 
http://david.marec.free.fr/
http://www.freebsd.org/fr/  http://www.diablotins.org/
___
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"


Xorg failed to run on old PC.

2007-06-27 Thread David Marec
hi


I am trying to configure an old "cirix166-48Mo RAM" workstation.

But, FreeBSD 6.2 installed, Xorg crashes on 
« Caught signal 11»

I tried three drivers, mga, vesa and vga.
The driver "mga" failed to load DRI module, which was not requested.

The log file, created with no "xorg.conf", can be uploaded here:
http://david.marec.free.fr/public/Xorg.0.log

It seems that i had the same problem when i tried to launch XUbuntu on it.
The only linux distribution that works is Damn Small Linux.

Any idea ?
Using the latest xorg 7 release ? 
Getting back to FreeBSD 4.x to try Xfree instead of xorg ?

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


Re: Xorg failed to run on old PC.

2007-06-29 Thread David Marec
Le Thursday 28 June 2007 13:35:57 Nikola Lecic, vous avez écrit :


> * You must create a config file; you can start with 'Xorg -configure',
>   it will create an initial /root/xorg.conf.new; then you can test it
>   with 'X -config /root/xorg.conf.new'. I think you need something like:
>
>   in Section "Monitor"
> HorizSync   31.5 - 48.5  # try also: 31.5 - 57.0
> VertRefresh 50 - 70  # try also: 50 - 75
>
>   in Section "Screen"
> DefaultColorDepth 16 # start with the lower value
> SubSection "Display"
> Depth 16
> Modes "1024x768" "800x600" "640x480"
> EndSubSection
> # delete here all subsections with higher colour depth and modes.

The problem is the same.
i published the new log file 
http://david.marec.free.fr/public/Xorg.0.log
and the http://david.marec.free.fr/public/xorg.conf.new


> * (If you need a really good assistance in creating xorg.conf, use
>   Knoppix; Greg Lehey once recommended it on freebsd-questions@; this
>   one is really different.)

--> kernel panic.


Thanks for your help



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


Re: Xorg failed to run on old PC.

2007-06-29 Thread David Marec
Le Saturday 30 June 2007 03:46:59 Nikola Lecic, vous avez écrit :

> Well, all I can
> say is that you should try to upgrade to Xorg-7.2 (it is even faster
> on older hardware -- and all those "exceeds DDC maximum 0MHz" shouldn't
> be in your log AFAIK) or to somehow check your memory, as Norberto has
> already suggested (that's why I cc him).

I had already checked RAM and memtest did not found any error.

> (And maybe that I once experienced that the mouse had caused similarly
> weird situation, so you can try to disconnect it or to add Option
> "AllowMouseOpenFail" "true" in ServerFlags section.)

Maybe, it's a serial mouse.

> Btw, have you used this machine before -- you know that hardware is ok?

Yes. W98 was shipped on it and it was running correctly;  DSL is running well, 
with the XVESA driver.

I have tried to run with another Matrox Mystic card, for the same result.

Thanks.

-- 

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


Owncloud upgrade failure

2017-05-30 Thread David Marec

Hi,

After updating owncloud from the early 10.0.1 package, the upgrading 
process failed on the following:


root:/<1>local/www/owncloud#sudo -u www php occ upgrade
The process control (PCNTL) extensions are required in case you want to 
interrupt long running commands - see 
http://php.net/manual/en/book.pcntl.php
ownCloud or one of the apps require upgrade - only a limited number of 
commands are available

You may use your browser or the occ upgrade command to do the upgrade
Set log level to debug
Updating database schema
Doctrine\DBAL\Exception\DriverException: An exception occurred while 
executing 'CREATE TABLE oc_account_terms (id BIGINT UNSIGNED 
AUTO_INCREMENT NOT NULL, account_id BIGINT UNSIGNED NOT NULL, term 
VARCHAR(256) NOT NULL, INDEX account_id_index (account_id), INDEX 
term_index (term), PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8 COLLATE 
utf8_bin ENGINE = InnoDB':


SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key 
was too long; max key length is 767 bytes

Update failed
Maintenance mode is kept active
Reset log level


Any clue to get this working again ?

--
David Marec
https://lapinbilly.eu/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Owncloud upgrade failure

2017-05-30 Thread David Marec

Le 30.05.2017 à 22:29, David Marec a écrit :
CREATE TABLE oc_account_terms (id BIGINT UNSIGNED AUTO_INCREMENT NOT 
NULL, account_id BIGINT UNSIGNED NOT NULL, term VARCHAR(256) NOT NULL, 
INDEX account_id_index (account_id), INDEX term_index (term), PRIMARY 
KEY(id)) DEFAULT CHARACTER SET utf8 COLLATE utf8_bin ENGINE = InnoDB'


An attempt to feed this to mysql using the command line tool triggers 
the same error. With or without the 'ENGINE' clause.




--
David Marec
https://lapinbilly.eu/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Owncloud upgrade failure

2017-05-30 Thread David Marec

Le 30.05.2017 à 22:29, David Marec a écrit :


Doctrine\DBAL\Exception\DriverException: An exception occurred while 
executing 'CREATE TABLE oc_account_terms (id BIGINT UNSIGNED 
AUTO_INCREMENT NOT NULL, account_id BIGINT UNSIGNED NOT NULL, term 
VARCHAR(256) NOT NULL, INDEX account_id_index (account_id), INDEX 
term_index (term), PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8 COLLATE 
utf8_bin ENGINE = InnoDB':


SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key 
was too long; max key length is 767 bytes

Update failed
Maintenance mode is kept active
Reset log level


Any clue to get this working again ?



As I understand the issue, the 'term' field stores too many bytes
- VARCHAR(256) * UTF8 > 767 ? -
to be used as a key index !?

(255 seems to be ok )


--
David Marec
https://lapinbilly.eu/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

[Upgrade to FreeBSD10] hplip issue

2014-02-01 Thread David Marec

greetings,

Since I upgraded my BSD-box to the recent 10.0 release, I m not able to 
scan any document using the port 'hplip', as i used to when running the 
9.2 release.


hp-scan failed on the following error:

---
hp-scan -otest.png
Using device: hpaio:/usb/Officejet_4500_G510a-f?serial=CN04EF11S905H2

error: Scanning disabled in build. Exiting
---

First, I had to rebuild the port to switch on the 'scanning feature', 
which is not available by the binary package, but scanning still fails.


root@dmarec:/usr/ports/print/hplip # make showconfig
===> The following configuration options are available for hplip-3.14.1:
 DOCS=off: Build and/or install documentation
 FAX=off: PC Send Fax support
 QT=off: Graphical User Interface (Qt 4)
 SCAN=on: Scanning support
 SNMP=off: Network/JetDirect support
 XSANE=off: Install XSane for scanning (requires SCAN)
===> Use 'make config' to modify these settings


I also tried to activate XSane,
- with the help of the new binary package installation-
but the error still occurs.

Any clue ?

--
David Marec.
___
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: [Upgrade to FreeBSD10] hplip issue

2014-02-01 Thread David Marec

On 01.02.2014 10:39, David Marec wrote:
First, I had to rebuild the port to switch on the 'scanning feature', 
which is not available by the binary package, but scanning still fails.


Finally, while checking in the hplip configuration files, I found that 
the scanning feature was still disabled in the file

/usr/local/etc/hp/hplip.conf
So, I changed the entry line :
scanner-build=yes

and now, the scanner can be used.

I don't know why this file was not updated during the hplip installation.

--
David Marec
___
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: [Upgrade to FreeBSD10] hplip issue

2014-02-03 Thread David Marec

On 03.02.2014 01:18, Scot Hetzel wrote:

On Sat, Feb 1, 2014 at 4:14 AM, David Marec  wrote:

I don't know why this file was not updated during the hplip installation.


[...]
  if there were any changes to hplip.conf file, it doesn't get removed
when the port is uninstalled.  And if the file exists, it won't
overwrite your changes.

Did you customize this file before you re-installed?


No. But I guess this file wasn't removed when I requested the deletion 
of all the ports using 'pkg delete', once FreeBSD was upgraded.

But, at that time, the scanning switch was enabled in the file.



Does the hplip.conf.sample file have scanner-build=yes?



The only difference is the line I set up to fix the issue, after the 
(re)installation:

david:/<1>local/etc/hp>diff hplip.conf hplip.conf.sample
25c25
< scanner-build=yes
---
> scanner-build=no

--
David Marec
___
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-10] slrn doesn't choose the right charset since the upgrade.

2014-02-27 Thread David Marec

Hello,

I am using  slrn and vim to post messages on Usenet.
Vim is running with the UTF-8 encoding set.

To avoid posting messages in UTF-8 when it is not needed, the following 
rules is defined in the slrn resource file:


charset outgoing "us-ascii,iso-8859-1,iso-8859-15,utf-8"

This means that slrn  will 'try the settings from left to right and use 
the first for which encoding succeeds'.



But, since I upgraded my desktop to FreeBSD-10, slnr was installed from 
the Freebsd pkg  repository,
the first setting is always choosen and the message is released with 
lots of "?" in place of any UTF-8/Latin1 characters.


A clue: I know that slrn calls 'iconv' for encoding and that iconv has 
been moved into the base system.


Is this an iconv-from-the-base issue ?


-- david Marec
___
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"