All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: error.h missing on mingw (grub-core/kern/emu/misc.c fails to compile)
Date: Sat, 28 Dec 2013 09:11:54 +0400	[thread overview]
Message-ID: <1388207514.918.81.camel@opensuse.site> (raw)
In-Reply-To: <52BDD629.3010906@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 942 bytes --]

В Пт, 27/12/2013 в 20:34 +0100, Vladimir 'φ-coder/phcoder' Serbinenko
пишет:
> On 27.12.2013 19:25, Andrey Borzenkov wrote:
> > В Чт, 26/12/2013 в 23:54 +0400, Andrey Borzenkov пишет:
> >> I'm not sure how to fix it. It is pulled in by build-grub-pep2elf and
> >> build-grub-pe2elf. Those are build time programs and so use
> >> BUILD_CPPFLAGS; adding CPPFLAGS_GNULIB is probably not appropriate. It
> >> compiles just fine with error.h commented out. May be something like
> >>
> >> #if !defined(GRUB_BUILD) || defined(HAVE_ERROR_H)
> >>
> > 
> > On the second glance - why is <error.h> needed at all? Nothing defined
> > there is used in misc.c and on Linux it compiles just fine with error.h
> > as well.
> > 
> > May be we could simply drop it?
> > 
> Yes. I was going to answer with this. Many of includes are inherited by
> copying of include parts.
> error.h there can simply be removed

done

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2013-12-28  5:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-26 19:54 error.h missing on mingw (grub-core/kern/emu/misc.c fails to compile) Andrey Borzenkov
2013-12-27 18:25 ` Andrey Borzenkov
2013-12-27 19:34   ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-28  5:11     ` Andrey Borzenkov [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=1388207514.918.81.camel@opensuse.site \
    --to=arvidjaar@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 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.