LibriumArcana.Games

Posted: **Tue Jul 11, 2006 5:10 am**

Well, I've been trying to install IceWM 1.2.26 on Mandriva 2005 LE. The Mandriva itself has been installed successfully.

I tried to compile the IceWM from scratch. I have the icewm-1.2.26.tar.gz file, and have successfully unzipped it with the following command:

tar xzf icewm-1.2.26.tar.gz

Then I went to the folder icewm-1.2.26 and execute the ./configure script. But all I got was the following message:

configure error: C++ compiler cannot create executables
See `config.log' for more details.

Why? I was sure I already included all libraries when installing the linux, including gtk. I have even re-installed the Mandriva the second time, and made sure that all and every libraries are installed, but it just kept failing.

Anyway, here's the content of config.log:

Code: Select all

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by configure, which was
generated by GNU Autoconf 2.59.  Invocation command line was

  $ ./configure 

## --------- ##
## Platform. ##
## --------- ##

hostname = localhost
uname -m = i686
uname -r = 2.6.11-6mdk
uname -s = Linux
uname -v = #1 Tue Mar 22 16:04:32 CET 2005

/usr/bin/uname -p = unknown
/bin/uname -X     = unknown

/bin/arch              = i686
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
hostinfo               = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /sbin
PATH: /usr/sbin
PATH: /bin
PATH: /usr/bin
PATH: /usr/X11R6/bin
PATH: /usr/local/bin
PATH: /usr/local/sbin


## ----------- ##
## Core tests. ##
## ----------- ##

configure:1387: checking build system type
configure:1405: result: i686-pc-linux-gnu
configure:1413: checking host system type
configure:1427: result: i686-pc-linux-gnu
configure:1435: checking target system type
configure:1449: result: i686-pc-linux-gnu
configure:1528: checking for g++
configure:1557: result: no
configure:1528: checking for c++
configure:1557: result: no
configure:1528: checking for gpp
configure:1557: result: no
configure:1528: checking for aCC
configure:1557: result: no
configure:1528: checking for CC
configure:1557: result: no
configure:1528: checking for cxx
configure:1557: result: no
configure:1528: checking for cc++
configure:1557: result: no
configure:1528: checking for cl
configure:1557: result: no
configure:1528: checking for FCC
configure:1557: result: no
configure:1528: checking for KCC
configure:1557: result: no
configure:1528: checking for RCC
configure:1557: result: no
configure:1528: checking for xlC_r
configure:1557: result: no
configure:1528: checking for xlC
configure:1557: result: no
configure:1570: checking for C++ compiler version
configure:1573: g++ --version </dev/null >&5
./configure: line 1574: g++: command not found
configure:1576: $? = 127
configure:1578: g++ -v </dev/null >&5
./configure: line 1579: g++: command not found
configure:1581: $? = 127
configure:1583: g++ -V </dev/null >&5
./configure: line 1584: g++: command not found
configure:1586: $? = 127
configure:1609: checking for C++ compiler default output file name
configure:1612: g++    conftest.cc  >&5
./configure: line 1613: g++: command not found
configure:1615: $? = 127
configure: failed program was:
| /* confdefs.h.  */
| 
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h.  */
| 
| int
| main ()
| {
| 
|   ;
|   return 0;
| }
configure:1654: error: C++ compiler cannot create executables
See `config.log' for more details.

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_build=i686-pc-linux-gnu
ac_cv_build_alias=i686-pc-linux-gnu
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_host=i686-pc-linux-gnu
ac_cv_host_alias=i686-pc-linux-gnu
ac_cv_target=i686-pc-linux-gnu
ac_cv_target_alias=i686-pc-linux-gnu

## ----------------- ##
## Output variables. ##
## ----------------- ##

