Skip to contentSkip to conversation

m4-native, zedboard, "Please port gnulib fseeko.c to your platform"

DISCUSSION Robert P. J. Day 4 participants 4 messages Nov 13, 2018 – Nov 14, 2018

lore
Share & tools
lore
#0 lore raw

been away from YP for a few months, diving back in, want to build a
core-image-minimal for my zedboard, and i will first admit that i'm using a non-approved distro (fully-updated fedora 29):

"WARNING: Host distribution "fedora-29" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution."

no matter, i will live dangerously. but then things take an ugly
turn:

"WARNING: Your host glibc verson (2.28) is newer than that in uninative (2.27). Disabling uninative so that sstate is not corrupted."

ok, let's see how far we get ... and that's here, trying to compile
m4-native:

| gcc -I. -I../../m4-1.4.18/lib
-isystem/home/rpjday/oe/builds/zedboard/tmp/work/x86_64-linux/m4-native/1.4.18-r0/recipe-sysroot-native/usr/include -isystem/home/rpjday/oe/builds/zedboard/tmp/work/x86_64-linux/m4-native/1.4.18-r0/recipe-sysroot-native/usr/include -O2 -pipe -c -o freadahead.o ../../m4-1.4.18/lib/freadahead.c
| gcc -I. -I../../m4-1.4.18/lib
-isystem/home/rpjday/oe/builds/zedboard/tmp/work/x86_64-linux/m4-native/1.4.18-r0/recipe-sysroot-native/usr/include -isystem/home/rpjday/oe/builds/zedboard/tmp/work/x86_64-linux/m4-native/1.4.18-r0/recipe-sysroot-native/usr/include -O2 -pipe -c -o fseeko.o ../../m4-1.4.18/lib/fseeko.c

| ../../m4-1.4.18/lib/freadahead.c: In function ‘freadahead’:
| ../../m4-1.4.18/lib/fseeko.c: In function ‘rpl_fseeko’:
| ../../m4-1.4.18/lib/freadahead.c:92:3: error: #error "Please port

gnulib freadahead.c to your platform! Look at the definition of fflush, fread, ungetc on your system, then report this to bug-gnulib."
| #error "Please port gnulib freadahead.c to your platform! Look at
the definition of fflush, fread, ungetc on your system, then report this to bug-gnulib."
| ^~~~~
| ../../m4-1.4.18/lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib."
| #error "Please port gnulib fseeko.c to your platform! Look at the
code in fseeko.c, then report this to bug-gnulib."

and so on. red hat's bugzilla has an entry for just this:

https://bugzilla.redhat.com/show_bug.cgi?id=1595702

but i'm unsure (read, have no clue) how to deal with this, and i suspect it affects more targets than just zedboard which is why i'm asking on the general YP list.

thoughts? is there a cheap fix for this? i'm about to dive into
debugging this, but if someone wants to make my life easy, that'd be great.

rday

Signature · 7 lines
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                  http://crashcourse.ca/dokuwiki

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
#1 lore raw

Robert,

Quoted 47 lines · Robert P. J. Day

been away from YP for a few months, diving back in, want to build a
core-image-minimal for my zedboard, and i will first admit that i'm using a non-approved distro (fully-updated fedora 29):

"WARNING: Host distribution "fedora-29" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution."

no matter, i will live dangerously. but then things take an ugly
turn:

"WARNING: Your host glibc verson (2.28) is newer than that in uninative (2.27). Disabling uninative so that sstate is not corrupted."

ok, let's see how far we get ... and that's here, trying to compile
m4-native:

| gcc -I. -I../../m4-1.4.18/lib

(quoted diff) +0 -3
-isystem/home/rpjday/oe/builds/zedboard/tmp/work/x86_64-linux/m4-native/1.4.18-r0/recipe-sysroot-native/usr/include
-isystem/home/rpjday/oe/builds/zedboard/tmp/work/x86_64-linux/m4-native/1.4.18-r0/recipe-sysroot-native/usr/include
-O2 -pipe -c -o freadahead.o ../../m4-1.4.18/lib/freadahead.c

