Re: undefined symbol: O_CREAT

[Dirk Zimoch <dirk.zimoch@psi.ch>]

Kasemir, Kay schrieb:
> Hi:
>
> I think you're using that in the vxWorks shell,
> in the st.cmd.
Thanks Kay! I completely missed that point. I thought is was a compiled 
program that failed to load in the st.cmd.
Zhang Yuliang, sorry for my misleading previous mail.

It is an annoying issue with vxWorks that the shell does not know about 
macros and often the manuals don't mention the numerical values. The 
only way is then to look up the values in the vxWorks header files.
Dirk

> As Dirk wrote, O_CREAT is a #define for the C/C++ preprocessor.
> It's not available in the vxWorks shell.
>
> In the vxWorks shell you'll have to use the numeric value 0, 1, ...
> that you determine from the #include file, something like this:
>
> fgrep -r O_CREAT /usr/include/*
> /usr/include/sys/fcntl.h:#define	O_CREAT		0x0200		/* create if nonexistant
> */
>
>
>
>
> -Kay
>
>
>
> On 3/9/12 09:22 , "Dirk Zimoch" <dirk.zimoch@psi.ch> wrote:
>
> > ÕÅÓñÁÁ wrote:
> > > Hello,
> > >
> > > I tried to open a file on my linux host machine via vxworks function
> > > open("filename", O_CREAT|O_WRONLY, 0644) from target ME5100. When I run
> > > the start file st.cmd ,it printed "undefined symbol: O_CREAT". Which
> > > supprot should add to the vxworks kernel image?
> > >
> > > Thank you in advance!
> > >
> > > Zhang Yuliang
> > > Insititute of High Energy Physics
> > O_CREAT is a macro that should be defined when you #include <fcntl.h>.
> >
> > Didn't you get any compiler warnings? They are often more useful than
> > errors from the loader.
> >
> > Didn't you have any problems with O_WRONLY? O_CREAT and O_WRONLY are
> > defined in the same file!
> >
> > Dirk