APPLICATIONS='icewm icewm-session icesh icewmhint icewmbg icewmtray'
AUDIO_CFLAGS=''
AUDIO_LIBS=''
BASEBINS=''
BASEOBJS=''
BINDIR=''
BINFILES=''
CFGDIR=''
CONFIG_GNOME1_MENU_DIR=''
CONFIG_GNOME2_MENU_DIR=''
CONFIG_KDE_MENU_DIR=''
CORE_CFLAGS=''
CORE_LIBS=''
CPPFLAGS=''
CXX='g++'
CXXCPP=''
CXXFLAGS=''
CXX_LINK=''
DEBUG=''
DEFS=''
DOCDIR=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
ESD_CONFIG=''
EXEEXT=''
GCCDEP=''
GNOME1_CFLAGS=''
GNOME1_CONFIG=''
GNOME1_LIBS=''
GNOME2_CFLAGS=''
GNOME2_LIBS=''
GNOME_VER=''
GWMDIR=''
HOSTCPU=''
HOSTOS=''
IMAGE_CFLAGS=''
IMAGE_LIBS=''
IMLIB_CONFIG=''
INSTALL=''
INSTALLBIN=''
INSTALLDIR=''
INSTALLETC=''
INSTALLLIB=''
INSTALLMAN=''
INSTALL_DATA=''
INSTALL_PROGRAM=''
INSTALL_SCRIPT=''
KDEDIR=''
LDFLAGS=''
LIBDIR=''
LIBOBJS=''
LIBS=''
LOCDIR=''
LTLIBOBJS=''
MANDIR=''
MKFONTDIR=''
MSGFMT=''
MSGMERGE=''
NLS_MOFILES=''
NLS_POFILES=''
NLS_POXFILES=''
NLS_SOURCES=''
OBJEXT=''
PACKAGE=''
PACKAGE_BUGREPORT=''
PACKAGE_NAME=''
PACKAGE_STRING=''
PACKAGE_TARNAME=''
PACKAGE_VERSION=''
PATH_SEPARATOR=':'
PKG_CONFIG=''
PREFIX=''
SHELL='/bin/sh'
TARGETS='base'
TARGETS_INSTALL=''
TESTBINS=''
TESTCASES='testarray testdesktop testlocale testmap testmenus testnetwmhints testwinhints iceview icesame iceicon icerun icelist'
TESTOBJS=''
VERSION=''
XFT_CONFIG=''
XGETTEXT=''
X_CFLAGS=''
X_EXTRA_LIBS=''
X_LIBS=''
X_PRE_LIBS=''
ac_ct_CXX='g++'
bindir='${exec_prefix}/bin'
build='i686-pc-linux-gnu'
build_alias=''
build_cpu='i686'
build_os='linux-gnu'
build_vendor='pc'
datadir='${prefix}/share'
exec_prefix='NONE'
host='i686-pc-linux-gnu'
host_alias=''
host_cpu='i686'
host_os='linux-gnu'
host_vendor='pc'
includedir='${prefix}/include'
infodir='${prefix}/info'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localstatedir='${prefix}/var'
mandir='${prefix}/man'
oldincludedir='/usr/include'
prefix='NONE'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target='i686-pc-linux-gnu'
target_alias=''
target_cpu='i686'
target_os='linux-gnu'
target_vendor='pc'

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define PACKAGE_BUGREPORT ""
#define PACKAGE_NAME ""
#define PACKAGE_STRING ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""

configure: exit 77

Posted: **Tue Jul 11, 2006 7:26 am**

When you installed Mandriva, did you remember to check program devlopment packages?

The configure script says it cannot find the compiler, so that is the most likely explaination.

For some stupid reason, Mandriva doesn't install the compiler by default.

Posted: **Tue Jul 11, 2006 9:16 pm**

Destructionator XV wrote:When you installed Mandriva, did you remember to check program devlopment packages?

I believe I did. However, I'm going to reinstall again this morning to be sure. Thanks!

Posted: **Wed Jul 12, 2006 5:55 am**

