root@bbs:/srv/fido/src/husky/fidoconf# make all
gcc -Wall -c -s -O3 -fomit-frame-pointer -fstrength-reduce -fPIC -O3 -DUNIX -DCFGDIR=\"/etc/fido\" -DPATH_DELIM=\'/\' -c -fPIC -Wall -ggdb -DUNIX -I.. -Wno-char-subscripts -Ifidoconf -I/usr/include
src/afixcmn.c src/afixcmn.c: In function
‘createXMSG’: src/afixcmn.c:342:67: error: ‘FTSC_DATE_SIZE’ undeclared (first use in this function); did you mean
‘XMSG_TO_SIZE’? strncpy((char *)msgHeader.__ftsc_date, (char *)msg->datetime, FTSC_DATE_SIZE);
^~~~~~~~~~~~~~
XMSG_TO_SIZE src/afixcmn.c:342:67: note: each undeclared identifier is reported only once for each function it appears in
make: *** [makefile.inc:27: afixcmn.o] Error 1
How can i fix it?
How can i fix it?
FTSC_DATE_SIZE is defined in smapi. The error means you did not install smapi after compiling it. You have to install every subproject producing a library before compiling the next subproject.
-DUNIX -I.. -Wno-char-subscripts -Ifidoconf -I/usr/include
src/afixcmn.c src/afixcmn.c: In function
‘createXMSG’: src/afixcmn.c:342:67: error: ‘FTSC_DATE_SIZE’ undeclared (first use in this function); did you mean
‘XMSG_TO_SIZE’?
strncpy((char *)msgHeader.__ftsc_date, (char *)msg->datetime, FTSC_DATE_SIZE);
^~~~~~~~~~~~ ~~
Hello Angel,
Please pull fidoconf and rebuild it.
BTW it is not recommended to compile a program from root. It is better to build it this way:
Now i can't complile areafix:^^^^^^^^^^
In file included from src/areafix.c:65: /usr/local/include/fidoconf/common.h:166:16: note: expected
Hello Angel,
Monday March 15 2021, Angel Ripoll wrote to Michael Dukelsky:
Now i can't complile areafix:
In file included from src/areafix.c:65:
/usr/local/include/fidoconf/common.h:166:16: note: expected
^^^^^^^^^^
The header file was taken from /usr/local/include but you installed fidoconf header files to /usr/include. You have to use the same huskymak.cfg for all Husky compilations. The files in /usr/local/include could stay from the previous builds. It is better to delete now areafix, fidoconf, smapi, huskylib subdirectories of the /usr/local/include directory together with all files inside the subdirectories.
^^^^^^^^^^^^^^^^^^ It is the same.Now i can't complile areafix:
In file included from src/areafix.c:65:
/usr/local/include/fidoconf/common.h:166:16: note: expected
^^^^^^^^^^
The header file was taken from /usr/local/include but you
installed fidoconf header files to /usr/include. You have to use
the same huskymak.cfg for all Husky compilations. The files in
/usr/local/include could stay from the previous builds. It is
better to delete now areafix, fidoconf, smapi, huskylib
subdirectories of the /usr/local/include directory together with
all files inside the subdirectories.
Ok. I'm going to download all the sources again to start from
scratch. I'm going to compile them in their order (and not from root).
Now the only error gives me in hpucode:
***************
ftn@bbs:/usr/src/ftn/husky/hpucode$ make all
gcc -I/usr/local/include -I./h -c -s -O3 -fomit-frame-pointer
gcc -I/usr/local/include -I./h -c -s -O3 -fomit-frame-pointer
^^^^^^^^^^^^^^^^^^ It is the same.
The directory is defined by setting the variable PREFIX in your huskymak.cfg. If you specify PREFIX=/usr, then the header files will be taken from /usr/include and if you specify PREFIX=/usr/local, then the header files will be taken from /usr/local/include. That is why it is important to use the same huskymak.cfg in all compilations.
-DUNIX -c src/uuefile.c src/uuefile.c: In function ‘MakeTicFile’: src/uuefile.c:385:34: error: ‘CHAR’ undeclared (first use in this function); did you mean ‘UCHAR’?
recodeToTransportCharset((CHAR*)uuc->description);
^~~~
UCHAR
recodeToTransportCharset((CHAR*)uuc->description);
^~~~
UCHAR
Fixed.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 368 |
Nodes: | 16 (2 / 14) |
Uptime: | 87:02:44 |
Calls: | 7,895 |
Calls today: | 1 |
Files: | 12,968 |
Messages: | 5,792,152 |