All of lore.kernel.org
 help / color / mirror / Atom feed
From: ANDY KENNEDY <ANDY.KENNEDY@adtran.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question about openssh.mk
Date: Mon, 8 Sep 2014 21:05:19 +0000	[thread overview]
Message-ID: <F9C551623D2CBB4C9488801D14F864C68C8AD8FA@ex-mb3.corp.adtran.com> (raw)
In-Reply-To: <20140908225258.7fd77c81@free-electrons.com>

> > 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).

Hmmm.  I see TARGET_LDFLAGS only as --static on my system.  I do know that I
desire this flag to be sent down to the build, which, as it stands right now,
it doesn't (since the TARGET_LDFLAGS is not getting passed to LDFLAGS as a part
of configure).

So, what about something like this:

OPENSSH_LDFLAGS_FOR_CONF = $(TARGET_CFLAGS)

ifeq ($(BR2_PREFER_STATIC_LIB),y)
OPENSSH_LDFLAGS_FOR_CONF += --static
endif

OPENSSH_CONFIGURE_ENV += LDFLAGS="$(OPENSSH_LDFLAGS_FOR_CONF)"

???

Assuming that what I wrote down below [I modified this section after
typing the below -- you cannot read my e-mails straight through as I'm
a bit scatter-brained] does holds true for several rebuilds.

> 
> > 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.

Right, but the top-level is .NOTPARALLEL:, so it would stand that this would
not be possible to ever make happen.  Given that openssh has a HARD dependency
on openssl.

I dunno.  I'm still working on it.  I did just try to pass in TARGET_LDFLAGS
to LDFLAGS as part of the CONFIGURE_ENV and that seemed to have worked.

I'll have to run it again a few times before I'm comfortable with that.

I'm perplexed.

Andy

      reply	other threads:[~2014-09-08 21:05 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
2014-09-08 21:05       ` ANDY KENNEDY [this message]

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=F9C551623D2CBB4C9488801D14F864C68C8AD8FA@ex-mb3.corp.adtran.com \
    --to=andy.kennedy@adtran.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.