netdev - Re: net-next-2.6 phonet causes build error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A6DC804.4010803@hartkopp.net>
Date:	Mon, 27 Jul 2009 17:30:12 +0200
From:	Oliver Hartkopp <oliver@...tkopp.net>
To:	Marcel Holtmann <marcel@...tmann.org>
CC:	David Miller <davem@...emloft.net>, remi.denis-courmont@...ia.com,
	netdev@...r.kernel.org
Subject: Re: net-next-2.6 phonet causes build error

Marcel Holtmann wrote:
> Hi Dave,
> 
>>>> net/phonet/pn_dev.c: In function ‘phonet_init_net’:
>>>> net/phonet/pn_dev.c:221: error: implicit declaration of function
>>>> ‘proc_net_fops_create’
>>>> net/phonet/pn_dev.c: In function ‘phonet_exit_net’:
>>>> net/phonet/pn_dev.c:242: error: implicit declaration of function
>>>> ‘proc_net_remove’
>>> Oops. This makes me wonder why I did not get that one here on my test 
>>> builds???
>> Because the headers on your platform with your configuration end up
>> including linux/proc_fs.h indirectly.
> 
> this and similar automatic includes on x86 are still a problem. I always
> try to compile test with a PPC based system, but even that architecture
> has a lot of indirect includes. I would be happy if we could get rid of
> these for x86 systems, but that seems a little bit wishful thinking.
> 

I second this. But in this special case i was using a x86 architecture, that
behaved correct.

Maybe one of the script wizards has an idea how to identify and /probably/ fix
these automatic includes ...

Regards,
Oliver

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html