Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] "multiple target patterns" error while building under cygwin
Date: Fri, 27 Jul 2007 20:05:40 +0200	[thread overview]
Message-ID: <20070727180540.GD11697@aon.at> (raw)
In-Reply-To: <E496871456016F4CA8959BE4105D2A890E8BA7@troe2k1.cs.myharris.net>

On Fri, Jul 27, 2007 at 01:04:00PM -0400, Crane, Matthew wrote:
>Hi, 
> 
>Thanks for your response.  I think my build error is the result of the
>dos2unix + unix2dos patch.  My cygwin system was installed with Unix
>text mode, and I've tried to explicitly set the locale, but fixdep
>always seems to output the Dos text. 
>
>I instead used the dos2unix/unix2dos patch to fix the fixdep output,
>which I think ending up causing the error below.  Not sure how though,
>or how to fix it.  Thanks,
>
>Matt
>
> 
>.applets.o.cmd looks like this:
> 
>cmd_applets/applets.o := <snip>
> 
>deps_applets/applets.o := \
>  applets/applets.c \
>    $(wildcard include/config/static.h) \
>    $(wildcard include/config/show/usage.h) \
><snip>
> 
>line 410: applets/applets.o: $(deps_applets/applets.o)
> 
>$(deps_applets/applets.o):
><eof>
> 
>I had already patched the make process so that it runs fixdep through
>unix2dos, dos2unix similar to this patch I found online:
> 
>define rule_cc_o_c
>     $(call echo-cmd,checksrc) $(cmd_checksrc)              \
>     $(call echo-cmd,cc_o_c) $(cmd_cc_o_c);                  \
>+    dos2unix $(depfile);                                              \
>     $(cmd_modversions)                          \
>-    scripts/basic/fixdep $(depfile) $@ '$(call make-cmd,cc_o_c)' >    \
>
>+ scripts/basic/fixdep $(depfile) $@ '$(call make-cmd,cc_o_c)' |
>unix2dos > \ 
>                                                   $(dot-target).tmp;  \
>     rm -f $(depfile);                          \
>     mv -f $(dot-target).tmp $(dot-target).cmd
>
>It proceeded to build, but failed with the above error.   Maybe related,
>not sure.  I'm looking forward to the day when cygwin support is
>completely transparent in buildroot, soon I'm sure.

This doesn't really sounds like a buildroot issue to me but rather a
busybox issue, fwiw.

Perhaps somebody else is aware of what's going on with busybox on
cygwin.

  reply	other threads:[~2007-07-27 18:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23 13:11 [Buildroot] package/linux/Makefile.in does not include 'openswan' patches Ulf Samuelsson
2007-07-23 13:29 ` Bernhard Fischer
2007-07-23 14:19   ` Ulf Samuelsson
2007-07-23 14:22   ` Bernhard Fischer
2007-07-23 14:43     ` Bernhard Fischer
2007-07-23 15:25       ` Ulf Samuelsson
2007-07-23 16:33         ` [Buildroot] "multiple target patterns" error while building under cygwin Crane, Matthew
2007-07-25 14:33           ` Rex Ashbaugh
     [not found]           ` <20070727162707.GH25147@aon.at>
2007-07-27 17:04             ` Crane, Matthew
2007-07-27 18:05               ` Bernhard Fischer [this message]
2007-07-23 16:56         ` [Buildroot] package/linux/Makefile.in does not include 'openswan' patches Bernhard Fischer
2007-07-23 15:19     ` Ulf Samuelsson
2007-07-23 16:41       ` Bernhard Fischer
2007-07-23 19:38         ` Ulf Samuelsson

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=20070727180540.GD11697@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