does some body can help me:
I found that mingw64 doesn't support publib libraries, so wanted to
compile one myself. After compiling the source code, this appears, how
to deal with it.
-----------------------------------
gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fndir.d -c
fname/fndir.c -o fname/fndir.o
gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fnhome.d -c
fname/fnhome.c -o fname/fnhome.o
fname/fnhome.c:38:10: fatal error: pwd.h: No such file or directory
38 | #include <pwd.h>
| ^~~~~~~
compilation terminated.
make: *** [Makefile:403: fname/fnhome.o] Error 1

--------------------------------------------------------------
but I found: Enviroument var:
C_INCLUDE_PATH=/mingw64/include:C:\msys64\mingw64\include
and:
ls -la /usr/include/pwd.h
-rw-r--r-- 1 spender None 2.7K Nov 30 14:03 /usr/include/pwd.h

soo:
export
C_INCLUDE_PATH=/mingw64/include:/usr/include:C:\msys64\mingw64\include

now error:
make
gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fnhome.d -c
fname/fnhome.c -o fname/fnhome.o
In file included from fname/fnhome.c:38:
C:\msys64\usr\include/pwd.h:50:9: error: unknown type name 'uid_t'
50 | uid_t pw_uid; /* user uid */
| ^~~~~
C:\msys64\usr\include/pwd.h:51:9: error: unknown type name 'gid_t'
51 | gid_t pw_gid; /* user gid */
| ^~~~~
fname/fnhome.c: In function 'fnhome':
fname/fnhome.c:50:32: warning: implicit declaration of function
'getuid'; did you mean 'getpid'? [-W
implicit-function-declaration]
50 | pwd = getpwuid(getuid());
| ^~~~~~
| getpid
make: *** [Makefile:403: fname/fnhome.o] Error 1

On 13.12.2023 04:13, spender wrote:
> does some body can help me:
> I found that mingw64 doesn't support publib libraries, so wanted to
> compile one myself. After compiling the source code, this appears, how
> to deal with it.
> -----------------------------------
> gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fndir.d -c
> fname/fndir.c -o fname/fndir.o
> gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fnhome.d -c
> fname/fnhome.c -o fname/fnhome.o
> fname/fnhome.c:38:10: fatal error: pwd.h: No such file or directory
> 38 | #include <pwd.h>
> | ^~~~~~~
> compilation terminated.
> make: *** [Makefile:403: fname/fnhome.o] Error 1
>
> --------------------------------------------------------------
> but I found: Enviroument var:
> C_INCLUDE_PATH=/mingw64/include:C:\msys64\mingw64\include
> and:
> ls -la /usr/include/pwd.h
> -rw-r--r-- 1 spender None 2.7K Nov 30 14:03 /usr/include/pwd.h
>
> soo:
> export
> C_INCLUDE_PATH=/mingw64/include:/usr/include:C:\msys64\mingw64\include

Doesn't a Win/DOS system require a device character before the path?
Something like C:\usr\include (or wherever that file is located)?

>
> now error:
> make
> gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fnhome.d -c
> fname/fnhome.c -o fname/fnhome.o
> In file included from fname/fnhome.c:38:
> C:\msys64\usr\include/pwd.h:50:9: error: unknown type name 'uid_t'
> 50 | uid_t pw_uid; /* user uid */
> | ^~~~~
> C:\msys64\usr\include/pwd.h:51:9: error: unknown type name 'gid_t'
> 51 | gid_t pw_gid; /* user gid */
> | ^~~~~
> fname/fnhome.c: In function 'fnhome':
> fname/fnhome.c:50:32: warning: implicit declaration of function
> 'getuid'; did you mean 'getpid'? [-W
> implicit-function-declaration]

Have you included the necessary header files for these functions?
#include <unistd.h>
#include <sys/types.h>

> 50 | pwd = getpwuid(getuid());
> | ^~~~~~
> | getpid
> make: *** [Makefile:403: fname/fnhome.o] Error 1

On 2023-12-13, spender <spender@yeah.net> wrote:
> does some body can help me:
> I found that mingw64 doesn't support publib libraries, so wanted to
> compile one myself. After compiling the source code, this appears, how
> to deal with it.
> -----------------------------------
> gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fndir.d -c
> fname/fndir.c -o fname/fndir.o
> gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fnhome.d -c
> fname/fnhome.c -o fname/fnhome.o
> fname/fnhome.c:38:10: fatal error: pwd.h: No such file or directory
> 38 | #include <pwd.h>
> | ^~~~~~~
> compilation terminated.
> make: *** [Makefile:403: fname/fnhome.o] Error 1

Cygwin has these Unix functions. They are not particularly useful on
Windows, but they work.

Why don't you compile your program under Cygwin?

--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca
NOTE: If you use Google Groups, I don't see you, unless you're whitelisted.

