This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/17582] Problem cross gcc with errno. Invalid reference.
- From: "sergey_s_m at mail dot ru" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 21 Sep 2004 13:53:50 -0000
- Subject: [Bug target/17582] Problem cross gcc with errno. Invalid reference.
- References: <20040921124401.17582.sergey_s_m@mail.ru>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From sergey_s_m at mail dot ru 2004-09-21 13:53 -------
So in gcc compilers I should #include<errno.h> for compile to executable file.
But if I do not include errno.h I thought that I cannot get executable file
but for cross compilers it's not right, I don't know why. I would like to know
what is in cross compilers that allowed me get executable file without errno.h
including. Why it don't alert me that variable errno is unrefered? I'll be
thankful if anybody can help me.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17582