From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] static klibc udev does not link against crt0.o
Date: Sun, 23 Nov 2003 06:00:03 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106956914415622@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106919488620180@msgid-missing>
On Sat, Nov 22, 2003 at 10:04:03AM +0100, Olaf Hering wrote:
> On Wed, Nov 19, Greg KH wrote:
>
> > > I did 'make KLIBC=true' in the current bk tree.
> >
> > try 'make -f Makefile.klibc' in the current tree. For some reason I
> > couldn't figure out how to have Makefile work for both KLIBC=true and
> > KLIBCúlse. But I didn't try too hard :)
>
> I dont understand that.
>
> please do rm -f Makefile.klibc; apply this patch and tell me what fails.
> works for me.
Doh, thanks, I've applied this and deleted Makefile.klibc. Thanks a lot
for this.
> %build
> make KLIBC=%{use_klibc} DEBUGúlse
> cp -av udev udev.static
> make KLIBC=%{use_klibc} DEBUGúlse clean
> make KLIBCúlse DEBUG=true
> cp -av udev udev.debug
> cd libsysfs
> ar cru libsysfs.a *.o ../logging.o
> ranlib libsysfs.a
> cd ..
> make -C extras/scsi_id CC="gcc $RPM_OPT_FLAGS -I`pwd`/libsysfs -L`pwd`/libsysfs"
>
> this is what I use.
Nice to see scsi_id building properly.
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
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
prev parent reply other threads:[~2003-11-23 6:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 22:33 [PATCH] static klibc udev does not link against crt0.o Olaf Hering
2003-11-19 6:52 ` Greg KH
2003-11-22 9:04 ` Olaf Hering
2003-11-23 6:00 ` Greg KH [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=marc-linux-hotplug-106956914415622@msgid-missing \
--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.