New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 890858 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Oct 2
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug
Build-Toolchain

Blocking:
issue 891103



Sign in to add a comment

u-boot-tools: failed to build on chromiumos-sdk builder

Project Member Reported by yunlian@chromium.org, Oct 1

Issue description

On chromiumos-sdk builder,

u-boot-tools-2017.05: /usr/include/libfdt_env.h:71:30: error: typedef redefinition with different
u-boot-tools-2017.05:       types ('uint64_t' (aka 'unsigned long') vs '__be64' (aka
u-boot-tools-2017.05:       'unsigned long long'))
u-boot-tools-2017.05: typedef uint64_t FDT_BITWISE fdt64_t;
u-boot-tools-2017.05:                              ^
u-boot-tools-2017.05: ././include/libfdt_env.h:19:16: note: previous definition is here
u-boot-tools-2017.05: typedef __be64 fdt64_t;
u-boot-tools-2017.05: In file included from                ^
u-boot-tools-2017.05: tools/kwbimage.c:13:
 
Cc: vapier@chromium.org sjg@chromium.org
@yunlian -
Is this causing a build failure?
Can you provide a link to this log?
Is this a regression?
If so when did it start?
Labels: OS-Chrome
Also I wonder what changed?
Labels: -Pri-3 Pri-1
It happens on chromiumos-sdk
https://cros-goldeneye.corp.google.com/chromeos/legoland/builderHistory?buildConfig=chromiumos-sdk&buildBranch=master

The log is here.
https://luci-logdog.appspot.com/v/?s=chromeos/buildbucket/cr-buildbucket.appspot.com/8933880528952486928/+/steps/SetupBoard__amd64-host_/0/stdout

Gentoo upstream 2018.05 does not have this problem. 
Mike, could you please put the tarball to our local mirror so that we can
upgrade u-boot-tools?
u-boot-2018.05.tar.bz2 is now available
Owner: yunlian@chromium.org
Blocking: 891103
Is this related to  bug 891103 ? I see we have issues with various u-boot builds in several overlays.
Status: Started (was: Untriaged)
Status: Verified (was: Started)
They are different issue because they are using different ebuild files and different source code.

Sign in to add a comment