From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Error with libusb-0.1.12
Date: Tue, 21 Aug 2007 20:17:30 +0200 [thread overview]
Message-ID: <20070821181730.GB19089@aon.at> (raw)
In-Reply-To: <1187712505.10375.19.camel@PC-EK.Solcon>
On Tue, Aug 21, 2007 at 06:08:25PM +0200, Emil Kr?per wrote:
>Hej!
>Builtroot stops building with an error, I tried several different
>snapshots from July to August and all break with complaining about
>libtool and unrecognized option `-DHAVE_CONFIG_H'.
>It happens even when I build an almost clean config with the only change
>to libusb enabled. Then I tried the same with 386. No difference, same
>fault.
Builds fine for me (>= r19625). Please confirm
next prev parent reply other threads:[~2007-08-21 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 16:08 [Buildroot] Error with libusb-0.1.12 Emil Krüper
2007-08-21 18:17 ` Bernhard Fischer [this message]
2007-08-22 8:18 ` Emil Krüper
-- strict thread matches above, loose matches on Subject: below --
2007-08-21 21:14 e.krueper at solcon-systemtechnik.de
2007-08-22 0:18 ` softa at ttechgroup.com
2007-08-23 9:53 ` Emil Krüper
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=20070821181730.GB19089@aon.at \
--to=rep.dot.nop@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