Bug 3714 - X32: hjl-tools missing from github.com for x32 kernel builds
Summary: X32: hjl-tools missing from github.com for x32 kernel builds
Status: RESOLVED WORKSFORME
Alias: None
Product: Other YP Layers
Classification: Build System, Metadata & Runtime
Component: layers (show other bugs)
Version: 1.2.2
Hardware: x86 x86_64
: Medium normal
Target Milestone: 1.2.2
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard:
: 3715 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-01-14 13:24 UTC by Alexandru Palalau
Modified: 2013-02-01 23:50 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
linux-libc-headers fetch fail log (99.74 KB, application/octet-stream)
2013-01-14 13:24 UTC, Alexandru Palalau 		no flags Details
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 Alexandru Palalau 2013-01-14 13:24:13 UTC 
Created attachment 1010 [details]
linux-libc-headers fetch fail log

local.conf parameters:
MACHINE ??= "qemux86-64"
DEFAULTTUNE = "x86-64-x32"

OE Build Configuration:
BB_VERSION        = "1.15.2"
TARGET_ARCH       = "x86_64"
TARGET_OS         = "linux-gnux32"
MACHINE           = "qemux86-64"
DISTRO            = "poky"
DISTRO_VERSION    = "1.2.2"
TUNE_FEATURES     = "mx32"
TARGET_FPU        = ""
meta              
meta-yocto        = "denzil:3456295898bf157e40ea1f8c335f0b7285d3d8a7"
meta-x32          = "denzil:d7088df5d4a64f071ec01748b1ca528cf2e85e88"

Attached error log file
Comment 1 Saul Wold 2013-01-14 22:08:08 UTC 
*** Bug 3715 has been marked as a duplicate of this bug. ***
Comment 2 Nitin Kamble 2013-01-14 22:25:09 UTC 
The issue is this URL is no more valid: 
   SRC_URI = "git://github.com/hjl-tools/linux.git;protocal=git;branch=hjl/x32/lfs/v3.1"
Comment 3 Nitin Kamble 2013-01-14 22:37:37 UTC 
  I see the git repo/branch is still present:

https://github.com/hjl-tools/linux/tree/hjl/x32/lfs/v3.1
Comment 4 Saul Wold 2013-01-24 21:50:12 UTC 
Did you  verify if this is a proxy issue?  This seema likw it might be a proxy 
or slow github response.
Please verify
Comment 5 Saul Wold 2013-02-01 23:50:43 UTC 
This might have been a proxy issue, the code is there and it correctly builds.