From: "Tom Hochstein" <tom.hochstein@nxp.com>
To: Tom Hochstein <tom.hochstein@nxp.com>, Jupiter <jupiter.hce@gmail.com>
Cc: Lauren Post <lauren.post@nxp.com>,
Otavio Salvador <otavio.salvador@ossystems.com.br>,
Andrey Zhizhikin <andrey.z@gmail.com>, Jun Zhu <junzhu@nxp.com>,
"meta-freescale@lists.yoctoproject.org"
<meta-freescale@lists.yoctoproject.org>
Subject: Re: [meta-freescale] MTD UBI undefined reference failed to build OE gatesgarth branch
Date: Tue, 19 Jan 2021 23:38:14 +0000 [thread overview]
Message-ID: <DBBPR04MB77531C1A231E655B31EA4151E2A30@DBBPR04MB7753.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <165BAE2FBF9D93F6.23889@lists.yoctoproject.org>
Okay, I found the lines responsible for build/tmp-glibc in poky/meta/conf/distro/defaultsetup.conf. It appears that your config is using the default for this, while we are overriding:
# Allow single libc distros to disable this code
TCLIBCAPPEND ?= "-${TCLIBC}"
TMPDIR .= "${TCLIBCAPPEND}"
-----Original Message-----
From: meta-freescale@lists.yoctoproject.org <meta-freescale@lists.yoctoproject.org> On Behalf Of Tom Hochstein via lists.yoctoproject.org
Sent: Tuesday, January 19, 2021 10:13 AM
To: Jupiter <jupiter.hce@gmail.com>
Cc: Lauren Post <lauren.post@nxp.com>; Otavio Salvador <otavio.salvador@ossystems.com.br>; Andrey Zhizhikin <andrey.z@gmail.com>; Jun Zhu <junzhu@nxp.com>; meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] MTD UBI undefined reference failed to build OE gatesgarth branch
Hi Jupiter,
In that case, you could try building with MACHINE=imx6ullevk, then compare the builds.
One thing I don't understand is your log shows build/tmp-glibc/work. I'm only familiar with builds using build/tmp/work.
Tom
-----Original Message-----
From: Jupiter <jupiter.hce@gmail.com>
Sent: Tuesday, January 19, 2021 2:57 AM
To: Tom Hochstein <tom.hochstein@nxp.com>
Cc: Lauren Post <lauren.post@nxp.com>; Otavio Salvador <otavio.salvador@ossystems.com.br>; Andrey Zhizhikin <andrey.z@gmail.com>; Jun Zhu <junzhu@nxp.com>; meta-freescale@lists.yoctoproject.org
Subject: Re: MTD UBI undefined reference failed to build OE gatesgarth branch
Hi Tom,
Thanks for your response and help.
> In trying to duplicate your issue, as Andrey pointed out, I see that
> imx6ullevk.conf does in fact not have support for nand. I'm not sure why, as
> we have had it in out meta-imx layer for some time.
Yes, indeed I was able to build it on the zeus branch and to work on
zeus for a long time.
> So I updated imx6ullevk.conf with nand support. It built fine.
It is not that problem, I defined nand support in my machine
configure already, do you have a build system with bitbake, oe-core
(poky) for building gatesgarth branch so I can debug it?
> Can you try building with my fork?
>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fthochstein%2Fmeta-freescale&data=04%7C01%7Ctom.hochstein%40nxp.com%7C9051a3894e6c4249f79f08d8bc953011%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637466696228174025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ianZoZDG1lUtI7RrRnKKtZ%2FuADlj2aqg056h2LJBdEI%3D&reserved=0
Which branch should I build it? I pulled your fork, but I could not
find gatesgarth, so I used master branch to build, it still has many
undefined references:
| /build/YoctoGatesgarth/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2020.04-r0/git/cmd/ubi.c:478:
undefined reference to `mtd_probe_devices'
| arm-oe-linux-gnueabi-ld.bfd:
/build/YoctoGatesgarth/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2020.04-r0/git/cmd/ubi.c:479:
undefined reference to `get_mtd_device_nm'
| arm-oe-linux-gnueabi-ld.bfd:
/build/YoctoGatesgarth/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2020.04-r0/git/cmd/ubi.c:484:
undefined reference to `put_mtd_device'
| arm-oe-linux-gnueabi-ld.bfd: drivers/built-in.o: in function
`ubi_detach_mtd_dev':
| /build/YoctoGatesgarth/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2020.04-r0/git/drivers/mtd/ubi/build.c:1161:
undefined reference to `put_mtd_device'
Thank you very much.
Kind regards,
Jupiter
prev parent reply other threads:[~2021-01-19 23:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 8:07 MTD UBI undefined reference failed to build OE gatesgarth branch JH
2021-01-15 19:32 ` JH
2021-01-15 20:12 ` [meta-freescale] " Andrey Zhizhikin
2021-01-15 20:43 ` JH
2021-01-18 0:21 ` JH
2021-01-19 0:16 ` Tom Hochstein
2021-01-19 8:56 ` JH
2021-01-19 16:13 ` Tom Hochstein
[not found] ` <165BAE2FBF9D93F6.23889@lists.yoctoproject.org>
2021-01-19 23:38 ` Tom Hochstein [this message]
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=DBBPR04MB77531C1A231E655B31EA4151E2A30@DBBPR04MB7753.eurprd04.prod.outlook.com \
--to=tom.hochstein@nxp.com \
--cc=andrey.z@gmail.com \
--cc=junzhu@nxp.com \
--cc=jupiter.hce@gmail.com \
--cc=lauren.post@nxp.com \
--cc=meta-freescale@lists.yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).