Hola Kai :)

Sorry Kai, it seems like I missed reading these message  :(

Viernes 25 Agosto 2006 10:58, Kai Richter escribió a Felipe T. Dorado:


 KR> "make" is not the first step. The first one is called rtfm. :)

;)   Yes, ok, I went through it several times and thought it was enough. I was wrong.

 FD>> gcc (GCC) 4.0.1 (Debian 4.0.1-2)

 KR> Hm, i don't know if that version will be fine for husky, but i hope you
 KR> can tell us later. :)

So far no problems on that front.

 FD>> huskybase-1.4-tar.gz

 KR> Your entry point for the linux version of husky installation can be found
 KR> within the file INSTALL of the huskybse module, filename
 KR> huskybase-1.4-tar.gz.

 KR> You find example huskymak.cfg there, required for compilation.

Yes, done that.

 KR> Your friends will need at last the module
 KR> hpt for tossing (check its VERSION file for  requirements of hpt,
 KR> then the VERSION files of the following required modules) and
 KR> an editor for reading/writing like golded or, as part of the husky tree,
 KR> msged, and finally a mailer to connect to the fidonet network.

Ok, this is really taken for granted in the doc and the web. Users are not
programmers.

 FD>> - copied huskymak.cfg from smapi/debian directory to the top level

 KR> Why? Who told you so? And who put the huskymak,cfg (the config file of the
 KR> husky modules) into smapi/debian (the module using the husky config)?
 KR> (Mine don't have huskymak.cfg in smapi/debian, version 2.4.0+rc5-1)

Let me check that ...
No it wasn't from smapi that I copied it, couldn't have 'cos there isn't
any there as you rightly say.
It must have been from huskybase ...
I have the husky files  I downloaded about a year and a half ago and had a
go at compiling those first, kind of trial. Since I wasn't getting very far
I started afresh with the actual stable releases at sf.   ...
With all that and my inexperience I got mistaken. :(

 KR> If you start with the first step: rtfm, you find that there is a
 KR> huskymak.cfg.debian in the huskybse (means huskybase) directory.

Having read the fine manual ...  ;)  which must be the huskybse/INSTALL
file, though there is another INSTALL in smapi which in turn tells you to
read huskybase/README.Makefiles first, I still fail to see, using a debian
system, whether I should use the general huskybse.cnf or the
husky.cfg.debian, sorry.
And I am a little apprehensive that these compilations will leave traces in
my system that will hamper future tries. Newbie's fears ;)

 FD>> - did not change anything in the huskymak.cfg so as to leave per
 FD>> default and because /usr/local is fine with me  (I presume that "and
 FD>> change all values according to your needs" means that if I do not
 FD>> change anything compilation should work fine).

 KR> Sorry, wrong. "Chance all values to your needs" means
that you MUST check
 KR> at last ALL values to your needs. If you don't check, you have a
"unsure"
 KR> config and maybe you are checking your problems at the wrong place.

Precisely. It is why I checked but did not see anything worth changing lest
I put in some wrong value.

 KR> For example: The huskymak.cfg.debian does not have /usr/local for default
 KR> installation path.

No, it has /usr as DESTDIR.

 KR> You may want to check the CFGDIR too.

Yeap, checked that the general makefile uses /etc/fido and the debian one
uses /etc/husky. I'm afraid no make install created any dir in /etc  :(
I now have an /etc/fido in which I have copied a config file from the node
in order to edit it manually because I've seen it is where it should be.
But it is really a far shot. Make install should have created it and
fidoInst created the config file.

 KR> The Keyword DYNLIBS may be a point of interesst if you think about later
 KR> updates. (i set 0)

Mmm. Too much for me yet. I can't think of updating what it is not yet
installed really.

Ok, all this is fine if one uses the debian make file. I did not. And you
seem to imply that I should have. But the manual leaves that as an option,
right :?

 KR> I think the other values of huskymak.cfg.debian are good default.

So, I should compile again but using:
make -f huskymak.cnf.debian    and
make -f huskymak.cnf.debian install
instead of the general make file. Is that right?

 FD>> - as root (to avoid possible access errors) I cd to smapi and type

 KR> ok.

 FD>> # make clean
 FD>> make: *** No hay ninguna regla para construir el objetivo `clean'.
 FD>> Alto. (There's no rule to build object "clean". Stop.)

 KR> Strange. Do you have a "Makefile" (capital M) in your
smapi directory?

This is "solved": not all files were decompressed, some were missing :(
It finally compiled fine after I decompressed again and made sure.

 KR> a check for DEBIAN, that changes the path to the wrong huskymak.cfg?
 KR> Strange! But it compares with the huskybse/debian/rules file. I don't know
 KR> how debian handles that rules file.

I understand that not having a basic knowledge of compiling prevents me 
from seeing the importance of Makefile/huskymak.cnf.*, the rules and some
other files. And you probably take for granted that what you see in the
dirs is the same I see ... No, I'm just a user that can read but not
program  ;)

 KR> If you read the INSTALL of the huskybse directory you found that debian is
 KR> not using legacy makefiles. The default linux makefile.lnx list "GNU gcc
 KR> (2.7..2.95, 3.x) for the compiler. You are using 4.x that may be another
 KR> problem.

No complaints so far there :)

 FD>> I've also tried copying huskymak.cfg.debian to top directory renaming
 FD>> it huskymak.cfg. No luck.

 KR> Ah, very good. Recheck its values.

I will re-do that :)

 KR> (you don't need luck to install husky ;-)

Sure?  Alright, off the window go the dice!   ;DDD

 FD>> My Points will never get as far as I've got.

 KR> If your points use the same Debian Version like you do, you can use
 KR> DYNLIBS=0 and give them the ready compiled binaries.

Let me make sure mine do work first.

 FD>> If there a debian package that I can apt-get install from some
 FD>> repository ;?)

 KR> I still have problems to install Debian to my node with some hpt
 KR> controller,

Ah, no "problemo"  ;)  Just ask me!  };)

 KR> later i want to move husky to it. So i think i will run into
 KR> the same problems like you did.

We are more or less on the same boat there, Kai.

 FD>> But I have to understand it first.

 KR> Me too. Not the husky modules only, the Debian package system too. That
 KR> will need a long time.

Yeap, same boat :)

Thanks a lot for your help. Making me look more in depth help learning.
Keepo at it ;)

Felipe :)

--- GoldED+/LNX 1.1.5