[Asterisk-Dev] Sparc Ultra Support

[dking at pimpsoft.com]

I suspect its also due to marketing that they didn't want you to do 
it. As it is the makefile system is geared to work best on AMD based 
i686 compatible chips and hates anything else.

You could even have the makefile run the autoconf system under the 
hood. Sure would be better then the pages of #ifdef code I had to 
suffer with.

I really don't see why not knowing how to use something is the issue, 
from the build system it shows very plainly that the person who 
started it had no idea what they where doing so it should not be that 
hard to work something that helps it be more portable. Most of the 
compiler problems I have seen are due to the build system being 
incompatible with porting, and starting with a autoconf system would 
let us be rid of these problems for good.

Just submit a patch for the makefiles that takes out all the crap and 
replaces it with the good stuff using the same basic calls to make if 
your offering, if your not then I may just read the docs and do it 
myself. Being too much of a baby to read the manual is no excuse to 
stop innovation and I would really like to know who told you ‘no’.

Just because someone is ignorant of something and is scared of 
learning doesn't mean these problems need to continue to exist if a 
fix can be had, in my humble opinion.

And remember this is open source, gnu tools are a part of the 
package.

<on soapbox>
Come on people,  WE ARE DEVELOPERS NOT SCRIPT KIDDIOTS! Don't be 
afraid of something you don't understand, just read the docs/ask 
questions and gain enlightenment, after all that's what the manual is 
for! 
</on soapbox>

*jumps down*
*stubs toe and falls*
*skins knees*
*falls on face*
*cough* *cough*

Ok I'm done now.

On 23 Sep 2004 at 19:02, Chris Albertson wrote:

> 
> 
> I offered to re-write the Asterisk build system using GNU
> "auto toola", autoconf and the like.  This would solve
> the problem once and for all.  But the powers that be
> basically said "I don't understand GNU autotools and
> don't want to learn."  Amazing how people will be happy
> to maintain such rubish as 100 nested #ifdefs if it
> saves then bit bit of RTFM.  I'd personally like to see
> Asterisk runing a SPARC/Solaris 
> but would not even think of attempting it with a 
> hand built Makefile.  But using the GNU tools (automake,
> autoconf and libtool) it's almost
> triveal to get my stuff to build on all four combinations
> of i386, Sparc, Linux and Solaris.
> 
> 
> > ifneq (${OSARCH},Darwin)
> > ifneq (${PROC},x86_64)
> > ifneq (${PROC},ultrasparc)
> > ifneq ($(shell uname -m),ppc)
> > ifneq ($(shell uname -m),alpha)
> > OPTIMIZE+=-march=$(PROC)
> > endif
> > endif
> > endif
> > endif
> > endif
> > 
> > It's clear that people have no idea what they're doing and are just
> > blindly adding gcc flags that they found from some unrealiable site
> > on the web that says it will give them a huge performance boost.
> > There are cases of -O4 and -O6 optimization levels in the Asterisk
> > Makefiles.  These don't even do anything.  -O3 is the highest
> > optimization level.  I have never seen a large *reliable*
> > performance boost from mucking w/all these platform specific
> > optimizations.  In fact, by removing -mtune -march, -O3, -O4, -O6,
> > etc. I have compiled Asterisk on:
> > 
> 
> =====
> Chris Albertson
>   Home:   310-376-1029  chrisalbertson90278 at yahoo.com
>   Cell:   310-990-7550
>   Office: 310-336-5189  Christopher.J.Albertson at aero.org
>   KG6OMK
> 
> 
> 		
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - Send 10MB messages!
> http://promotions.yahoo.com/new_mail 
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>