I cloned the necessary gits but during the building of huskylib, I am getting:

make -f make/makefile.lnx all
gcc -O3 -I./huskylib/ -Wall -Wno-long-long -g -pedantic -c src/version.c src/version.c:47:5: error: expected identifier or '('
if((need_major == huskylib_VER_MAJOR) && (need_minor == huskylib_VER_MINOR))
^
1 error generated.
make: *** [version.o] Error 1
sean@Seans-MacBook-Air huskylib %

I know I am doing something simple wrong, but just cannot work it out

Sean

--- BBBS/Li6 v4.10 Toy-5
* Origin: TCOB1 at tcob1.duckdns.org BinkP / Telnet (2:263/1)

Hello Sean,

Thursday December 09 2021, Sean Rima wrote to All:

I cloned the necessary gits but during the building of huskylib, I am getting:

[...skipped...]

I know I am doing something simple wrong, but just cannot work it out

The correct way of building Husky is described here:

https://github.com/huskyproject/huskybse/blob/master/INSTALL.asciidoc

Michael

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

Michael Dukelsky wrote to Sean Rima <=-

I cloned the necessary gits but during the building of huskylib, I

am

getting:

[...skipped...]

I know I am doing something simple wrong, but just cannot work it

out

The correct way of building Husky is described here:

https://github.com/huskyproject/huskybse/blob/master/INSTALL.asciidoc

ok, will do that and hopefully next message with be via hpt

Sean


... TCOB1: telnet/ binkd / https(P: 9043) tcob1.duckdns.org

--- BBBS/Li6 v4.10 Toy-5
* Origin: TCOB1 at tcob1.duckdns.org BinkP / Telnet (2:263/1)

Hello Michael!

10 Dec 21 11:14, you wrote to me:

I cloned the necessary gits but during the building of huskylib,
I am
getting:

[...skipped...]

I know I am doing something simple wrong, but just cannot work it
out

The correct way of building Husky is described here:

https://github.com/huskyproject/huskybse/blob/master/INSTALL.asciidoc

Michael

Thanks that worked :)
Sean
--- GoldED+/OSX 1.1.5-b20180707
* Origin: TCOB1 tcob1.duckdns.org (2:263/1.1)

Hello Michael!

10 Dec 21, Michael Dukelsky wrote to Sean Rima:

The correct way of building Husky is described here:

https://github.com/huskyproject/huskybse/blob/master/INSTALL.asciidoc

Is there an important reason for this file and its file extension?

Maybe i blame myself but i've never seen an *.asciidoc before. I don't understand why the correct way is not in the common README and INSTALL files?

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai,

Monday December 13 2021, Kai Richter wrote to Michael Dukelsky:

The correct way of building Husky is described here:

https://github.com/huskyproject/huskybse/blob/master/INSTALL.asci
idoc

Is there an important reason for this file and its file extension?

Yes, there is.

Maybe i blame myself but i've never seen an *.asciidoc before. I don't understand why the correct way is not in the common README and INSTALL files?

"There are more things in heaven and earth, Horatio,
Than are dreamt of in your philosophy." (C) Shakespeare. :)

There are several markup languages that GitHub can render into a nice looking HTML. One of them is called asciidoc.

https://en.wikipedia.org/wiki/AsciiDoc

GitHub demands a document written in asciidoc format to have a filename extension of .asciidoc, .adoc, or .ad for correct rendering. I'm not too fond of the two last variants, so I chose the first one.

Michael

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

Hello Michael!

13 Dec 21, Michael Dukelsky wrote to Kai Richter:

Maybe i blame myself but i've never seen an *.asciidoc before.

Ok, i did. :-)

https://en.wikipedia.org/wiki/AsciiDoc

GitHub demands a document written in asciidoc format to have a
filename extension of .asciidoc, .adoc, or .ad for correct rendering.
I'm not too fond of the two last variants, so I chose the first one.

I do agree. While Wikipedia shows a very simple example the homepage of asciidoc shows a lot of more. Very interesting is FAQ 15 "preferred file name extension for AsciiDoc files is .txt". Well, github may have reasons. (Not may, they do have, of course.)

Sigh... there are so many standards that there is no standard anymore.

As far as i understand you do a rebuild/upgrade of the make system. With the old INSTALL and the new INSTALL.asciidoc we have a transition phase. I'd like to suggest to add a soft link to INSTALL.asciidoc with 2 or 3 lines explanation into the INSTALL or README file.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai,

Tuesday December 14 2021, Kai Richter wrote to Michael Dukelsky:

As far as i understand you do a rebuild/upgrade of the make system.
With the old INSTALL and the new INSTALL.asciidoc we have a transition phase. I'd like to suggest to add a soft link to INSTALL.asciidoc with
2 or 3 lines explanation into the INSTALL or README file.

Thank you for reminding me that the old INSTALL file is still there. I am going to delete it, but first, I have to incorporate the chapter on legacy makefiles into INSTALL.asciidoc. Unfortunately, I have no
time for that now.

Michael

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

Hello Michael!

14 Dec 21, Michael Dukelsky wrote to Kai Richter:

Thank you for reminding me that the old INSTALL file is still there. I
am going to delete it, but first, I have to incorporate the chapter on legacy makefiles into INSTALL.asciidoc. Unfortunately, I have no time
for that now.

Thanks a lot in advance. There is no time pressure for the above but if possible a single line in the top of the INSTALL file like "Please refer to INSTALL.asciidoc first." would point the doc reading users into the right direction until you are done with the incorporation.

Btw, is there an asciidoc to plain txt converter?

I found PanDoc. But i can't see if it's supporting asciidoc -> txt.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai,

Wednesday December 15 2021, Kai Richter wrote to Michael Dukelsky:

Thank you for reminding me that the old INSTALL file is still
there. I am going to delete it, but first, I have to incorporate
the chapter on legacy makefiles into INSTALL.asciidoc.
Unfortunately, I have no time for that now.

Thanks a lot in advance. There is no time pressure for the above but
if possible a single line in the top of the INSTALL file like "Please refer to INSTALL.asciidoc first." would point the doc reading users
into the right direction until you are done with the incorporation.

Done.

Btw, is there an asciidoc to plain txt converter?

What for? You may read it as any other text file. Just open it using any text viewer or text editor.

Michael

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

Hello Michael!

15 Dec 21, Michael Dukelsky wrote to Kai Richter:

Btw, is there an asciidoc to plain txt converter?

What for? You may read it as any other text file.

The asciidoc standard supports many keywords that could make an asciidoc a little bit uncomfortable to read and it could be helpful to remove that keywords. I lost my first husky latest installation but now i can see the you don't use that, because ten minutes ago i solved some trouble with updating my jails system and i have a gitup clone of the new versions ready for FreeBSD testing. That will take some time, my xmas shedule would be set up at this weekend and my node migration doesn't have a high priority.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)