All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] grub2: fix build with gcc-7
Date: Tue, 22 Aug 2017 11:28:51 +0100	[thread overview]
Message-ID: <1503397731.32591.80.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+chaQfHU-5Jp2Q7171mcJkX8YGnFpngYG39PWeW4WhCjWp+bw@mail.gmail.com>

On Tue, 2017-08-22 at 11:26 +0100, Martin Jansa wrote:
> I'm sorry for the issues caused by this, can you share config.log
> from that build? Maybe the native compiler on that build host doesn't
> support this option?

The one I linked to was a debian9 system, config.log says:

gcc: error: unrecognized command line option '-qversion'; did you mean '--version'?
gcc: fatal error: no input files
compilation terminated.
configure:5052: $? = 1
configure:5072: checking whether the C compiler works
configure:5094: gcc   -Wno-error=trampolines -Wno-error=expansion-to-defined   conftest.c  >&5
cc1: error: -Werror=expansion-to-defined: no option -Wexpansion-to-defined
configure:5098: $? = 1
configure:5136: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "GRUB"
| #define PACKAGE_TARNAME "grub"
| #define PACKAGE_VERSION "2.02"
| #define PACKAGE_STRING "GRUB 2.02"
| #define PACKAGE_BUGREPORT "bug-grub@gnu.org"
| #define PACKAGE_URL ""
| #define PACKAGE "grub"
| #define VERSION "2.02"
| #define GRUB_BOOT_DIR_NAME "boot"
| #define GRUB_DIR_NAME "grub"
| /* end confdefs.h.  */
| 
| int
| main (void)
| {
| 
|   ;
|   return 0;
| }
configure:5141: error: in `/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/work/x86_64-linux/grub-efi-native/2.02-r0/build':
configure:5143: error: C compiler cannot create executables
See `config.log' for more details

So yes, it doesn't understand the option.

Cheers,

Richard



  reply	other threads:[~2017-08-22 10:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21 20:57 [PATCH 1/2] squashfs: fix build with glibc-2.26 Martin Jansa
2017-08-21 20:57 ` [PATCH 2/2] grub2: fix build with gcc-7 Martin Jansa
2017-08-21 23:52   ` Khem Raj
2017-08-22 17:21     ` Martin Jansa
2017-08-22 17:28       ` Khem Raj
2017-08-22 22:10       ` [PATCHv2] grub2: fix build on gcc where _FORTIFY_SOURCE is defined Martin Jansa
2017-08-22 10:22   ` [PATCH 2/2] grub2: fix build with gcc-7 Richard Purdie
2017-08-22 10:26     ` Martin Jansa
2017-08-22 10:28       ` Richard Purdie [this message]
2017-08-22 16:32     ` Khem Raj

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=1503397731.32591.80.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.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.