All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "João Costa" <joaocostalapin@gmail.com>, xenomai@xenomai.org
Subject: Re: error: implicit declarations while compiling (xenomai3.1+ubuntu20.04)
Date: Wed, 26 May 2021 07:02:58 +0200	[thread overview]
Message-ID: <a8412431-ccfb-dcc9-dfba-2da5374bcf1a@siemens.com> (raw)
In-Reply-To: <CAB9YM8jgdbEYTB8Sb7212KWcLEkRDSVjEYZ8P2qCCStaX9CuPQ@mail.gmail.com>

On 25.05.21 20:03, João Costa via Xenomai wrote:
> Hello,
> 
> I am having some problems with a fresh install of Xenomai 3.1 and I was
> hoping that someone could help me out solving those
>  or by sharing some installation instructions for dummies.
> 
> *Test bench configuration:*
> -Ubuntu server 20.04.2 running kernel 5.4.0-73-generic
> -Xenomai version 3.1
> -Kernel downloaded for patch/installation: linux-5.4.77.tar.gz (since I
> could not find an exact match with ipipe patch and the kernel already
> running)
> -ipipe-core-5.4.77-x86-2.patch
> 
> *I am following this instructions:*
> - https://www.programmersought.com/article/14375437246/
> - had the need to install/change some packages " gcc libncurses-dev flex
> bison openssl libssl-dev dkms libelf-dev libudev-dev libpci-dev
> libiberty-dev build-essential kernel-package"
> - assumed that where is written:
> $makeolddefconfig
> it should be
> $make oldconfig
> 
> *I am getting the following errors:*
> *after running* " CONCURRENCY_LEVEL=8 make-kpkg  --rootcmd fakeroot
> --initrd  --revision=1.0.0 kernel_image kernel_headers "
> *#1*
> 
>> kernel/ipipe/core.c: In function ‘__ipipe_spin_lock_irqsave’:
>> kernel/ipipe/core.c:547:9: error: implicit declaration of function
>> ‘arch_mangle_irq_bits’ [-Werror=implicit-function-declaration]
>>   547 |  return arch_mangle_irq_bits(s, flags);
>>       |         ^~~~~~~~~~~~~~~~~~~~
>>   CC      kernel/sched/cputime.o
>>
> *#2*
> 
>> kernel/ipipe/core.c: In function ‘__ipipe_spin_unlock_irqrestore’:
>> kernel/ipipe/core.c:574:7: error: implicit declaration of function
>> ‘arch_demangle_irq_bits’; did you mean ‘arch_early_irq_init’?
>> [-Werror=implicit-function-declaration]
>>   574 |  if (!arch_demangle_irq_bits(&x))
>>       |       ^~~~~~~~~~~~~~~~~~~~~~
>>       |       arch_early_irq_init
>>
> *#3*
> 
>>  arch/x86/kernel/process.c: In function ‘mwait_idle’:
>> arch/x86/kernel/process.c:699:4: error: implicit declaration of function
>> ‘__ipipe_halt_root’; did you mean ‘ipipe_test_root’?
>> [-Werror=implicit-function-declaration]
>>   699 |    __ipipe_halt_root(1);
>>       |    ^~~~~~~~~~~~~~~~~
>>       |    ipipe_test_root
> 
> cc1: some warnings being treated as errors
>>
> 
> 
>> make[3]: *** [scripts/Makefile.build:266: arch/x86/kernel/process.o] Error
>> 1
>> make[2]: *** [scripts/Makefile.build:500: arch/x86/kernel] Error 2
>> make[1]: *** [Makefile:1729: arch/x86] Error 2
> 
> 
>  make[1]: *** [Makefile:1729: kernel] Error 2
> 
> 
> *Notes:*
> - I am not sure it my answers when executing the $make oldconfig were the
> correct ones and/or can be related to these problems
> - Also, the checks/unchecks in the kernel menu ($menuconfig) are not
> exactly like the ones on those instructions since there are items that do
> not appear or are enabled/embedded by default and cannot be unselected
> 

Strange. There was either a problem with patching the kernel (you can
cross-check by downloading a prepatched one from [1]), or you found a
.config that exposes a build error (then please share it).

Jan

[1] https://source.denx.de/Xenomai/ipipe-x86

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux


  reply	other threads:[~2021-05-26  5:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 18:03 error: implicit declarations while compiling (xenomai3.1+ubuntu20.04) João Costa
2021-05-26  5:02 ` Jan Kiszka [this message]
2021-05-27 11:52   ` João Costa
2021-05-27 12:01     ` Jan Kiszka
2021-05-27 12:17       ` Jan Kiszka
2021-05-27 14:26         ` João Costa
2021-05-31 15:46           ` João Costa

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=a8412431-ccfb-dcc9-dfba-2da5374bcf1a@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=joaocostalapin@gmail.com \
    --cc=xenomai@xenomai.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.