From: Rob Landley <rob@landley.net>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot fails on powerpc with busybox login.c
Date: Wed, 13 Sep 2006 23:08:51 -0400 [thread overview]
Message-ID: <200609132308.51971.rob@landley.net> (raw)
In-Reply-To: <20060913154433.GC13069@aon.at>
On Wednesday 13 September 2006 11:44 am, Bernhard Fischer wrote:
> On Sun, Sep 10, 2006 at 09:34:47AM -0700, Michael Boutte wrote:
> >Hi,
> >Ever since approximately version 16076 the initial make of buildroot
>
> Sounds like vda's r16075 change to me.
>
> >fails with errors in the busybox/loginutils/login.c as shown in the snip
> >below.
> > CC loginutils/login.o
>
>/home/mike/projects/software/snip875/build-tools/uclibc-4/buildroot/build_powerpc/busybox/loginutils/login.c:
> >In function 'login_main':
>
>/home/mike/projects/software/snip875/build-tools/uclibc-4/buildroot/build_powerpc/busybox/loginutils/login.c:143:
> >warning: implicit declaration of function 'read_or_build_utent'
>
>
> r16112 has a partial fix to make it build again. We (e.g. vda ;) should
> provide empty bodies for read_or_build_utent() and write_utent() if UTMP
> support is disabled. This can go hand in hand with removing the
> pointless forward decls for said functions.
Stick "ALWAYS_INLINE" on 'em when you do, please.
Rob
--
Never bet against the cheap plastic solution.
next prev parent reply other threads:[~2006-09-14 3:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 16:34 [Buildroot] Buildroot fails on powerpc with busybox login.c Michael Boutte
2006-09-13 15:44 ` Bernhard Fischer
2006-09-14 3:08 ` Rob Landley [this message]
[not found] ` <200609141900.12420.vda.linux@googlemail.com>
2006-09-14 17:16 ` Bernhard Fischer
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=200609132308.51971.rob@landley.net \
--to=rob@landley.net \
--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.