| View previous topic :: View next topic |
| Author |
Message |
ansient Guru


Joined: 22 Jan 2005 Posts: 445 Location: Argentina
|
Posted: Tue Jun 21, 2005 8:18 pm Post subject: |
|
|
| Ateo wrote: | | Who said it's goal was to break debugging? I surely didn't. I short, I said, why use one flag when another one does the same thing? |
And I said the reason is the positive effects, which DO NOT DO THE SAME THING.
Your "does the same thing" is a reference to what they have in common, which is to break debugging.
| Quote: | | Sigh. Again, you're missing my point but that's ok. You're set with your flags and that's fine... Perhaps you have your reasons but why would you ever give those flags to a new linux user? As if they don't already have issues with needing to learn basics you throw in something completely over their heads.... |
It's a well-thought out set of safe flags that is unlikely to cause any issues. It certainly hasn't given me any trouble, and there are other people on these forums who use the same set.
| Quote: | | So if -O overrides the previous (which I did know) why would you need -O flags if the first one is omitted? It just doesn't make sense. |
It makes perfect sense, as I said: http://forums.gentoo.org/viewtopic-p-2513271.html#2513271
| Quote: | | My advice to new users is a short cflag string. I wouldn't want to add any more difficulty for them especially when packages start to not compile. But that's just me... | If you don't know what you are doing, then yes a short cflag string is a good idea. But if you're copying cflags from someone who understands how they work, length is irrelevant. |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|