[U-Boot] Build failure in u-boot-mmc/master: undefined reference to error
With the latest content of u-boot-mmc/master, 41dc35a149b3 "drivers: mmc: Avoid memory leak in case of failure", all Tegra boards (perhaps others too; my system only tests Tegra) fail to build with the following error:
drivers/built-in.o: In function `mmc_select_mode_and_width': /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/drivers/mmc/mmc.c:1847: undefined reference to `error' drivers/built-in.o: In function `bus_width': /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/drivers/mmc/mmc.c:1436: undefined reference to `error' /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/drivers/mmc/mmc.c:1436: undefined reference to `error' /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/drivers/mmc/mmc.c:1436: undefined reference to `error' drivers/built-in.o: In function `mmc_get_capabilities': /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/drivers/mmc/mmc.c:831: undefined reference to `error' arm-none-eabi-ld.bfd: BFD (2.24-2ubuntu2+4) 2.24 assertion fail ../../binutils-2.24/bfd/elf32-arm.c:7696 arm-none-eabi-ld.bfd: error: required section '.rel.plt' not found in the linker script arm-none-eabi-ld.bfd: final link failed: Invalid operation
Dear Stephen,
On 10/21/2017 12:47 AM, Stephen Warren wrote:
With the latest content of u-boot-mmc/master, 41dc35a149b3 "drivers: mmc: Avoid memory leak in case of failure", all Tegra boards (perhaps others too; my system only tests Tegra) fail to build with the following error:
I had found the same error at build testing, I will fix it on today. Thanks for noticing it.
Best Regards, Jaehoon Chung
drivers/built-in.o: In function `mmc_select_mode_and_width': /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/drivers/mmc/mmc.c:1847: undefined reference to `error' drivers/built-in.o: In function `bus_width': /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/drivers/mmc/mmc.c:1436: undefined reference to `error' /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/drivers/mmc/mmc.c:1436: undefined reference to `error' /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/drivers/mmc/mmc.c:1436: undefined reference to `error' drivers/built-in.o: In function `mmc_get_capabilities': /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/drivers/mmc/mmc.c:831: undefined reference to `error' arm-none-eabi-ld.bfd: BFD (2.24-2ubuntu2+4) 2.24 assertion fail ../../binutils-2.24/bfd/elf32-arm.c:7696 arm-none-eabi-ld.bfd: error: required section '.rel.plt' not found in the linker script arm-none-eabi-ld.bfd: final link failed: Invalid operation
On 10/22/2017 08:53 PM, Jaehoon Chung wrote:
Dear Stephen,
On 10/21/2017 12:47 AM, Stephen Warren wrote:
With the latest content of u-boot-mmc/master, 41dc35a149b3 "drivers: mmc: Avoid memory leak in case of failure", all Tegra boards (perhaps others too; my system only tests Tegra) fail to build with the following error:
I had found the same error at build testing, I will fix it on today. Thanks for noticing it.
Thanks.
I see that the build failures are fixed now, but the following unit-tests are failing on sandbox:
test_ut[ut_dm_blk_base] test_ut[ut_dm_blk_devnum] test_ut[ut_dm_blk_get_from_parent] test_ut[ut_dm_mmc_base] test_ut[ut_dm_mmc_blk]
For example:
=> ut dm blk_base Test: dm_test_blk_base: blk.c unable to select a mode mmc_init: -524, time 6 /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/test/dm/blk.c:40, dm_test_blk_base(): 0 == blk_first_device(IF_TYPE_HOST, &dev): Expected 0, got -524 Test: dm_test_blk_base: blk.c (flat tree) unable to select a mode mmc_init: -524, time 6 /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/test/dm/blk.c:40, dm_test_blk_base(): 0 == blk_first_device(IF_TYPE_HOST, &dev): Expected 0, got -524 Failures: 2
You should be able to reproduce this by running the following from the U-Boot source tree:
./test/py/test.py --bd sandbox --build
On 10/24/2017 12:22 AM, Stephen Warren wrote:
On 10/22/2017 08:53 PM, Jaehoon Chung wrote:
Dear Stephen,
On 10/21/2017 12:47 AM, Stephen Warren wrote:
With the latest content of u-boot-mmc/master, 41dc35a149b3 "drivers: mmc: Avoid memory leak in case of failure", all Tegra boards (perhaps others too; my system only tests Tegra) fail to build with the following error:
I had found the same error at build testing, I will fix it on today. Thanks for noticing it.
Thanks.
I see that the build failures are fixed now, but the following unit-tests are failing on sandbox:
test_ut[ut_dm_blk_base] test_ut[ut_dm_blk_devnum] test_ut[ut_dm_blk_get_from_parent] test_ut[ut_dm_mmc_base] test_ut[ut_dm_mmc_blk]
For example:
=> ut dm blk_base Test: dm_test_blk_base: blk.c unable to select a mode mmc_init: -524, time 6 /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/test/dm/blk.c:40, dm_test_blk_base(): 0 == blk_first_device(IF_TYPE_HOST, &dev): Expected 0, got -524 Test: dm_test_blk_base: blk.c (flat tree) unable to select a mode mmc_init: -524, time 6 /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/test/dm/blk.c:40, dm_test_blk_base(): 0 == blk_first_device(IF_TYPE_HOST, &dev): Expected 0, got -524 Failures: 2
You should be able to reproduce this by running the following from the U-Boot source tree:
./test/py/test.py --bd sandbox --build
Will check. thanks!
On 10/24/2017 01:54 AM, Jaehoon Chung wrote:
On 10/24/2017 12:22 AM, Stephen Warren wrote:
On 10/22/2017 08:53 PM, Jaehoon Chung wrote:
Dear Stephen,
On 10/21/2017 12:47 AM, Stephen Warren wrote:
With the latest content of u-boot-mmc/master, 41dc35a149b3 "drivers: mmc: Avoid memory leak in case of failure", all Tegra boards (perhaps others too; my system only tests Tegra) fail to build with the following error:
I had found the same error at build testing, I will fix it on today. Thanks for noticing it.
Thanks.
I see that the build failures are fixed now, but the following unit-tests are failing on sandbox:
test_ut[ut_dm_blk_base] test_ut[ut_dm_blk_devnum] test_ut[ut_dm_blk_get_from_parent] test_ut[ut_dm_mmc_base] test_ut[ut_dm_mmc_blk]
For example:
=> ut dm blk_base Test: dm_test_blk_base: blk.c unable to select a mode mmc_init: -524, time 6 /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/test/dm/blk.c:40, dm_test_blk_base(): 0 == blk_first_device(IF_TYPE_HOST, &dev): Expected 0, got -524 Test: dm_test_blk_base: blk.c (flat tree) unable to select a mode mmc_init: -524, time 6 /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/test/dm/blk.c:40, dm_test_blk_base(): 0 == blk_first_device(IF_TYPE_HOST, &dev): Expected 0, got -524 Failures: 2
You should be able to reproduce this by running the following from the U-Boot source tree:
./test/py/test.py --bd sandbox --build
Will check. thanks!
Jaehoon, did you find the issue? I don't see any new commits pushed.
On 11/03/2017 05:52 AM, Stephen Warren wrote:
On 10/24/2017 01:54 AM, Jaehoon Chung wrote:
On 10/24/2017 12:22 AM, Stephen Warren wrote:
On 10/22/2017 08:53 PM, Jaehoon Chung wrote:
Dear Stephen,
On 10/21/2017 12:47 AM, Stephen Warren wrote:
With the latest content of u-boot-mmc/master, 41dc35a149b3 "drivers: mmc: Avoid memory leak in case of failure", all Tegra boards (perhaps others too; my system only tests Tegra) fail to build with the following error:
I had found the same error at build testing, I will fix it on today. Thanks for noticing it.
Thanks.
I see that the build failures are fixed now, but the following unit-tests are failing on sandbox:
test_ut[ut_dm_blk_base] test_ut[ut_dm_blk_devnum] test_ut[ut_dm_blk_get_from_parent] test_ut[ut_dm_mmc_base] test_ut[ut_dm_mmc_blk]
For example:
=> ut dm blk_base Test: dm_test_blk_base: blk.c unable to select a mode mmc_init: -524, time 6 /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/test/dm/blk.c:40, dm_test_blk_base(): 0 == blk_first_device(IF_TYPE_HOST, &dev): Expected 0, got -524 Test: dm_test_blk_base: blk.c (flat tree) unable to select a mode mmc_init: -524, time 6 /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/test/dm/blk.c:40, dm_test_blk_base(): 0 == blk_first_device(IF_TYPE_HOST, &dev): Expected 0, got -524 Failures: 2
You should be able to reproduce this by running the following from the U-Boot source tree:
./test/py/test.py --bd sandbox --build
Will check. thanks!
Jaehoon, did you find the issue? I don't see any new commits pushed.
Sorry for late. I didn't see this issue.. Well, i'm checking one more..
On 11/27/2017 02:59 AM, Jaehoon Chung wrote:
On 11/03/2017 05:52 AM, Stephen Warren wrote:
On 10/24/2017 01:54 AM, Jaehoon Chung wrote:
On 10/24/2017 12:22 AM, Stephen Warren wrote:
On 10/22/2017 08:53 PM, Jaehoon Chung wrote:
Dear Stephen,
On 10/21/2017 12:47 AM, Stephen Warren wrote:
With the latest content of u-boot-mmc/master, 41dc35a149b3 "drivers: mmc: Avoid memory leak in case of failure", all Tegra boards (perhaps others too; my system only tests Tegra) fail to build with the following error:
I had found the same error at build testing, I will fix it on today. Thanks for noticing it.
Thanks.
I see that the build failures are fixed now, but the following unit-tests are failing on sandbox:
test_ut[ut_dm_blk_base] test_ut[ut_dm_blk_devnum] test_ut[ut_dm_blk_get_from_parent] test_ut[ut_dm_mmc_base] test_ut[ut_dm_mmc_blk]
For example:
=> ut dm blk_base Test: dm_test_blk_base: blk.c unable to select a mode mmc_init: -524, time 6 /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/test/dm/blk.c:40, dm_test_blk_base(): 0 == blk_first_device(IF_TYPE_HOST, &dev): Expected 0, got -524 Test: dm_test_blk_base: blk.c (flat tree) unable to select a mode mmc_init: -524, time 6 /var/lib/jenkins/workspace/u-boot-denx_uboot_mmc-master-build/src/u-boot/test/dm/blk.c:40, dm_test_blk_base(): 0 == blk_first_device(IF_TYPE_HOST, &dev): Expected 0, got -524 Failures: 2
You should be able to reproduce this by running the following from the U-Boot source tree:
./test/py/test.py --bd sandbox --build
Will check. thanks!
Jaehoon, did you find the issue? I don't see any new commits pushed.
Sorry for late. I didn't see this issue.. Well, i'm checking one more..
FYI the latest code pushed within the last 24 hours still has the same issue.
participants (2)
-
Jaehoon Chung -
Stephen Warren