I've tried

and after it just 'make' worked.

M kernel is much older:

and I've used --disable-device-mapper because I do not have the library installed.

I suggest to start from scratch (i.e. empty build directory) and use the above command line for configure (just another prefix).

Ubuntu 10.04 Lucid , ( kernel 2.6.32-21 )
cd parted-2.3/ && ./configure --with-readline
( The other mentioned options are included by default ).

No errors.
..

So, again, the distro is Slackware 13.1, but it's modified with a lot of custom packages. This means also the kernel is newer, new kernel headers and so on.

I think one of the packages does this... but which one I dont know.

I've also try to just rebuild the exact packages from Slackware 13.1 repository and fails with the same error.

So I suppose some headers, some place changed and they are not fully compatible with what parted needs... this is what I think, but as Im not a programmer, I have no idea what is screwing this up.

P.S. libc, gcc, make and so on is still Slackware 13.1.

Tried make distclean; ./configure --without-readline; make and still the same error.

This is not what I've suggested - the devil is in the details.

Doesnt really help...

Just tried on my Slackware64 with a 2.6.34 kernel and it compiles just fine.
I guess you've somehow mixed scsi.h provided by the kernel you're using with scsi.h provided by glibc

Crap! First of all... thx, but second, wtf?! Why are they so different?

Crap it worked, I reinstalled glibc and parted 2.3 got compiled. Why ... why!? @#?$@#%@#$%

Ok if glibc contains some scsi files and the linux kernel does also... how do you know... which is good and which is bad!?! How does the guys from Slackware do this packages?!

I guess they are different because glibc headers are used to compile programs, while kernel headers are used when compiling device drivers
I think that it's you that have mixed them, because otherwise kernel headers are located in /usr/src/linux-<kernel-version>/include

Anyway glad to see it worked. You can mark the thread "solved" using the thread tools

Cheers