FW: [Xorp-users] XORP 1.1RC Install under OpenBSD 3.6

[Pavlin Radoslavov]

> Thank you for the information below, I installed python-2.1.3p2.tgz and
> bash-3.0-static.tgz and reran the gmake check and now came up with the
> following errors. Attached is the output from the gmake check.... Any
> additional help would be greatly appreciated...
> 
> 
> [ 2005/04/14 05:21:25 WARNING test_lemming XrlFinderTarget ] Handling
> method for finder/0.2/resolve_xrl failed:  XrlCmdError 102 Command
> failed Xrl target is not enabled.
> =20
> [ 2005/04/14 05:21:43 ERROR test_lemming XRL ] NO FINDER
> 
> [ 2005/04/14 05:22:40 WARNING test_finder_events FINDER ] ready is 1 not
> zero

You can ignore the above messages. If the test itself returns
"PASS" (which seems to be the case based on your "gmake check" log
file), then it should be fine.

> peer.cc:797: invalid `asm': operand number out of range
> peer.cc:799: invalid `asm': operand number out of range
> peer.cc:801: invalid `asm': operand number out of range
> peer.cc:805: invalid `asm': operand number out of range
> peer.cc:805: invalid `asm': operand number out of range
> peer.cc:805: invalid `asm': operand number out of range
> peer.cc:818: invalid `asm': operand number out of range
> peer.cc:834: invalid `asm': operand number out of range
> peer.cc:834: invalid `asm': operand number out of range
> peer.cc:834: invalid `asm': operand number out of range
> peer.cc:846: invalid `asm': operand number out of range

The above compilation errors seem to be triggered by lines that
use htons(), htonl() and friends. Those innocent-looking lines
should not trigger such compilation errors.

What is the particular hardware you are using?
Also, what is the gcc/g++ compiler version (gcc --version)?

If I remember correctly, some time ago I saw similar errors on older
versions of OpenBSD (3.5?). At that time I concluded that this is a
compiler's problem (I was using the OpenBSD-3.5 default 2.95.x
compiler), and indeed after I installed a newer compiler from the
ports collection, that problem went away.

I don't remember whether I have tried vanilla OpenBSD-3.6, but you
may have a look in the OpenBSD-3.5 section in BUILD_NOTES and see if
the info there will help you for 3.6.
I have tried with OpenBSD-3.6-current (as of February 2005) on amd64
and i386 (the default compiler is gcc (GCC) 3.3.5 (propolice)), and
I haven't seen that compilation error.

Pavlin

> {standard input}: Assembler messages:
> {standard input}:42351: Error: expecting operand after ','; got nothing
> {standard input}:42397: Error: expecting operand after ','; got nothing
> {standard input}:42448: Error: expecting operand after ','; got nothing
> {standard input}:42543: Error: expecting operand after ','; got nothing
> {standard input}:42543: Error: expecting operand after ','; got nothing
> {standard input}:42543: Error: expecting operand after ','; got nothing
> {standard input}:42670: Error: expecting operand after ','; got nothing
> {standard input}:42770: Error: expecting operand after ','; got nothing
> {standard input}:42770: Error: expecting operand after ','; got nothing
> {standard input}:42770: Error: expecting operand after ','; got nothing
> {standard input}:42831: Error: expecting operand after ','; got nothing
> gmake[3]: *** [peer.o] Error 1
> gmake[3]: Leaving directory `/xorp/xorp-1.1-RC/bgp/harness'
> gmake[2]: *** [check-am] Error 2
> gmake[2]: Leaving directory `/xorp/xorp-1.1-RC/bgp/harness'
> gmake[1]: *** [check-recursive] Error 1
> gmake[1]: Leaving directory `/xorp/xorp-1.1-RC/bgp'
> gmake: *** [check-recursive] Error 1