All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Fwd: statically built libuuid?
Date: Wed, 30 Mar 2016 10:59:07 -0300	[thread overview]
Message-ID: <56FBDBAB.3040302@zacarias.com.ar> (raw)
In-Reply-To: <CAK7rcp-pi4VgM8oWyep_GCVT5UVuiA6qm_LbdT16dJZd_2v38g@mail.gmail.com>

On 30/03/16 10:53, Kenneth Adam Miller wrote:

> I have a custom package that depends on BR2_PACKAGE_UTIL_LINUX_UUIDD,
> which we have correct selected and built. I can see libuuid.so in my
> output directory when I do a find, but when I go to compile, adding in
> any directory that libuuid could possibly be in, the compiler says:
>
> ld: cannot find -luuid
>
> Which is irritating. I have the --static flag on to my compiler, so I
> wonder if that might be the problem. I didn't see libuuid.a in my output
> directory for my bzImage, so I think that that is the problem. If I take
> away the --static flag, compilation succeeds just fine. But I have to
> compile my targets statically, it won't work any other way.

Hi.
Did you enable static-only or static/shared library builds in build options?
Because the default is to build shared-only, hence not having a static 
libuuid.a is expected.
Regards.

      reply	other threads:[~2016-03-30 13:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAK7rcp9og0N_merFniFx=ucrebUUONhkKZ3Ao919Ks46813vFg@mail.gmail.com>
2016-03-30 13:53 ` [Buildroot] Fwd: statically built libuuid? Kenneth Adam Miller
2016-03-30 13:59   ` 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=56FBDBAB.3040302@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 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.