Skip to contentSkip to conversation

coreutils: Add gcc parameter for ptest

PATCH Superseded [email protected] 4 participants 10 messages Apr 14, 2023 – Apr 18, 2023

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 coreutils: Add gcc parameter for ptest

From: Qiu Tingting <[email protected]>

If gcc is installed in image, ptest result has 4 ERROR.
ERROR: tests/rm/r-root.sh
ERROR: tests/rm/rm-readdir-fail.sh
ERROR: tests/cp/nfs-removal-race.sh
ERROR: tests/ls/getxattr-speedup.sh

r-root.log as an example:
--------------------------
k.c:1:10: fatal error: stdio.h: No such file or directory

      1 | #include <stdio.h>
        |          ^~~~~~~~~

compilation terminated.
r-root.sh: set-up failure: failed to build shared library ERROR tests/rm/r-root.sh (exit status: 99)
--------------------------

reason:
In these cases, k.c file is created and compiled by gcc before run. There is a stdio.h file in /usr/include/ directory,
but gcc parameter is not set it.

solution:
Add "-l /usr/include/" in gcc parameter.

other:
If gcc is not installed in image, these cases will be skipped.

---
 meta/recipes-core/coreutils/coreutils_9.1.bb | 1 +
 1 file changed, 1 insertion(+)
