All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Galbusera <gizero@gmail.com>
To: Mathias Rudnik <rudnik.mathias@googlemail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Error do_compile libepoxy
Date: Wed, 17 Jan 2018 13:58:32 +0100	[thread overview]
Message-ID: <CAC+thW1kL2F2LKxpnLMTd-YfWZV8KNzDSqpF8q2KdOBENBjt4g@mail.gmail.com> (raw)
In-Reply-To: <FBE5527A-743B-468F-9CEA-FC1732314AFE@googlemail.com>

Hi!

On Wed, Jan 17, 2018 at 1:46 PM, Mathias Rudnik
<rudnik.mathias@googlemail.com> wrote:
> Hello,
>
> I am trying to build libepoxy but the do_compile tasks breaks.
> I found following error messages in the logs:
>
> arm-poky-linux-gnueabi-gcc -march=armv6 -mfpu=vfp -mfloat-abi=hard
> -mtune=arm1176jzf-s -mfpu=vfp
> --sysroot=/hdd_gold1/mathias/git/poky/rpi-build/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/libepoxy/1.4.3-r0/recipe-sysroot
> '-Itest/egl_common at sta' '-Itest' '-Iinclude/epoxy'
> '-I../libepoxy-1.4.3/test' '-Iinclude' '-I../libepoxy-1.4.3/include' '-Isrc'
> '-I../libepoxy-1.4.3/src' '-fdiagnostics-color=always' '-pipe'
> '-D_FILE_OFFSET_BITS=64' '-Wall' '-Winvalid-pch' '-std=gnu99' '-O2' '-g'
> '-O2' '-g' '-feliminate-unused-debug-types'
> '-fdebug-prefix-map=/hdd_gold1/mathias/git/poky/rpi-build/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/libepoxy/1.4.3-r0=/usr/src/debug/libepoxy/1.4.3-r0'
> '-fdebug-prefix-map=/hdd_gold1/mathias/git/poky/rpi-build/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/libepoxy/1.4.3-r0/recipe-sysroot-native='
> '-fdebug-prefix-map=/hdd_gold1/mathias/git/poky/rpi-build/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/libepoxy/1.4.3-r0/recipe-sysroot='
> '-lEGL' '-fPIC' '-Wpointer-arith' '-Wmissing-declarations' '-Wformat=2'
> '-Wstrict-prototypes' '-Wmissing-prototypes' '-Wnested-externs'
> '-Wbad-function-cast' '-Wold-style-definition'
> '-Wdeclaration-after-statement' '-Wunused' '-Wuninitialized' '-Wshadow'
> '-Wmissing-noreturn' '-Wmissing-format-attribute' '-Wredundant-decls'
> '-Wlogical-op' '-Werror=implicit' '-Werror=nonnull' '-Werror=init-self'
> '-Werror=main' '-Werror=missing-braces' '-Werror=sequence-point'
> '-Werror=return-type' '-Werror=trigraphs' '-Werror=array-bounds'
> '-Werror=write-strings' '-Werror=address' '-Werror=int-to-pointer-cast'
> '-Werror=pointer-to-int-cast' '-fno-strict-aliasing' '-Wno-int-conversion'
> '-MMD' '-MQ' 'test/egl_common at sta/egl_common.c.o' '-MF' 'test/egl_common
> at sta/egl_common.c.o.d' -o 'test/egl_common at sta/egl_common.c.o' -c
> ../libepoxy-1.4.3/test/egl_common.c
> ../libepoxy-1.4.3/test/egl_common.c: In function 'get_egl_display_or_skip':
> ../libepoxy-1.4.3/test/egl_common.c:36:5: error: unknown type name
> 'Display'; did you mean 'EGLDisplay'?
>      Display *dpy = XOpenDisplay(NULL);
>      ^~~~~~~
>      EGLDisplay
> ../libepoxy-1.4.3/test/egl_common.c:36:20: error: implicit declaration of
> function 'XOpenDisplay'; did you mean 'eglGetDisplay'?
> [-Werror=implicit-function-declaration]
>      Display *dpy = XOpenDisplay(NULL);
>                     ^~~~~~~~~~~~
>                     eglGetDisplay
> ../libepoxy-1.4.3/test/egl_common.c:36:20: warning: nested extern
> declaration of 'XOpenDisplay' [-Wnested-externs]
> cc1: some warnings being treated as errors
>
> Does anybody know what i am doing wrong?

Just noticed this also here in CI builds. Unfortunately I'm building
with lot of new stuff from master branches wrt latest successful
build. In my case meta-raspberrypi is in the pile, but I haven't had
the time to investigate yet. At first glance at least commit
043f0218491452de223a5f0b47945fc6ec1633eb (libepoxy related) should be
in my bisecting range. Will report back if something comes up.


  parent reply	other threads:[~2018-01-17 12:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 12:46 Error do_compile libepoxy Mathias Rudnik
2018-01-17 12:53 ` Burton, Ross
2018-01-17 12:58 ` Andrea Galbusera [this message]
2018-01-18  8:58   ` Andrea Galbusera
2018-01-18  9:05     ` Alexander Kanavin
2018-01-18 10:00       ` Martin Jansa
2018-01-18 10:57         ` Alexander Kanavin
2018-01-18 13:13       ` Max Krummenacher
2018-01-18 13:41         ` Andrea Galbusera
2018-01-18 13:49           ` Alexander Kanavin
2018-01-19  3:29             ` Andre McCurdy
2018-01-19  7:45               ` Alexander Kanavin
2018-01-19 10:45                 ` Andrea Galbusera
2018-01-19 12:32                   ` Alexander Kanavin
2018-01-19 16:36                     ` Andrea Galbusera
2018-01-22 13:08                       ` Alexander Kanavin
2018-01-20  9:29                     ` Anuj Mittal
2018-01-20 17:07                       ` Andrea Galbusera
2018-01-21 15:23                         ` Anuj Mittal
2018-01-22  9:12                           ` Andrea Galbusera
2018-01-22 13:59                             ` Trevor Woerner
2018-01-18 14:08       ` Trevor Woerner
2018-01-18 15:05         ` Michael Gloff
2018-01-18 20:48           ` Trevor Woerner
2018-01-19  1:35             ` Michael Gloff
2018-01-18  9:09     ` Burton, Ross
  -- strict thread matches above, loose matches on Subject: below --
2018-01-12 13:39 Mathias Rudnik
2018-01-11 19:18 Mathias Rudnik
2018-01-14 20:05 ` Trevor Woerner

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=CAC+thW1kL2F2LKxpnLMTd-YfWZV8KNzDSqpF8q2KdOBENBjt4g@mail.gmail.com \
    --to=gizero@gmail.com \
    --cc=rudnik.mathias@googlemail.com \
    --cc=yocto@yoctoproject.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.