slackbuild guidance needed
 

First off, thanks to the folks at slackbuilds.org for all their efforts, especially the HOWTOs, FAQ and other very clear docs.

I've succeeded in making a slackbuild for kphotoalbum but have come across conflicting advice.
http://www.slackbuilds.com/guidelines/ tells me to include these lines:
but the tutorial http://www.slackwiki.org/Writing_A_SlackBuild_Script says
Which is preferred?

You know what ARCH you are building it for, right? Or you are building a generic build for using in multiple machines?

The latter - hopefully I won't be only the person to use it :)

I recommend asking this on the SlackBuilds.org mailing list.

Use i486 and add warning it is not intended for i386 use.

Agreed. That is by far the best place for such a question.

But to answer your question (remember my answer isn't the official slackBuilds.org answer), the first code snippet is generally used. Just take a look at a lot of the other slackBuilds and you will see this.

All of them, as far as I know, either by default build for i486 or noarch (unless they repackage binaries). I typically choose i686 for my builds if applicable.

Thanks for the replies.

I did a quick survey of a few slackbuilds from slackbuilds.org and the first snippet is the most common, but of course, that doesn't mean it's the best choice.

I'll go explain to my inbox that I'm joining another mailing list :)

EDIT: Forget what I posted before. I just read Carlos' answer on the mailing list. In short: The first one is preferred, the second makes no sense anymore for Slackware versions > 9.0.

http://lists.slackbuilds.org/piperma...ay/002620.html

You can use your own, will work whatever ARCH is set. Something like this:

march option implies also mtune in recent GCC versions. With GCC-4.2 and newer you can omit it all and just use march=native.

Starting with glibc-2.6, i486 is the minimum supported arch so it really doesn't make a whole lot of sense to build anything else at i386...

I ussually don't even include CFLAGS in my build scripts. I set it globaly on my login shell and then forget about it. Reduces the clutter in your build scripts.

Also, putting -march=native would optimize for your machine only ( -mtune=native is implied). The use of mtune is still as applicable as it's ever been. -march=i486 -mtune=generic would be the better option IMO. If you just want to build for your machine then -march=native is fine.