meta/recipes-core/coreutils/coreutils_9.1.bb +1 -0
index 4807eefd04..fe785b673d 100644
@@ -184,6 +184,7 @@ do_install_ptest () {
     install ${S}/build-aux/test-driver ${D}${PTEST_PATH}/build-aux/
     cp ${B}/Makefile ${D}${PTEST_PATH}/
     cp ${S}/init.cfg ${D}${PTEST_PATH}/
+    sed -i 's/CC -Wall -shared/CC -Wall -shared -l \/usr\/include\//g' ${D}${PTEST_PATH}/init.cfg
     cp -r ${B}/src ${D}${PTEST_PATH}/
     cp -r ${S}/src/*.c ${D}${PTEST_PATH}/src
     sed -i '/^VPATH/s/= .*$/= ./g' ${D}${PTEST_PATH}/Makefile
Signature · 1 line
2.25.1
#1 lore raw

Hello Qiu,

Quoted 18 lines · On Fri, 14 Apr 2023 16:53:20 +0800 "[email protected]" <[email protected]>…

From: Qiu Tingting <[email protected]>

If gcc is installed in image, ptest result has 4 ERROR.
ERROR: tests/rm/r-root.sh
ERROR: tests/rm/rm-readdir-fail.sh
ERROR: tests/cp/nfs-removal-race.sh
ERROR: tests/ls/getxattr-speedup.sh

r-root.log as an example:
--------------------------
k.c:1:10: fatal error: stdio.h: No such file or directory

      1 | #include <stdio.h>
        |          ^~~~~~~~~

compilation terminated.
r-root.sh: set-up failure: failed to build shared library ERROR tests/rm/r-root.sh (exit status: 99)
--------------------------

Quoted 7 lines

reason:
In these cases, k.c file is created and compiled by gcc before run. There is a stdio.h file in /usr/include/ directory,
but gcc parameter is not set it.

solution:
Add "-l /usr/include/" in gcc parameter.

Why "-l"? Shouldn't it be "-I"?

Best regards,
Luca

Signature · 3 lines
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
#2 lore raw

Hi Luca,

Quoted 36 lines

-----Original Message-----
From: Luca Ceresoli <[email protected]>
Sent: Friday, April 14, 2023 5:41 PM
To: Qiu, Tingting/仇 婷婷 <[email protected]>
Cc: [email protected]; FNST fnstml-fujitsuten <[email protected]>
Subject: Re: [OE-core] [PATCH V1] coreutils: Add gcc parameter for ptest

Hello Qiu,

Quoted 23 lines · On Fri, 14 Apr 2023 16:53:20 +0800 "[email protected]" <[email protected]>…

From: Qiu Tingting <[email protected]>

If gcc is installed in image, ptest result has 4 ERROR.
ERROR: tests/rm/r-root.sh
ERROR: tests/rm/rm-readdir-fail.sh
ERROR: tests/cp/nfs-removal-race.sh
ERROR: tests/ls/getxattr-speedup.sh

r-root.log as an example:
--------------------------
k.c:1:10: fatal error: stdio.h: No such file or directory

      1 | #include <stdio.h>
        |          ^~~~~~~~~

compilation terminated.
r-root.sh: set-up failure: failed to build shared library ERROR tests/rm/r-root.sh (exit status: 99)
--------------------------

reason:
In these cases, k.c file is created and compiled by gcc before run. There is a stdio.h file in /usr/include/ directory,
but gcc parameter is not set it.

Quoted 4 lines
Quoted 2 lines

solution:
Add "-l /usr/include/" in gcc parameter.

Why "-l"? Shouldn't it be "-I"?

Yes, it should be "-I".
Thanks

Best regards,
Qiu Tingting

Quoted 8 lines

Best regards,
Luca

--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

#3 lore raw
In reply to [email protected]
Quoted 26 lines · On Fri, 2023-04-14 at 16:53 +0800, [email protected] wrote:

From: Qiu Tingting <[email protected]>

If gcc is installed in image, ptest result has 4 ERROR.
ERROR: tests/rm/r-root.sh
ERROR: tests/rm/rm-readdir-fail.sh
ERROR: tests/cp/nfs-removal-race.sh
ERROR: tests/ls/getxattr-speedup.sh

r-root.log as an example:
--------------------------
k.c:1:10: fatal error: stdio.h: No such file or directory

      1 | #include <stdio.h>
        |          ^~~~~~~~~

compilation terminated.
r-root.sh: set-up failure: failed to build shared library ERROR tests/rm/r-root.sh (exit status: 99)
--------------------------

reason:
In these cases, k.c file is created and compiled by gcc before run. There is a stdio.h file in /usr/include/ directory,
but gcc parameter is not set it.

solution:
Add "-l /usr/include/" in gcc parameter.

Quoted 7 lines

other:
If gcc is not installed in image, these cases will be skipped.

---
 meta/recipes-core/coreutils/coreutils_9.1.bb | 1 +
 1 file changed, 1 insertion(+)

I'm a bit puzzled by this. Wouldn't on target gcc have /usr/include as part of it's default search path? Why isn't the default search path working?

Cheers,

Richard

Quoted 21 lines
meta/recipes-core/coreutils/coreutils_9.1.bb +1 -1
index 4807eefd04..fe785b673d 100644
@@ -184,6 +184,7 @@ do_install_ptest () {
     install ${S}/build-aux/test-driver ${D}${PTEST_PATH}/build-aux/
     cp ${B}/Makefile ${D}${PTEST_PATH}/
     cp ${S}/init.cfg ${D}${PTEST_PATH}/
+    sed -i 's/CC -Wall -shared/CC -Wall -shared -l \/usr\/include\//g' ${D}${PTEST_PATH}/init.cfg
     cp -r ${B}/src ${D}${PTEST_PATH}/
     cp -r ${S}/src/*.c ${D}${PTEST_PATH}/src
     sed -i '/^VPATH/s/= .*$/= ./g' ${D}${PTEST_PATH}/Makefile
-=-=-=-=-=-=-=-=-=-=-=-

Links: You receive all messages sent to this group.
View/Reply Online (#179993): https://lists.openembedded.org/g/openembedded-core/message/179993
Mute This Topic: https://lists.openembedded.org/mt/98258324/1686473
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#4 lore raw
Quoted 37 lines · Richard Purdie
Quoted 26 lines · On Fri, 2023-04-14 at 16:53 +0800, [email protected] wrote:

From: Qiu Tingting <[email protected]>

If gcc is installed in image, ptest result has 4 ERROR.
ERROR: tests/rm/r-root.sh
ERROR: tests/rm/rm-readdir-fail.sh
ERROR: tests/cp/nfs-removal-race.sh
ERROR: tests/ls/getxattr-speedup.sh

r-root.log as an example:
--------------------------
k.c:1:10: fatal error: stdio.h: No such file or directory

      1 | #include <stdio.h>
        |          ^~~~~~~~~

compilation terminated.
r-root.sh: set-up failure: failed to build shared library ERROR tests/rm/r-root.sh (exit status: 99)
--------------------------

reason:
In these cases, k.c file is created and compiled by gcc before run. There is a stdio.h file in /usr/include/ directory,
but gcc parameter is not set it.

solution:
Add "-l /usr/include/" in gcc parameter.

Quoted 7 lines

other:
If gcc is not installed in image, these cases will be skipped.

---
 meta/recipes-core/coreutils/coreutils_9.1.bb | 1 +
 1 file changed, 1 insertion(+)
Quoted 3 lines

I'm a bit puzzled by this. Wouldn't on target gcc have /usr/include as part of it's default search path? Why isn't the default search path working?

yeah. Perhaps looking at full compiler commandline used just for this test would help maybe there is something like -ffreestanding or something passed to it.

Quoted 31 lines

Cheers,

Richard

Quoted 8 lines
meta/recipes-core/coreutils/coreutils_9.1.bb +0 -0
index 4807eefd04..fe785b673d 100644

meta/recipes-core/coreutils/coreutils_9.1.bb do_install_ptest () { · line 190

Quoted 7 lines
meta/recipes-core/coreutils/coreutils_9.1.bb +1 -0
@@ -184,6 +184,7 @@ do_install_ptest () {
     install ${S}/build-aux/test-driver ${D}${PTEST_PATH}/build-aux/
     cp ${B}/Makefile ${D}${PTEST_PATH}/
     cp ${S}/init.cfg ${D}${PTEST_PATH}/
+    sed -i 's/CC -Wall -shared/CC -Wall -shared -l \/usr\/include\//g' ${D}${PTEST_PATH}/init.cfg
     cp -r ${B}/src ${D}${PTEST_PATH}/
     cp -r ${S}/src/*.c ${D}${PTEST_PATH}/src
     sed -i '/^VPATH/s/= .*$/= ./g' ${D}${PTEST_PATH}/Makefile

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#179996): https://lists.openembedded.org/g/openembedded-core/message/179996
Mute This Topic: https://lists.openembedded.org/mt/98258324/1997914
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#5 lore raw
Quoted 50 lines

-----Original Message-----
From: Khem Raj <[email protected]>
Sent: Saturday, April 15, 2023 12:11 AM
To: Richard Purdie <[email protected]>
Cc: Qiu, Tingting/仇 婷婷 <[email protected]>; [email protected]; FNST fnstml-fujitsuten <[email protected]>
Subject: Re: [OE-core] [PATCH V1] coreutils: Add gcc parameter for ptest

Quoted 37 lines · Richard Purdie
Quoted 33 lines · On Fri, 2023-04-14 at 16:53 +0800, [email protected] wrote:

From: Qiu Tingting <[email protected]>

If gcc is installed in image, ptest result has 4 ERROR.
ERROR: tests/rm/r-root.sh
ERROR: tests/rm/rm-readdir-fail.sh
ERROR: tests/cp/nfs-removal-race.sh
ERROR: tests/ls/getxattr-speedup.sh

r-root.log as an example:
--------------------------
k.c:1:10: fatal error: stdio.h: No such file or directory

      1 | #include <stdio.h>
        |          ^~~~~~~~~

compilation terminated.
r-root.sh: set-up failure: failed to build shared library ERROR tests/rm/r-root.sh (exit status: 99)
--------------------------

reason:
In these cases, k.c file is created and compiled by gcc before run. There is a stdio.h file in /usr/include/ directory,
but gcc parameter is not set it.

solution:
Add "-l /usr/include/" in gcc parameter.

other:
If gcc is not installed in image, these cases will be skipped.

---
 meta/recipes-core/coreutils/coreutils_9.1.bb | 1 +
 1 file changed, 1 insertion(+)
Quoted 7 lines
Quoted 3 lines

I'm a bit puzzled by this. Wouldn't on target gcc have /usr/include as part of it's default search path? Why isn't the default search path working?

yeah. Perhaps looking at full compiler commandline used just for this test would help maybe there is something like -ffreestanding or something passed to it.

Normal gcc have /usr/include as part of its default search path.
I used aarch64-agl-linux-gcc for aarch64 board, which does not search this path.

Best regards,
Qiu Tingting

Quoted 37 lines
Quoted 26 lines

Cheers,

Richard

Quoted 9 lines
meta/recipes-core/coreutils/coreutils_9.1.bb +0 -0
index 4807eefd04..fe785b673d 100644

meta/recipes-core/coreutils/coreutils_9.1.bb do_install_ptest () { · line 190

Quoted 8 lines
meta/recipes-core/coreutils/coreutils_9.1.bb +2 -0
@@ -184,6 +184,7 @@ do_install_ptest () {
     install ${S}/build-aux/test-driver ${D}${PTEST_PATH}/build-aux/
     cp ${B}/Makefile ${D}${PTEST_PATH}/
     cp ${S}/init.cfg ${D}${PTEST_PATH}/
+    sed -i 's/CC -Wall -shared/CC -Wall -shared -l
+ \/usr\/include\//g' ${D}${PTEST_PATH}/init.cfg
     cp -r ${B}/src ${D}${PTEST_PATH}/
     cp -r ${S}/src/*.c ${D}${PTEST_PATH}/src
     sed -i '/^VPATH/s/= .*$/= ./g' ${D}${PTEST_PATH}/Makefile
Quoted 7 lines

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#179996):
https://lists.openembedded.org/g/openembedded-core/message/179996
Mute This Topic: https://lists.openembedded.org/mt/98258324/1997914
Group Owner: [email protected] Unsubscribe:

https://lists.openembedded.org/g/openembedded-core/unsub

Quoted 3 lines

[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#6 lore raw
Quoted 55 lines · Tingting Qiu (Fujitsu)
Quoted 50 lines

-----Original Message-----
From: Khem Raj <[email protected]>
Sent: Saturday, April 15, 2023 12:11 AM
To: Richard Purdie <[email protected]>
Cc: Qiu, Tingting/仇 婷婷 <[email protected]>; [email protected]; FNST fnstml-fujitsuten <[email protected]>
Subject: Re: [OE-core] [PATCH V1] coreutils: Add gcc parameter for ptest

Quoted 37 lines · Richard Purdie
Quoted 33 lines · On Fri, 2023-04-14 at 16:53 +0800, [email protected] wrote:

From: Qiu Tingting <[email protected]>

If gcc is installed in image, ptest result has 4 ERROR.
ERROR: tests/rm/r-root.sh
ERROR: tests/rm/rm-readdir-fail.sh
ERROR: tests/cp/nfs-removal-race.sh
ERROR: tests/ls/getxattr-speedup.sh

r-root.log as an example:
--------------------------
k.c:1:10: fatal error: stdio.h: No such file or directory

      1 | #include <stdio.h>
        |          ^~~~~~~~~

compilation terminated.
r-root.sh: set-up failure: failed to build shared library ERROR tests/rm/r-root.sh (exit status: 99)
--------------------------

reason:
In these cases, k.c file is created and compiled by gcc before run. There is a stdio.h file in /usr/include/ directory,
but gcc parameter is not set it.

solution:
Add "-l /usr/include/" in gcc parameter.

other:
If gcc is not installed in image, these cases will be skipped.

---
 meta/recipes-core/coreutils/coreutils_9.1.bb | 1 +
 1 file changed, 1 insertion(+)
Quoted 5 lines
Quoted 3 lines

I'm a bit puzzled by this. Wouldn't on target gcc have /usr/include as part of it's default search path? Why isn't the default search path working?

yeah. Perhaps looking at full compiler commandline used just for this

Quoted 8 lines

test

Quoted 1 line

would help maybe there is something like -ffreestanding or something

passed

Quoted 1 line

to it.

Normal gcc have /usr/include as part of its default search path. I used aarch64-agl-linux-gcc for aarch64 board, which does not search this path.

This should be a symlink to gcc on target so I wonder why it does not work

Quoted 41 lines

Best regards,
Qiu Tingting

Quoted 37 lines
Quoted 26 lines

Cheers,

Richard

Quoted 9 lines
meta/recipes-core/coreutils/coreutils_9.1.bb +0 -0
index 4807eefd04..fe785b673d 100644

meta/recipes-core/coreutils/coreutils_9.1.bb do_install_ptest () { · line 190

Quoted 8 lines
meta/recipes-core/coreutils/coreutils_9.1.bb +2 -0
@@ -184,6 +184,7 @@ do_install_ptest () {
     install ${S}/build-aux/test-driver ${D}${PTEST_PATH}/build-aux/
     cp ${B}/Makefile ${D}${PTEST_PATH}/
     cp ${S}/init.cfg ${D}${PTEST_PATH}/
+    sed -i 's/CC -Wall -shared/CC -Wall -shared -l
+ \/usr\/include\//g' ${D}${PTEST_PATH}/init.cfg
     cp -r ${B}/src ${D}${PTEST_PATH}/
     cp -r ${S}/src/*.c ${D}${PTEST_PATH}/src
     sed -i '/^VPATH/s/= .*$/= ./g' ${D}${PTEST_PATH}/Makefile
Quoted 7 lines

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#179996):
https://lists.openembedded.org/g/openembedded-core/message/179996
Mute This Topic: https://lists.openembedded.org/mt/98258324/1997914
Group Owner: [email protected] Unsubscribe:

https://lists.openembedded.org/g/openembedded-core/unsub

Quoted 3 lines

[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#7 lore raw

From: Khem Raj <[email protected]>
Sent: Tuesday, April 18, 2023 9:14 AM
To: Qiu, Tingting/仇 婷婷 <[email protected]>
Cc: Richard Purdie <[email protected]>; FNST fnstml-fujitsuten <[email protected]>; [email protected]
Subject: Re: [OE-core] [PATCH V1] coreutils: Add gcc parameter for ptest

Quoted 48 lines · On Mon, Apr 17, 2023 at 6:05 PM Tingting Qiu (Fujitsu)…

-----Original Message-----
From: Khem Raj <[email protected]<mailto:[email protected]>>
Sent: Saturday, April 15, 2023 12:11 AM
To: Richard Purdie <[email protected]<mailto:[email protected]>>
Cc: Qiu, Tingting/仇 婷婷 <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; FNST fnstml-fujitsuten <[email protected]<mailto:[email protected]>>
Subject: Re: [OE-core] [PATCH V1] coreutils: Add gcc parameter for ptest

Quoted 37 lines · On Fri, Apr 14, 2023 at 3:06 AM Richard Purdie…
Quoted 33 lines · On Fri, 2023-04-14 at 16:53 +0800, [email protected]<mailto:[email protected]>…

From: Qiu Tingting <[email protected]<mailto:[email protected]>>

If gcc is installed in image, ptest result has 4 ERROR.
ERROR: tests/rm/r-root.sh
ERROR: tests/rm/rm-readdir-fail.sh
ERROR: tests/cp/nfs-removal-race.sh
ERROR: tests/ls/getxattr-speedup.sh

r-root.log as an example:
--------------------------
k.c:1:10: fatal error: stdio.h: No such file or directory

      1 | #include <stdio.h>
        |          ^~~~~~~~~

compilation terminated.
r-root.sh: set-up failure: failed to build shared library ERROR tests/rm/r-root.sh (exit status: 99)
--------------------------

reason:
In these cases, k.c file is created and compiled by gcc before run. There is a stdio.h file in /usr/include/ directory,
but gcc parameter is not set it.

solution:
Add "-l /usr/include/" in gcc parameter.

other:
If gcc is not installed in image, these cases will be skipped.

---
 meta/recipes-core/coreutils/coreutils_9.1.bb<http://coreutils_9.1.bb> | 1 +
 1 file changed, 1 insertion(+)
Quoted 7 lines
Quoted 3 lines

I'm a bit puzzled by this. Wouldn't on target gcc have /usr/include as part of it's default search path? Why isn't the default search path working?

yeah. Perhaps looking at full compiler commandline used just for this test would help maybe there is something like -ffreestanding or something passed to it.

Normal gcc have /usr/include as part of its default search path.
I used aarch64-agl-linux-gcc for aarch64 board, which does not search this path.

This should be a symlink to gcc on target so I wonder why it does not work

First, see the coreutils’ files which installed on target.
================
Makefile -->created by cross-compile
build-aux
init.cfg --> copied from src
run-ptest
tests
================
In Makefile, CC is defined by aarch64-agl-linux-gcc with --sysroot=recipe-sysroot.
CC = aarch64-agl-linux-gcc -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=recipe-sysroot
In init.cfg, CC is used to compile k.c file.
$CC -Wall -shared --std=gnu99 -fPIC -O2 $* "$in" -o "$out" $gcc_shared_libs_
Because of “--sysroot=recipe-sysroot”, it does not work.
So, we could add “-I /usr/include” in Makefile or init.cfg, or delete “--sysroot=recipe-sysroot” from Makefile.
Which one is better?
Let me know, and I will send the patch v2.
thanks.

Best regards,
Qiu Tingting

Best regards,
Qiu Tingting

Quoted 37 lines
Quoted 26 lines

Cheers,

Richard

Quoted 9 lines
meta/recipes-core/coreutils/coreutils_9.1.bb<http://coreutils_9.1.bb> +0 -0
index 4807eefd04..fe785b673d 100644

meta/recipes-core/coreutils/coreutils_9.1.bb<http://coreutils_9.1.bb> do_install_ptest () {

Quoted 8 lines
meta/recipes-core/coreutils/coreutils_9.1.bb<http://coreutils_9.1.bb> +2 -0
@@ -184,6 +184,7 @@ do_install_ptest () {
     install ${S}/build-aux/test-driver ${D}${PTEST_PATH}/build-aux/
     cp ${B}/Makefile ${D}${PTEST_PATH}/
     cp ${S}/init.cfg ${D}${PTEST_PATH}/
+    sed -i 's/CC -Wall -shared/CC -Wall -shared -l
+ \/usr\/include\//g' ${D}${PTEST_PATH}/init.cfg
     cp -r ${B}/src ${D}${PTEST_PATH}/
     cp -r ${S}/src/*.c ${D}${PTEST_PATH}/src
     sed -i '/^VPATH/s/= .*$/= ./g' ${D}${PTEST_PATH}/Makefile
Quoted 7 lines

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#179996):
https://lists.openembedded.org/g/openembedded-core/message/179996
Mute This Topic: https://lists.openembedded.org/mt/98258324/1997914
Group Owner: [email protected]<mailto:openembedded-core%[email protected]> Unsubscribe:

https://lists.openembedded.org/g/openembedded-core/unsub

Quoted 3 lines

[[email protected]<mailto:[email protected]>]
-=-=-=-=-=-=-=-=-=-=-=-

#8 lore raw
In reply to Khem Raj
Quoted 7 lines

This should be a symlink to gcc on target so I wonder why it does not work

First, see the coreutils’ files which installed on target.

================

Makefile  -->created by cross-compile

build-aux

init.cfg     --> copied from src

run-ptest

tests

================

In Makefile, CC is defined by aarch64-agl-linux-gcc with --sysroot=recipe-sysroot.

CC = aarch64-agl-linux-gcc  -fstack-protector-strong  -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=recipe-sysroot

In init.cfg, CC  is used to compile k.c file.

$CC -Wall -shared --std=gnu99 -fPIC -O2 $* "$in" -o "$out" $gcc_shared_libs_

Because of “ --sysroot=recipe-sysroot ” , it does not work.

So, we could add “ -I /usr/include ” in Makefile or init.cfg, or delete “ --sysroot=recipe-sysroot ” from Makefile.

Which one is better?

Let me know, and I will send the patch v2.

thanks.

#9 lore raw
Quoted 30 lines · On Mon, Apr 17, 2023 at 8:42 PM [email protected] <[email protected]> wrote:

This should be a symlink to gcc on target so I wonder why it does not work

First, see the coreutils’ files which installed on target.

================

Makefile -->created by cross-compile

build-aux

init.cfg --> copied from src

run-ptest

tests

================

In Makefile, CC is defined by aarch64-agl-linux-gcc with --sysroot=recipe-sysroot.

CC = aarch64-agl-linux-gcc -fstack-protector-strong -O2
-D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=recipe-sysroot

In init.cfg, CC is used to compile k.c file.

$CC -Wall -shared --std=gnu99 -fPIC -O2 $* "$in" -o "$out"
$gcc_shared_libs_

Quoted 7 lines

Because of “--sysroot=recipe-sysroot”, it does not work.

So, we could add “-I /usr/include” in Makefile or init.cfg, or delete “ --sysroot=recipe-sysroot” from Makefile.

Which one is better?

Delete sysroot

Quoted 15 lines

Let me know, and I will send the patch v2.

thanks.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#180174):
https://lists.openembedded.org/g/openembedded-core/message/180174
Mute This Topic: https://lists.openembedded.org/mt/98258324/1997914
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-