From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Beginner help: Compilation errors for bison, ncurses and arm-buildroot-linux-uclibcgnueabihf
Date: Tue, 4 Sep 2018 10:20:05 +0200 [thread overview]
Message-ID: <20180904102005.1d63cc85@windsurf> (raw)
In-Reply-To: <CAL8qis=5F5kDuMjpsZJZLbnAkFKBVaH_V1CcV6uuK5Lu1ooPAw@mail.gmail.com>
Hello,
On Tue, 4 Sep 2018 11:24:53 +0000, Faisal Mehmood wrote:
> ################################1#1#1#1#1#1#1#1#1#1########################
>
> /home/kenobi/projects/zero/rootfs/buildroot-2018.02.5/output/host/arm-buildroot-linux-uclibcgnueabihf/sysroot/usr/lib/Scrt1.o:
> In function `_start':
> (.text+0x54): undefined reference to `main'
> collect2: error: ld returned 1 exit status
> make[2]: *** [Makefile:850: ../lib/libncurses.so.6.0] Error 1
> make[2]: Leaving directory
> '/home/kenobi/projects/zero/rootfs/buildroot-2018.02.5/output/build/ncurses-6.0/ncurses'
> make[1]: *** [Makefile:114: all] Error 2
> make[1]: Leaving directory
> '/home/kenobi/projects/zero/rootfs/buildroot-2018.02.5/output/build/ncurses-6.0'
> make: *** [package/pkg-generic.mk:226:
> /home/kenobi/projects/zero/rootfs/buildroot-2018.02.5/output/build/ncurses-6.0/.stamp_built]
> Error 2
>
> ################################1#1#1#1#1#1#1#1#1#1########################
This one looks a bit weird. Are you sure you are getting this after a
full rebuild, i.e "make clean all" ?
> lib/fseterr.c: In function 'fseterr':
> lib/fseterr.c:77:3: error: #error "Please port gnulib fseterr.c to
> your platform! Look at the definitions of ferror and clearerr on your
> system, then report this to bug-gnulib."
> #error "Please port gnulib fseterr.c to your platform! Look at the
> definitions of ferror and clearerr on your system, then report this to
> bug-gnulib."
> ^~~~~
What is your host system ? I guess it's a pretty new one, which uses
glibc-2.28. This issue has been fixed in master in commit
373ac58b82d2430b745e90c7c8b39e319949882a, but it hasn't been backported
yet to our 2018.02.x branch. It will be backported soon by Peter
Korsgaard, who maintains the 2018.02.x branch.
> ##############################3#3#3#3#3#3#3#3#3#3#3#3#######################
> /home/kenobi/Downloads/buildroot-2018.08-rc3/output/host/bin/arm-buildroot-linux-uclibcgnueabihf-gcc
> -shared -Wl,-soname,libz.so.1,--version-script,zlib.map -fPIE
> -Wl,-z,now -Wl,-z,relro -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> -D_FILE_OFFSET_BITS=64 -Os -fPIC -fPIC -D_LARGEFILE64_SOURCE=1
> -DHAVE_HIDDEN -o libz.so.1.2.11 adler32.lo crc32.lo deflate.lo
> infback.lo inffast.lo inflate.lo inftrees.lo trees.lo zutil.lo
> compress.lo uncompr.lo gzclose.lo gzlib.lo gzread.lo gzwrite.lo -lc
> -pie
> /home/kenobi/Downloads/buildroot-2018.08-rc3/output/host/arm-buildroot-linux-uclibcgnueabihf/sysroot/usr/lib/Scrt1.o:
> In function `_start':
> (.text+0x54): undefined reference to `main'
> collect2: error: ld returned 1 exit status
Same issue as for ncurses, building shared libraries doesn't work.
Again, are you sure this happens after a full rebuild, i.e "make clean
all".
If that happens after a full rebuild, could you provide:
- Details on your host system
- Your Buildroot .config file
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-04 8:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 11:24 [Buildroot] Beginner help: Compilation errors for bison, ncurses and arm-buildroot-linux-uclibcgnueabihf Faisal Mehmood
2018-09-04 8:20 ` Thomas Petazzoni [this message]
[not found] ` <CAL8qisnsRCYbC5+x8GAT+wZ_qiB=6EGBUVkK=GRk0JHy-T4ifA@mail.gmail.com>
2018-09-04 15:32 ` [Buildroot] Fwd: " Faisal Mehmood
2018-09-04 20:17 ` Arnout Vandecappelle
2018-09-05 10:51 ` Faisal Mehmood
2018-09-05 6:19 ` Vadim Kochan
2018-09-05 12:24 ` Faisal Mehmood
2018-09-05 8:42 ` Baruch Siach
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=20180904102005.1d63cc85@windsurf \
--to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox