flying everywhere! Chipping through the armor, flames are getting through
   ... ooh! FVWM escapes by shedding its modules again, while K is trapped.
   Something's bound to [102]overload... K's gears grind slowly to a halt,
   while Gnome has the [103]metacity to pick on E's [104]incomplete brother
   which valiantly struggles to code up
   href="http://enlightenment.org/pages/news.html">newfeaturesbeforetimeout.
   [105]XFce zooms into the fray -- "wanna piece of me?" Then the commercial
   desktops enter the fray, xig's CDE-like [106]DeXtop rushing forward only to
   wedge in the pit of interoperability. [107]Athene constantly regenerates but
   when the battle gets toe to toe, the obscurity spikes pin it down, the
   [108]theme of the day turns [109]Fvwm's way -- and it looks like we've a
   champion.

   But what's this? The arena has been invaded. Who are these interlopers?
   [110]screen has taken to the field, with [111]twin nipping at its heels. A
   growl from behind, but they squish [112]splitvt together, [113]dtach another
   tiny opponent, then turn back to each other -- only to wail as [114]emacs
   turns its [115]Gnu-like head in their direction, establishing a sessions
   server...

   Is it possible for there to be any more carnage than this? Probably. Seen on
   alt.sysadmin.recovery:

     I am now taking bets on when this planet will reach its window manager
     event horizon. At some distant point in the future some sort of alien
     life-form is going to land on this planet and find everything dead except
     for a lone Sparcstation in an abandoned building waiting for a consignment
     of small lemon-soaked [116]Motif widgets to be loaded.

                                                         -- Peter Gutmann

   Ok, ok. That was overkill. I'm sorry, really sorry that I had to pub late
   this month, but as you can see now, my place is a shambles. But I did find
   something cool while finishing up... hooray! Someone in Ireland actually
   *CAUGHT* a spammer. Better yet, got them [117]hauled away by the cops.
   (Alleged, hah. Caught with everything but a patsy present in person and
   teary-eyed.) Not even April fooling. Enjoy your month, folks. I know I will.

   [NOTE] So that's it. Answers by Jim Dennis, Ben Okopnik, Thomas, Faber, many
   others among The Answer Gang... and you! If you've got some great Linux
   answers - [118]send them to us. Ideally the answers explain why things work
   in a friendly manaer and with some enthusiasm, thus Making Linux Just A
   Little More Fun! Good short bits will probably go in Two Cent Tips, but
   truly juicy explanations, especially those that get the Gnag jumping in,
   could end up here. We don't promise that we'll publish everything, though.
   Also - you can be anonymous, either asking or answering - just tell us so,
   and Tux will eat the herring we wrote your name on. We swear.
            ____________________________________________________

(?) Compile on one, run on another machine

   From Ferenc-Jan 

                                                Answered By: Thomas Adam 

   Hi there! 

   I've got a question that may be of interest to the linuxgazette community.
   Where does one go to find out more about cross compiling? (I'm not even
   sure cross compiling is the correct term for this.) 

     (!)  [Thomas] Cross-compiling refers to compiling applications on a
     computer that is not intended for the same computer because often the
     target computer has a different architecture.

   (?) The case is this: I often want to compile stuff on one machine but run
   it on another. My permanently-in-disrepair, bleedingly fast & incredibly
   messy test system is the machine of choice for compiling all kinds of linux
   stuff. The barely alive, old laptop or the lean & mean firewall box aren't -
   besides, I don't want a full blown gcc environment on those. But I run into
   problems most of the time. 

   Approach A: compile it as per instructions. Then I have to go and find all
   the nitty bitty parts of the package, that are now residing everywhere on
   the  test system's drive. This often fails because missing parts don't
   always generate comprehensible error messages. 

     (!) [Thomas] This is not an approach, this is what usually happens when
     you compile a program.

   (?) Approach B: try to install it to a different directory, i.e. /tmp/ and
   then move it to the other machine. This often founders on hard coded file
   location,    i.e.    when    /tmp/lib/something    is    actually   at
   /usr/local/lib/something (like it should be.) 

     (!) [Thomas] This is dependant upon how ldconfig registers where the
     libraries are (possibly by way of $LD_LIBRARY_PATH).

   (?) I don't consider myself a beginner, but who does. I don't seem to be
   able to google the answer to this problem, but surely I'm not the only one
   running into this? 

   Any hints would be much appreciated, but I understand this must be relevant
   to linuxzgazette before you can spend your time on this. 

     (!) [Thomas] I'm not quite sure what it is you're asking. If it is "how
     can I compile applications such that I can minimise the number of (likely)
     errors",  then  the  answer is to compile it statically so that the
     application doesn't have to go using any external libraries. Thr only
     disadvantage with this is that the resultant binary is often very large.