spender <spender@yeah.net> writes:
> does some body can help me:
> I found that mingw64 doesn't support publib libraries, so wanted to
> compile one myself. After compiling the source code, this appears, how
> to deal with it.
> -----------------------------------
> gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fndir.d -c
> fname/fndir.c -o fname/fndir.o
> gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fnhome.d -c
> fname/fnhome.c -o fname/fnhome.o
> fname/fnhome.c:38:10: fatal error: pwd.h: No such file or directory
> 38 | #include <pwd.h>
> | ^~~~~~~
> compilation terminated.
> make: *** [Makefile:403: fname/fnhome.o] Error 1
>
> --------------------------------------------------------------
> but I found: Enviroument var:
> C_INCLUDE_PATH=/mingw64/include:C:\msys64\mingw64\include
> and:
> ls -la /usr/include/pwd.h
> -rw-r--r-- 1 spender None 2.7K Nov 30 14:03 /usr/include/pwd.h

How was C_INCLUDE_PATH set?

That value appears to be a mix of a Unix-style path:
/mingw64/include
and a Windows-style path:
C:\msys64\mingw64\include

You haven't told us what environment you're using. How exactly are you
invoking the compiler? CMD prompt? Cygwin? Powershell?

Unix-style paths use '/' as a directory delimiter, and ':' to separate
entries. Windows-style paths use '\' as a directory delimiter, and ';'
to separate entries. Don't mix them.

> soo:
> export
> C_INCLUDE_PATH=/mingw64/include:/usr/include:C:\msys64\mingw64\include

Again, don't mix Unix-style and Windows-style paths. Use the style
associated with the environment from which you're invoking the compiler.

[...]

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Will write code for food.
void Void(void) { Void(); } /* The recursive call of the void */

On 13/12/2023 05:12, Keith Thompson wrote:
> spender <spender@yeah.net> writes:
>> does some body can help me:
>> I found that mingw64 doesn't support publib libraries, so wanted to
>> compile one myself. After compiling the source code, this appears, how
>> to deal with it.
>> -----------------------------------
>> gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fndir.d -c
>> fname/fndir.c -o fname/fndir.o
>> gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fnhome.d -c
>> fname/fnhome.c -o fname/fnhome.o
>> fname/fnhome.c:38:10: fatal error: pwd.h: No such file or directory
>> 38 | #include <pwd.h>
>> | ^~~~~~~
>> compilation terminated.
>> make: *** [Makefile:403: fname/fnhome.o] Error 1
>>
>> --------------------------------------------------------------
>> but I found: Enviroument var:
>> C_INCLUDE_PATH=/mingw64/include:C:\msys64\mingw64\include
>> and:
>> ls -la /usr/include/pwd.h
>> -rw-r--r-- 1 spender None 2.7K Nov 30 14:03 /usr/include/pwd.h
>
> How was C_INCLUDE_PATH set?
>
> That value appears to be a mix of a Unix-style path:
> /mingw64/include
> and a Windows-style path:
> C:\msys64\mingw64\include
>
> You haven't told us what environment you're using. How exactly are you
> invoking the compiler? CMD prompt? Cygwin? Powershell?
>
> Unix-style paths use '/' as a directory delimiter, and ':' to separate
> entries. Windows-style paths use '\' as a directory delimiter, and ';'
> to separate entries. Don't mix them.
>
>> soo:
>> export
>> C_INCLUDE_PATH=/mingw64/include:/usr/include:C:\msys64\mingw64\include
>
> Again, don't mix Unix-style and Windows-style paths. Use the style
> associated with the environment from which you're invoking the compiler.
>
> [...]
>

It is probably easier to keep track of what is what if you don't mix
path styles, but they should work fine either way. mingw64 (and gcc for
mingw64 hosts) handles conversion of path styles when accessing files.
It's even fine to mix forward and backwards slashes in the same
pathname. I personally prefer to use *nix-style pathnames when using
mingw64 programs, regardless of whether I am invoking them from a CMD
prompt, an msys2 bash, or (most commonly) "make". But that is because I
use Linux and Windows, and my makefiles must work on both systems.

But while the forward and backwards slashes should be fine, the
directory delimiter in the path chain might be an issue - I don't know
how that will work. It is unlikely to be the problem here, however,
since /mingw64/include and c:\msys64\mingw64\include refer to the same
directory (for default installations). And after adding the path to
"pwd.d" to his C_INCLUDE_PATH, the compiler clearly found that file.

No, I think the problem is simply that Windows does not support anything
directly matching *nix users, groups, and related concepts - they are
handled in a completely different way on Windows. mingw64 aims to be a
/minimal/ conversion layer between *nix-style user code and the Windows
system, and it does not support things that can't be handled directly.
It doesn't cover user names, fork(), device files, and many other such
things. Code that relies on this kind of thing is unlikely to compile,
and very unlikely to do anything sensible if forced to compile.

In the OP's case, however, the actual use of user and group information
should be quite minimal, so it could be possible to get it working.
There may be additional configuration or pre-defined macros needed when
compiling this code with mingw64 controlling conditional compilation, so
that the headers and C files adapt to the right environment.