Well you're correct, Adam. Mandriva 2005 didn't install the necessary gcc libraries because I skipped CD #2 and CD #3.

Anyway, after reinstalling Mandriva (and all necessary gcc libraries), eventually I executed these commands with success:

./configure --prefix=/home/Program_Files/IceWM --exec-prefix=/home/Program_Files/IceWM --with-xpm

make

make install

I didn't get any error messages, except few warning messages about unused parameters. I guess I have successfully installed IceWM, haven't I?

The problem is, when I execute /usr/sbin/chksession -l, there is no "IceWM" at all among the possible values. All I got were only "KDE", "default", and "failsafe". Nope, there's no IceWM at all.

When I tried to configure the Desktop Manager through Mandriva KDE GUI, I found that I got two selection: KDM and XDM. The default value was KDM, so I changed it into XDM. But when Mandriva restarted the session, I still got the KDE, only this time I lost the ability to shut down the computer through GUI (logout -=> shutdown). I did the cold boot, but I still got KDE.

Help!

Posted: **Wed Jul 12, 2006 7:13 am**

Well, now you want to change the window manager. kdm and xdm are both display managers. They give you the graphical login screen and restart the X server if it dies.

Why did you change the prefix in configure? Usally you want to keep the default because that is where the system would look for new binaries. If it is in the normal place, then the GUIs should pick it up and let you choose it.

Posted: **Wed Jul 12, 2006 11:39 am**

Destructionator XV wrote:Well, now you want to change the window manager. kdm and xdm are both display managers. They give you the graphical login screen and restart the X server if it dies.

Why did you change the prefix in configure? Usally you want to keep the default because that is where the system would look for new binaries. If it is in the normal place, then the GUIs should pick it up and let you choose it.

Well, actually I'm experimenting with Linux whose interfaces really resembles Windows, including folders and the likes. Is it because I changed the default prefix? I'm gonna' try it again tommorrow.

By the way, what is the purpose of "emerge" command? Is it to activate the program we have installed? Probably I need to "activate" the IceWM before using it?

Posted: **Wed Jul 12, 2006 11:44 am**

Nah, emerge is one of the package management commands. I never use that package system, so I don't know for sure, but I beleive you emerge program_name and it automatically downloads and installs it.

Try typing "man emerge" in a terminal for more info. The man command brings up that program's manual page, if it exists on your system.

If you change the prefix, you also need to append that directory to your path, otherwise the system can't find it automatically, and you would have to invoke it always manually or from a script (which can be used like shortcuts on Windows). Altering an individual user's path for a session is easy, but changing it system wide is distribution dependent, and I don't know how to do it on Mandriva.

Posted: **Wed Jul 12, 2006 11:47 am**

Also, on making the folders look like Windows: why? Do users really care if the folders are called "Program Files" or "Documents and Settings" as long as it works? I would focus on making it just work, so users never need to know where program folders are.

If you still want folders by those names, you could make them symlinks, like this:

ln -s /usr/local/bin /home/Program\ Files

But I don't see what advantage using that naming scheme would have, More trouble than it is worth.

Posted: **Wed Jul 12, 2006 12:11 pm**

Destructionator XV wrote:If you still want folders by those names, you could make them symlinks, like this:

ln -s /usr/local/bin /home/Program\ Files

Ah, I see. So it means I can make "C:" for "/", and "D:" for "/home", am I correct?

Anyway, Mandriva 2005 actually comes with IceWM, but it is version 1.2.10 (IIRC), while I want to install version 1.2.26 to make it more compatible with later themes (like Silver XP). I guess it'll be easier for me to install the IceWM that comes with Mandriva, and upgrading later, won't it?

By the way, thanks again Adam.

Posted: **Wed Jul 12, 2006 12:20 pm**

Kreshna Aryaguna Nurzaman wrote:Ah, I see. So it means I can make "C:" for "/", and "D:" for "/home", am I correct?

You could, but you would have to put them somewhere in the actual *nix filesystem.

