Date: Fri, 8 Dec 2017 15:02:48 +0100 From: Gary Jennejohn <gljennjohn@gmail.com> To: blubee blubeeme <gurenchan@gmail.com> Cc: FreeBSD current <freebsd-current@freebsd.org> Subject: Re: valloric YCM [header definitions] Message-ID: <20171208150248.3338c2cc@ernst.home> In-Reply-To: <CALM2mEnGEwXOkeAO_igPrY_QoCvvvUESx23ygKF-oY9etqOLQg@mail.gmail.com> References: <CALM2mEnH6J%2BV08uhahcSwhZ6%2BdAaustmT3Y=r12P-mAVXAG4Tg@mail.gmail.com> <CALM2mEnGEwXOkeAO_igPrY_QoCvvvUESx23ygKF-oY9etqOLQg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 8 Dec 2017 21:23:04 +0800
blubee blubeeme <gurenchan@gmail.com> wrote:
> On Wed, Dec 6, 2017 at 2:18 AM, blubee blubeeme <gurenchan@gmail.com> wrote:
>
> > I'm looking for where the u_int, u_long headers are defined?
> >
These are not headers, they're typedefs.
These are defined in /usr/include/sys/types.h. This is the standard
loacation for globally used typedefs.
> > for instance MOD_LOAD, UNLOAD, ENOTSUP along with u_int and u_long aren't
> > being picked up by libclang
> >
Errors like ENOTSUP are defined in /usr/include/sys/errno.h. This is
the standard location for globally used error codes.
> > module_t isn't being found either but I located that header file in
> > /usr/include/sys/module.h
> >
> > snd_modevent(module_t mod, int type, void *data)
> > {
> >
> > switch (type) {
> > case MOD_LOAD:
> > break;
> > case MOD_UNLOAD:
> > break;
> > default:
> > return (ENOTSUP);
> > break;
> > }
> > return 0;
> > }
> >
> > Anyone here uses YCM?
> >
[snip]
Apparently not.
You seem to have all the usual include paths in the list. No idea
why it's not working.
--
Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171208150248.3338c2cc>