| gcc -I. -I../../m4-1.4.18/lib

(quoted diff) +0 -3
-isystem/home/rpjday/oe/builds/zedboard/tmp/work/x86_64-linux/m4-native/1.4.18-r0/recipe-sysroot-native/usr/include
-isystem/home/rpjday/oe/builds/zedboard/tmp/work/x86_64-linux/m4-native/1.4.18-r0/recipe-sysroot-native/usr/include
-O2 -pipe -c -o fseeko.o ../../m4-1.4.18/lib/fseeko.c
| ../../m4-1.4.18/lib/freadahead.c: In function ‘freadahead’:
| ../../m4-1.4.18/lib/fseeko.c: In function ‘rpl_fseeko’:
| ../../m4-1.4.18/lib/freadahead.c:92:3: error: #error "Please port

gnulib freadahead.c to your platform! Look at the definition of fflush, fread, ungetc on your system, then report this to bug-gnulib."
| #error "Please port gnulib freadahead.c to your platform! Look at
the definition of fflush, fread, ungetc on your system, then report this to bug-gnulib."
| ^~~~~
| ../../m4-1.4.18/lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib."
| #error "Please port gnulib fseeko.c to your platform! Look at the
code in fseeko.c, then report this to bug-gnulib."

and so on. red hat's bugzilla has an entry for just this:

https://bugzilla.redhat.com/show_bug.cgi?id=1595702

Quoted 7 lines

but i'm unsure (read, have no clue) how to deal with this, and i suspect it affects more targets than just zedboard which is why i'm asking on the general YP list.

thoughts? is there a cheap fix for this? i'm about to dive into
debugging this, but if someone wants to make my life easy, that'd be great.

Thud has :
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/recipes-devtools/m4?h=thud&id=95ca077ab871ceff46c2052f324f879a1d624ff4

with backports pending verification for sumo but missed th Rocko cutoff.

- armin

Quoted 3 lines

rday

#2 lore raw
In reply to Robert P. J. Day

Robert,

Quoted 4 lines · Robert P. J. Day

been away from YP for a few months, diving back in, want to build a
core-image-minimal for my zedboard, and i will first admit that i'm using a non-approved distro (fully-updated fedora 29):

[...]

Quoted 1 line

but i'm unsure (read, have no clue) how to deal with this

If upgrading Yocto/poky and layers is not an option for you, then building in a container is the typical approach. This isolates you from any host- distro issues, since any distro can be used in the container.

Many just set up their own with a simple Docker file, but from what I remember the CROPS project is one common project recommended in the past. Here's a random starting point I found [1].

HTH,
- Gunnar

[1] https://www.yoctoproject.org/learn-items/cross-platform-enablement-for-t
he-yocto-project-with-containers/

#3 lore raw
Quoted 13 lines · Gunnar Andersson

Robert,

Quoted 4 lines · Robert P. J. Day

been away from YP for a few months, diving back in, want to build a
core-image-minimal for my zedboard, and i will first admit that i'm using a non-approved distro (fully-updated fedora 29):

[...]

Quoted 1 line

but i'm unsure (read, have no clue) how to deal with this

Quoted 8 lines

If upgrading Yocto/poky and layers is not an option for you, then building in a container is the typical approach. This isolates you from any host- distro issues, since any distro can be used in the container.

Many just set up their own with a simple Docker file, but from what I remember the CROPS project is one common project recommended in the past. Here's a random starting point I found [1].

move to thud, ive confirmed it works on fedora 29 after seeing the same issue, or ...VM with Debian / Ubuntu

Quoted 12 lines

HTH,
- Gunnar

[1] https://www.yoctoproject.org/learn-items/cross-platform-enablement-for-t
he-yocto-project-with-containers/

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto