[Bug target/17582] New: Problem cross gcc with errno. Invalid reference.

[Bug target/17582] New: Problem cross gcc with errno. Invalid reference.

[sergey_s_m at mail dot ru]

I've tested next example for gcc-3.3.1 and for two cross compilers: mips_fp_be-
gcc and arm_v4t_le-gcc 3.3.1 as well.
(main.c)
------------------------------------------------------------------
extern int errno;
main()
{
printf("errno=%d\n",errno);
}
1. For native compiler the result was:
In function 'main':
: undefined reference to 'errno'
collect2: ld returned 1 exit status
2. For cross compilers the result was a.out file without any mistakes.
So I think there is a bug into cross compilers. Does anybody know how to fix 
it?
PS: I've compiled like: gcc main.c; or mips_fp_be-gcc main.c; or arm_v4t_le-
gcc main.c

-- 
           Summary: Problem cross gcc with errno. Invalid reference.
           Product: gcc
           Version: 3.3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: sergey_s_m at mail dot ru
                CC: gcc-bugs at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17582

[Bug target/17582] Problem cross gcc with errno. Invalid reference.

[schwab at suse dot de]

------- Additional Comments From schwab at suse dot de  2004-09-21 12:50 -------
First, this is not a gcc bug, second, use #include <errno.h>. 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID
            Summary|Problem cross gcc with      |Problem cross gcc with
                   |errno. Invalid reference.   |errno. Invalid reference.


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17582

[Bug target/17582] Problem cross gcc with errno. Invalid reference.

[sergey_s_m at mail dot ru]

------- Additional Comments From sergey_s_m at mail dot ru  2004-09-21 13:10 -------
I know, that I should use #include<errno.h>
Do you think it's ld problem?



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17582

[Bug target/17582] Problem cross gcc with errno. Invalid reference.

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-09-21 13:15 -------
No it is neither a GCC bug or libc bug, the C standard says that errno can be defined as a macro and 
you have include errno.h to get it.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17582

[Bug target/17582] Problem cross gcc with errno. Invalid reference.

[sergey_s_m at mail dot ru]

------- 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