All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 457] New: e2fsprogs link problem
Date: Mon, 13 Jul 2009 19:12:33 +0000 (UTC)	[thread overview]
Message-ID: <bug-457-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=457

              Host: x86-64
            Target: SH4
           Summary: e2fsprogs link problem
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: lionel.landwerlin at openwide.fr
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Hi,

when link e2fsck from the e2fsprogs package, you might experience a problem at
the link. e2fsck is looking for -lintl.

Please find a fix as attachment.

Regards,

Lionel


-- 
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.

             reply	other threads:[~2009-07-13 19:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13 19:12 bugzilla at busybox.net [this message]
2009-07-13 19:13 ` [Buildroot] [Bug 457] e2fsprogs link problem bugzilla at busybox.net
2009-07-17 10:13 ` bugzilla at busybox.net
2009-07-17 11:24 ` bugzilla at busybox.net
2009-07-27 15:44 ` bugzilla at busybox.net
2009-08-31  8:03 ` bugzilla at busybox.net
2009-08-31  8:30 ` bugzilla at busybox.net
2010-02-21 17:59 ` 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-457-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 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.