Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Emil Krüper" <e.krueper@solcon-systemtechnik.de>
To: buildroot@busybox.net
Subject: [Buildroot] Error with libusb-0.1.12
Date: Wed, 22 Aug 2007 10:18:48 +0200	[thread overview]
Message-ID: <1187770728.10375.29.camel@PC-EK.Solcon> (raw)
In-Reply-To: <20070821181730.GB19089@aon.at>

On Tue, 2007-08-21 at 20:17 +0200, Bernhard Fischer wrote:
> 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

At first, my apologies for starting a new thread, I am not that familiar
with the use of mailingslist and hope this one goes where it belongs.
So now I am back at work again and tried building r19625 at my debian
etch x86 box and the only change to the default config was activating
libusb. 

Best regards

Emil Kr?per

And here comes the error:

config.status: creating config.h
config.status: config.h is unchanged
/usr/bin/make  all-recursive
make[2]: Entering directory
`/home/buildroot/buildroot_r19625/build_i386/libusb-0.1.12'
Making all in .
make[3]: Entering directory
`/home/buildroot/buildroot_r19625/build_i386/libusb-0.1.12'
if /bin/sh ./libtool
--mode=compile /home/buildroot/buildroot_r19625/build_i386/libusb-0.1.12/compile /home/buildroot/buildroot_r19625/build_i386/staging_dir/usr/bin/i386-linux-uclibc-gcc -Os -pipe  -I/home/buildroot/buildroot_r19625/build_i386/staging_dir/usr/include -I/home/buildroot/buildroot_r19625/build_i386/staging_dir/include --sysroot=/home/buildroot/buildroot_r19625/build_i386/staging_dir/ -isysroot /home/buildroot/buildroot_r19625/build_i386/staging_dir -mtune=i386 -march=i386 -DHAVE_CONFIG_H   -I.  -Werror  -g -O2 -Wall -MT usb.lo -MD -MP -MF ".deps/usb.Tpo" -c -o usb.lo usb.c; \
        then mv -f ".deps/usb.Tpo" ".deps/usb.Plo"; else rm -f
".deps/usb.Tpo"; exit 1; fi
libtool: compile: unable to infer tagged configuration
libtool: compile: specify a tag with `--tag'
make[3]: *** [usb.lo] Error 1
make[3]: Leaving directory
`/home/buildroot/buildroot_r19625/build_i386/libusb-0.1.12'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/buildroot/buildroot_r19625/build_i386/libusb-0.1.12'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/home/buildroot/buildroot_r19625/build_i386/libusb-0.1.12'
make: ***
[/home/buildroot/buildroot_r19625/build_i386/staging_dir/lib/libusb.so]
Error 2

real    31m19.975s
user    19m16.216s
sys     3m24.281s
PC-EK:/home/buildroot/buildroot_r19625#

  reply	other threads:[~2007-08-22  8:18 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
2007-08-22  8:18   ` Emil Krüper [this message]
  -- 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=1187770728.10375.29.camel@PC-EK.Solcon \
    --to=e.krueper@solcon-systemtechnik.de \
    --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