Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: lemonoje <lemonoje@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] tried to add ethtool now get config error - Working zlib library and headers not found
Date: Wed, 24 May 2017 07:31:17 -0700 (PDT)	[thread overview]
Message-ID: <1495636277129-165570.post@n4.nabble.com> (raw)
In-Reply-To: <20170524160133.73c8229a@free-electrons.com>

Okay I had done a fresh clone and checkout, but then I coped in my .config
file to pickup everything I had in before, and there were issues with that
build.  Something must have gone wrong there, or my sequence of operations
produced the issue... In any case it is building properly now.  Thank you  

John



--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/tried-to-add-ethtool-now-get-config-error-Working-zlib-library-and-headers-not-found-tp165534p165570.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

      reply	other threads:[~2017-05-24 14:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 21:23 [Buildroot] tried to add ethtool now get config error - Working zlib library and headers not found lemonoje
2017-05-24 14:01 ` Thomas Petazzoni
2017-05-24 14:31   ` lemonoje [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=1495636277129-165570.post@n4.nabble.com \
    --to=lemonoje@gmail.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