From: Hendrik Visage <hvisage@envisage.co.za>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] linux-sources-2.4.15-pre5
Date: Thu, 22 Nov 2001 16:40:28 +0200 [thread overview]
Message-ID: <20011122164028.V19649@hvs.envisage.co.za> (raw)
In-Reply-To: <20011122073719.274e2d3b.erichey2@home.com>; from erichey2@home.com on Thu, Nov 22, 2001 at 07:37:19AM -0700
Yip, that's way it's called "Pre-release", thus it's not guaranteed to do
anything, except perhaps to crash a compilation or system ;^)
Seriously, if you aren't a kernel developer or tester, then steer clear
of the pre-releases. You might be better off to got to the -ac patches if there
are features that you are needing that's not yet in the mainstream Linus Kernel
Greetz
HEndrik
On Thu, Nov 22, 2001 at 07:37:19AM -0700, Collins Richey wrote:
> FYI,
>
> linux source is broken.
>
> sis_main.c: In function `sisfb_heap_init':
> sis_main.c:1265: `HW_CURSOR_AREA_SIZE' undeclared (first use in this
> function)
> sis_main.c:1265: (Each undeclared identifier is reported only once
> sis_main.c:1265: for each function it appears in.)
> sis_main.c:1087: warning: unused variable `temp'
> sis_main.c: In function `sisfb_post_setmode':
> sis_main.c:1647: `IND_SIS_CRT2_WRITE_ENABLE' undeclared (first use in
> this function)
> make[3]: *** [sis_main.o] Error 1
> make[3]: Leaving directory
> `/usr/src/linux-2.4.15-pre5/drivers/video/sis'
>
> Thanks,
> --
> Collins Richey
> Denver Area
> gentoo_rc6 xfce+sylpheed
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
--
------------------------
Hendrik Visage
hvisage@envisage.co.za
prev parent reply other threads:[~2001-11-22 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 14:37 [gentoo-dev] linux-sources-2.4.15-pre5 Collins Richey
2001-11-22 14:40 ` Hendrik Visage [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=20011122164028.V19649@hvs.envisage.co.za \
--to=hvisage@envisage.co.za \
--cc=gentoo-dev@gentoo.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