From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001533]: lockfile-progs 0.1.10 breaks in compilation - PATCH
Date: Tue, 16 Oct 2007 14:20:24 -0700 [thread overview]
Message-ID: <ee0cf29f38637b66c62cf5a77c4842f3@busybox.net> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=1533
======================================================================
Reported By: sushisan
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1533
Category: Architecture Specific
Reproducibility: always
Severity: crash
Priority: normal
Status: assigned
======================================================================
Date Submitted: 10-16-2007 14:20 PDT
Last Modified: 10-16-2007 14:20 PDT
======================================================================
Summary: lockfile-progs 0.1.10 breaks in compilation - PATCH
Description:
lockfile-progs 0.1.10 breaks with this error:
undefined reference to `*rindex*'
This patch update the package to 0.1.11 and add a patch to solve this.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
10-16-07 14:20 sushisan New Issue
10-16-07 14:20 sushisan Status new => assigned
10-16-07 14:20 sushisan Assigned To => buildroot
10-16-07 14:20 sushisan File Added: br2-lockfile-progs.patch
======================================================================
next reply other threads:[~2007-10-16 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 21:20 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-19 19:53 [Buildroot] [buildroot 0001533]: lockfile-progs 0.1.10 breaks in compilation - PATCH bugs 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=ee0cf29f38637b66c62cf5a77c4842f3@busybox.net \
--to=bugs@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