[Slackbuilds-users] virtualbox-ose (3.0.4) on x86_64
Eric Hameleers (SBo)
alien at slackbuilds.org
Sun Sep 13 20:14:29 UTC 2009
Murat D. Kadirov schreef:
> On Thu, Sep 03, 2009 at 08:56:02PM +0200, Eric Hameleers (SBo) wrote:
>> Murat D. Kadirov schreef:
>>> On Thursday 03 September 2009 03:57:36 Heinz Wiesinger wrote:
>>>> If I understood Eric's multilib setup correctly, running this prior to
>>>> building virtualbox will result in virtualbox trying to build a 32bit
>>>> binary on a 64bit system, which is not what we (I) want. VirtualBox needs
>>>> 32bit- compat libs available in the system to build a *64bit* package (that
>>>> won't run on a 32bit system).
>>> I am working on 32-bit multilibs/gcc* slackbuilds for SlackBuilds.org.
>> I am curious as to how you are going to achieve that. Creating a
>> SlackBuild script that builds a multilib gcc requires the presence of
>> both a multilib glibc and a multilib gcc. The process is iterative and
>> you'll need more than just one SlackBuild script.
>> You can try to cheat of course, by first installing a non-Slackware
>> multilib gcc/glibc but then the SlackBuild would not be accepted
>> because it does not work on a vanilla Slackware.
>> Let me know your ideas.
> Hi, Eric!
> I am sorry for so long silence, it took me some time to conquer the Elbrus.
> I was a little bit untimely about my "work". But I have an offer, that
> could be interesting for you. I suppose, creation of some binary
> meta-package special for SlackBuilds.org project would be right and
> convinient decision for many maintainers (for me also, because my
> slackbuilds netkit-* also need it) and users.
> The main idea is that one of motive forces for me and possibly other
> maintainers is the opportunity to use the single repository for all
> other software, which is not distributed in Slackware. Eric, your
> repository is wonderful, so as your articles and how-tos, I often
> return to them. But the main aim of SlackBuilds.org project is in
> creation of single repository for software, which is necessary for
> slackware users, that is why I think, that creation of above-mentioned
> meta-package or something like this is appropriate for users and
> maintainers of SlackBuilds.org resource.
> With all respect,
I have no idea what you mean by "meta package".
But in any case, SlackBuilds.org will not accept binary packages.
We are a repository of SlackBuild _scripts_ that are tested and proven
to compile a working package on Slackware. If the SlackBuild can not
compile a working package on a certain version of Slackware, then the
missing dependencies must also be provided in the form of SlackBuild
scripts that build the packages for these dependencies.
I think that what you want to achieve, is not suited for the
More information about the SlackBuilds-users