Re: valloric YCM [header definitions]
On Fri, 8 Dec 2017 21:23:04 +0800
blubee blubeeme wrote:
> On Wed, Dec 6, 2017 at 2:18 AM, blubee blubeeme 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
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: valloric YCM [header definitions]
On 12/08/17 14:23, blubee blubeeme wrote:
On Wed, Dec 6, 2017 at 2:18 AM, blubee blubeeme wrote:
Hi,
These questions are better off at questi...@freebsd.org :-)
I'm looking for where the u_int, u_long headers are defined?
Anyway, it appears you are having some fun figuring out how the FreeBSD
sources are organized.
Everything in /usr/include is only meant for user-space.
Integer types are defined by and .
grep -rE "^typedef.*u_int" /usr/include/
for instance MOD_LOAD, UNLOAD, ENOTSUP along with u_int and u_long aren't
being picked up by libclang
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?
I recommend not compiling kernel code outside the Makefile environment.
Examples of valid kernel-side Makefiles you find in /usr/src/sys/modules
make -C /usr/src/sys/modules/sound clean
make -C /usr/src/sys/modules/sound depend
make -C /usr/src/sys/modules/sound all
Here's a verbose output of my global ycm_config. I hard coded the values
to test but still some headers like u_int, u_long and the above mentioned
MOD_* aren't being picked up.
--HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: valloric YCM [header definitions]
On Wed, Dec 6, 2017 at 2:18 AM, blubee blubeeme wrote:
> I'm looking for where the u_int, u_long headers are defined?
>
> for instance MOD_LOAD, UNLOAD, ENOTSUP along with u_int and u_long aren't
> being picked up by libclang
>
> 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?
>
> Here's a verbose output of my global ycm_config. I hard coded the values
> to test but still some headers like u_int, u_long and the above mentioned
> MOD_* aren't being picked up.
>
> Any ideas why?
>
> '-std=c99',
> '-x',
> 'c',
> '-I',
> '/usr/local/include',
> '-I',
> '/usr/include',
> '-I',
> '/usr/include/teken',
> '-I',
> '/usr/include/geom',
> '-I',
> '/usr/include/netgraph',
> '-I',
> '/usr/include/isofs',
> '-I',
> '/usr/include/net80211',
> '-I',
> '/usr/include/gssapi',
> '-I',
> '/usr/include/xlocale',
> '-I',
> '/usr/include/netpfil',
> '-I',
> '/usr/include/gcc',
> '-I',
> '/usr/include/bsnmp',
> '-I',
> '/usr/include/libxo',
> '-I',
> '/usr/include/ssp',
> '-I',
> '/usr/include/devdctl',
> '-I',
> '/usr/include/security',
> '-I',
> '/usr/include/crypto',
> '-I',
> '/usr/include/cam',
> '-I',
> '/usr/include/rdma',
> '-I',
> '/usr/include/infiniband',
> '-I',
> '/usr/include/rpcsvc',
> '-I',
> '/usr/include/atf-c',
> '-I',
> '/usr/include/netnatm',
> '-I',
> '/usr/include/ufs',
> '-I',
> '/usr/include/edit',
> '-I',
> '/usr/include/nfsserver',
> '-I',
> '/usr/include/netsmb',
> '-I',
> '/usr/include/gnu',
> '-I',
> '/usr/include/net',
> '-I',
> '/usr/include/private',
> '-I',
> '/usr/include/nfsclient',
> '-I',
> '/usr/include/openssl',
> '-I',
> '/usr/include/libmilter',
> '-I',
> '/usr/include/atf-c++',
> '-I',
> '/usr/include/netinet6',
> '-I',
> '/usr/include/x86',
> '-I',
> '/usr/include/dev',
> '-I',
> '/usr/include/bsm',
> '-I',
> '/usr/include/netipsec',
> '-I',
> '/usr/include/netinet',
> '-I',
> '/usr/include/krb5',
> '-I',
> '/usr/include/casper',
> '-I',
> '/usr/include/protocols',
> '-I',
> '/usr/include/lib80211',
> '-I',
> '/usr/include/arpa',
> '-I',
> '/usr/include/pcap',
> '-I',
> '/usr/include/nfs',
> '-I',
> '/usr/include/machine',
> '-I',
> '/usr/include/fs',
> '-I',
> '/usr/include/sys',
> '-I',
> '/usr/include/rpc',
> '-I',
> '/usr/include/kadm5',
> '-I',
> '/usr/include/vm',
> '-I',
> '/usr/include/c++',
> '-I',
> '/usr/include/lzma',
> '-I',
> '/sys',
> '-I',
> '/dev',
> '-I',
> '/usr/src',
>
>
There's no one on this mailing list that uses YCM for their FreeBSD
development?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: valloric YCM [header definitions]
On Wed, Dec 06, 2017 at 02:18:29AM +0800, blubee blubeeme wrote: > I'm looking for where the u_int, u_long headers are defined? Although it seems to be out-of-date, for something fundamental like this you should be able to use the FXR instance: http://fxr.watson.org/fxr/search mcl ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
