Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] sysvinit-2.88 build is failing for ARM64
Date: Thu, 17 Sep 2015 14:12:17 +0300	[thread overview]
Message-ID: <20150917111217.GP11632@tarshish> (raw)
In-Reply-To: <55FA9C24.2060901@synopsys.com>

Hi Joao,

On Thu, Sep 17, 2015 at 11:55:32AM +0100, Joao Pinto wrote:
> The library is checked as:
> ifneq ($(wildcard $(SYSROOT)/usr/lib*/libcrypt.a),)
> 
> And the library is located at:
> output/host/usr/aarch64-buildroot-linux-gnu/sysroot/usr/lib/aarch64-linux-gnu/libcrypt.a
> 
> Maybe for ARM64 we have to make an extra check?

This check is from package/sysvinit/0001-fix-libcrypt-test.patch. You'll 
probably need to adjust that patch to match this Linaro toolchain.

baruch

> On 9/17/2015 11:39 AM, Joao Pinto wrote:
> > On 9/17/2015 11:35 AM, Baruch Siach wrote:
> >> On Thu, Sep 17, 2015 at 11:28:43AM +0100, Joao Pinto wrote:
> >>> I am trying to build sysvinit-2.88 for ARM64 and it is failing as shown 
> >>> bellow:
> >>>
> >>> Error log:
> >>>
> >>> droot-linux-gnu/sysroot -C
> >>> /media/Dev_Disk/buildroot-junor1/output/build/sysvinit-2.88/src
> >>> make[1]: Entering directory
> >>> `/media/Dev_Disk/buildroot-junor1/output/build/sysvinit-2.88/src'
> >>> /media/Dev_Disk/buildroot-junor1/output/host/usr/bin/aarch64-linux-gnu-gcc
> >>> sulogin.o    -o sulogin
> >>> /media/Dev_Disk/buildroot-junor1/output/host/usr/bin/aarch64-linux-gnu-gcc
> >>> last.o oldutmp.h   -o last
> >>> sulogin.o: In function `main':
> >>> sulogin.c:(.text.startup+0x648): undefined reference to `crypt'
> >>> collect2: error: ld returned 1 exit status
> >>> make[1]: *** [sulogin] Error 1
> >>> make[1]: *** Waiting for unfinished jobs....
> >>> make[1]: Leaving directory
> >>> `/media/Dev_Disk/buildroot-junor1/output/build/sysvinit-2.88/src'
> >>> make: ***
> >>> [/media/Dev_Disk/buildroot-junor1/output/build/sysvinit-2.88/.stamp_built] Error 2
> >>>
> >>> I have checked from mailing history that this problem has already been addressed
> >>> and tested against X86_64. Did anyone tested in ARM64?
> >>> In the meanwhile I will try to fix this problem and I will send the fix patch.
> >>
> >> Please attach the Buildroot .config file to your failure reports so we can try 
> >> to reproduce the issue you encounter.
> >>
> >> baruch
> >>
> > 
> > Sending in attachment the buildroot' config. The build is successfull if I make
> > the following in the src/Makefile:
> > 
> > # Additional libs for GNU libc.
> > #ifneq ($(wildcard $(SYSROOT)/usr/lib*/libcrypt.a),)
> >   SULOGINLIBS	+= -lcrypt
> > #endif
> > 
> > Thanks,
> > Joao

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2015-09-17 11:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17  9:40 [Buildroot] [PATCH v2] mplayer: enable building on ARM64 jpinto
2015-09-17 10:28 ` [Buildroot] sysvinit-2.88 build is failing for ARM64 Joao Pinto
2015-09-17 10:35   ` Baruch Siach
2015-09-17 10:39     ` Joao Pinto
2015-09-17 10:55       ` Joao Pinto
2015-09-17 11:12         ` Baruch Siach [this message]
2015-09-17 11:13           ` Joao Pinto
2015-09-17 21:07           ` Thomas Petazzoni
2015-09-17 21:39             ` Baruch Siach
2015-09-18  7:26               ` Thomas Petazzoni
2015-09-19 19:34                 ` Baruch Siach
2015-09-17 21:31 ` [Buildroot] [PATCH v2] mplayer: enable building on ARM64 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=20150917111217.GP11632@tarshish \
    --to=baruch@tkos.co.il \
    --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