Subject: devel-digest V2 #175
From: [email-masked] (devel-digest)
To: [email-masked]

devel-digest          Thursday, May 20 1999          Volume 02 : Number 175

In this issue:

    Re: KDE 1.1.1 anyone?
    Re: KDE 1.1.1 anyone?
    Re: KDE 1.1.1 anyone?
    Re: KDE 1.1.1 anyone?
    Re: KDE 1.1.1 anyone?
    DM-13 trouble
    Re: KDE 1.1.1 anyone? 
    Re: DM-13 trouble
    Re: KDE 1.1.1 anyone?
    Re: DM-13 trouble is DM 14 ..
    Re: DM-13 trouble is DM 14 ..
    Re: DM-13 trouble is DM 14 ..
    Re: KDE 1.1.1 anyone?
    Re: KDE 1.1.1 anyone? 
    Re: KDE 1.1.1 anyone? 
    Re: DM-13 trouble is DM 14 ..

See the end of this digest for information about devel-digest.

----------------------------------------------------------------------

Date: Wed, 19 May 1999 07:39:20 -0700
From: Jon Olson <[email-masked]>
Subject: Re: KDE 1.1.1 anyone?

On Tue, 18 May 1999, Tim Rowledge wrote:
>Has anyone got around to building KDE 1.1.1 yet?
>
Yup, built it about a week ago.  No problems building it...
I'll make a tarball soon and upload it to
ftp.netwinder.org:/home/ftp/users/j/jpolson

- --
Jon Olson, Modular Mining Systems
	   3289 E. Hemisphere Loop
	   Tucson, AZ 85706
INTERNET:  [email-masked]
PHONE:     (520)746-9127
FAX:       (520)889-5790
- --
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel" as the body of your message.

------------------------------

Date: Wed, 19 May 1999 08:42:36 -0700 (BST)
From: Tim Rowledge <[email-masked]>
Subject: Re: KDE 1.1.1 anyone?

On Wed 19 May, Jon Olson wrote:
> On Tue, 18 May 1999, Tim Rowledge wrote:
> >Has anyone got around to building KDE 1.1.1 yet?
> >
> Yup, built it about a week ago.  No problems building it...
Strictly for the educational value, do you mean that you had no work todo
beyond the rpm mumble, or that there was something needing doing but it was
simple and obvious to someone who knows what they are doing?
If the latter, maybe a few words of explanation would help me to move a
little along the path of enlightenment so that by the time KDE 5.0.0 comes
out _I_ can be the one that says it was no problem... :-)

tim
PS Is anyone around here expert in KDE configuration? I would like to be
able to set things such that it takes a double-click to open a
file/directory in kfm, rather than a single. Not found anything mentioned
in any doc so far, but there is a lot to dig through.

- -- 
A conscience is what hurts when all your other parts feel so good.
Tim Rowledge:  [email-masked] (w)  +1 (650) 842-6110 (w)
 [email-masked] (h)  <http://sumeru.stanford.edu/tim>

- --
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel" as the body of your message.

------------------------------

Date: Wed, 19 May 1999 08:46:23 -0700
From: Jon Olson <[email-masked]>
Subject: Re: KDE 1.1.1 anyone?

On Wed, 19 May 1999, Tim Rowledge wrote:
>On Wed 19 May, Jon Olson wrote:

>> Yup, built it about a week ago.  No problems building it...
>Strictly for the educational value, do you mean that you had no work todo
>beyond the rpm mumble, or that there was something needing doing but it was
>simple and obvious to someone who knows what they are doing?
>If the latter, maybe a few words of explanation would help me to move a
>little along the path of enlightenment so that by the time KDE 5.0.0 comes
>out _I_ can be the one that says it was no problem... :-)
>

The KDE source packages come as a group of tarballs named things like:

	kdelibs-1.1.1.tar.gz
	kdebase-1.1.1.tar.gz
	kdeadmin-1.1.1.tar.gz
		etc...

	qt-1.4.tar.gz		(I think that this is the current version of QT)

To build it, you first untar and build `qt', then untar, configure, and build
all the KDE packages.  The only trick is to make sure you add the following
options to CFLAGS.  In `qt', you must edit a config file; in KDE, you can
just add it to the ./configure command line.

	-fno-exceptions -fno-rtti -fomit-frame-pointer

