[Slackbuilds-users] Is the default ARCH=i486
disturbed1976 at gmail.com
Wed Jan 27 04:06:24 UTC 2010
On Tue, Jan 26, 2010 at 10:39 PM, Matthew Fillpot <mfilpot at gmail.com> wrote:
> On Tue, Jan 26, 2010 at 10:21 PM, Keith Richie <disturbed1976 at gmail.com> wrote:
>> Is there a standard that the default arch should be i486? I raised an
>> issue to the Sbopkg team about exporting ARCH=i486 as I recently came
>> across 2 packages which have the arch set to x86_64 (quesoglc and
>> warzone2100). http://code.google.com/p/sbopkg/issues/detail?id=37 .
>> Quesoglc compiles and installs, but because the libs end up in the
>> wrong location, Warzone fails to build.
>> There's also a similar thread at linuxquestions.org
>> The applications in question are not x86_64 only, and do build
>> correctly when the arch is set to i486 for 32bit machines.
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
> My apologies for those builds, which are mine. I seem to have forgot
> to change it back to 486 after testing it on x86_64. When you
> encountered the issue with the Quesoglc was that because you did not
> change the architecture on the slackbuild file?
> Also, should I submit new builds for these two with that line
> corrected or can someone at SBo make those simple corrections for me?
> -Thank You,
> -Matthew Fillpot
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
No problem. I was hoping since it's a simple edit a member of the team
could handle it.
I was using Sbopkg, and queued up a few items for our newly acquired
32bit machines. Once I edited the SlackBuild all was fine. They build
one x86_64 without problems.
More information about the SlackBuilds-users