mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] migrating a BSP from 2012.03.0 to 2019.03.1 , building kernel module for linux-3.0.35
Date: Wed, 24 Apr 2019 09:49:07 +0200	[thread overview]
Message-ID: <67597906-3159-f0c8-2cb9-b124c95c8bc6@pengutronix.de> (raw)
In-Reply-To: <DM6PR02MB597737AAC1EB0DCA5EB65D68FD230@DM6PR02MB5977.namprd02.prod.outlook.com>

Hello Patrick,

On 23/4/19 19:01, Patrick Murray wrote:
> Hi ,
> 
> I am getting this include error while building a kernel module after migrating from BSP 2012.03.0 to 2019.03.1 .
> 
> What's the easiest route to proceed .
> 
> Regards
> P.
> 
> -D"KBUILD_BASENAME=KBUILD_STR(bounds)"  -D"KBUILD_MODNAME=KBUILD_STR(bounds)" -fverbose-asm -S -o kernel/bounds.s kernel/bounds.c
> In file included from include/linux/compiler.h:48:0,
>                  from include/linux/stddef.h:4,
>                  from include/linux/posix_types.h:4,
>                  from include/linux/types.h:17,
>                  from include/linux/page-flags.h:8,
>                  from kernel/bounds.c:9:
> include/linux/compiler-gcc.h:94:30: fatal error: linux/compiler-gcc5.h: No such file or directory

GCC 5.x was released 2015, while Linux 3.0.35 you attempt to build came out in 2012.

Your options are (in the order I would suggest):
- update your kernel to one that supports GCC 5.x (and preferably still gets bug fixes)
- using an older toolchain for the kernel
- transplant GCC 5.x support into your 3.0.35 kernel (just copying the header isn't enough, you
  must verify that you don't miss any other gcc 5.x specific patches)

Cheers
Ahmad

> compilation terminated.
> make[2]: *** [/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/platform-phyFLEX-i.MX6/build-target/linux-3.0.35/./Kbuild:36: kernel/bounds.s] Error 1
> make[1]: *** [Makefile:985: prepare0] Error 2
> make[1]: Leaving directory '/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/platform-phyFLEX-i.MX6/build-target/linux-3.0.35'
> make: *** [/opt/lib/ptxdist-2019.03.1/rules/kernel.make:178: /opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/platform-phyFLEX-i.MX6/state/kernel.compile] Error 2
> dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4$
> dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4$ gcc --version
> gcc (Ubuntu 8.2.0-7ubuntu1) 8.2.0
> Copyright (C) 2018 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4$ uname -r
> 4.18.0-17-generic
> dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4$
> dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4$ ptxdist print PATH
> /opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/platform-phyFLEX-i.MX6/sysroot-host/bin:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/platform-phyFLEX-i.MX6/sysroot-host/sbin:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/selected_toolchain:/opt/lib/ptxdist-2019.03.1/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/opt/bin
> dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4$
> dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4$ ^C
> dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4$ ptxdist toolchain
> found and using toolchain:
> '/opt/OSELAS.Toolchain-2016.06.0/arm-v5te-linux-gnueabi/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/bin'
> 
> dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4$
> dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4$<mailto:dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4$>
> 
> dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/platform-phyFLEX-i.MX6/build-target/linux-3.0.35/include$ find . -name compiler*.h
> ./linux/compiler.h
> ./linux/compiler-gcc.h
> ./linux/compiler-intel.h
> ./linux/compiler-gcc4.h
> ./linux/compiler-gcc3.h
> dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/platform-phyFLEX-i.MX6/build-target/linux-3.0.35/include$<mailto:dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/platform-phyFLEX-i.MX6/build-target/linux-3.0.35/include$>
> 
> 
> This email and any attachments may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication or any of its contents is strictly prohibited. If you are not the named recipient, or have otherwise received this communication in error, please delete it from your inbox, notify the sender immediately, and do not disclose the contents to any other person or use them for any purpose, or store them in any medium. Thank you for your cooperation.
> 
> 
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2019-04-24  7:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 17:01 Patrick Murray
2019-04-24  7:49 ` Ahmad Fatoum [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=67597906-3159-f0c8-2cb9-b124c95c8bc6@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox