From: <bogus@does.not.exist.com>
To: buildroot@busybox.net
Subject: No subject
Date: Tue, 06 Feb 2007 07:08:39 -0000 [thread overview]
Message-ID: <mailman.1.1171287961.4267.buildroot@uclibc.org> (raw)
the build_i386/staging_dir. It seems to be creating a full usr/include,
usr/lib, etc directory hierarchy under inside build_i386/staging_dir,
rather than integrating with the include/lib/etc dirs that exist at the
staging_dir level (ie. the installation of gettext files occurs at one
level too deep)
This means that libintl.h and the shared libraries aren't where other apps
expect it and compilation errors can occur.
The attached patch fixes this - hope it's ok.
Cheers,
Marcus
======================================================================
----------------------------------------------------------------------
prpplague - 05-24-06 07:49
----------------------------------------------------------------------
fixed as of revision 15160
Issue History
Date Modified Username Field Change
======================================================================
11-29-05 07:56 crafterm New Issue
11-29-05 07:56 crafterm Status new => assigned
11-29-05 07:56 crafterm Assigned To => uClibc
11-29-05 07:56 crafterm File Added: gettext-stagingfix.patch
05-24-06 07:49 prpplague Note Added: 0001377
05-24-06 07:49 prpplague Status assigned => closed
02-12-07 05:45 vapier Status closed => assigned
02-12-07 05:45 vapier Assigned To uClibc => buildroot
======================================================================
next reply other threads:[~2007-02-06 7:08 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 7:08 bogus [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-07 21:22 No subject bogus
2008-11-21 1:22 bogus
2008-10-23 17:17 bogus
2008-10-23 17:17 bogus
2008-10-23 17:17 bogus
2008-09-15 17:22 bogus
2008-09-15 17:22 bogus
2008-07-14 13:16 bogus
2008-07-14 13:16 bogus
2008-07-14 13:16 bogus
2008-07-14 13:16 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-03-17 22:01 bogus
2007-12-01 7:52 bogus
2007-12-01 7:52 bogus
2007-10-06 20:13 bogus
2007-10-06 20:13 bogus
2007-10-06 20:13 bogus
2007-07-23 18:04 bogus
2007-07-23 18:04 bogus
2007-06-23 20:07 bogus
2007-02-14 8:32 bogus
2007-02-14 8:32 bogus
2007-02-14 8:32 bogus
2007-02-14 8:32 bogus
2007-02-06 7:08 bogus
2007-02-06 7:08 bogus
2007-02-06 7:08 bogus
2006-08-17 1:58 bogus
2006-08-17 1:58 bogus
2006-08-17 1:58 bogus
2006-08-17 1:58 bogus
2006-08-17 1:58 bogus
2006-08-17 1:58 bogus
2006-08-17 1:58 bogus
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=mailman.1.1171287961.4267.buildroot@uclibc.org \
--to=bogus@does.not.exist.com \
--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