The -fomit-frame-pointer is just for optimization.  The -fno-exceptions
- -fno-rtti is NECESSARY because of the broken exception handling in
the ARM egcs compiler.  In addition, exceptions blimps out the binaries
by at least 50% and causes nasty core dumps at line numbers where there
is only a `}'.  Actually, the core dump is in the exception stack manipulation
code emitted by the compiler in each destructor.

There is one unimportant module that actually does throw exceptions,
ksirc I think, so you either don't compile it or build that module with
exceptions enabled realizing that it probably won't work.

- --
Jon Olson, Modular Mining Systems
	   3289 E. Hemisphere Loop
	   Tucson, AZ 85706
INTERNET:  [email-masked]
PHONE:     (520)746-9127
FAX:       (520)889-5790
- --
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel" as the body of your message.

------------------------------

Date: Wed, 19 May 1999 09:17:38 -0700 (BST)
From: Tim Rowledge <[email-masked]>
Subject: Re: KDE 1.1.1 anyone?

On Wed 19 May, Jon Olson wrote:

> The KDE source packages come as a group of tarballs named things like:
[sNIP]
> To build it, you first untar and build `qt', then untar, configure, and
> build all the KDE packages.  The only trick is to make sure you add the
> following options to CFLAGS.  In `qt', you must edit a config file; in
> KDE, you can just add it to the ./configure command line.
Ah! Maybe this little snippet of information might explain why I was able
to compile all the qtlib stuff except (some of) the examples? When I loaded
the kde1.1-pre2(or whatever) and had to build the qtlib from source,
everything was ok except some examples.

Thanks for the info. Little by little I'm figuring this stuff out....

- -- 
Useful Latin Phrases:- Fac me cocleario vomere!
Gag me with a spoon!
Tim Rowledge:  [email-masked] (w)  +1 (650) 842-6110 (w)
 [email-masked] (h)  <http://sumeru.stanford.edu/tim>

- --
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel" as the body of your message.

------------------------------

Date: Wed, 19 May 1999 13:38:25 +0300 (GMT)
From: Roberto Alsina <[email-masked]>
Subject: Re: KDE 1.1.1 anyone?

On Wed, 19 May 1999, Tim Rowledge wrote:

> On Wed 19 May, Jon Olson wrote:
> > On Tue, 18 May 1999, Tim Rowledge wrote:
> > >Has anyone got around to building KDE 1.1.1 yet?
> > >
> > Yup, built it about a week ago.  No problems building it...
> Strictly for the educational value, do you mean that you had no work todo
> beyond the rpm mumble, or that there was something needing doing but it was
> simple and obvious to someone who knows what they are doing?
> If the latter, maybe a few words of explanation would help me to move a
> little along the path of enlightenment so that by the time KDE 5.0.0 comes
> out _I_ can be the one that says it was no problem... :-)
> 
> tim
> PS Is anyone around here expert in KDE configuration?

I think I may qualify.

> I would like to be
> able to set things such that it takes a double-click to open a
> file/directory in kfm, rather than a single. Not found anything mentioned
> in any doc so far, but there is a lot to dig through.

Currently there is no way to do that.

 ("\''/").__..-''"`-. .         Roberto Alsina
 `9_ 9  )   `-. (    ).`-._.`)  [email-masked]
 (_Y_.)' ._   ) `._`.  " -.-'   Centro de Telematica
  _..`-'_..-_/ /-'_.'           Universidad Nacional del Litoral
(l)-'' ((i).' ((!.'             Santa Fe - Argentina
                                KDE Developer (MFCH)
An opinion you can't give reasons for is not an opinion worth having (I)

- --
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel" as the body of your message.

------------------------------

Date: Wed, 19 May 1999 19:11:23 +0200
From: "Jan Rinze" <[email-masked]>
Subject: DM-13 trouble

Hi there,

I have uploaded and installed the dm-13 disc image.

BUT ...

While booting there is a response that grep can't open /proc/cmdline.

Lots of other problems arise from this.

It appears that /proc does not function properly ...

For example , insmod thinks it is rmmod and modules don't get loaded.

Any suggestions on how to fix this ?
Jan Rinze.

- --
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel" as the body of your message.

------------------------------

Date: Wed, 19 May 1999 18:16:47 +0100
From: Philip Blundell <[email-masked]>
Subject: Re: KDE 1.1.1 anyone? 

>The -fomit-frame-pointer is just for optimization.  The -fno-exceptions
>-fno-rtti is NECESSARY because of the broken exception handling in
>the ARM egcs compiler.  In addition, exceptions blimps out the binaries

Is this exception handling still broken in the current sources?  If so, I will 
see if I can fix it for gcc 2.95 so long as you can provide a testcase.

p.

- --
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel" as the body of your message.

------------------------------

Date: Wed, 19 May 1999 17:20:13 +0000
From: Ralph Siemsen <[email-masked]>
Subject: Re: DM-13 trouble

Jan Rinze wrote:
> 
> Hi there,
> 
> I have uploaded and installed the dm-13 disc image.

Well, i'm not sure where you obtained this image from (it was never released
officially, build #12 is the latest released).  If you really did get build
#13, please let us know how, so we can plug the leak :)

It looks like proc isn't being mounted - check that there is an entry for it
in /etc/fstab, also check that there is an empty directory called "proc" in
your root directory (might not have been created by untarring) since this is
needed as a mountpoint for the filesystem.

- -- 
Ralph Siemsen -- [email-masked]
- --
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel" as the body of your message.

------------------------------

Date: Wed, 19 May 1999 13:26:10 -0400
From: Pat Beirne <[email-masked]>
Subject: Re: KDE 1.1.1 anyone?

Tim Rowledge wrote:

> On Wed 19 May, Jon Olson wrote:
> > On Tue, 18 May 1999, Tim Rowledge wrote:
> > >Has anyone got around to building KDE 1.1.1 yet?
> > >
> > Yup, built it about a week ago.  No problems building it...
> Strictly for the educational value, do you mean that you had no work todo
> beyond the rpm mumble, or that there was something needing doing but it was
> simple and obvious to someone who knows what they are doing?
> If the latter, maybe a few words of explanation would help me to move a
> little along the path of enlightenment so that by the time KDE 5.0.0 comes
> out _I_ can be the one that says it was no problem... :-)

Tim,

I, too, did a build of 1.1.0, back about 4 months ago. No problems
building, based on Jon's instructions.

Pat

- --
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel" as the body of your message.

------------------------------

Date: Wed, 19 May 1999 19:44:44 +0200
From: "Jan Rinze" <[email-masked]>
Subject: Re: DM-13 trouble is DM 14 ..

- ----- Original Message -----
From: Ralph Siemsen <[email-masked]>
To: <[email-masked]>
Sent: Wednesday, May 19, 1999 7:20 PM
Subject: Re: DM-13 trouble

>Jan Rinze wrote:
>>
>> Hi there,
>>
>> I have uploaded and installed the dm-13 disc image.
>
>Well, i'm not sure where you obtained this image from (it was never
released
>officially, build #12 is the latest released).  If you really did get build
>#13, please let us know how, so we can plug the leak :)

Correct it is #14 .. sorry.

>It looks like proc isn't being mounted - check that there is an entry for
it
>in /etc/fstab, also check that there is an empty directory called "proc" in
>your root directory (might not have been created by untarring) since this
is
>needed as a mountpoint for the filesystem.

Well proc is mounted through fstab but it seems to be full of crap.

The cmdline stays the same whatever has happened.

Looking at 'mount'

it seems that proc is mounted twice ... ??

Jan Rinze.

- --
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel" as the body of your message.

------------------------------

Date: Wed, 19 May 1999 14:25:05 -0400
From: "Andrew E. Mileski" <[email-masked]>
Subject: Re: DM-13 trouble is DM 14 ..

> Correct it is #14 .. sorry.

From ftp://netwinder.org/devteam/andrewm/redhat/.message
  "Everything here is unsupported.  Use entirely at your own risk!"
Others are welcome to help you out, just don't _expect_ support from
the devteam or Rebel.com

That said, I don't recommend build 14 for general use.  Hence it wasn't
announced, and is not in the official image area of the ftp site.

- --
Andrew E. Mileski - Software Engineer [OS Team Leader]
Rebel.com  http://www.rebel.com/
- --
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel" as the body of your message.

------------------------------

Date: Wed, 19 May 1999 20:48:54 +0200
From: "Jan Rinze" <[email-masked]>
Subject: Re: DM-13 trouble is DM 14 ..

- ----- Original Message ----- 
From: Andrew E. Mileski <[email-masked]>
To: <[email-masked]>
Sent: Wednesday, May 19, 1999 8:25 PM
Subject: Re: DM-13 trouble is DM 14 ..

>> Correct it is #14 .. sorry.
>
>From ftp://netwinder.org/devteam/andrewm/redhat/.message
>  "Everything here is unsupported.  Use entirely at your own risk!"
>Others are welcome to help you out, just don't _expect_ support from
>the devteam or Rebel.com
>
>That said, I don't recommend build 14 for general use.  Hence it wasn't
>announced, and is not in the official image area of the ftp site.

darn !

I guess the 300 Mb I downloaded was not really what I needed...

Hmmm... Thats really sad ..

I still wonder why my /proc does not work.
I even tried a different kernel.

Well, I will try to find the reason.
I noticed that there is a message that /proc might be wrongly mounted.
can't really say I understand how.

I replaced the insmod binary, now insmod works...

Jan Rinze

- --
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel" as the body of your message.

------------------------------

Date: Wed, 19 May 1999 12:23:10 -0700
From: Jon Olson <[email-masked]>
Subject: Re: KDE 1.1.1 anyone?

On Wed, 19 May 1999, Philip Blundell wrote:
>>The -fomit-frame-pointer is just for optimization.  The -fno-exceptions
>>-fno-rtti is NECESSARY because of the broken exception handling in
>>the ARM egcs compiler.  In addition, exceptions blimps out the binaries
>
>Is this exception handling still broken in the current sources?  If so, I will 
>see if I can fix it for gcc 2.95 so long as you can provide a testcase.
>
>p.
>

Haven't tried it lately, but when I built KDE 1.1 for the netwinder, it was.
Does the current gcc implement range table exception handling for
StrongARM yet (and all the associated DWARF2 stack unwinding
stuff) or must we still use setjmp/longjmp?  If so, exception handling
makes the C++ code so terrible it's best to leave it off.

- --
Jon Olson, Modular Mining Systems
	   3289 E. Hemisphere Loop
	   Tucson, AZ 85706
INTERNET:  [email-masked]
PHONE:     (520)746-9127
FAX:       (520)889-5790
- --
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel" as the body of your message.

------------------------------

Date: Wed, 19 May 1999 20:35:15 +0100
From: Philip Blundell <[email-masked]>
Subject: Re: KDE 1.1.1 anyone? 

>Does the current gcc implement range table exception handling for
>StrongARM yet (and all the associated DWARF2 stack unwinding
>stuff) or must we still use setjmp/longjmp?  If so, exception handling
>makes the C++ code so terrible it's best to leave it off.

To be honest, I'm not sure.  I will try to find out.  GCC does know how to 
generate Dwarf2 tables for ARM nowadays (eg if you use -gdwarf-2) but I don't 
know whether you have to do anything more to use them for exception purposes, 
or if higher intelligences within the compiler cause this to "just work".

Regardless it would be interesting to know whether setjmp/longjmp exceptions 
do actually work with the current gcc sources.  There were problems related to 
threading at one point but I believe they've been fixed.  Scott may be able to 
say more.

p.

- --
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel" as the body of your message.

------------------------------

Date: Wed, 19 May 1999 20:47:10 +0100
From: Philip Blundell <[email-masked]>
Subject: Re: KDE 1.1.1 anyone? 

>Does the current gcc implement range table exception handling for
>StrongARM yet (and all the associated DWARF2 stack unwinding

I just looked at this.  The answer is currently no and it's not obvious to 
me right away what would need to be done to make it so.  I think that defining 
INCOMING_RETURN_ADDR_RTX might suffice to convince gcc that Dwarf2 unwind 
*should* work (and make it the default) but of course theory and practice are 
sometimes rather different.

If you want to give it a go, try adding to config/arm/arm.h something like

/* Take the return address from the link register.  */
#define INCOMING_RETURN_ADDR_RTX  gen_rtx_REG (Pmode, 14)

I'd be interested to hear what happens, even if the result is complete 
and utter devastation. :-)

p.

- --
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel" as the body of your message.

------------------------------

Date: Wed, 19 May 1999 19:22:57 -0400
From: "Andrew E. Mileski" <[email-masked]>
Subject: Re: DM-13 trouble is DM 14 ..

> >That said, I don't recommend build 14 for general use.  Hence it wasn't
> >announced, and is not in the official image area of the ftp site.
>
> I still wonder why my /proc does not work.
> I even tried a different kernel.

Me too...it's really weird.  Your the first to report that.

> Well, I will try to find the reason.
> I noticed that there is a message that /proc might be wrongly mounted.
> can't really say I understand how.
> 
> I replaced the insmod binary, now insmod works...

That's equally weird, as insmod works fine on my 3 systems which
are all build 14.

- --
Andrew E. Mileski - Software Engineer [OS Team Leader]
Rebel.com  http://www.rebel.com/
- --
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel" as the body of your message.

------------------------------

End of devel-digest V2 #175
***************************

--
This list is run automagically by Majordomo 1.94.4
Please send email questions to [email-masked]
To UNSUBSCRIBE: email [email-masked] with
"unsubscribe devel-digest" as the body of your message.