Freebsd macbook: Cut-and-paste in Icewm?

2009-12-01 Thread w s
Hi again,

(My macbook is now a freebsd machine with 90% of my favorite programs
built and running...  Yay!   Thanks to the community and the list!  To
get octave I needed to symlink f77-gfortran and use gmake instead of
make, but otherwise everything went swimmingly once I figured out
gpart.)

Question -- I would like to have generic cut-and-paste in my icewm X
session, but I have the single button funky macintosh set up.  Is
there a tutorial on how to set this up?

I don't mind using the keyboard while I click and drag and whatever,
but I haven't a clue where to start with setting that up.

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


Re: icewm - error during portupgrade / compiling

2009-11-10 Thread Eitan Adler
Hey,
I'm the maintainer for x11-wm/icewm.

Could you tell me if add the port devel/gnome-vfs helps? And could you
tell me what the output of make showconfig is for icewm?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


icewm - error during portupgrade / compiling

2009-08-10 Thread Ewald Jenisch
Hi,

During a portupgrade done today the upgrade of icewm
(/usr/ports/x11-wm/icewm) stopped with the following symptoms:

.
.
.
gnome2.cc:25:19: error: gnome.h: No such file or directory
gnome2.cc:27:40: error: libgnomevfs/gnome-vfs-init.h: No such file or directory
gnome2.cc: In member function 'void GnomeMenu::addEntry(const char*, const 
char*, int, bool)':
gnome2.cc:122: error: 'gnome_pixmap_file' was not declared in this scope
gnome2.cc: In function 'int main(int, char**)':
gnome2.cc:351: error: 'gnome_vfs_init' was not declared in this scope
gmake[1]: *** [gnome2.o] Error 1
gmake[1]: Leaving directory `/usr/ports/x11-wm/icewm/work/icewm-1.2.37/src'
gmake: *** [base] Error 2
*** Error code 1

Stop in /usr/ports/x11-wm/icewm.
*** Error code 1

Stop in /usr/ports/x11-wm/icewm.
#


Even a make clean; make in /usr/ports/x11-wm/icewm didn't help - it
simply doesn't compile.

Has anybody else seen this problems recently?

Any know cure?

Thanks in advance for your help,
-ewald
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: icewm - error during portupgrade / compiling

2009-08-10 Thread Polytropon
On Mon, 10 Aug 2009 14:07:15 +0200, Ewald Jenisch a...@jenisch.at wrote:
 gnome2.cc:25:19: error: gnome.h: No such file or directory
 gnome2.cc:27:40: error: libgnomevfs/gnome-vfs-init.h: No such file or 
 directory

This seems to be the cause of the error: a missing dependency (here:
missing header files, BDEPS).

 Has anybody else seen this problems recently?

Not recently, but I'm sure I have seen this.



 Any know cure?

Maybe not very elegant, but I did pkg_add -r for the dependencies.
I think you can compile the dependencies that are problematic,
it seems to be gnome-vfs, by hand, and then start rebuilding your
icewm port.




-- 
Polytropon
From Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


idesk, rox, and icewm

2006-03-31 Thread Logan McNaughton
Okay, im trying to use icewm with rox and idesk, I start icewm, then start
rox pinboard, then idesk, but idesk always starts behind the rox pinboard
backdrop and I cant see the idesk. I went into winoptions for icewm, and
changed ROX-Pinboard.layer to behind (says to do that in the rox manual),
still cant see idesk, then i change idesk.layer to OnTop, still cant see it,
any suggestions?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


icewm tools

2006-03-31 Thread Logan McNaughton
Hey, ive tried to download and compile IceWM Control Panel, it required
python for an install shield, so I got python, and it needed py-gtk, so I
got py24-gtk from ports, all that went fine, I tried to run the install
shield, and it gave me errors about really strange stuff

So I tried IceWM Control Center, required qt, so I got qt, but when i ran
./configure, it says i dont have the qt libraries, any suggestions?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: icewm tools

2006-03-31 Thread Norberto Meijome
On Fri, 31 Mar 2006 15:32:01 -0700
Logan McNaughton [EMAIL PROTECTED] wrote:

 Hey, ive tried to download and compile IceWM Control Panel, it
 required python for an install shield, so I got python, and it needed
 py-gtk, so I got py24-gtk from ports, all that went fine, I tried to
 run the install shield, and it gave me errors about really strange
 stuff
 
 So I tried IceWM Control Center, required qt, so I got qt, 

how did you get qt? /usr/ports/x11-toolkits/qt33 ?

 but when i
 ran ./configure, it says i dont have the qt libraries, any
 suggestions?

install the package or from port. If you have, you may have to pass an
option to configure telling it where to find the QT libraries (as they
would be in /usr/local/lib/... ./configure --help should help you out)

beto

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


Re: icewm tools

2006-03-31 Thread Logan McNaughton
I installed qt from a package (pkg_add), Ill try that configure thing,
thanks

On 3/31/06, Norberto Meijome [EMAIL PROTECTED] wrote:

 On Fri, 31 Mar 2006 15:32:01 -0700
 Logan McNaughton [EMAIL PROTECTED] wrote:

  Hey, ive tried to download and compile IceWM Control Panel, it
  required python for an install shield, so I got python, and it needed
  py-gtk, so I got py24-gtk from ports, all that went fine, I tried to
  run the install shield, and it gave me errors about really strange
  stuff
 
  So I tried IceWM Control Center, required qt, so I got qt,

 how did you get qt? /usr/ports/x11-toolkits/qt33 ?

  but when i
  ran ./configure, it says i dont have the qt libraries, any
  suggestions?

 install the package or from port. If you have, you may have to pass an
 option to configure telling it where to find the QT libraries (as they
 would be in /usr/local/lib/... ./configure --help should help you out)

 beto


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


icewm or..?

2004-07-26 Thread dick hoogendijk
Recently I read in this mailinglist some advice about a windowmanager
even more flexible then Icewm. I can't remember the name though ;-(

Someone wrote that all you need to do to add a program to the menu was:
open the menu some place and choose add ;-)

I remember is was not fvwm (which I use now), blackbox, etc..
Any ideas? Would be a great help..

-- 
dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE
++ Running FreeBSD 4.10 ++ Debian GNU/Linux (Woody)
+ Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilya
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: icewm or..?

2004-07-26 Thread Arek Czereszewski
dick hoogendijk wrote:
Recently I read in this mailinglist some advice about a windowmanager
even more flexible then Icewm. I can't remember the name though ;-(
Someone wrote that all you need to do to add a program to the menu was:
open the menu some place and choose add ;-)
I remember is was not fvwm (which I use now), blackbox, etc..
Any ideas? Would be a great help..
Maybe you think about xfce4??
Arek
--
Arek Czereszewski   | jid: aro(at)chrome.pl
arek(at)wup-katowice.pl |  gg: 1349941
*nix is like a wigwam:
no windows, no gates, apache inside.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Statically Linked IceWM

2003-10-24 Thread Abhijeet
hi ,
Can some one tell me if it is possible to build IceWM statically linked 
( FreeBSD as well as linux  i am using FreeBSD 5.0).i downloaded the 
source tar and made changes to the make script by adding the -static  
parameter but still the executable produced is not statically linked 
but dynamically linked. Please tell me the way to go ahead.

( tell me if it is possible also)

Thanks in advance.

Abhijeet Sane
[EMAIL PROTECTED]
Pune ( India )
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


icewm port: make error

2003-10-23 Thread [EMAIL PROTECTED]
Hi,
while trying to install the icewm (a window manager) port,
the make command stops with the error :
.
.
configure: error: Xinerama can not be found . . . . . 
.
.
the full message is reported in the output included below 
(see OUTPUT of the make command).

Anybody can help ?
Thank you
Bruno

OUTPUT OF 'uname -a':
FreeBSD seekingjob.singles.it 4.9-RC FreeBSD 4.9-RC #0: Wed Oct 15 00:12:26 CEST 2003  
   root@:/usr/obj/usr/src/sys/CURRENT_WINE  i386

OUTPUT of the make command:
===   icewm-1.2.13 depends on executable: gmake - found
===   icewm-1.2.13 depends on executable: pkg-config - found
===   icewm-1.2.13 depends on shared library: intl.5 - found
===   icewm-1.2.13 depends on shared library: Xft.2 - found
===   icewm-1.2.13 depends on shared library: X11.6 - found
===   icewm-1.2.13 depends on shared library: esd.2 - found
===   icewm-1.2.13 depends on shared library: glib12.3 - found
===   icewm-1.2.13 depends on shared library: gtk12.2 - found
===   icewm-1.2.13 depends on shared library: Imlib.5 - found
===  Configuring for icewm-1.2.13
checking build system type... i386-portbld-freebsd4.9
checking host system type... i386-portbld-freebsd4.9
checking target system type... i386-portbld-freebsd4.9
checking for gcc... cc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ANSI C... none needed
checking whether the C compiler (cc) understands C++... yes
checking whether we are using the GNU C++ compiler... yes
checking whether cc accepts -g... yes
checking for gcc... (cached) cc
checking whether we are using the GNU C compiler... (cached) yes
checking whether cc accepts -g... (cached) yes
checking for cc option to accept ANSI C... (cached) none needed
checking whether the C++ compiler (cc) accepts no_rtti... yes
checking whether the C++ compiler (cc) accepts no_exceptions... yes
checking whether the C++ compiler (cc) accepts warn_xxx... yes
checking whether the C++ compiler (cc) accepts permissive... yes
checking if we need our own C++ allocation operators... no
checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for sys/wait.h that is POSIX.1 compatible... yes
checking how to run the C++ preprocessor... cc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... no
checking for unistd.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking for strings.h... (cached) yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for unistd.h... (cached) yes
checking linux/threads.h usability... no
checking linux/threads.h presence... no
checking for linux/threads.h... no
checking linux/tasks.h usability... no
checking linux/tasks.h presence... no
checking for linux/tasks.h... no
checking kstat.h usability... no
checking kstat.h presence... no
checking for kstat.h... no
checking for size_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for char... yes
checking size of char... 1
checking for short... yes
checking size of short... 2
checking for int... yes
checking size of int... 4
checking for long... yes
checking size of long... 4
checking return type of signal handlers... void
checking for strftime... yes
checking for vprintf... yes
checking for _doprnt... no
checking for gettimeofday... yes
checking for putenv... yes
checking for select... yes
checking for socket... yes
checking for strtol... yes
checking for strtoul... yes
checking for basename... yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking types of arguments for select... int,fd_set *,struct timeval *
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include

icewm port: make error

2003-10-23 Thread [EMAIL PROTECTED]
Hi,
while trying to install the icewm (a window manager) port,
the make command stops with the error :
.
.
configure: error: Xinerama can not be found . . . . . 
.
.
the full message is reported in the output included below 
(see OUTPUT of the make command).

Anybody can help ?
Thank you
Bruno

OUTPUT OF 'uname -a':
FreeBSD seekingjob.singles.it 4.9-RC FreeBSD 4.9-RC #0: Wed Oct 15 00:12:26 CEST 2003  
   root@:/usr/obj/usr/src/sys/CURRENT_WINE  i386

OUTPUT of the make command:
===   icewm-1.2.13 depends on executable: gmake - found
===   icewm-1.2.13 depends on executable: pkg-config - found
===   icewm-1.2.13 depends on shared library: intl.5 - found
===   icewm-1.2.13 depends on shared library: Xft.2 - found
===   icewm-1.2.13 depends on shared library: X11.6 - found
===   icewm-1.2.13 depends on shared library: esd.2 - found
===   icewm-1.2.13 depends on shared library: glib12.3 - found
===   icewm-1.2.13 depends on shared library: gtk12.2 - found
===   icewm-1.2.13 depends on shared library: Imlib.5 - found
===  Configuring for icewm-1.2.13
checking build system type... i386-portbld-freebsd4.9
checking host system type... i386-portbld-freebsd4.9
checking target system type... i386-portbld-freebsd4.9
checking for gcc... cc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ANSI C... none needed
checking whether the C compiler (cc) understands C++... yes
checking whether we are using the GNU C++ compiler... yes
checking whether cc accepts -g... yes
checking for gcc... (cached) cc
checking whether we are using the GNU C compiler... (cached) yes
checking whether cc accepts -g... (cached) yes
checking for cc option to accept ANSI C... (cached) none needed
checking whether the C++ compiler (cc) accepts no_rtti... yes
checking whether the C++ compiler (cc) accepts no_exceptions... yes
checking whether the C++ compiler (cc) accepts warn_xxx... yes
checking whether the C++ compiler (cc) accepts permissive... yes
checking if we need our own C++ allocation operators... no
checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for sys/wait.h that is POSIX.1 compatible... yes
checking how to run the C++ preprocessor... cc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... no
checking for unistd.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking for strings.h... (cached) yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for unistd.h... (cached) yes
checking linux/threads.h usability... no
checking linux/threads.h presence... no
checking for linux/threads.h... no
checking linux/tasks.h usability... no
checking linux/tasks.h presence... no
checking for linux/tasks.h... no
checking kstat.h usability... no
checking kstat.h presence... no
checking for kstat.h... no
checking for size_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for char... yes
checking size of char... 1
checking for short... yes
checking size of short... 2
checking for int... yes
checking size of int... 4
checking for long... yes
checking size of long... 4
checking return type of signal handlers... void
checking for strftime... yes
checking for vprintf... yes
checking for _doprnt... no
checking for gettimeofday... yes
checking for putenv... yes
checking for select... yes
checking for socket... yes
checking for strtol... yes
checking for strtoul... yes
checking for basename... yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking types of arguments for select... int,fd_set *,struct timeval *
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include

Re: problems installing icewm from ports Re: problems installing fvwm2 from ports

2002-07-15 Thread Manuel Hendel

I still got a problem installing fvwm2 from ports on one box. I already installed
it on two other boxes successfully. I get the following error message:

install: /usr/X11R6/man/man1/fvwm2.1: Too many levels of symbolic links
gmake[3]: *** [install-man1] Error 71
gmake[3]: Leaving directory `/usr/ports/x11-wm/fvwm2/work/fvwm-2.4.8/fvwm'
gmake[2]: *** [install-man] Error 2
gmake[2]: Leaving directory `/usr/ports/x11-wm/fvwm2/work/fvwm-2.4.8/fvwm'
gmake[1]: *** [install-am] Error 2
gmake[1]: Leaving directory `/usr/ports/x11-wm/fvwm2/work/fvwm-2.4.8/fvwm'
gmake: *** [install-recursive] Error 1
*** Error code 2

