Hello everyone

My apologies for wasting electrons (doh) for committing a noob mistake.

I've been thinking on terms of CentOS/Redhat == Redsleeve at 100%
compatible.

Never occurred to me for a minute that Raspberry Pi's kernel (3.18.9) is
not the same as the kernel shipped by the upstream vendors.

While the upstream vendors clearly specify that they did not include the
kernel drivers, the developers mentioned that their product are part of the
kernel since 2.6.33 and the Raspberry Pi's kernel does not come from the
upstream vendors.

Sorry for barking up the wrong tree.


Sincere regards and thanks

Maulvi

On Sun, Mar 22, 2015 at 4:35 AM, Maulvi Bakar <[email protected]> wrote:

> Hello Jacco
>
> Thank you for your earlier reply. The new RPMs
> for raspberrypi2-kernel-3.18.9-v7+.2.20150314gitf1b6b1c is working fine.
>
> I was trying to rebuild DRBD 8.4 Packages which I sourced from ELRepo
>
>
> http://elrepo.org/linux/elrepo/el6/SRPMS/drbd84-kmod-8.4.5-2.el6.elrepo.src.rpm
>
> http://elrepo.org/linux/elrepo/el6/SRPMS/drbd84-utils-8.9.1-1.el6.elrepo.src.rpm
>
> While the drbd84-utils rebuilds perfectly, the drbd84-kmod however is
> still having troubles.
>
> My buildlogs are as below along with the spec file -
>
> build-err - http://www.screencast.com/t/BNB3vpHGBu
> build-out - http://www.screencast.com/t/czv9PM1ugGCR
> drbd4-kmod.spec - http://www.screencast.com/t/Bu8wkPzb2U
>
> I am still encountering the same issues as mentioned earlier.
>
> I am speculating that the Raspberry Pi's version of 3.18.9 kernel might
> not be designed for Redhat-styled kernel modules. Hopefully someone can
> clarify this.
>
>
> Sincere regards and thanks
>
> Maulvi
>
> On Sun, Mar 15, 2015 at 9:12 AM, Jacco Ligthart <[email protected]>
> wrote:
>
>>  On 03/15/2015 12:27 AM, Maulvi Bakar wrote:
>>
>>  Hello everyone
>>
>>  I am attempting to rebuild a kmod package for block device
>>
>>  My build-error log spews a bunch of errors.  The first error
>> encountered is as below -
>>
>>  ./arch/arm/include/asm/barrier.h:41:27: error: mach/barriers.h: No such
>> file or directory
>>
>>  From my observation of the contents of
>> "/usr/src/kernels/3.18.9-v7+.1.20150314gitf1b6b1c", specifically in the
>> "arch/arm/", I noticed that there are sub-folders "mach-bcm2708" and
>> "mach-2709".
>>
>>  While "mach-bcm2708" contains an "include" directory, the
>> "mach-bcm2709" did not.
>>
>>  Previous Pi was based on bcm2708 and the newer Pi2 is on bcm2709, hence
>> I think the reason for the new kernel - kernel7.img
>>
>>
>> That's indeed an oops from my side. I forgot to edit this in the spec
>> file for the kernel. Please try the latest version (of 15 mins ago)
>>
>>
>>  While this is a hack, I overcome the error above by transplanting the
>> "bcm2709/include" from ArchLinuxArm's RaspberryPi2 package '
>> http://os.archlinuxarm.org/armv7h/core/linux-raspberrypi-headers-3.18.9-2-armv7h.pkg.tar.xz
>> '.
>>
>>  While the error on barriers.h has gone away, I am still encountering
>> the other errors as listed below -
>>
>>  error: expected identifier or '(' before 'do'
>>  error: expected identifier or '(' before 'while'
>>  error: redefinition of 'kref_sub'
>>  error: redefinition of 'kref_get_unless_zero'
>>
>> This is not enough information to go on for me. What are you building?
>> what gives this error?
>>
>> Jacco
>>
>>
>> _______________________________________________
>> users mailing list
>> [email protected]
>> http://lists.redsleeve.org/mailman/listinfo/users
>>
>>
>
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users

Reply via email to