From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question about openssh.mk
Date: Mon, 8 Sep 2014 22:52:58 +0200 [thread overview]
Message-ID: <20140908225258.7fd77c81@free-electrons.com> (raw)
In-Reply-To: <F9C551623D2CBB4C9488801D14F864C68C8AD897@ex-mb3.corp.adtran.com>
Hello,
On Mon, 8 Sep 2014 20:46:05 +0000, ANDY KENNEDY wrote:
> > Yes, that's what we want to do: openssh uses $(LD) and
> > $(TARGET_LDFLAGS) as if they were the compiler. In which case have you
> > identified this to not work?
>
> Okay, then it should probably be LDFAGS="$(TARGET_CFLAGS) $(TARGET_LDFLAGS)".
No, because $(TARGET_LDFLAGS) may contain flags that are not valid for
$(TARGET_CC).
> For some reason, it breaks on every third or so build. I dunno why.
> Working on it. I don't even have enough info to tell you where it is
> breaking (at the moment). I'll keep you advised.
>
> It probably has something to do with the fact that I use
> BR2_PREFER_STATIC_LIB=y
> Though, I have built with this several times today and I only got the
> error once out of three times. It is complaining that it cannot build
> a shared object with openssl.a as it is statically linked.
>
> Like I said, I don't really have enough info to tell you what is broken.
Weird. If it happens once in a while, it might look like a parallel
build issue.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-09-08 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 18:49 [Buildroot] Question about openssh.mk ANDY KENNEDY
2014-09-08 19:40 ` Thomas Petazzoni
2014-09-08 20:46 ` ANDY KENNEDY
2014-09-08 20:52 ` Thomas Petazzoni [this message]
2014-09-08 21:05 ` ANDY KENNEDY
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=20140908225258.7fd77c81@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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.