From: "Sourav K. Mandal" <sourav.mandal@gmail.com>
To: gentoo-gnustep@lists.gentoo.org
Subject: Re: [gentoo-gnustep] Re: Help with gnustep
Date: Thu, 02 Aug 2007 10:57:18 -0700 [thread overview]
Message-ID: <1186077438.13486.87.camel@localhost> (raw)
In-Reply-To: <eb806add0708020918j115d01cdo815701d61216be77@mail.gmail.com>
[quote snipped]
Comments:
* I would be nervous to use the ~x86 keyword except for specific
packages at a high-level. The reason it takes a while for things to get
into x86 is because there are obscure bugs which can affect obscure
setups -- unfortunately, GNUstep is in this category. A small bug in
the toolchain can screw up everything else on top of it. At a minimum,
I would revert to gcc-4.1 and glibc-2.5 in x86.
* Consider adding "-ggdb" to your C(XX)FLAGS, and "splitdebug" to your
features. Compilation will produce gdb-compatible debugging symbols,
but they'll be split off into /usr/lib/debug to reduce loading times for
binaries. This works for ObjC/GNUstep; if you are serious about
debugging, do this.
* You have a ton of USE flags. The more intricate/featureful your
system, the more likely you are to get weird bugs. Consider paring it
down to exactly what you need.
Good luck,
Sourav
--
Sourav K. Mandal
http://sourav.net/
PGP: 7E7E 14CD A983 484C 8A43 55CA DBAC 539C 1814 3DAF
--
gentoo-gnustep@gentoo.org mailing list
next prev parent reply other threads:[~2007-08-02 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 3:20 [gentoo-gnustep] Help with gnustep Luis Felipe Strano Moraes
2007-08-02 3:24 ` [gentoo-gnustep] " Luis Felipe Strano Moraes
2007-08-02 9:33 ` Sourav K. Mandal
2007-08-02 16:18 ` Luis Felipe Strano Moraes
2007-08-02 17:57 ` Sourav K. Mandal [this message]
2007-08-02 19:34 ` Luis Felipe Strano Moraes
2007-08-02 19:44 ` Luis Felipe Strano Moraes
2007-08-04 19:24 ` Sourav K. Mandal
2007-08-04 20:22 ` Luis Felipe Strano Moraes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1186077438.13486.87.camel@localhost \
--to=sourav.mandal@gmail.com \
--cc=gentoo-gnustep@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox