Hello forum,
Anyone know if the Slackwarearm current supports
hard float?
My hardware is a iMX6q based similar to wandboard,
and I'm looking for a minirootfs that supports harddfloat,
preferably slackware base.

did you see this ? http://www.linuxquestions.org/questi...at-4175512987/

Thanks I read that, I'm hoping the slackwarearm "current" not the 14.1,
will support hard float by default.

No, Slackware ARM is a soft float port. The only way it'd become hard float is if I started from scratch and dropped soft float support, but kept the name "Slackware ARM".
A hard float port would be a separate project and need a separate name such as "ARMhf" or something in the same way that Debian have.

Thank you, that clear things up for me.

I am currently trying to create just that for my beagle bone black. After building the base libraries I am now busy with the toolchain stuff in a multi arch setup. I just need to finish the gcc package to get completly rid of the debian compiler I used for bootstrapping.

There already is a hardfloat arm project btw, it is called armv7hf. However it is a complete port (so no multi arch like tricks) and seems to be a bit dated.

My goal is to have a number of packages that can be installed on an existing slackwarearm resulting in a multiarch setup similar to x86_64 and x86. This way it is not needed to immediatly port all slackware packages to get a functional system. (not everything uses floating point or benefits from it anyway).
I'll post a link as soon as I have a set of packages which can be used without any bootstrapping or tricks.

Please do and thanks.
I've been trying to get a build with the scripts Mr. Hameleers posted here:http://alien.slackbook.org/blog/armport/
but no success yet.

That's an interesting approach - I have not thought of that or heard of anybody else doing it either!

I meant an official port would need to have a different target name. I know Eric's port but the last time I checked, only the base stuff was done -- I didn't realise how many of the packages had been built until I just looked.

It's a lot more than just a base with over 1300 packages done. Right before real life caught up with me, I had Slackware armv7hl running KDE 4.10.2 on my ChromeBook, off a SD card.
There's a hardfloat miniroot here if you want to try that (almost 2 years old but still): http://taper.alienbase.nl/mirrors/al...hl/chromebook/

The first basic set of packages is located here: http://video.vreeken.net/slackingbeagle/

First a disclaimer: USE AT YOUR OWN RISK.
I installed them on a beagle bone black (on top of the slackwarearm mini rootfs and a few packages) so they probably work, but they were not extensivly tested.

Then some hints:
start with a/aaa_base and a/etc and then l/glibc-solibs, this will make sure that any binaries and libs you install after that can be loaded.

There are currently 221 packages based on slackware64-current of march 5t
These packages were choosen because they where either neede as a base, needed to build the toolchain and those I found usefull myself.

Thanks, I'll give it a try.

EDIT:

It's trickier than I thought. I managed to boot the minirootfs
with my cross built kernel 3.10.53.

aaa_base,etc installed ok, but after glibc-solibs installed
it complains about missing libc.so.6. Which I found out
is a symlink created if glibc-2.21 is installed.
Obviously I'm doing something wrong. Is it the order
of installation? or the way I do the installation?
I use upgradepkg when allowed then installpkg if not.

EDIT2:

I managed to get it working, well atleast it didn't
complain anymore about libc.s0.6 . I'm still getting a hang
with mounting "non-root local filesystem" but that's another story,
since I also get that before the upgrade. I installed glibc-solibs last.
This time I didn't upgrade I just installed. I haven't install the x packages yet.
I'll be backing up my sdcard first before going any further just-in-case.

Thanks it's a good starting point.

There is a middle ground that seems to be working quite nicely: softfp. It seems to be compatible with packages compiled for soft, but with the right optimization can provide performance that is not much worse than hard float.

I haven't used upgradepkg yet, I just use installpkg. The only importand order I have to take into account is etc and base before glibc. (To make sure ld actually has the right search path).
Maybe upgradepkg does something different.

From what I understand upgradepkg deletes files first before installing,
it could be that's what happened. I'm most likely wrong.

So far I managed to run xenomai on my board. I'm attempting to make machinekit run on it.
I'm still a long way from making it happen.

It might be a good idea to have patch be part of your d packages, just a thought.