Hi,

When compiling BULLSEYE.SRC Baja gives error:

SYNTAX ERROR (expecting variable name)
bullseye.src 24: _errno

Do i need to add "!include errno.inc" - did not help
or add "str _errno" - did help.

i did it right?



Nidas




---
■ Synchronet ■ Perkunas BBS ■ 212.47.115.162

Hi,

When compiling BULLSEYE.SRC Baja gives error:

SYNTAX ERROR (expecting variable name)

bullseye.src 24: _errno

Do i need to add "!include errno.inc" - did not help

or add "str _errno" - did help.

i did it right?

Can you extract the original .src file and compare the two (your edited
one with the virgin file?

What's the difference?

Post the altered lines.

-
James King, Coldwater, Mi And that's JIM to you guys!
Tip of the day: http://setiathome.berkeley.edu Echo
---
■ OLXWin 1.00b ■ Back Up My Hard Drive? I Can't Find The Reverse Switch!
■ Synchronet ■ Bits-N-Bytes BBS One hellava BBS 24.241.127.99

RE: BULLSEYE.SRC compiling
BY: Jim to Nidas on Thu Mar 01 2001 08:58:00

Can you extract the original .src file and compare the two (your edited
one with the virgin file?

What's the difference?

Post the altered lines.

I only changed a color of prompt line from blue to cyan. :-)
I downloaded BSEYE100.ZIP from VERT, the file included is identical, it wouldn't compile (well without any extra options as i always do..)
The line with problem is #21:

printf "\r\n!ERROR %ld opening %s\r\n" _errno str

so i asked is it correct to add line "str _errno" to solve the problem


Nidas


---
■ Synchronet ■ Perkunas BBS ■ 212.47.115.162

RE: BULLSEYE.SRC compiling
BY: Nidas to All on Thu Mar 01 2001 11:38 am

When compiling BULLSEYE.SRC Baja gives error:

SYNTAX ERROR (expecting variable name)
bullseye.src 24: _errno

Do i need to add "!include errno.inc" - did not help

No, you need to include sbbsdefs.inc

or add "str _errno" - did help.

i did it right?

No.

Rob

RE: BULLSEYE.SRC compiling
BY: Nidas to Jim on Thu Mar 01 2001 07:21 pm

Can you extract the original .src file and compare the two (your edited one with the virgin file?

What's the difference?

Post the altered lines.

I only changed a color of prompt line from blue to cyan. :-)
I downloaded BSEYE100.ZIP from VERT, the file included is identical, it wouldn't compile (well without any extra options as i always do..)
The line with problem is #21:

printf "\r\n!ERROR %ld opening %s\r\n" _errno str

You must have removed the !include sbbsdefs.inc line because it's in original.

Rob

RE: BULLSEYE.SRC compiling
BY: Digital Man to Nidas on Thu Mar 01 2001 10:44:00

Do i need to add "!include errno.inc" - did not help

No, you need to include sbbsdefs.inc

Yes, it's included, as i said i compile unmodified source.

This is real strange.. I found another source that has _errno in it (QNET.src) and that doesn't compile too (at least for me)


Nidas


---
■ Synchronet ■ Perkunas BBS ■ 212.47.115.162

RE: BULLSEYE.SRC compiling
BY: Digital Man to Nidas on Thu Mar 01 2001 10:48:00

printf "\r\n!ERROR %ld opening %s\r\n" _errno str

You must have removed the !include sbbsdefs.inc line because it's in origina

Now i checked this sbbsdefs.inc file..

from my old BBS backup - file sbbsdefs.inc has line !global _ERRNO
this file dated 1996-07-04.

file i have in \EXEC dir. doesn't have above mentioned line.
this file dated 2000-10-24

any comments?

Nidas



---
■ Synchronet ■ Perkunas BBS ■ 212.47.115.162

RE: BULLSEYE.SRC compiling

BY: Jim to Nidas on Thu Mar 01 2001 08:58:00

Can you extract the original .src file and compare the two (your edited

one with the virgin file?

What's the difference?

Post the altered lines.

I only changed a color of prompt line from blue to cyan. :-)

I downloaded BSEYE100.ZIP from VERT, the file included is identical, it
wouldn't compile (well without any extra options as i always do..)
The line with problem is #21:

printf "\r\n!ERROR %ld opening %s\r\n" _errno str

set str "%zBULLSEYE.CFG"
fopen file O_RDONLY str
if_false
printf "\r\n!ERROR %ld opening %s\r\n" _errno str
return
end_if

Mine runs and it is compiled without the additional include.

Possible the re error is being generated above but reported on this
line.

If you have access to the sbbs3.0c maybe you can extract what you need
from there.

so i asked is it correct to add line "str _errno" to solve the problem

-
James King, Coldwater, Mi And that's JIM to you guys!
Tip of the day: http://setiathome.berkeley.edu Echo
---
■ OLXWin 1.00b ■ This tagline is umop apisdn
■ Synchronet ■ Bits-N-Bytes BBS One hellava BBS 24.241.127.99

RE: BULLSEYE.SRC compiling
BY: Nidas to Digital Man on Thu Mar 01 2001 09:04 pm

RE: BULLSEYE.SRC compiling
BY: Digital Man to Nidas on Thu Mar 01 2001 10:44:00

Do i need to add "!include errno.inc" - did not help

No, you need to include sbbsdefs.inc

Yes, it's included, as i said i compile unmodified source.

This is real strange.. I found another source that has _errno in it (QNET.sr and that doesn't compile too (at least for me)

Is your sbbsdefs.inc missing the !include errno.inc line? You are compiling this files in your EXEC directory, right?

Rob

RE: BULLSEYE.SRC compiling
BY: Nidas to Digital Man on Thu Mar 01 2001 09:23 pm

printf "\r\n!ERROR %ld opening %s\r\n" _errno str

You must have removed the !include sbbsdefs.inc line because it's in orig

Now i checked this sbbsdefs.inc file..

from my old BBS backup - file sbbsdefs.inc has line !global _ERRNO
this file dated 1996-07-04.

file i have in \EXEC dir. doesn't have above mentioned line.
this file dated 2000-10-24

any comments?

_errno is defined in errno.inc, but sbbsdefs.inc INCLUDES errno.inc, so you should not have to include errno.inc if you're already including sbbsdefs.inc. Make sense?

21:17 C:\sbbs\exec grep errno *.inc
File errno.inc:
# errno.inc
# Defines the system error variable _errno and the error
File sbbsdefs.inc:
!include errno.inc

Rob

RE: BULLSEYE.SRC compiling
BY: Digital Man to Nidas on Thu Mar 01 2001 21:40:00

_errno is defined in errno.inc, but sbbsdefs.inc INCLUDES errno.inc, so you should not have to include errno.inc if you're already including sbbsdefs.in Make sense?

21:17 C:\sbbs\exec grep errno *.inc
File errno.inc:
# errno.inc
# Defines the system error variable _errno and the error
File sbbsdefs.inc:
!include errno.inc

OK Rob, i finally figured it out: i had sbbsdefs.inc from ver3.00c, which !includes errno.inc, but errno.inc i had, was from ver. 3.00b, which did
not have line !global _ERRNO. How it happened that i had such setup-
i don't know. Was installing ver3.00C UPGRADE on top of 3.00b.

To figure this out i had to fresh install both ver.3.00b and 3.00c
As i'm writing about this i want to ask if it's necessary to first
Uninstall the intalled version. Or it's no problem to install 2nd, 3rd
copy of Synchronet to other base directory, and then after uninstall
everything should be OK with original BBS installation.
In other words -does Synchronet use Windows registry for settings, or
every setting is in installed base dir, configuration files, etc..
I personally would like it be second variant.

Well thanks for the replies. Good to have a software, where author can
respond usually within 24hours. And asking questions is one of the
ways of quick learning. Don't you agree?

Nidas


p.s. my BBS name change occured after original 'Byte's Hell' sysop
visited (now he's a CoSysop). I was thinking of changing it anyway.
Now should be more understandable for foreign users ;)


---
■ Synchronet ■ The Byte's Hell ■ tbh.dtdns.net

RE: BULLSEYE.SRC compiling
BY: Nidas to Digital Man on Fri Mar 02 2001 09:16 pm

_errno is defined in errno.inc, but sbbsdefs.inc INCLUDES errno.inc, so y should not have to include errno.inc if you're already including sbbsdefs Make sense?

21:17 C:\sbbs\exec grep errno *.inc
File errno.inc:
# errno.inc
# Defines the system error variable _errno and the error
File sbbsdefs.inc:
!include errno.inc

OK Rob, i finally figured it out: i had sbbsdefs.inc from ver3.00c, which !includes errno.inc, but errno.inc i had, was from ver. 3.00b, which did not have line !global _ERRNO. How it happened that i had such setup-
i don't know. Was installing ver3.00C UPGRADE on top of 3.00b.

Perhaps the upgrade is missing errno.inc <shrug>

To figure this out i had to fresh install both ver.3.00b and 3.00c
As i'm writing about this i want to ask if it's necessary to first
Uninstall the intalled version.

No, it's not necessary.

Rob