http://git.buildroot.net/buildroot/tree/board/raspberrypi/readme.txt states the following — where the last line is the interesting one:
The raspberrypi_defconfig configuration is a minimal configuration
with all that is required to bring the Raspberry Pi up. You should
base your work on this defconfig:
$ make raspberrypi_defconfig
Alternatively, if you want to test support for the Device Tree:
$ make raspberrypi_dt_defconfig
For Raspberry Pi 2 use a different defconfig:
$ make raspberrypi2_defconfig
Is that raspberrypi2_defconfig required to use buildroot on an Raspberry Pi 2, or does it just contain RPi2 optimizations? The reason why I'm asking is that I don't find that configuration in the latest stable version of Buildroot, and the current git version abort the build with an
"HTTP request sent, awaiting response... 404: Not Found"
====================================
Console printout after second build crasch:
make[1]: Leaving directory `/home/fredrik/buildroot/output/build/host-lzop-1.03'
>>> linux 2c4959b772a35d9d459b0a92f39bb066e9a44d37 Downloading
Doing shallow clone
Cloning into bare repository 'linux-2c4959b772a35d9d459b0a92f39bb066e9a44d37'...
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-BVQjKJ/pkcs11: No such file or directory
POST git-upload-pack (gzip 1077 to 570 bytes)
POST git-upload-pack (gzip 1086 to 577 bytes)
remote: Counting objects: 223619, done.
remote: Compressing objects: 100% (141382/141382), done.
remote: Total 223619 (delta 145491), reused 134621 (delta 80295), pack-reused 0
Receiving objects: 100% (223619/223619), 271.86 MiB | 1.80 MiB/s, done.
Resolving deltas: 100% (145491/145491), done.
warning: Remote branch 2c4959b772a35d9d459b0a92f39bb066e9a44d37 not found in upstream origin, using HEAD instead
fatal: not a tree object
--2015-04-13 00:26:38-- http://sources.buildroot.net/linux-2c4959b772a35d9d459b0a92f39bb066e9a44d37.tar.gz
Resolving sources.buildroot.net (sources.buildroot.net)... 176.9.16.109
Connecting to sources.buildroot.net (sources.buildroot.net)|176.9.16.109|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2015-04-13 00:26:38 ERROR 404: Not Found.
make: *** [/home/fredrik/buildroot/output/build/linux-2c4959b772a35d9d459b0a92f39bb066e9a44d37/.stamp_downloaded] Error 1
It's not mandatory, but it's a prebuilt configuration that ensures that you will have a working system.
When pasting errors, please include more lines (like 50-100 lines), because the real error is not this 404. It's earlier, the fact that it can't find in the RPi kernel Git repository the commit we're looking for. Try again with the latest Buildroot, I think we've updated the raspberrypi2_defconfig with a more recent RPi kernel commit.
The problem is that the RPi kernel git repository is often rebased against the linux-stable kernel, which means that the commit that buildroot refers to is no longer accessible.
The solution is to use a stable branch from the RPi kernel git repository, where no rebasing is done. This is done by this patch.
Related
I have a folder with codes, i pushed it on github after creating a repository but the process was successful but i can not see any file in the repository, any help guys, this is my cli codes
SydoTech#DESKTOP-PUHK97G MINGW64 /d/james/ict-specialists (master)
$ git remote add origin https://github.com/Kato669/ict-specialist-website.git
SydoTech#DESKTOP-PUHK97G MINGW64 /d/james/ict-specialists (master)
$ git push origin main
error: src refspec main does not match any
error: failed to push some refs to 'https://github.com/Kato669/ict-specialist-website.git'
SydoTech#DESKTOP-PUHK97G MINGW64 /d/james/ict-specialists (master)
$ git push origin master
Enumerating objects: 1383, done.
Counting objects: 100% (1383/1383), done.
Delta compression using up to 4 threads
Compressing objects: 100% (1380/1380), done.
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)
send-pack: unexpected disconnect while reading sideband packet
Writing objects: 100% (1383/1383), 35.93 MiB | 323.00 KiB/s, done.
Total 1383 (delta 181), reused 0 (delta 0), pack-reused 0
fatal: the remote end hung up unexpectedly
Everything up-to-date
SydoTech#DESKTOP-PUHK97G MINGW64 /d/james/ict-specialists (master)
$
So I'm trying to clone my Azure DevOps Git repo. If I use SSH, I get the following error:
$ git clone <ssh-url> az-lynx
Cloning into 'az-lynx'...
remote: Azure Repos
remote: Found 177467 objects to send. (371 ms)
Receiving objects: 100% (177467/177467), 395.46 MiB | 7.01 MiB/s, done.
Resolving deltas: 100% (130228/130228), done.
Updating files: 100% (13436/13436), done.
Downloading /jquery-1.10.2.min.map (140 KB)
Error downloading object: /jquery-1.10.2.min.map (3b5c544): Smudge error: Error downloading /jquery-1.10.2.min.map (3b5c544e238a129e2b7296ad731f8963ea092843967a4bbc2d748e471ae115b9): batch request: unexpected end of JSON input
Errors logged to C:\projects\az-lynx\.git\lfs\logs\20210926T085414.2333448.log
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: /jquery-1.10.2.min.map: smudge filter lfs failed
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'
Now, if I use HTTPS instead, it works just fine with the file downloaded correctly
got clone <https-url>
Cloning into 'az-lynx'...
remote: Azure Repos
remote: Found 177467 objects to send. (428 ms)
Receiving objects: 100% (177467/177467), 395.46 MiB | 8.64 MiB/s, done.
Resolving deltas: 100% (130228/130228), done.
Updating files: 100% (13436/13436), done.
Filtering content: 100% (4253/4253), 263.01 MiB | 7.52 MiB/s, done.
Aren't both SSH and HTTPS pointing to the same repo? Why SSH is complaining missing files while HTTPS works just fine?
I have an old repository on Github (the last commit was 2 years ago). Recently I worked with the local copy, and performed several commits, tried to push, it gave me the following error
$git push
fatal: The current branch master has no upstream branch.
To push the current branch and set the remote as upstream, use
git push --set-upstream origin master
I searched for a solution here , I tried $ git push --set-upstream origin masterthe following errors occurred:
Enumerating objects: 182, done.
Counting objects: 100% (182/182), done.
Delta compression using up to 8 threads
Compressing objects: 100% (110/110), done.
error: RPC failed; curl 18 transfer closed with outstanding read data remaining
send-pack: unexpected disconnect while reading sideband packet
Writing objects: 100% (166/166), 2.44 GiB | 599.00 KiB/s, done.
Total 166 (delta 61), reused 147 (delta 47), pack-reused 0
fatal: the remote end hung up unexpectedly
Everything up-to-date
I tried another solution from the same post $ git push -u origin head
it gives me some extra errors
git push -u origin master
Warning: Permanently added the RSA host key for IP address '140.82.112.4' to the list of known hosts.
Enumerating objects: 182, done.
Counting objects: 100% (182/182), done.
Delta compression using up to 8 threads
Compressing objects: 100% (110/110), done.
remote: fatal: pack exceeds maximum allowed size
fatal: sha1 file '<stdout>' write error: Broken pipeB/s
error: remote unpack failed: index-pack abnormal exit
To github.com:drnesr/PrayerTimesStudies.git
! [remote rejected] master -> master (failed)
error: failed to push some refs to 'github.com:AcountName/RepoName.git'
How can I solve this push to GitHub problem?
I want to build kernel with some flags enabled for my Samsung Nexus 10. Here is the info from android About device.
Android version
5.1.1
Kernel Version
3.4.67-g84ad5a4
android-build#wpee22.hot.corp.google.com#1
Fri Nov 13 21:33:05 UTC 2015
Build Number
LMY49J
I am following this AOSP guide to build the kernel -
https://source.android.com/source/building-kernels
I have cloned the repo but have no clue which branch and the commit to checkout.
arpit#arpit-ubuntu:~/kernel$ git clone https://android.googlesource.com/kernel/exynos.git
Cloning into 'exynos'...
remote: Sending approximately 874.72 MiB ...
remote: Counting objects: 15, done
remote: Total 3997821 (delta 3353407), reused 3997821 (delta 3353407)
Receiving objects: 100% (3997821/3997821), 874.72 MiB | 9.86 MiB/s, done.
Resolving deltas: 100% (3353407/3353407), done.
Checking connectivity... done.
arpit#arpit-ubuntu:~/kernel$ cd exynos/
arpit#arpit-ubuntu:~/kernel/exynos$ ls -l
total 0
arpit#arpit-ubuntu:~/kernel/exynos$
This directory is empty, so the logic given on AOSP to find commit and branch info from kernel binary logs is not applicable here.
git branch -a returns the following .
arpit#arpit-ubuntu:~/kernel/exynos$ git branch -a
* master
remotes/origin/HEAD -> origin/master
remotes/origin/android-exynos-3.4
remotes/origin/android-exynos-koi-3.10-marshmallow-dr1-wear-release
remotes/origin/android-exynos-koi-3.10-marshmallow-mr1-wear-release
remotes/origin/android-exynos-koi-3.18-nougat-mr1-wear-release
remotes/origin/android-exynos-manta-3.4-adf
remotes/origin/android-exynos-manta-3.4-jb-mr1
remotes/origin/android-exynos-manta-3.4-jb-mr1-fr
remotes/origin/android-exynos-manta-3.4-jb-mr1.1
remotes/origin/android-exynos-manta-3.4-jb-mr2
remotes/origin/android-exynos-manta-3.4-kitkat-mr0
remotes/origin/android-exynos-manta-3.4-kitkat-mr1
remotes/origin/android-exynos-manta-3.4-kitkat-mr2
remotes/origin/android-exynos-manta-3.4-lollipop-mr1
remotes/origin/android-exynos-manta-3.4-lollipop-release
remotes/origin/master
arpit#arpit-ubuntu:~/kernel/exynos$
My possible guess is the branch name is remotes/origin/android-exynos-manta-3.4-lollipop-mr1.
But none of the commits in this branch has this substring 84ad5a4 (Obtained from kernel version on device). Google search for string 84ad514 also doesn't return anything.
So I am struck here. I want to use the exact code corresponding to the kernel shipped on my device and not the most recent code on the kernel branch. Can you tell me how to figure out the branch and exact commit corresponding to the shipped kernel on my device.
When I try to push an update to Heroku in one of my PHP apps I get the following problem:
Counting objects: 25, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (12/12), done.
Writing objects: 100% (13/13), 1.20 KiB, done.
Total 13 (delta 10), reused 0 (delta 0)
-----> Heroku receiving push
-----> Fetching custom buildpack... done
-----> PHP app detected
-----> Run Sitebase buildpack
-----> Bundling Apache version 2.2.22
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Exiting with failure status due to previous errors
! Heroku push rejected, failed to compile Php app
To git#heroku.com:x
! [remote rejected] feature-removeapi -> master (pre-receive hook declined)
error: failed to push some refs to 'git#heroku.com:x'
Never had this problem before so I totally don't have a clue what the problem can be.
Is it possible that this is a bug on Heroku's side?
If I look in the Heroku logs I also see the following line:
Slug compilation failed: failed to compile Php app
All help is welcome.
I my cases that I had this problem it seemed to be a Heroku problem. Just waiting 10 minutes or so did the trick for me.
After so many years and still, this issue occurs.
Btw: My fix was to pin to a specific version as mentioned here:
heroku buildpacks:set https://github.com/heroku/heroku-buildpack-nodejs#v75 -a my-app
Same issue had occurred for my Java application which was built with Maven.
It got fixed by configuring Java buildpack provided by Heroku (Earlier I was using custom buildpack which used to work on heroku for same application).