1 In this file the Callback Frequently Asked Questions are assembled.
2 This file is part of the distribution, but not necessarily the most recent
5 The most recent version of the callback FAQ can be found at ftp.icce.rug.nl,
6 directory pub/unix, file callback.FAQ
8 Q:'s are questions, A:'s answers
15 The problems I had are the following.
16 I installed the icmake, i download the .bin version I copied all the
17 files within /usr/local/bin. It seems to work.
18 Then I unpacked the callback 4.10, but as soon as I run build
22 ICCE Make Utility Version 6.10
23 Copyright (c) ICCE 1992-1994. All rights reserved.
24 ICMAKE consists of a set of five programs. Together, they can
25 be used for managing program development comparable to, e.g.,
26 the UNIX make facility, or as a SHELL-script language.
30 Get the most recent icmake distribution from ftp.icce.rug.nl/pub/unix,
31 icmake-X.Y.bin.tgz, and install the icmake binaries in /usr/local/bin
32 The callback 'build' script assumes the icmake programs in /usr/local/bin,
33 as can be seen from the headerline of the 'build' script:
35 #!/usr/local/bin/icmake -qt /tmp/callback
37 Also, you need a /tmp directory that is writable for the user starting the
41 the build script doesn't do the compilation
42 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
45 I'm just compiling the callback package now, and find that the build
46 didn't go through the first time because I, like many people, don't keep
47 "." in the search path (for security reasons). The script changes
48 directory to lib, then runs "build", and fails to find it. If the script
49 were instead to run "./build" everything would be fine.
52 the shortest solution is to change your path temporarily so that it
53 takes . as well. Alternatively, change the lines in the build script
54 where other build-scripts are called (e.g.,
61 It will be repaired in the next release
63 the build script won't run
64 ~~~~~~~~~~~~~~~~~~~~~~~~~~
67 I'm trying to install callback but during instalation I'can't to run the
68 program 'build'. Such communicate is displying 'No such file or directory'
69 though this program exist in my catalog.
72 You must have the icmake programs in /usr/local/bin, as you can see
73 from the first line in the build-script. If you start icmake without
74 arguments it should show 'Version 6.11'. If you start icmake, and you
75 get the usage information, then maybe one of the programs used in the
76 build-script are not on your system. You need:
77 rm, echo, cp, cat, touch, chmod,
78 bison, flex, strip, ar, mkdir, gcc
79 and for the documentation:
81 And, of course, the 'build'-script itself must be in your path.
83 Furthermore, the build-script uses the /tmp directory for temporary files.
84 This directory must be readable/writable/executable for you. If
85 you do not have the most recent version of either callback or icmake,
86 try to upgrade: the most recent version of all our software is at
87 ftp.icce.rug.nl, /pub/unix.
94 When I invoked build, it work for a few seconds, and then.... It was very
95 unhappy about your C++ comment in lib/log/logv.c! (You haven't been
96 commenting your program in last minutes have you? ;-)
99 Indeed, there is a C++ comment in that source. My compiler (2.7.2) doesn't
100 choke on it, though. Anyway, remove the comment in lib/log/logv.c and it
101 compiles fine. Jesper Pedersen who sent me the mail wrote next:
103 I use 2.7.0....Hmm glad that gcc now likes //, I've often compiled with
104 g++ just to get this feature.
106 So, the compiler version solves the problem as well.
109 cblogin isn't started
110 ~~~~~~~~~~~~~~~~~~~~~
114 > I beleive that you have forgotten to tell in the manual that if one
115 > install mgetty himself, he has to remember to add a line like this:
116 > * - - /usr/local/lib/callback/cblogin @
119 the question solves the problem itself. It's in the INSTALL file of
120 the next release, but as of now, I home this will be sufficient.