From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] setserial fails to build (after uClibc 0.9.30.3 upgrade?)
Date: Sun, 14 Mar 2010 22:42:45 +0100 [thread overview]
Message-ID: <87k4teziju.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4B9CBD6D.6010606@gmail.com> (Paulius Zaleckas's message of "Sun, 14 Mar 2010 12:41:49 +0200")
>>>>> "Paulius" == Paulius Zaleckas <paulius.zaleckas@gmail.com> writes:
Hi,
Paulius> setserial.c: In function ?print_hayesesp?:
Paulius> setserial.c:362: error: storage size of ?esp? isn?t known
Paulius> setserial.c: In function ?set_hayesesp?:
Paulius> setserial.c:378: error: storage size of ?esp? isn?t known
Paulius> setserial.c:384: warning: incompatible implicit declaration of
Paulius> built-in function ?exit?
Paulius> make[1]: *** [setserial] Error 1
Paulius> make[1]: Leaving directory `/home/paulius/buildroot/output/build/setserial-2.17'
Paulius> make: *** [/home/paulius/buildroot/output/build/setserial-2.17/setserial] Error 2
Paulius> Actual problem I see here is not with uClibc, but with setserial.c not including
Paulius> stdlib.h. Due to my very limited time I can't provide fix now...
No, the stdlib.h stuff is only warnings, the error is that it tries to
use a struct hayes_esp_config because the kernel headers on x86 has the
TIOCGHAYESESP ioctl defined in asm/ioctls.h (E.G. on ARM it isn't
defined, and there it builds).
The hayes stuff is for a really ancient driver (which has recently been
removed by Alan Cox).
As far as I can see, this has nothing to do with uClibc - Did you
recently change the kernel headers version?
As for a fix - We could add an #undef TIOCGHAYESESP after include
<linux/serial.h>, but I would like to know when the problem started first.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-03-14 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 10:41 [Buildroot] setserial fails to build (after uClibc 0.9.30.3 upgrade?) Paulius Zaleckas
2010-03-14 21:42 ` Peter Korsgaard [this message]
2010-03-15 7:33 ` Paulius Zaleckas
2010-03-15 14:17 ` Peter Korsgaard
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=87k4teziju.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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.