You can't for example have a c:/something, but you could have a /c:/something. But all that does is add to confusion and limit possibilities, so I wouldn't.

The only time where it might be useful bringing in stuff like that would be shortcuts on the user's desktop. That is actually a good idea: just focus on making the desktop itself easy to use: have all relevent programs and folders there as shortcuts with names they would know.

Anyway, Mandriva 2005 actually comes with IceWM, but it is version 1.2.10 (IIRC), while I want to install version 1.2.26 to make it more compatible with later themes (like Silver XP). I guess it'll be easier for me to install the IceWM that comes with Mandriva, and upgrading later, won't it?

Oh probably. Upgrading a preinstalled package with a self compiled program often leaves stuff behind. It is possible, but a little harder to do.

Posted: **Wed Jul 12, 2006 12:34 pm**

Destructionator XV wrote:
Anyway, Mandriva 2005 actually comes with IceWM, but it is version 1.2.10 (IIRC), while I want to install version 1.2.26 to make it more compatible with later themes (like Silver XP). I guess it'll be easier for me to install the IceWM that comes with Mandriva, and upgrading later, won't it?
Oh probably. Upgrading a preinstalled package with a self compiled program often leaves stuff behind. It is possible, but a little harder to do.

Guess I need to find a Mandriva RPM package for IceWM 1.2.26 then...

Posted: **Fri Jul 14, 2006 4:18 am**

Update: I've successfully installed IceWM 1.2.20, which included in Mandriva 2005 LE. So I installed by simply including it in Mandriva installation options, and set it as default through the same Mandriva GUI-based installation options. What a newbie I am... :sad:

Ah, well. The important thing is that now I have IceWM as default whenever I boot to Mandriva. However, there are things that make me puzzled.

(1) according Linux Productivity Magazine (September 2002), which, by the way, contains a very detailed steps to install IceWM and set it as default, there is supposed to be a file named desktop in either /etc/sysconfig/ or $HOME which contains the text that determines your default desktop (DESKTOP=KDE or DESKTOP=IceWM). However, in my Mandriva, there is NO such file at all. Now how come IceWM becomes my default desktop without the file?

(2) When using KDE, I can still use KDE GUI to shut down the laptop ("log off", then "shut down"). In IceWM, selecting "log off" just brings me back to the login menu, so I need to execute init 6 as root to shut down the laptop. How to add GUI shutdown to IceWM?

(3) Where (on the net) can I find the best instruction to install Konqueror Explorer (you know, the one that is like Windows Explorer) in IceWM?

Thanks,
-Kresh

Posted: **Sat Jul 15, 2006 9:08 am**

Kreshna Aryaguna Nurzaman wrote: (1) according Linux Productivity Magazine (September 2002), which, by the way, contains a very detailed steps to install IceWM and set it as default, there is supposed to be a file named desktop in either /etc/sysconfig/ or $HOME which contains the text that determines your default desktop (DESKTOP=KDE or DESKTOP=IceWM). However, in my Mandriva, there is NO such file at all.

On my Slackware system, there is a directory /etc/sysconfig/ but it is not used. I've never heard of that controlling the desktop. Maybe one of those "user friendly" distros do that. I don't bloody know.

Now how come IceWM becomes my default desktop without the file?

Probably because it is started up in the /etc/X11/xinit/xinitrc or the ~/.xinitrc files, which are scripts that are run when the X window system starts up (X is the GUI on most systems).

Your other questions are going to take some time to look into, I am installing IceWM on my system now so I can follow along. Until then, check out the website, manual, and FAQ:

http://www.icewm.org/
http://www.icewm.org/manual/
http://www.icewm.org/FAQ/

Curious though, why not just use KDE? It has almost everything you could want all right there, and is generally easy to set up and use.

Posted: **Sat Jul 15, 2006 1:06 pm**

