From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] undefined reference to `bcopy' - what's changed?
Date: Sun, 30 Sep 2007 01:04:26 +0300 [thread overview]
Message-ID: <46FECBEA.6060005@promwad.com> (raw)
In-Reply-To: <20070929162659.GP20951@aon.at>
Bernhard Fischer ?????:
> On Sat, Sep 29, 2007 at 07:28:36PM +0300, Ivan Kuten wrote:
>> Hi,
>>
>> I started getting this error. The same config for ARM920T, just doing svn ups and rebuilding buildroot.
>> Day ago it wasn't there.
>
> You're trying to use a SUSv3 LEGACY function. I'd fix the package, but
> if you're not converned about bloating your build with LEGACY stuff then
> you can of course turn on support for legacy in uClibc.
Please apply fix:
package/x11r7/xlib_libXfont/xlib_libXfont-1.2.7-bcopy-replacement.patch
diff -urN xlib_libXfont-1.2.7.orig/src/builtins/file.c xlib_libXfont-1.2.7/src/builtins/file.c
--- xlib_libXfont-1.2.7.orig/src/builtins/file.c 2007-01-17 23:49:10.000000000 +0200
+++ xlib_libXfont-1.2.7/src/builtins/file.c 2007-09-30 00:52:55.000000000 +0300
@@ -50,7 +50,7 @@
len = BUFFILESIZE;
if (len > left)
len = left;
- bcopy (io->file->bits + io->offset, f->buffer, len);
+ memmove (f->buffer, io->file->bits + io->offset, len);
io->offset += len;
f->left = len - 1;
f->bufp = f->buffer + 1;
Best regards,
Ivan
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------
next prev parent reply other threads:[~2007-09-29 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 16:28 [Buildroot] undefined reference to `bcopy' - what's changed? Ivan Kuten
2007-09-29 16:26 ` Bernhard Fischer
2007-09-29 22:04 ` Ivan Kuten [this message]
2007-09-29 21:31 ` Bernhard Fischer
2007-09-29 22:36 ` Ivan Kuten
2007-09-29 23:05 ` Ivan Kuten
2007-09-30 0:17 ` Ivan Kuten
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=46FECBEA.6060005@promwad.com \
--to=ivan.kuten@promwad.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 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.