All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results
Date: Thu, 28 Aug 2014 09:52:17 -0300	[thread overview]
Message-ID: <20140828125217.GA3389@arch.cereza> (raw)
In-Reply-To: <20140825181614.3f5c22a0@free-electrons.com>

(Ccing Frank)

On 25 Aug 06:16 PM, Thomas Petazzoni wrote:
> >      nios2 |              util-linux-2.24.2 | NOK | http://autobuild.buildroot.net/results/fd30974bf2f976c600717268ce340f73d48dda34/
> 
> sys-utils/prlimit.o: In function `main':
> prlimit.c:(.text.startup+0x440): undefined reference to `prlimit64'
> prlimit.c:(.text.startup+0x5d0): undefined reference to `prlimit64'
> collect2: error: ld returned 1 exit status
> 
> Ezequiel, an idea?
> 

This is probably the same missing fallocate64 deal. The function is simply not
available, yet detected (Frank: please correct me if I'm wrong).

By doing something similar to what we do for e2fsprogs:

+ifeq ($(BR2_nios2),y)
+UTIL_LINUX_CONF_ENV += ac_cv_func_prlimit=no
+endif
+

I can avoid the SYS_prlimit64 usage. However, we then get conflicting types:

  CC       sys-utils/prlimit.o
  CC       sys-utils/lscpu.o
sys-utils/prlimit.c:139:12: error: conflicting types for 'prlimit'
In file included from /home/zeta/buildroot/buildroot-nios2/output/host/usr/nios2-buildroot-linux-gnu/sysroot/usr/include/sys/resource.h:25:0,
                 from sys-utils/prlimit.c:28:
/home/zeta/buildroot/buildroot-nios2/output/host/usr/nios2-buildroot-linux-gnu/sysroot/usr/include/bits/resource.h:313:12: note: previous declaration of 'prlimit' was here

I wonder if anyone has an idea to disable the prlimit build, and all the
commands that depend on it.

Notice that we have a similar issue on other packages, but the proposed
solution's have been too hacky to be accepted:

http://lists.busybox.net/pipermail/buildroot/2014-May/096203.html
-- 
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

  parent reply	other threads:[~2014-08-28 12:52 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-25  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-08-24 Thomas Petazzoni
2014-08-25 16:16 ` [Buildroot] Analysis of build results Thomas Petazzoni
2014-08-25 16:26   ` Phil Eichinger
2014-08-25 17:47     ` Thomas Petazzoni
2014-08-25 21:07   ` Peter Korsgaard
2014-08-25 21:13   ` Jörg Krause
2014-08-26  6:17   ` Alexander Lukichev
2014-08-28 12:52   ` Ezequiel Garcia [this message]
2014-08-31 16:58     ` Frank Bergmann
2014-08-31 21:13       ` Ezequiel Garcia
  -- strict thread matches above, loose matches on Subject: below --
2014-08-30  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-08-29 Thomas Petazzoni
2014-08-30  9:07 ` [Buildroot] Analysis of build results Thomas Petazzoni
2014-11-11  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-11-10 Thomas Petazzoni
2014-11-11 22:49 ` [Buildroot] Analysis of build results Thomas Petazzoni
2014-11-11 23:41   ` Gustavo Zacarias
2014-11-12  2:30   ` Nathaniel Roach
2014-11-12 14:09   ` Jörg Krause
2014-11-16 10:07   ` Yann E. MORIN
2014-11-22 11:10   ` Bernd Kuhls
2020-02-19  7:48 [Buildroot] [autobuild.buildroot.net] Daily results for 2020-02-18 Thomas Petazzoni
     [not found] ` <20200220034343.2370e4e4@windsurf>
2020-02-20 13:36   ` [Buildroot] Analysis of build results Giulio Benetti
2020-02-21  8:23   ` Romain Naour
     [not found]   ` <94c8edad-773d-2b36-5daf-b6ee60dd747f@micronovasrl.com>
     [not found]     ` <3e7b016b-eca6-b768-3fca-8fd7e44d0299@micronovasrl.com>
     [not found]       ` <20200220190807.505b4fb2@windsurf>
     [not found]         ` <00751b5d-ca05-fe42-0e9b-6a1005a09e6d@micronovasrl.com>
     [not found]           ` <20200220192344.03785f04@windsurf>
     [not found]             ` <bcc10a0e-c54e-5b75-9b77-8922b85a925a@micronovasrl.com>
     [not found]               ` <fe7d07df-71a0-e317-6b91-ade479545ec4@smile.fr>
     [not found]                 ` <28258465-4f79-3f47-189d-bb066b0aa9f7@micronovasrl.com>
2020-02-22 19:10                   ` Romain Naour
2020-02-22 19:44                     ` Giulio Benetti
2020-02-22 21:11                       ` Fabrice Fontaine
2020-02-22 21:48                         ` Giulio Benetti
2020-02-22 22:00                           ` Fabrice Fontaine
2020-02-22 23:48   ` Romain Naour
2020-02-27  9:31 [Buildroot] [autobuild.buildroot.net] Daily results for 2020-02-26 Thomas Petazzoni
2020-02-27 22:49 ` [Buildroot] Analysis of build results Thomas Petazzoni
2020-02-27 23:06   ` Max Filippov
2020-02-27 23:18   ` Giulio Benetti
2020-02-28  8:03     ` Thomas Petazzoni
2020-02-28 18:06     ` Giulio Benetti
2020-02-28  6:21   ` Heiko Thiery
2020-02-28  7:56     ` Sergio Prado
2020-02-28  8:01     ` Thomas Petazzoni
2020-02-28  7:32   ` Romain Naour
2020-02-28 15:02     ` Peter Seiderer
2020-02-29 21:15       ` Romain Naour
2020-02-29 23:17         ` Peter Seiderer

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=20140828125217.GA3389@arch.cereza \
    --to=ezequiel.garcia@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.