Destructionator XV wrote:
Kreshna Aryaguna Nurzaman wrote: (1) according Linux Productivity Magazine (September 2002), which, by the way, contains a very detailed steps to install IceWM and set it as default, there is supposed to be a file named desktop in either /etc/sysconfig/ or $HOME which contains the text that determines your default desktop (DESKTOP=KDE or DESKTOP=IceWM). However, in my Mandriva, there is NO such file at all.
On my Slackware system, there is a directory /etc/sysconfig/ but it is not used. I've never heard of that controlling the desktop. Maybe one of those "user friendly" distros do that. I don't bloody know.

The worst thing is that the article says that it is the 'Mandriva way', too bad, in my Mandriva, the etc/sysconfig/ doesn't contain such thing. Another alternative is $HOME/ (although it's user-specific instead of system wide), but it contains no such thing either.

Destructionator XV wrote:
Now how come IceWM becomes my default desktop without the file?
Probably because it is started up in the /etc/X11/xinit/xinitrc or the ~/.xinitrc files, which are scripts that are run when the X window system starts up (X is the GUI on most systems).

Thanks! I'm gonna' trace the xinitrc files.

Anyway, what originally disturbed me that IceWM does not show up when I executed chksession -l. But now here's more: after successfully compiling IceWM (executing make install with no error message), it seemed that the IceWM was not being installed at all. Yes, I checked the list of installed software through Mandriva Software Manager, and no, no IceWM at all. :sad:

A friend suggested that IceWM 1.2.26 may be incompatible with Mandriva 2005, but we did the same thing on Mandriva 2006, and the result was still the same. No, no IceWM at all on the list of installed software. :thewall:

Destructionator XV wrote:Your other questions are going to take some time to look into, I am installing IceWM on my system now so I can follow along.

Thanks! Glad to hear that. I always wonder if I really miss something. When you have successfully installed it, let me know, would ya?

Destructionator XV wrote:Until then, check out the website, manual, and FAQ:

http://www.icewm.org/
http://www.icewm.org/manual/
http://www.icewm.org/FAQ/

Yup, gonna' skim through the docs again. Probably there's something I really miss.

Destructionator XV wrote:Curious though, why not just use KDE? It has almost everything you could want all right there, and is generally easy to set up and use.

Well actually my concern is resource consumption, but if everything fails, KDE would me my resort. KDE is also costumizable (icons, Start Menu, appearances, etc), isn't it?

Posted: **Sat Jul 15, 2006 9:05 pm**

Kreshna Aryaguna Nurzaman wrote:Anyway, what originally disturbed me that IceWM does not show up when I executed chksession -l. But now here's more: after successfully compiling IceWM (executing make install with no error message), it seemed that the IceWM was not being installed at all. Yes, I checked the list of installed software through Mandriva Software Manager, and no, no IceWM at all.

That software manager thing must only work with their own packages. When you make install, it copies the needed files to the right folder, but it does so in a generic way; it doesn't tell any distro specific software what it did.

Big complaint I have about Linux: all the damn distributions have to do everything their own way.

A friend suggested that IceWM 1.2.26 may be incompatible with Mandriva 2005, but we did the same thing on Mandriva 2006, and the result was still the same. No, no IceWM at all on the list of installed software.

Probably just a better thing to do would be to learn to do it all manually. These user friendly tools aren't worth it in my opnion.

Thanks! Glad to hear that. I always wonder if I really miss something. When you have successfully installed it, let me know, would ya?

Well, I have it installed now, and running in a nested X server. I invoked everything manually, and it worked as expected. I can now work on modifying icons, menus, etc.

Well actually my concern is resource consumption, but if everything fails, KDE would me my resort.

KDE does take more than simple managers like IceWM, but it really does pay off. You get a full desktop with plenty of features. And since you said you want to use Konqueror anyway, that means the KDE libraries will already be loaded, so might was well use them to the fullest potential.

Unless you are using really old computers, it should be worth it.

