From mint-bounce@lists.fishpool.fi Wed Jan 27 17:57:06 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=lJuH5kT3pA2HO2hERam2qr7DoNdGYnpMWhaVFz7Mvtk=; b=cU8AVTNxyclKZY3B7jNcKBZQaSjDJks88CeCz0q0Ufz6xrm0OzkusbJkP0fKUWBewA Mayy/47Hic7pT5TLI1ij3oM2JVCoG74HdI+nwrBpVRnGPMXxaBzKRD6eztcq4m9cFaY5 Nd37BAtM+DrRhvi/pMlcg/CYSoiGDcXeCkMa8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=mrviG1EZwHdHbLM8nWInckp+jwxBGGn9jFJ2nuMDB+xxjL6U6ZI+ELViPeucVqewNv RQkztfUutz9qf/t6XmO+hfhz9f0Sfl9809x00iED7FRJ7B2ifL+xw58LxE9lysII+liS AFBN8seOE688BnuLOhaZ1UeAB3v6dlZpcFfdw= MIME-Version: 1.0 In-Reply-To: <4B60C22C.1010204@abbuc.de> References: <4B60C22C.1010204@abbuc.de> Date: Wed, 27 Jan 2010 23:55:07 +0100 Message-ID: Subject: Re: [MiNT] Correct steps after installing EasyMiNT From: Miro Kropacek To: Stefan Niestegge Cc: mint@lists.fishpool.fi Content-Type: multipart/alternative; boundary=000325559c4a3efef4047e2d4b6e X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: miro.kropacek@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: --000325559c4a3efef4047e2d4b6e Content-Type: text/plain; charset=ISO-8859-1 > Which post-installation steps would you recommend to get a working setup > for compiling > stuff? There are for sure the 2.20 binutils and the gcc 4.4.2 to install, > also mintlib. > But is gcc 4.4.3 good for me already? Should i ask Mark for his updated > rpms? > As you say, fresh mintlib and gcc/binutils are the must. I think 4.4.2 is enough, there's nothing special in 4.4.3. Apropo, what about binary release of mintlib 0.59? I've done it for myself (thanks to my patches =) but some official build wouldn't hurt. > But there are also some updates that i am not sure whether they help or > hurt. > And a messed up install with wild trial and error installs i already had. > Was no fun. > First rule: always install into /usr/local -- then, if you something mess up, you're free to type "rm -rf /usr/local" and you're OK (no need to worry about file structure, every "make install" creates directories if necessary). Second rule: don't forget to set PATH to point first into /usr/loca/bin :) (for example in .bashrc) And last, it depends on what you want to build... most of GNU software requires newer autotools, texinfo etc packages (available from Keith for some time or you can build it by yourself, mostly "./configure && make && make install" kind of work) ... SDL library (available from Patrice or again, make your own build) is helpful for porting things ... as I say, it varies a lot. And of course, if you don't plan to build anything (or kernel only) you don't need any update -- kernel does not link against mintlib (or any other lib except libgcc). -- MiKRO / Mystic Bytes http://mikro.atari.org --000325559c4a3efef4047e2d4b6e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Which post-installation steps would you recommend to get a working setup fo= r compiling
stuff? There are for sure the 2.20 binutils and the gcc 4.4.2 to install, a= lso mintlib.
But is gcc 4.4.3 good for me already? Should i ask Mark for his updated rpm= s?
As you say, fresh mintlib and gcc/binutils are the = must. I think 4.4.2 is enough, there's nothing special in 4.4.3.

Apropo, what about binary release of mintlib 0.59? I've done it for= myself (thanks to my patches =3D) but some official build wouldn't hur= t.
=A0

--
MiKRO / Mys= tic Bytes
http://mikro.atari.org
--000325559c4a3efef4047e2d4b6e--