1851284 Members
3986 Online
104057 Solutions
New Discussion

WindowMaker project

 
SOLVED
Go to solution
John Ramsay_2
Regular Advisor

WindowMaker project

Ok, a new thread. HP-UX 11.00 on a HP-712/100.
My personal unix box at home to learn unix.
I'm root.
I'm trying to install WindowMaker-0.80.2 with the ./configure make amd make install.
I've installed tiff-3.5.7
zlib-1.1.4
bison-1.875
flex-2.5.4a
gcc-3.3.2
jpeg-6b
make-3.80
For the entry below am I looking for a "yes" after everything?
Since some of these are installed but not seen do I have to put them in my path?
Where do I check to see the results to an added LD_LIBRARY_PATH?

Here is what I get when I do a ./configure
./configure
checking for a BSD-compatible install... ./install-sh -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking build system type... hppa1.1-hp-hpux11.00
checking host system type... hppa1.1-hp-hpux11.00
checking for gcc... no
checking for cc... 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... no
checking whether cc accepts -g... yes
checking for non-GNU ld... /bin/ld
checking if the linker (/bin/ld) is GNU ld... no
checking for /bin/ld option to reload object files... -r
checking for BSD-compatible nm... /bin/nm -p
checking for a sed that does not truncate output... /bin/sed
checking whether ln -s works... yes
checking how to recognise dependant libraries... file_magic (s[0-9][0-9][0-9]|PA-RISC[0-9].[0-9]) shared library
checking command to parse /bin/nm -p output... ok
checking how to run the C preprocessor... cc -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 dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for cc option to produce PIC... +Z
checking if cc PIC flag +Z works... yes
checking if cc static flag -Wl,-a -Wl,archive works... yes
checking if cc supports -c -o file.o... no
checking if we can lock with hard links... yes
checking whether the linker (/bin/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... relink
checking whether stripping libraries is possible... no
checking dynamic linker characteristics... hpux11.00 dld.sl
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
creating libtool
checking for strerror in -lcposix... no
checking for gcc... (cached) cc
checking whether we are using the GNU C compiler... (cached) no
checking whether cc accepts -g... (cached) yes
checking whether ln -s works... yes
checking for vprintf... yes
checking for _doprnt... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for gethostname... yes
checking for select... yes
checking for poll... yes
checking for strerror... yes
checking for strcasecmp... yes
checking for strncasecmp... yes
checking for setpgid... yes
checking for atexit... yes
checking for mallinfo... yes
checking for mkstemp... yes
checking for snprintf... yes
checking for vsnprintf... yes
checking for asprintf... no
checking for vasprintf... no
checking for C99 vsnprintf... no
checking for dlopen... no
checking for dlopen in -ldl... no
checking for cpp... /lib/cpp
checking for sys/wait.h that is POSIX.1 compatible... yes
checking whether time.h and sys/time.h may both be included... 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 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 sys/types.h... (cached) yes
checking libintl.h usability... no
checking libintl.h presence... no
checking for libintl.h... no
checking sys/select.h usability... no
checking sys/select.h presence... no
checking for sys/select.h... no
checking poll.h usability... yes
checking poll.h presence... yes
checking for poll.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking ctype.h usability... yes
checking ctype.h presence... yes
checking for ctype.h... yes
checking for string.h... (cached) yes
checking for strings.h... (cached) yes
checking for sys_siglist declaration in signal.h or unistd.h... no
checking for cc option to accept ANSI C... none needed
checking for an ANSI C-conforming const... no
checking return type of signal handlers... void
checking for gettext... no
checking for gettext in -lintl... no
checking for xgettext... xgettext
checking for connect... yes
checking for gethostbyname... yes
checking for inet_aton... yes
checking for X... no
configure: error: The path for the X11 files not found!
Make sure you have X and it's headers and libraries (the -devel packages
in Linux) installed.
#
13 REPLIES 13
Robert-Jan Goossens
Honored Contributor

Re: WindowMaker project

Hello John,

Oke try this.

# echo $PATH

# your PATH is set in the .profile
# vi .profile and add the /usr/bin/X11 directory
PATH=$PATH:/usr/bin/X11

Regards,
Robert-Jan
Mark Grant
Honored Contributor

Re: WindowMaker project

Ok,

Most of these "no" answers are not going to be a bother. The problem is that configure can't find the libraries and include files for building an X application.

