From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Compiling grub2 on OpenBSD
Date: Sat, 2 Feb 2008 13:28:07 +0100 [thread overview]
Message-ID: <200802021328.07862.okuji@enbug.org> (raw)
In-Reply-To: <20080201214147.GB4855@thorin>
On Friday 01 February 2008 22:41, Robert Millan wrote:
> On Fri, Feb 01, 2008 at 12:49:11PM -0800, walt wrote:
> > I got grub2 compiled on NetBSD, so now on to OpenBSD:
> >
> > In file included from ../util/i386/pc/grub-mkimage.c:29:
> > ../include/grub/misc.h:43: warning: conflicting types for built-in
> > function `memcpy'
> > In file included from ../util/i386/pc/grub-mkimage.c:33:
> > /usr/include/string.h:60: error: conflicting types for `memcpy'
> > ../include/grub/misc.h:43: error: previous declaration of `memcpy'
>
> Sounds strange. Why do we have memcpy at all? Shouldn't it be
> grub_memcpy?
IIRC, GCC implicitly generates references to memcpy, thus somebody has added
memcpy as an alias to grub_memcpy.
I don't know how to solve it cleanly. If you have an idea, I'd like to know.
Okuji
prev parent reply other threads:[~2008-02-02 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 20:49 Compiling grub2 on OpenBSD walt
2008-02-01 21:41 ` Robert Millan
2008-02-02 12:28 ` Yoshinori K. Okuji [this message]
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=200802021328.07862.okuji@enbug.org \
--to=okuji@enbug.org \
--cc=grub-devel@gnu.org \
/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.