From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: compiling problems
Date: Wed, 19 Jan 2005 19:41:33 +0000 [thread overview]
Message-ID: <20050119194133.GK2367@kroah.com> (raw)
In-Reply-To: <681F01116A860B46874E634854F4DE620E704C@coastapps.westcoastdhb.org.nz>
On Fri, Jan 14, 2005 at 08:51:41PM +1300, Miles Roper wrote:
>
> this is what I get when doing a make USE_KLIBC=true
>
> bash# make USE_KLIBC=true
> make -C klibc SUBDIRS=klibc TESTS> make[1]: Entering directory `/source/udev-050/klibc'
> make[2]: Entering directory `/source/udev-050/klibc/klibc'
> gcc -Wp,-MT,arch/i386/crt0.o,-MD,arch/i386/.crt0.o.d -march=i386 -Os -g
> -malign-functions=0 -malign-jumps=0 -malign-loops=0 -nostdinc -iwithprefix
> include -D__KLIBC__ -DBITSIZE2 -I../include/arch/i386 -I../include/bits32
> -I../include -I../linux/include -I../linux/include2 -I../linux/include
> -DWITH_ERRLIST -W -Wall -Wpointer-arith -Wwrite-strings -Wstrict-prototypes
> -Winline -D__ASSEMBLY__ -c -o arch/i386/crt0.o arch/i386/crt0.S
> Usage: cpp0 [switches] input output
<snip> me too. Ick. At first glance, it looks ok, but odds are there's
a command line argument that should not be there. Anyone else spot it?
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-01-19 19:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 7:27 compiling problems Miles Roper
2005-01-12 8:09 ` Greg KH
2005-01-12 20:03 ` Kay Sievers
2005-01-12 21:43 ` Greg KH
2005-01-13 0:20 ` Kay Sievers
2005-01-13 6:29 ` Miles Roper
2005-01-13 8:53 ` Miles Roper
2005-01-13 16:41 ` Richard Troth
2005-01-13 17:17 ` Greg KH
2005-01-14 7:51 ` Miles Roper
2005-01-19 19:41 ` Greg KH [this message]
2005-01-19 21:06 ` Kay Sievers
2005-01-19 21:31 ` Greg KH
2005-01-20 8:12 ` Miles Roper
2005-01-20 8:41 ` Miles Roper
2005-01-20 14:27 ` Greg KH
2005-01-21 9:47 ` Miles Roper
2005-01-21 17:05 ` Greg KH
2005-01-21 18:43 ` Chris Larson
2005-01-25 8:14 ` Miles Roper
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=20050119194133.GK2367@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.org \
/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.