Re: sysklogd -17.1 NMU build broken in mips/mipsel
- To: Henrique de Moraes Holschuh <email@example.com>
- Cc: firstname.lastname@example.org
- Subject: Re: sysklogd -17.1 NMU build broken in mips/mipsel
- From: Chris Stromsoe <email@example.com>
- Date: Sun, 2 Apr 2006 16:59:19 -0700 (PDT)
- Message-id: <[🔎] Pine.LNX.firstname.lastname@example.org>
- In-reply-to: <20060223182837.GB20928@khazad-dum.debian.net>
- References: <Pine.LNX.email@example.com> <20060223032227.GA27868@khazad-dum.debian.net> <20060223044731.GA2083@tennyson.dodds.net> <20060223115512.GC19397@networkno.de> <20060223134008.GP21473@wavehammer.waldi.eu.org> <20060223180019.GC9501@khazad-dum.debian.net> <20060223181312.GB28036@wavehammer.waldi.eu.org> <20060223182837.GB20928@khazad-dum.debian.net>
On Thu, 23 Feb 2006, Henrique de Moraes Holschuh wrote:
On Thu, 23 Feb 2006, Bastian Blank wrote:
On Thu, Feb 23, 2006 at 03:00:19PM -0300, Henrique de Moraes Holschuh
So far so good, but why is it allowed for a kernel header to include a
file that does not exist?
mips is not managed in the tree of linus. So it is likely that it
Then it is not "only a sysklogd bug", but rather two bugs, one in
sysklogd, one in the kernel headers.
This is old, but was never really resolved.
In module.h I commented out
and rebuilt sysklogd without any errors. Is there any platform that needs
asm/atomic.h for some reason? If not, a bug to remove the #include should
Current sysklogd in stable (1.4.1-17) has an error in the rules file that
caused it to be built without large file support, which means I can't keep
weekly (or in some cases daily) log files on busy machines and have to do
frequent rotations to avoid losing data at 2gb.
sysklogd 1.4.1-17.1 has the patched rules file and builds correctly with
lfs. What will it take to get a corrected -17.2 without the #include into