Closed GoogleCodeExporter closed 9 years ago
I can't seem to reproduce this:
$ export NACL_SDK_ROOT=$HOME/nacl_sdk/pepper_39
$ ./make_all.sh clean
$ make glibc-compat V=1
Works fine for me at 4eee51203.
Original comment by sbc@chromium.org
on 10 Nov 2014 at 5:37
The file in question "include/fcntl.h" is found in source control at
"ports/glibc-compat/include/sys/fcntl.h". This file does not contain FIONBIO
at 4eee512. It looks like it was removed at e08c19df (on sept 11 2014) so I
suspect you have a some kind of stale checkout?
Original comment by sbc@google.com
on 10 Nov 2014 at 5:41
BTW, I'm about to create branches for pepper_38, pepper_39 and pepper_40 in the
naclports repo that we can use to avoid breaking older SDK as we make change
(which are mostly tested against pepper_canary).
Original comment by sbc@google.com
on 10 Nov 2014 at 5:42
Running make with V=1 shows this additional line:
Prebuilt package was built with different SDK version: 38 vs 39
Running ./make_all.sh clean and then make fixes the problem.
So I guess there was some stale state around. It certainly wasn't a stale
checkout of anything, but a stale build (which means the Makefile isn't smart
enough about deciding what needs to be rebuilt).
Original comment by mgiuca@chromium.org
on 10 Nov 2014 at 11:04
I don't really understand how you could have got this error:
include/fcntl.h:11:1: error: "FIONBIO" redefined
Unless you have a file called ports/glibc-compat/include/fcntl.h. Yes this file
was removed here:
https://codereview.chromium.org/418103005
If the fcntl.h was installed in the toolchain it would aprear as a full path
name.
Sorry I don't have any other clues here.
Please re-open if it happens again.
Original comment by sbc@google.com
on 10 Nov 2014 at 11:15
Yeah I think what happened was I had ports/glibc-compat/include/fcntl.h left
over from an old build (pre-pepper-38). Then when I re-ran make
(post-pepper-39), it was not deleted and something was still referring to it.
Now it is working.
Original comment by mgiuca@chromium.org
on 11 Nov 2014 at 12:53
Original issue reported on code.google.com by
mgiuca@chromium.org
on 10 Nov 2014 at 6:41