[SOLVED] make failure when building bigforth

psionl0 · 03-16-2011, 02:32 AM

I am trying to make a slackbuild for the bigforth package (source: http://www.jwdt.com/~paysan/bigforth-2.2.0.tar.bz2). However when I run make I get the following error messages:

Code:

bash-4.1# make
env LIBDIR=/usr/local/lib/bigforth SRC=/usr/local/lib/bigforth/src ./forthker -e " include startup.fb ' .blk is .status warning on savesystem bigforth cr bye"

./bigforth -e " use x.fs use glconst.fs use float.fb include startx.fb warning on savesystem xbigforth cr bye"

No protocol specified
 Can't connect  
make: *** [ok] Error 254
bash-4.1#

Can anybody tell from this what "protocol" is missing?

Richard Cranium · 03-16-2011, 06:29 AM

A little bit of grep-fu will lead you to line 549 of minos-base.fs...

Code:

   545  \ XResource                                            17sep07py
   546  
   547          : open ( string -- )  [ also DOS ]
   548            6 0" " setlocale 0= abort" Cannot set locale"
   549            XOpenDisplay dup dpy ! 0= abort" Can't connect"
   550            XSupportsLocale IF
   551               s" XMODIFIERS" env$ drop ?dup IF
   552               XSetLocaleModifiers  0= IF
   553                  ." Warning: Cannot set locale modifiers to '"
   554                  s" XMODIFIERS" env$ type  ." '" cr THEN  THEN
   555            THEN [ toss ] ;

...so there's something off with your X environment in that shell (or the way Minos accesses it), since he's reporting that the call to XOpenDisplay is returning a zero. You can check the man page for the XOpenDisplay call to see what it is doing.

I've never run BigForth and I can't do so on my 64 bit system, so that's all the "help" that I can provide. Sorry.

BroX · 03-16-2011, 05:37 PM

I assume you get "No protocol specified, Can't connect" because as root you are not allowed to connect to the X server. I don't know if this is the 'legal' way, but I usually solve this by

Code:

$ xhost +
access control disabled, clients can connect from any host

You might want to read up on 'man xhost' first.

psionl0 · 03-16-2011, 09:54 PM

Quote:

Originally Posted by BroX

I assume you get "No protocol specified, Can't connect" because as root you are not allowed to connect to the X server.

THAT was the problem.

When I logged in as root rather than running su the problems disappeared. (I seem to vaguely remember reading something about this in slackbuilds).

Now I can continue with the challenge of making a slackware package out of this (the Makefile does not recognize DESTDIR so still some fun to come). Thanks for the solution.