public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "qiutt@fujitsu.com" <qiutt@fujitsu.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V1] coreutils: Add gcc parameter for ptest
Date: Mon, 17 Apr 2023 20:42:33 -0700	[thread overview]
Message-ID: <17294.1681789353965294418@lists.openembedded.org> (raw)
In-Reply-To: <CAMKF1socwNE1yE3ywMyimSqu8JF03hzKR27YKXL6qJu-1r2d3g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 973 bytes --]

> 
> 
> 
> 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.

[-- Attachment #2: Type: text/html, Size: 3783 bytes --]

  parent reply	other threads:[~2023-04-18  3:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14  8:53 [PATCH V1] coreutils: Add gcc parameter for ptest qiutt
2023-04-14  9:41 ` [OE-core] " Luca Ceresoli
2023-04-18  1:00   ` Tingting Qiu (Fujitsu)
2023-04-14 10:06 ` Richard Purdie
2023-04-14 16:11   ` Khem Raj
2023-04-18  1:05     ` Tingting Qiu (Fujitsu)
2023-04-18  1:13       ` Khem Raj
2023-04-18  3:27         ` Tingting Qiu (Fujitsu)
2023-04-18  3:42         ` qiutt [this message]
2023-04-18  5:22           ` Khem Raj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17294.1681789353965294418@lists.openembedded.org \
    --to=qiutt@fujitsu.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox