From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] 2013.02: sysvinit-2.88 build failure undefined reference to -lcrypt
Date: Wed, 13 Mar 2013 01:04:16 +0100 [thread overview]
Message-ID: <513FC280.5040008@mind.be> (raw)
In-Reply-To: <CAG0mjpsiXECXSfAC2_K5GfwMhC76Tws-yw9ygst=_EMRAZG4tA@mail.gmail.com>
On 03/12/13 10:37, Roland Uuesoo wrote:
>
> Sysvinit doesn't build on the following system:
>
> Buildroot: 2013.02
> OS: Ubuntu 12.10 x64
>
> The problem looks very similar to this....
> http://buildroot-busybox.2317881.n4.nabble.com/Bug-2401-New-sysvinit-2-86-fails-to-build-on-MIPS-because-is-missing-lcrypt-td6901.html
>
>
> Compile output is basically the same as the link above:
> sulogin.c:(.text+0xf94): undefined reference to `crypt'
>
> As I understand the problem is this...
>
> sysvinit's makefile can't find libcrypt.a and doesn't add -lcrypt to
> sulogin.c linker options.
>
> On 64bit ubuntu the libcrypt.a is located at
> /usr/lib/x86_64-linux-gnu/libcrypt.a
Wow, it looks like this one has been lingering around ever since
7e2bf630 in December 2010...
It looks like the LCRYPT variable is no longer working. I'll cook up a
patch, but can't really test it since the included makefile works for me.
If my patch works, please reply to it with
Tested-by: Roland Uuesoo <rolandu@gmail.com>
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-03-13 0:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 9:37 [Buildroot] 2013.02: sysvinit-2.88 build failure undefined reference to -lcrypt Roland Uuesoo
2013-03-13 0:04 ` Arnout Vandecappelle [this message]
2013-03-13 0:05 ` [Buildroot] [PATCH] sysvinit: fix linking of sulogin with -lcrypt Arnout Vandecappelle
2013-04-14 21:22 ` 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=513FC280.5040008@mind.be \
--to=arnout@mind.be \
--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