*> The application will need to include platform specific errno defines when building with a given platform (ifdef's), so the applications can not be binary compatible across different platforms.* ODP application are not binary compatible between different platforms. The ODP header files are full of definitions that are platform-specific (but the symbolic names and their meanings are well defined, creating source code compatibility). If we want to create binary compatibility, we will have to rework the interface between the application and ODP.
BTW I think you will get all common errno definitions by including <errno.h>. On 2 September 2014 18:56, Wiles, Roger Keith <[email protected]> wrote: > > For errno we are going to use POSIX errno values. > > Found this one from open group, which I believe to be the current IEEE std: > http://pubs.opengroup.org/onlinepubs/9699919799/ > > Will the above reference be OK with everyone as a reference for ERRNO > names? Linux man page seem to suggest it is following that standard. > > It appears the standard does not define the value only the name of the > errno. I had not look directly at the standard before :-( Just assuming the > applications must be compiled with the system it will be run. I assume we > are not trying to be binary compatible here. > > After tracking down the errno values/defines on my Ubuntu 14.04 system > they really love to hide them now a days. > > /usr/include/sys/errno.h —> > /usr/include/errno.h —> > /usr/include/bits/errno.h —> > /usr/include/linux/errno.h —> > /usr/include/asm/errno.h —> > /usr/include/asm-generic/errno.h —> > > /usr/include/asm-generic/errno-base.h —> > > /usr/include/asm-generic/errno.h > The last two define most of the defines we are interested in for ODP, but > a few of the ones above define a few extras :-( > > As long as we use the same define names then we should be OK. > > If ODP needs a set of defines not able to be mapped to POSIX then we need > to define a name space to hold these defines similar to what Bill was > suggesting with some type of prefix for all ODP errnos. The platform should > do the same, but this is were the problems begin for the application. The > application will need to include platform specific errno defines when > building with a given platform (ifdef's), so the applications can not be > binary compatible across different platforms. > > Does this summarize the errno discussion today and hopefully add some more > definition around how ODP uses errnos? > > Here is a link that someone produced by platform, which was a lot of work > IMO :-) and may not be up to date. > http://www.ioplex.com/~miallen/errcmp.html > > Thanks > ++Keith > > Keith Wiles, Principal Technologist with CTO office, Wind River mobile > 972-213-5533 > > > _______________________________________________ > lng-odp mailing list > [email protected] > http://lists.linaro.org/mailman/listinfo/lng-odp >
_______________________________________________ lng-odp mailing list [email protected] http://lists.linaro.org/mailman/listinfo/lng-odp