If you have installed them then try running "./configure --help". Here you will probably see options that allow you to specify where these headers and libraries are.

I just looked on one of our boxes which is pretty much a default 11.11 install and found that some libraries are in /lib/X11R6 but I don't seem to have the header files anywhere.
Never preceed any demonstration with anything more predictive than "watch this"
Alex Glennie
Honored Contributor

Re: WindowMaker project

John Ramsay_2
Regular Advisor

Re: WindowMaker project

Ok, I told it where the X11 stuff is and it made alot of new makefile stuff. I ran make and got the following:

# make
No suffix list.
Making all in wrlib
/bin/sh ../libtool --mode=compile cc -DHAVE_CONFIG_H -I. -I. -I../src -I/usr/local/include -I/usr/bin/X11 -g -c LookupCmap.c
mkdir .libs
cc -DHAVE_CONFIG_H -I. -I. -I../src -I/usr/local/include -I/usr/bin/X11 -g -c LookupCmap.c +Z -DPIC
(Bundled) cc: warning 480: The -g option is available only with the C/ANSI C product; ignored.
(Bundled) cc: warning 480: The +Z option is available only with the C/ANSI C product; ignored.
cpp: "LookupCmap.c", line 36: error 4036: Can't open include file 'X11/Xlib.h'.
cpp: "LookupCmap.c", line 37: error 4036: Can't open include file 'X11/Xatom.h'.
cpp: "LookupCmap.c", line 38: error 4036: Can't open include file 'X11/Xutil.h'.
cpp: "StdCmap.h", line 38: error 4036: Can't open include file 'X11/Xfuncproto.h'.
*** Error exit code 1

Stop.
*** Error exit code 1

Stop.
#
Alex Glennie
Honored Contributor
Solution

Re: WindowMaker project

fyi /usr/include/X11/Xatom.h etc are included in the Motif Dev kit as per my previous post ...so if a ll on /usr/include/X11/ yeilds the files do not exist I'd advise installing the required header files and try again ?

If they are installed let us know.
John Ramsay_2
Regular Advisor

Re: WindowMaker project

I've installed the developers kit and they are there...Sorry for being so dumb about this as I've only been doing this a week. My concern now is the ./configure--x-includes...
What directory should I provide for these 2 entries as I've got several X11 directories?
John Ramsay_2
Regular Advisor

Re: WindowMaker project

I didn't need the extra lines for ./configure now as the dev kit fixed that. Now I get errors like:
(Bunbled) cc: "wraster.h", line 355: error1000:Unexpected symbol"*"
and also Unable to open intrinsic file /usr/local/lib/sysintr

The file is not found on my system...What am I missing?
Then it panicked because of two many errors
John Ramsay_2
Regular Advisor

Re: WindowMaker project

No one wants to help??? Fine..To hell with WindowMaker
T G Manikandan
Honored Contributor

Re: WindowMaker project

It is not that no one wants to help you.

Once the thread is assigned with the magic answer i.e. a rabbit(assigning points 8/9 or 10 will do that)

Only when you query is answered completely do assign such points.
If your query is not completely answered assign points below 8.

Forumers will not open the questions with rabbit on it because they would assume that the query is resolved.

OK,I will come to your query.

Actually there seems like the dependencies are missing.

I too tried looking at www.windowmaker.org where the documentation does not speak about the pre-requisite.

I can suggest you two things


1.Get the ready made binary from the HP porting center and then load it using swinstall.

http://hpux.cs.utah.edu/hppd/hpux/X11/WM/WindowMaker-0.80.2/

Be careful on the dependencies.
you should load all the dependent packages shown in the above link so that the product would work great!

2.The other way would be,Just load the dependecies as shown in the page above and continue building the tool manually.

I would recommend the first option which is the readymade binary for HPUX11.

Please revert
John Ramsay_2
Regular Advisor

Re: WindowMaker project

Thanks for the response. Will it run ok on a hp712/100 or will it be real slow?
T G Manikandan
Honored Contributor

Re: WindowMaker project

If the workstation has sufficient memory,it should give good results!
Alex Glennie
Honored Contributor

Re: WindowMaker project

Appologies for the late reply .... I do this on a voluntary basis and have been up to my eye's all day to day in my main support role.
John Ramsay_2
Regular Advisor

Re: WindowMaker project

Thanks...I got it working