From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: GRUB2 on OpenBSD 5.3-amd64: linking problem
Date: Thu, 15 Aug 2013 17:00:31 +0200 [thread overview]
Message-ID: <520CED0F.4070008@gmail.com> (raw)
In-Reply-To: <520B8ACF.4010309@gmail.com>
On 14.08.2013 15:49, Grégoire Sutre wrote:
> On 08/14/2013 03:31 PM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>> On 14.08.2013 15:09, Ilya Bakulin wrote:
>>> ./lib/posix_wrap/sys/types.h:25: error: conflicting types for 'size_t'
>>> /usr/include/stddef.h:48: error: previous declaration of 'size_t' was
>>> here
>>> gmake[3]: *** [fs/squash4_module-squash4.o] Error 1
>> You need to modify following:
>> #ifndef __APPLE__
>> typedef grub_size_t size_t;
>> #else
>> #include <stddef.h>
>> #endif
>> to
>> #if !defined (__APPLE__) && !defined (__OPENBSD__)
>
> For the record, this is also needed for NetBSD (when building
> within the pkgsrc framework -- see pkgsrc's sysutils/grub2 package).
>
> A similar patch (for NetBSD, but maybe also for OpenBSD?) is:
>
> --- grub-core/lib/posix_wrap/wchar.h.orig 2012-02-08
> 20:34:24.000000000 +0000
> +++ grub-core/lib/posix_wrap/wchar.h
> @@ -29,7 +29,11 @@ enum
> };
>
> /* UCS-4. */
> +#if !defined(__NetBSD__)
> typedef grub_int32_t wchar_t;
> +#else
> +#include <stddef.h>
> +#endif
>
This is not right fix. Many systems incorrectly define wchar_t as 16-bit
type whil GRUB needs at least 21 as we handle all unicode characters.
Please try:
=== modified file 'grub-core/lib/posix_wrap/wchar.h'
--- grub-core/lib/posix_wrap/wchar.h 2012-02-09 13:24:55 +0000
+++ grub-core/lib/posix_wrap/wchar.h 2013-08-15 14:55:59 +0000
@@ -21,6 +21,11 @@
#include <grub/charset.h>
+#if defined(__NetBSD__) || defined(__OPENBSD__)
+#define wchar_t grub_posix_wchar_t
+#define mbstate_t grub_posix_mbstate_t
+#endif
+
/* UCS-4. */
typedef grub_int32_t wint_t;
enum
next prev parent reply other threads:[~2013-08-15 15:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201308091537.37473.Ilya_Bakulin@genua.de>
[not found] ` <520A9F30.6080901@gmail.com>
2013-08-14 8:59 ` GRUB2 on OpenBSD 5.3-amd64: linking problem Vladimir 'φ-coder/phcoder' Serbinenko
2013-08-14 13:09 ` Ilya Bakulin
2013-08-14 13:27 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-08-14 13:31 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-08-14 13:49 ` Grégoire Sutre
2013-08-14 15:16 ` Ilya Bakulin
2013-08-14 16:28 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-08-16 14:33 ` Ilya Bakulin
2013-08-16 14:41 ` Grégoire Sutre
2013-08-16 14:51 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-08-15 15:00 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-08-15 23:12 ` Grégoire Sutre
[not found] ` <52150FC5.3040109@gmail.com>
[not found] ` <52165590.4050207@gmail.com>
[not found] ` <201308231126.22583.Ilya_Bakulin@genua.de>
2013-08-23 9:31 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-08-23 11:53 ` Ilya Bakulin
2013-08-30 17:33 ` Douglas Ray
2013-09-18 11:49 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-09-23 15:59 ` Ilya Bakulin
2013-09-23 16:16 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-10-07 9:05 ` Ilya Bakulin
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=520CED0F.4070008@gmail.com \
--to=phcoder@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).