Stop in /usr/ports/x11-wm/fvwm2.


Does anyone has a clue what's going on here?

Thanks in advance for any help,

manuel

-- 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



problems installing icewm from ports

2002-07-12 Thread Manuel Hendel

I got a FreeBSD 4.6 installed. I tried to do a make clean install for
the icewm port and got the following error message:

yapp.cc: In method `int YApplication::mainLoop()':
yapp.cc:882: passing `int *' as argument 2 of `select(int, fd_set *,
fd_set *, fd_set *, timeval *)'
yapp.cc:839: warning: `int rc' might be used uninitialized in this
function
gmake[1]: *** [yapp.o] Error 1
gmake[1]: Leaving directory
`/usr/ports/x11-wm/icewm/work/icewm-1.0.9/src'
gmake: *** [base] Error 2
*** Error code 2

Stop in /usr/ports/x11-wm/icewm.

Does anyone know what's going wrong here?

Thanks for any help.

manuel

-- 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: problems installing icewm from ports Re: problems installing fvwm2 from ports

2002-07-12 Thread Manuel Hendel

On Fri, Jul 12, 2002 at 03:54:28AM -0500, Kevin Kinsey, DaleCo, S.P. wrote:
 
 I believe you've just discovered the difference between
 FBSD's make and the GNU make.  If you can figure out
 why you are running GNU's make (which it looks like from
 here) instead of FBSD's that might fix your problem.
 
 Best of luck,
 
 Kevin Kinsey
 

