Skip to content

devmem: Reorder headers#37

Open
shenki wants to merge 1 commit intoamboar:mainfrom
shenki:devmem-build-fix
Open

devmem: Reorder headers#37
shenki wants to merge 1 commit intoamboar:mainfrom
shenki:devmem-build-fix

Conversation

@shenki
Copy link
Contributor

@shenki shenki commented Mar 2, 2023

Convention is to include system headers first, and local ones last. This resolves a build issue on centos7:

cc -Isrc/culvert.p -Isrc -I../src -I../src/arch/x86_64 -Isrc/devicetree
-flto -DNDEBUG -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra
-std=gnu99 -O2 -g -MD -MQ src/culvert.p/bridge_devmem.c.o -MF
src/culvert.p/bridge_devmem.c.o.d -o src/culvert.p/bridge_devmem.c.o -c
../src/bridge/devmem.c
In file included from /usr/include/fcntl.h:77:0,
from ../src/bridge/devmem.c:19:
/usr/include/bits/stat.h:106:31: error: expected identifier or '(' before '[' token
__syscall_slong_t __unused[3];
^

Convention is to include system headers first, and local ones last. This
resolves a build issue on centos7:

 cc -Isrc/culvert.p -Isrc -I../src -I../src/arch/x86_64 -Isrc/devicetree
 -flto -DNDEBUG -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra
 -std=gnu99 -O2 -g -MD -MQ src/culvert.p/bridge_devmem.c.o -MF
 src/culvert.p/bridge_devmem.c.o.d -o src/culvert.p/bridge_devmem.c.o -c
 ../src/bridge/devmem.c
 In file included from /usr/include/fcntl.h:77:0,
                  from ../src/bridge/devmem.c:19:
 /usr/include/bits/stat.h:106:31: error: expected identifier or '(' before '[' token
      __syscall_slong_t __unused[3];
                               ^

Signed-off-by: Joel Stanley <joel@jms.id.au>
@amboar
Copy link
Owner

amboar commented Mar 3, 2023

Hmm, let me poke at this. I tend to order local includes before system includes so the local headers can adjust the behaviour of system headers as necessary. The fact that re-ordering fixes it feels a bit off?

@shenki
Copy link
Contributor Author

shenki commented Mar 3, 2023

That's generally the opposite of what you should be doing, for this very reason.

@shenki
Copy link
Contributor Author

shenki commented Mar 3, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants