From: ren_guo <ren_guo@c-sky.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot defconfig failures
Date: Thu, 11 May 2017 19:33:14 +0800 [thread overview]
Message-ID: <6ac5b223-e348-7c0d-4ca0-2f4c4c1e6a1d@c-sky.com> (raw)
In-Reply-To: <2a49a86b-da86-6e7e-df4d-bf857d3ee66c@mind.be>
Dear Arnout,
> 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 Best
Regards |
--
Guo Ren, Software Engineer, C-SKY
3 XiDoumen Rd,BldgA,15F,Hangzhou,China
P.C: 310012
http://www.c-sky.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170511/b593779b/attachment.html>
next prev parent reply other threads:[~2017-05-11 11:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 12:55 [Buildroot] Buildroot defconfig failures Thomas Petazzoni
2017-05-07 13:38 ` Thomas Petazzoni
2017-05-07 19:24 ` Peter Korsgaard
2017-05-08 0:25 ` Fabio Estevam
2017-05-09 18:35 ` Fabio Estevam
2017-05-08 2:33 ` ren_guo
2017-05-08 12:20 ` Thomas Petazzoni
2017-05-08 13:43 ` ren_guo
2017-05-08 14:33 ` Arnout Vandecappelle
2017-05-09 13:49 ` ren_guo
2017-05-11 11:33 ` ren_guo [this message]
2017-05-11 11:41 ` Thomas Petazzoni
2017-05-11 12:05 ` ren_guo
2017-05-11 14:34 ` Thomas Petazzoni
2017-05-08 19:21 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6ac5b223-e348-7c0d-4ca0-2f4c4c1e6a1d@c-sky.com \
--to=ren_guo@c-sky.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.