KDE is also costumizable (icons, Start Menu, appearances, etc), isn't it?

Yeah, lots of stuff you can change with it.

Posted: **Wed Jul 19, 2006 10:21 pm**

Destructionator XV wrote:Big complaint I have about Linux: all the damn distributions have to do everything their own way.

What's the most 'generic' and 'standard' linux distro then? Is it Debian?

Destructionator XV wrote:Well, I have it installed now, and running in a nested X server. I invoked everything manually, and it worked as expected. I can now work on modifying icons, menus, etc.

Wait, wait. So it works? Could you elaborate your installation steps?

I assume you did the following:

(1)! compile the package using ./configure command

(2) make

(3) make install

(4) edit your xinittrc or xsession file

Am I correct? Is the installation steps above complete? Or Is there any step I miss?

Posted: **Wed Jul 19, 2006 10:56 pm**

Kreshna Aryaguna Nurzaman wrote:What's the most 'generic' and 'standard' linux distro then? Is it Debian?

Eh, hard to say. They all do things their own way. I like the Slackware approach: it does the bare minimum and leaves the rest of the details to me, which is why I use it.

Debian has its own system, but at least it is rather wide spread, so it is almost useful. Red Hat does too. Mandriva I think just uses their systems.

The thing is I don't like any of their ways of doing things. And no one in the Linux community can agree on what they want, so it will remain fragmented.

Wait, wait. So it works? Could you elaborate your installation steps?

Well, I ran it on top of what I already have running, so my steps would be a little different, but this is what I did:

./configure
make (btw: this is the step where it does the actual compilation)
sudo make install

Then I ran a Xnest and punched up the wm manually:

Xnest :10 &
icewm --display=localhost:10 &

(by the way, I hate the way icewm requires 2 dashes. Every other program needs only one for the display option. Why the hell did they have to go and be different?)

Now, if I was going to set it to be used always by me, I would have added it to my ~/.xinitrc file, which would then look like this:

Code: Select all

#!/bin/sh
# $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/usr/X11R6/lib/X11/xinit/.Xresources
sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then
    xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f $userresources ]; then
    xrdb -merge $userresources
fi

if [ -f $usermodmap ]; then
    xmodmap $usermodmap
fi

     # Start the window manager:
exec /usr/local/bin/icewm

After that, when I startx, icewm would start up. However, if I were to log in through the graphical login screen, gdm or kdm, it would not. I would have to select it from the menu there and set it to default when it asks me to do so.

Posted: **Thu Jul 20, 2006 12:13 am**

Destructionator XV wrote:Eh, hard to say. They all do things their own way. I like the Slackware approach: it does the bare minimum and leaves the rest of the details to me, which is why I use it.

Debian has its own system, but at least it is rather wide spread, so it is almost useful. Red Hat does too. Mandriva I think just uses their systems.

The thing is I don't like any of their ways of doing things. And no one in the Linux community can agree on what they want, so it will remain fragmented.

I see :sad:

Destructionator XV wrote: Well, I ran it on top of what I already have running, so my steps would be a little different, but this is what I did:

./configure
make (btw: this is the step where it does the actual compilation)
sudo make install

Wait, when executing ./configure, did you specify any switches (like --with-kdm, etc), or just executing it as it is?

Destructionator XV wrote:After that, when I startx, icewm would start up. However, if I were to log in through the graphical login screen, gdm or kdm, it would not. I would have to select it from the menu there and set it to default when it asks me to do so.

Ah, I guess that was my problem! By the way, what menu did you refer? The available selections in Mandriva are xdm and kdm (when choosing the default Windows Manager from Mandriva Control Center).

LibriumArcana.Games

Help! Cannot compile IceWM in Mandriva 2005

#1 Help! Cannot compile IceWM in Mandriva 2005

#2

#3

#4

#5

#6

#7

#8

#9

#10

#11

#12

#13

#14

#15

#16

#17

#18