Path: csiph.com!news.swapon.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: altering winbase.h Date: Sun, 25 Dec 2016 12:17:41 -0800 Organization: None to speak of Lines: 48 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="c83c5ff845c78dc2a3ff0094095b3024"; logging-data="26997"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/ngAjZ9b3xKLhnb68clcCJ" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:06snST3IhvdSKI/2oBrnXqlicGc= sha1:HR16/lgoMGZz1XvIwa4ZdF18eAU= Xref: csiph.com comp.lang.c:100274 jacobnavia writes: > Add this to winbase.h > BOOLEAN WINAPI CreateSymbolicLink(LPTSTR lpSymlinkFileName, > LPTSTR lpTargetFileName, > DWORD dwFlags > ); > > #define SYMBOLIC_LINK_FLAG_DIRECTORY 1 Disclaimer: I don't know what winbase.h is. If it's provided by the OS or by some installable package (another followup suggests that it's part of a Perl installation, in C:\Perl\site\lib\auto\MinGW\include), then modifying it is unlikely to be the best solution. It might fix your own build problem but if your application's source code depends on a change to some system header it's going to be a real portability problem. Instead, I'd suggest adding that declaration somewhere in your own application's source code. And if that's a missing declaration that *should* be in that header, consider reporting the problem to the provider of that header file. There's no winbase.h in the Perl source tree. Perhaps it's provided by some third party, likely Strawberry or ActiveState. Upthread, Michael Holiday wrote: I was advised to define SYMBOLIC_LINK_FLAG_DIRECTORY . I ran the result with the same litany of errors then defined it to be 1 with the same result. What I seek is the command to reveal what is defined before compilation on the gcc implementation used by contemporary perl. Did you define that macro *before* the relevant #include directive(s)? If you mean you want to see the output of the preprocessor, you can use "gcc -E". I'll note again that I don't know what winbase.h is or who provides it. I'm making assumptions based on the directory path. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"