issue in svn 792

[yoyofr]

It seems in latest svn there is an issue with __errno which is not defined.
I've to put it in my sourcecode in order to compile.

[jason867]

I don't know if this is a coincidence or what, but I've been having problems getting the toolchain script to run properly, and when I perform the fourth process, './toolchain.sh -d -p' it gives errors and at one point it says, "Checked out revision 792" Since it's the same number, I didn't know if it was related or not...

[yoyofr]

right now I'm using a previous version, it seems to work better.
I guess we'll have to have wait for an update.

[ooPo]

It would be helpful if either, or both, of you would post the actual errors you're having instead of just waving your arms around in some nebulous fashion and sitting around for an update.

[jason867]

True, I didn't post the errors here, although I did on my 'how long does ./toolchain.sh take' thread a few days ago, and I have yet been contacted with anyone who might have a clue what those errors mean. The only person to reply was a fellow who tried something and found that it worked and suggested I try the same, although he/she didn't seem to have a clue what the error meant either.

[edit] The errors I posted a few days ago are not the same ones that I asked about here.

[Agoln]

True, I didn't post the errors here, although I did on my 'how long does ./toolchain.sh take' thread a few days ago, and I have yet been contacted with anyone who might have a clue what those errors mean. The only person to reply was a fellow who tried something and found that it worked and suggested I try the same, although he/she didn't seem to have a clue what the error meant either.

Although you did post those errors, and not many people know what they mean, at least we have a starting point on where to help you out. With this error, it may at least be a common error, or an error easily fixed, if we knew what it was.

[yoyofr]

It would be helpful if either, or both, of you would post the actual errors you're having instead of just waving your arms around in some nebulous fashion and sitting around for an update.

woua, you're quite nervous today ? ;-)
I was thinking my description was enough :

if you compile code which relies on errno (for example using a math function as sqrt, or file io stuff), it will fail at linking. I assume something was broken and errno isn't defined in svn 792.
I can provide log if you need tonight when I'll be back at home

[yoyofr]

ok, I'm now back at home, here's what I get if I compile with svn 792 :

zlib/gzio.o: In function `destroy':
zlib/gzio.c:349: undefined reference to `__errno'
zlib/gzio.o: In function `check_header':
zlib/gzio.c:252: undefined reference to `__errno'
zlib/gzio.c:252: undefined reference to `__errno'
zlib/gzio.c:252: undefined reference to `__errno'
zlib/gzio.c:252: undefined reference to `__errno'
zlib/gzio.o:zlib/gzio.c:252: more undefined references to `__errno' follow
collect2: ld returned 1 exit status
make: *** [os9xpsp.elf] Error 1

I noticed too that I get some crashes when doing file io stuff (like writing a file), which I haven't if I take an older svn

[yoyofr]

tried some previous version of svn, and I found that before, errno was defined in libcglue.c, perhaps the issue is related.

here's what I found in an older version in libcglue,

/* newlib's errno.h wants a function that returns a pointer to errno. */
#ifdef F_glue___errno
#undef errno

int errno;

/* TODO: Should this be made reentrant (wrapping interrupt disable/enable
around it should do it)? */
int * __errno(void)
{
return &errno;
}
#endif