From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2401] New: sysvinit-2.86 fails to build on MIPS because is missing -lcrypt
Date: Wed, 11 Aug 2010 18:55:19 +0000 (UTC) [thread overview]
Message-ID: <bug-2401-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=2401
Summary: sysvinit-2.86 fails to build on MIPS because is
missing -lcrypt
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: sergio at sergiomb.no-ip.org
CC: buildroot at uclibc.org
Estimated Hours: 0.0
with buildroot git version from today .
same config of bug #635 (https://bugs.busybox.net/attachment.cgi?id=2269)
buildroot/output/staging/usr/bin/mipsel-unknown-linux-uclibc-gcc
--sysroot=buildroot/output/staging -o bootlogd bootlogd.o -lutil
sulogin.o: In function `main':
sulogin.c:(.text+0xf94): undefined reference to `crypt'
collect2: ld returned 1 exit status
make[1]: *** [sulogin] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory `buildroot/output/build/sysvinit-2.86/src'
make: *** [buildroot/output/build/sysvinit-2.86/src/init] Error 2
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-08-11 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 18:55 bugzilla at busybox.net [this message]
2010-08-11 19:15 ` [Buildroot] [Bug 2401] sysvinit-2.86 fails to build on MIPS because is missing -lcrypt bugzilla at busybox.net
2010-08-13 14:28 ` bugzilla at busybox.net
2010-08-13 14:29 ` bugzilla at busybox.net
2010-08-13 15:00 ` bugzilla at busybox.net
2010-08-13 15:14 ` bugzilla at busybox.net
2010-08-22 6:41 ` bugzilla at busybox.net
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=bug-2401-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox