From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Thu, 11 May 2017 13:41:13 +0200 Subject: [Buildroot] Buildroot defconfig failures In-Reply-To: <6ac5b223-e348-7c0d-4ca0-2f4c4c1e6a1d@c-sky.com> References: <20170507145548.336e29ad@free-electrons.com> <20170508142023.6b95ccf7@free-electrons.com> <2a49a86b-da86-6e7e-df4d-bf857d3ee66c@mind.be> <6ac5b223-e348-7c0d-4ca0-2f4c4c1e6a1d@c-sky.com> Message-ID: <20170511134113.5d0858c0@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Thu, 11 May 2017 19:33:14 +0800, ren_guo wrote: > > You can just create a gitlab account, fork the official gitlab buildroot > > repository, modify .gitlab-ci.yml and push it. The you use the real gitlab > > server for you debugging. > > > > You can do this on a branch that you delete later to "forget" about this > > debugging run. > > 1. The problem is lose "libelf1" package, csky-linux-gcc will failed like this: > > |$ echo 'void main(){}' | ./bin/csky-linux-gcc -fstack-protector -x c - > -o hello && echo y > /builds/guoren83/buildroot/bin/../libexec/gcc/csky-linux/4.5.1/cc1: > error while loading shared libraries: libelf.so.1: cannot open shared > object file: No such file or directory test failed log: > https://gitlab.com/guoren83/buildroot/builds/16073656 2. I add libelf1 > in .gitlab-ci.yml, see below > https://gitlab.com/guoren83/buildroot/commit/8e718d6ac2d49900042861652cac585c2cb063c7 > Test is OK :) https://gitlab.com/guoren83/buildroot/builds/16074189 Ah, good finding. Thanks for this investigation! However, do we want to add libelf1 ? Shouldn't you tweak your toolchain build process to link gcc statically with libelf1 ? It is worth mentioning that gcc no longer depends on libelf since gcc 4.6. Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com