Bug 12795 - [2.6 M1] gcc/g++ doesn't work on beaglebone black
Summary: [2.6 M1] gcc/g++ doesn't work on beaglebone black
Status: VERIFIED FIXED
Alias: None
Product: General Runtime
Classification: Runtime
Component: General Runtime (show other bugs)
Version: 2.6
Hardware: BeagleBone Multiple
: Undecided major
Target Milestone: ---
Assignee: Khem Raj
QA Contact: Yi Zhao
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-06-19 01:11 UTC by Yi Zhao
Modified: 2018-07-23 00:47 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yi Zhao 2018-06-19 01:11:55 UTC 
Git rev: master/ddbd7b0cd6580ee26e11aa87e426fb294b372d64
Image location: https://autobuilder.yocto.io/pub/releases/yocto-2.6_M1.rc1/machines/beaglebone-yocto/

The gcc/g++ doesn't work on beaglebone black:

$ gcc -o test test.c
cc1: error: -mfloat-abi=hard: selected processor lacks an FPU




$ cat test.c
#include <stdio.h>

int main()
{
        printf("Hello world!\n");
        return 0;
}
Comment 1 Khem Raj 2018-06-20 02:25:13 UTC 
Can you post the following.

log.do_configure and log.do_compile for target gcc ?

There was such an issue in gcc8 but it was fixed and I checked we
have that fix on OE gcc 8, therefore it must be something new
Comment 2 Khem Raj 2018-06-20 05:22:57 UTC 
Patch is on ml
https://patchwork.openembedded.org/patch/151841/
Comment 4 Yi Zhao 2018-07-23 00:47:38 UTC 
Verified with 2.6 M2 RC1 build.
Poky git rev: b0f2f690a3513e4c9fa30fee1b8d7ac2d7140657