Notes |
(0000698)
vapier
11-25-05 11:33
|
that header is only included if configure detects that it is available
post the config.log file as an attachment |
| |
(0000708)
crafterm
11-29-05 02:50
|
Ok, uploaded, from inspecting the config.log:
configure:10316: checking sys/stropts.h usability
configure:10328: /home/crafterm/workspace/build/buildroot/build_i386/staging_dir/bin/i386-linux-uclibc-gcc -c -Os -pipe conftest.c >&5
conftest.c:103:25: sys/stropts.h: No such file or directory
configure:10334: $? = 1
..<strip>...
configure:10356: result: no
configure:10360: checking sys/stropts.h presence
configure:10370: gcc -E conftest.c
configure:10376: $? = 0
configure:10396: result: yes
configure:10409: WARNING: sys/stropts.h: present but cannot be compiled
configure:10411: WARNING: sys/stropts.h: check for missing prerequisite headers?
configure:10413: WARNING: sys/stropts.h: see the Autoconf documentation
configure:10415: WARNING: sys/stropts.h: section "Present But Cannot Be Compiled"
configure:10417: WARNING: sys/stropts.h: proceeding with the preprocessor's result
configure:10419: WARNING: sys/stropts.h: in the future, the compiler will take precedence
configure:10431: checking for sys/stropts.h
configure:10438: result: yes
To me it looks like the first check is using the uclibc toolchain compiler, which fails as it should since stropts.h doesn't exist in any of the toolchain include dirs - however the second check seems to be using my systems gcc compiler which succeeds - causing the compilation error a bit later on
Is this expected behaviour as far as autoconf goes in buildroot? Is there something else we can define to ensure the correct c compiler is used?
Cheers,
Marcus |
| |
(0000709)
crafterm
11-29-05 03:14
|
On further inspection, it looks like the setting for the preprocessor isn't being overridden and it left as:
CPP='gcc -E'
Should buildroot be overriding the preprocessor and pointing it to the buildroot toolchain compiler perhaps?
Just a thought. |
| |
(0000710)
crafterm
11-29-05 03:25
|
Ok, think i've been able to fix it. With the attached patch, CPP is defined to be the toolchain C compiler/preprocessor, and this lets everything compile as expected.
What do you guys think? Is the patch ok?
Cheers,
Marcus |
| |
(0001995)
bernhardf
01-19-07 08:06
|
We have updated to strace-4.5.14 meanwhile, so closing. |
| |