But gmake seams to be needed by fvwm2 an icewm.

partagas:/usr/ports/x11-wm/fvwm2$ make clean
===  Cleaning for gmake-3.79.1_2
===  Cleaning for imake-4.2.0_1
===  Cleaning for libtool-1.3.4_4
===  Cleaning for m4-1.4_1
===  Cleaning for freetype2-2.1.2
===  Cleaning for XFree86-libraries-4.2.0_1
===  Cleaning for fvwm-2.4.8
partagas:/usr/ports/x11-wm/fvwm2$


partagas:/usr/ports/x11-wm/icewm$ make clean
===  Cleaning for esound-0.2.28
===  Cleaning for libaudiofile-0.2.3
===  Cleaning for libiconv-1.8
===  Cleaning for autoconf-2.53
===  Cleaning for bison-1.35_1
===  Cleaning for gettext-0.11.2
===  Cleaning for gmake-3.79.1_2
===  Cleaning for imake-4.2.0_1
===  Cleaning for libgnugetopt-1.1
===  Cleaning for libtool-1.3.4_4
===  Cleaning for m4-1.4_1
===  Cleaning for pkgconfig-0.12.0
===  Cleaning for freetype2-2.1.2
===  Cleaning for expat-1.95.3
===  Cleaning for XFree86-libraries-4.2.0_1
===  Cleaning for icewm-esound-1.0.9.2
partagas:/usr/ports/x11-wm/icewm$ 


