Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Build errors in libnl
Date: Thu, 12 Sep 2013 08:46:58 -0300	[thread overview]
Message-ID: <5231A9B2.20302@zacarias.com.ar> (raw)
In-Reply-To: <BECCD53EFF877A4F8D909C37120A85375303BD96@CHEWBACCA.connectBlue.local>

On 09/12/2013 06:39 AM, Jonas Ludvigsson wrote:

> I got the following build errors when building ?libnl? (3.2.22):
> 
>  
> 
>   CC     addr.lo
> 
>   CC     nl.lo
> 
>   CC     object.lo
> 
>   CC     utils.lo
> 
>   CC     socket.lo
> 
> addr.c:1027: error: 'AF_RDS' undeclared here (not in a function)
> 
> addr.c:1033: error: 'AF_CAN' undeclared here (not in a function)
> 
> addr.c:1034: error: 'AF_TIPC' undeclared here (not in a function)
> 
> addr.c:1038: error: 'AF_ISDN' undeclared here (not in a function)
> 
> addr.c:1039: error: 'AF_PHONET' undeclared here (not in a function)
> 
> make[3]: *** [addr.lo] Error 1
> 
>  
> 
> I?m quite new to Linux and Buildroot, but as far as I understand my
> configuration is missing something. Any ideas on what it could be?

Ahhh trigger happy version bumping! :)
There's a reason we're sticking with libnl 3.2.21 still, and that's it.
You need a mode modern (snapshot/git) uClibc version with updated
bits/socket.h for it to work, or switch to some other external toolchain
that's up to date, or backport the changes for your current uClibc.
Regards.

      reply	other threads:[~2013-09-12 11:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12  9:39 [Buildroot] Build errors in libnl Jonas Ludvigsson
2013-09-12 11:46 ` Gustavo Zacarias [this message]

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=5231A9B2.20302@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox