From: Roland Hieber <r.hieber@af-inventions.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] gobject-introspection: syntax error, unexpected typedef-names
Date: Fri, 9 Sep 2016 12:41:14 +0200 [thread overview]
Message-ID: <edf44eb4-41fe-64aa-1267-f00ab2684bde@af-inventions.de> (raw)
In-Reply-To: <20160909063830.piscnph6lskbhqxm@pengutronix.de>
On 09.09.2016 08:38, Michael Olbrich wrote:
> I don't know how to find out the minimum required kernel version for a
> compiled glibc but I looked at the configure options used for
> OSELAS.Toolchain-2016.06.0. The minimum required kernel version is set to
> 3.18 :-/.
OK, I tried building on kernel 4.6.0 from jessie-backports. The FATAL
errors are gone but, the syntax errors in the g-i compile stage are
still being thrown:
.../sysroot-target/usr/include/glib-2.0/gio/gio-autocleanups.h:106:
syntax error, unexpected typedef-name, expecting identifier or '(' in
'typedef GProxy *GProxy_autoptr;' at 'GProxy_autoptr'
...although they don't seem to affect the build, since g-i now
targetinstalls correctly :)
> You could hack ./platform-arm-hf/sysroot-cross/bin/qemu-cross to add '-r
> 3.18' to the qemu command-line. That may help, but could cause other issues
> later, but probably not for the g-i stuff.
Uhh, that seems more like a dirty hack than a real fix to me ;-) I'll
rather compile with a newer host kernel.
Thanks!
- Roland
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2016-09-09 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 17:21 Roland Hieber
2016-09-02 9:17 ` Michael Olbrich
2016-09-02 15:17 ` Roland Hieber
2016-09-05 13:07 ` Michael Olbrich
2016-09-08 13:15 ` Roland Hieber
2016-09-09 6:38 ` Michael Olbrich
2016-09-09 10:41 ` Roland Hieber [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=edf44eb4-41fe-64aa-1267-f00ab2684bde@af-inventions.de \
--to=r.hieber@af-inventions.de \
--cc=ptxdist@pengutronix.de \
/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