But I deinstalled gmake and retried to install icewm and fvwm2, this
doesn't work as well.

partagas:/usr/ports/x11-wm/fvwm2$ make clean
===  Cleaning for gmake-3.79.1_2
===  Cleaning for imake-4.2.0_1
===  Cleaning for libtool-1.3.4_4
===  Cleaning for m4-1.4_1
===  Cleaning for freetype2-2.1.2
===  Cleaning for XFree86-libraries-4.2.0_1
===  Cleaning for fvwm-2.4.8
partagas:/usr/ports/x11-wm/fvwm2$ make
===  Extracting for fvwm-2.4.8
 Checksum OK for fvwm-2.4.8.tar.bz2.
 Checksum OK for fvwm_icons.tgz.
===   fvwm-2.4.8 depends on executable: gmake - not found
===Verifying install for gmake in /usr/ports/devel/gmake
===  Building for gmake-3.79.1_2
make  all-recursive
Making all in glob
cc -DHAVE_CONFIG_H -I. -I. -I..   -I/usr/local/include -DHAVE_LOCALE_H
-DHAVE_LC_MESSAGES  -O -pipe -c glob.c
glob.c: In function `glob_in_dir':
glob.c:1319: `DIR' undeclared (first use in this function)
glob.c:1319: (Each undeclared identifier is reported only once
glob.c:1319: for each function it appears in.)
glob.c:1319: syntax error before `)'
glob.c:1322: dereferencing pointer to incomplete type
glob.c:1333: dereferencing pointer to incomplete type
glob.c:1339: dereferencing pointer to incomplete type
glob.c:1404: syntax error before `)'
glob.c:1416: syntax error before `)'
*** Error code 1

Stop in /usr/ports/devel/gmake/work/make-3.79.1/glob.
*** Error code 1

Stop in /usr/ports/devel/gmake/work/make-3.79.1.
*** Error code 1

Stop in /usr/ports/devel/gmake/work/make-3.79.1.
*** Error code 1

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

Stop in /usr/ports/x11-wm/fvwm2.
partagas:/usr/ports/x11-wm/fvwm2$


===  Building for gmake-3.79.1_2
make  all-recursive
Making all in glob
cc -DHAVE_CONFIG_H -I. -I. -I..   -I/usr/local/include -DHAVE_LOCALE_H
-DHAVE_LC_MESSAGES  -O -pipe -c glob.c
glob.c: In function `glob_in_dir':
glob.c:1319: `DIR' undeclared (first use in this function)
glob.c:1319: (Each undeclared identifier is reported only once
glob.c:1319: for each function it appears in.)
glob.c:1319: syntax error before `)'
glob.c:1322: dereferencing pointer to incomplete type
glob.c:1333: dereferencing pointer to incomplete type
glob.c:1339: dereferencing pointer to incomplete type
glob.c:1404: syntax error before `)'
glob.c:1416: syntax error before `)'
*** Error code 1

Stop in /usr/ports/devel/gmake/work/make-3.79.1/glob.
*** Error code 1

Stop in /usr/ports/devel/gmake/work/make-3.79.1.
*** Error code 1

Stop in /usr/ports/devel/gmake/work/make-3.79.1.
*** Error code 1

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

Stop in /usr/ports/x11-wm/icewm.
partagas:/usr/ports/x11-wm/icewm$


manuel

-- 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message