David Brown <david.brown@hesbynett.no> writes:
> On 13/12/2023 05:12, Keith Thompson wrote:
>> spender <spender@yeah.net> writes:
>>> does some body can help me:
>>> I found that mingw64 doesn't support publib libraries, so wanted to
>>> compile one myself. After compiling the source code, this appears, how
>>> to deal with it.
>>> -----------------------------------
>>> gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fndir.d -c
>>> fname/fndir.c -o fname/fndir.o
>>> gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fnhome.d -c
>>> fname/fnhome.c -o fname/fnhome.o
>>> fname/fnhome.c:38:10: fatal error: pwd.h: No such file or directory
>>> 38 | #include <pwd.h>
>>> | ^~~~~~~
>>> compilation terminated.
>>> make: *** [Makefile:403: fname/fnhome.o] Error 1
>>>
>>> --------------------------------------------------------------
>>> but I found: Enviroument var:
>>> C_INCLUDE_PATH=/mingw64/include:C:\msys64\mingw64\include
>>> and:
>>> ls -la /usr/include/pwd.h
>>> -rw-r--r-- 1 spender None 2.7K Nov 30 14:03 /usr/include/pwd.h
>> How was C_INCLUDE_PATH set?
>> That value appears to be a mix of a Unix-style path:
>> /mingw64/include
>> and a Windows-style path:
>> C:\msys64\mingw64\include
>> You haven't told us what environment you're using. How exactly are
>> you
>> invoking the compiler? CMD prompt? Cygwin? Powershell?
>> Unix-style paths use '/' as a directory delimiter, and ':' to
>> separate
>> entries. Windows-style paths use '\' as a directory delimiter, and ';'
>> to separate entries. Don't mix them.
>>
>>> soo:
>>> export
>>> C_INCLUDE_PATH=/mingw64/include:/usr/include:C:\msys64\mingw64\include
>> Again, don't mix Unix-style and Windows-style paths. Use the style
>> associated with the environment from which you're invoking the compiler.
>> [...]
>>
>
> It is probably easier to keep track of what is what if you don't mix
> path styles, but they should work fine either way.

Not in a PATH-style environment variable.

An environment such as Cygwin might interpret "C:\msys64\mingw64\include"
correctly (as equivalent to "/cygdrive/c/msys64/mingw64/include"),
but the ":" in "C:\..." will be treated as a delimiter between elements
of the search path, so the elements will be:

/mingw64/include
/usr/include
C
\msys64\mingw64\include

We need to know what environment the OP is working in.

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Will write code for food.
void Void(void) { Void(); } /* The recursive call of the void */

Thanks everyone!

mingw64 worked at windows, soo, It don't support function:
getpwuid, More information :
https://www.gnu.org/software/gnulib//manual/html_node/getpwuid.html

Abort(). thinks

在 2023/12/13 11:33, Janis Papanagnou 写道:
> On 13.12.2023 04:13, spender wrote:
>> does some body can help me:
>> I found that mingw64 doesn't support publib libraries, so wanted to
>> compile one myself. After compiling the source code, this appears, how
>> to deal with it.
>> -----------------------------------
>> gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fndir.d -c
>> fname/fndir.c -o fname/fndir.o
>> gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fnhome.d -c
>> fname/fnhome.c -o fname/fnhome.o
>> fname/fnhome.c:38:10: fatal error: pwd.h: No such file or directory
>> 38 | #include <pwd.h>
>> | ^~~~~~~
>> compilation terminated.
>> make: *** [Makefile:403: fname/fnhome.o] Error 1
>>
>> --------------------------------------------------------------
>> but I found: Enviroument var:
>> C_INCLUDE_PATH=/mingw64/include:C:\msys64\mingw64\include
>> and:
>> ls -la /usr/include/pwd.h
>> -rw-r--r-- 1 spender None 2.7K Nov 30 14:03 /usr/include/pwd.h
>>
>> soo:
>> export
>> C_INCLUDE_PATH=/mingw64/include:/usr/include:C:\msys64\mingw64\include
>
> Doesn't a Win/DOS system require a device character before the path?
> Something like C:\usr\include (or wherever that file is located)?
>
>>
>> now error:
>> make
>> gcc -Iincludes -D__publib__ -g -O2 -Wall -MD -MF fname/fnhome.d -c
>> fname/fnhome.c -o fname/fnhome.o
>> In file included from fname/fnhome.c:38:
>> C:\msys64\usr\include/pwd.h:50:9: error: unknown type name 'uid_t'
>> 50 | uid_t pw_uid; /* user uid */
>> | ^~~~~
>> C:\msys64\usr\include/pwd.h:51:9: error: unknown type name 'gid_t'
>> 51 | gid_t pw_gid; /* user gid */
>> | ^~~~~
>> fname/fnhome.c: In function 'fnhome':
>> fname/fnhome.c:50:32: warning: implicit declaration of function
>> 'getuid'; did you mean 'getpid'? [-W
>> implicit-function-declaration]
>
> Have you included the necessary header files for these functions?
> #include <unistd.h>
> #include <sys/types.h>
>
>
>> 50 | pwd = getpwuid(getuid());
>> | ^~~~~~
>> | getpid
>> make: *** [Makefile:403: fname/fnhome.o] Error 1
>