Error in glibc while cross compiling uClinux for ARM environment

In file included from :0:0: ../misc/syslog.c: In function ‘vsyslog_chk’: ../misc/syslog.c:121:30: error: inlining failed in call to always_inline ‘syslog’: function not inlinable ldbl_strong_alias (__syslog, syslog) ^ ./../include/libc-symbols.h:100:26: note: in definition of macro ‘_strong_alias’ extern __typeof (name) aliasname __attribute ((alias (#name))); ^ ../sysdeps/generic/math_ldbl_opt.h:12:44: note: in expansion of macro ‘strong_alias’ #define ldbl_strong_alias(name, aliasname) strong_alias (name, aliasname) ^ ../misc/syslog.c:121:1:…

Details

Is it bad practice to put includes inside a header file?

For example, I am building an IRC Client for various IRC networks (freenode, twitch, etc…). I have a source file for various irc functions IRC_functions.c void *get_in_addr(struct sockaddr *sa) { … } void init_addrinfo(struct addrinfo *hints) { … } void remove_newline(char *str) { … } and a IRC_functions.h header #ifndef IRC_FUNCTIONS #def IRC_FUNCTIONS #include <sys/socket.h>…

Details

Is it bad practice to put includes inside a header file?

For example, I am building an IRC Client for various IRC networks (freenode, twitch, etc…). I have a source file for various irc functions IRC_functions.c void *get_in_addr(struct sockaddr *sa) { … } void init_addrinfo(struct addrinfo *hints) { … } void remove_newline(char *str) { … } and a IRC_functions.h header #ifndef IRC_FUNCTIONS #def IRC_FUNCTIONS #include <sys/socket.h>…

Details

Is it bad practice to put includes inside a header file?

For example, I am building an IRC Client for various IRC networks (freenode, twitch, etc…). I have a source file for various irc functions IRC_functions.c void *get_in_addr(struct sockaddr *sa) { … } void init_addrinfo(struct addrinfo *hints) { … } void remove_newline(char *str) { … } and a IRC_functions.h header #ifndef IRC_FUNCTIONS #def IRC_FUNCTIONS #include <sys/socket.h>…

Details