From: "Thomas Strösslin" <am33@2wire.ch>
To: linux-hotplug@vger.kernel.org
Subject: udev compile problem: dlist
Date: Mon, 20 Dec 2004 17:12:08 +0000 [thread overview]
Message-ID: <41C707E8.9040007@2wire.ch> (raw)
Hi,
I failed to compile udev-050.
in dlist.c, the function dlist_sort_custom() contains:
dlist_start(list);
struct dlist *listsource, *listdest, *swap;
etc.
This does not compile on my system (SuSE 7.3, gcc 2.95.3)
It does compile if you move dlist_start(list) below all declarations. I
actually don't understand how it could compile on any system...
cheers,
tom
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
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 reply other threads:[~2004-12-20 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 17:12 Thomas Strösslin [this message]
2004-12-20 19:10 ` udev compile problem: dlist Tobias Klauser
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=41C707E8.9040007@2wire.ch \
--to=am33@2wire.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).