TIP: Click on subject to list as thread! ANSI
echo: fidosoft.husky
to: Angel Ripoll
from: Michael Dukelsky
date: 2021-03-20 16:53:00
subject: Error compiling fidoconf

Hello Angel,

Friday March 19 2021, Angel Ripoll wrote to Michael Dukelsky:

 AR>>>     Now i can't complile areafix:

 AR>>> In file included from src/areafix.c:65:
 AR>>> /usr/local/include/fidoconf/common.h:166:16: note: expected

 MD>>      ^^^^^^^^^^
 MD>> The header file was taken from /usr/local/include but you
 MD>> installed fidoconf header files to /usr/include. You have to use
 MD>> the same huskymak.cfg for all Husky compilations. The files in
 MD>> /usr/local/include could stay from the previous builds. It is
 MD>> better to delete now areafix, fidoconf, smapi, huskylib
 MD>> subdirectories of the /usr/local/include directory together with
 MD>> all files inside the subdirectories.

 AR>     Ok. I'm going to download all the sources again to start from
 AR> scratch. I'm going to compile them in their order (and not from root).

 AR>     Now the only error gives me in hpucode:

 AR> ***************
 AR> ftn@bbs:/usr/src/ftn/husky/hpucode$ make all
 AR> 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.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Moscow, Russia (2:5020/1042)

SOURCE: echomail via QWK@pharcyde.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.