Outreachy Linux Kernel Community
 help / color / mirror / Atom feed
From: Sumitra Sharma <sumitraartsy@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: outreachy@lists.linux.dev
Subject: Re: Unable to find module location
Date: Sat, 18 Mar 2023 05:15:08 -0700	[thread overview]
Message-ID: <20230318121508.GA37278@sumitra.com> (raw)
In-Reply-To: <ZBWA3rb9nVP8ho05@debian.me>

On Sat, Mar 18, 2023 at 04:14:06PM +0700, Bagas Sanjaya wrote:
> On Sat, Mar 18, 2023 at 01:40:48AM -0700, Sumitra Sharma wrote:
> >   │ Symbol: NVEC_PAZ00 [=n]                                                                                          │
> >   │ Type  : tristate                                                                                                 │
> >   │ Defined at drivers/staging/nvec/Kconfig:45                                                                       │
> >   │   Prompt: Support for OEM specific functions on Compal PAZ00 based devices                                       │
> >   │   Depends on: STAGING [=y] && MFD_NVEC [=n] && LEDS_CLASS [=y]                                                   │
> 
> Hi,
> 
> MFD_NVEC depends on ARCH_TEGRA, which requires arm64
> (aarch64-*-linux-gnu) cross-compiler. If don't have it yet, you can
> build one with crosstool-NG. When the cross-compiler have been successfully
> built and installed, add <cross-compiler prefix>/bin to PATH.
> 
> Now in order to cross-compile the kernel (to arm64 in this case),
> you need to pass `ARCH=arm64 and CROSS_COMPILE=aarch64-<vendor>-linux-gnu-`
> to each invocation of `make`.
>

HI,

I tried your way. Build and Install aarch64-linux-gnu-gcc, added the
path and run the command 'make -j2 ARCH=arm
CROSS_COMPILE=aarch64-linux-gnu-'

But receiving these errors.

aarch64-linux-gnu-gcc: error: unrecognized argument in option ‘-mabi=aapcs-linux’
aarch64-linux-gnu-gcc: note: valid arguments to ‘-mabi=’ are: ilp32 lp64
  CC      scripts/mod/devicetable-offsets.s
aarch64-linux-gnu-gcc: error: unrecognized command line option ‘-mapcs’
aarch64-linux-gnu-gcc: error: unrecognized argument in option ‘-mabi=aapcs-linux’
aarch64-linux-gnu-gcc: note: valid arguments to ‘-mabi=’ are: ilp32 lp64
aarch64-linux-gnu-gcc: error: unrecognized command line option ‘-mno-sched-prolog’
aarch64-linux-gnu-gcc: error: unrecognized command line option ‘-mtp=cp15’
aarch64-linux-gnu-gcc: error: unrecognized command line option ‘-mfpu=vfp’
aarch64-linux-gnu-gcc: error: unrecognized command line option ‘-msoft-float’
make[1]: *** [scripts/Makefile.build:252: scripts/mod/empty.o] Error 1
make[1]: *** Waiting for unfinished jobs....
aarch64-linux-gnu-gcc: error: unrecognized command line option ‘-mapcs’
aarch64-linux-gnu-gcc: error: unrecognized command line option ‘-mno-sched-prolog’
aarch64-linux-gnu-gcc: error: unrecognized command line option ‘-mtp=cp15’
aarch64-linux-gnu-gcc: error: unrecognized command line option ‘-mfpu=vfp’
aarch64-linux-gnu-gcc: error: unrecognized command line option ‘-msoft-float’
make[1]: *** [scripts/Makefile.build:114: scripts/mod/devicetable-offsets.s] Error 1
make: *** [Makefile:1286: prepare0] Error 2


Regards,

Sumitra


> Thanks.
> 
> -- 
> An old man doll... just what I always wanted! - Clara



  reply	other threads:[~2023-03-18 12:15 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-18  8:40 Unable to find module location Sumitra Sharma
2023-03-18  9:13 ` Deepak R Varma
2023-03-18 13:02   ` Sumitra Sharma
2023-03-18 16:08     ` Deepak R Varma
2023-03-19  8:45       ` Sumitra Sharma
2023-03-20  9:19         ` Deepak R Varma
2023-03-20 10:02           ` Sumitra Sharma
2023-03-20 10:16             ` Deepak R Varma
2023-03-20 10:21               ` Deepak R Varma
2023-03-22  4:12                 ` Sumitra Sharma
2023-03-18  9:14 ` Bagas Sanjaya
2023-03-18 12:15   ` Sumitra Sharma [this message]
2023-03-18 12:34     ` Bagas Sanjaya
2023-03-18 12:49       ` Sumitra Sharma
2023-03-18 13:01         ` Bagas Sanjaya
2023-03-18 17:57           ` Sumitra Sharma
2023-03-19  2:08             ` Bagas Sanjaya
2023-03-19  8:32               ` Sumitra Sharma
2023-03-19  8:40                 ` Julia Lawall
2023-03-19  8:56                   ` Julia Lawall
2023-03-19 12:10                     ` Sumitra Sharma
2023-03-19 12:36                       ` Julia Lawall
2023-03-20  8:46                         ` Sumitra Sharma
2023-03-20  8:56                           ` Julia Lawall
2023-03-20  8:59                           ` Bagas Sanjaya
2023-03-20  9:04                             ` Julia Lawall
2023-03-20  9:03                           ` Julia Lawall
2023-03-20  9:53                             ` Sumitra Sharma
2023-03-20 13:04                               ` Julia Lawall
2023-03-22  4:10                                 ` Sumitra Sharma

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=20230318121508.GA37278@sumitra.com \
    --to=sumitraartsy@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=outreachy@lists.linux.dev \
    /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