modula3.github.io/known-problems.html at master · modula3/modula3.github.io · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <META HTTP-EQUIV="Content-Type" CONTENT="text/html">
    <META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
    <META HTTP-EQUIV="Resource-type" CONTENT="document">
    <META HTTP-EQUIV="Description" CONTENT="Modula-3 Resource Page">
    <META HTTP-EQUIV="Distribution" CONTENT="global">
    <META HTTP-EQUIV="Keywords" CONTENT="m3, modula-3, modula3, M3, Modula-3, modula-3, cm3, CM3, FreeCM3">
    <META HTTP-EQUIV="Reply-to" CONTENT="m3-support@elego.de">
    <LINK HREF="normal.css" REL="stylesheet" TYPE="text/css">
    <title>Known Problems with CM3 5.1 and 5.2</title>
  </head>

  <body bgcolor="#ffffff">
    <h2>Known Problems with CM3</h2>

    <p>
      Contents:<br><br>

      <a href="#p_1">1 General Problems</a><br>
      &nbsp;&nbsp;
      <a href="#p_1_1">1.1 Linkage failure: cannot find -lXaw</a><br>
      &nbsp;&nbsp;
      <a href="#p_1_2">1.2 Filenames with spaces</a><br>
      &nbsp;&nbsp;
      <a href="#p_1_3">1.3 Unresolved X11 libraries on NetBSD</a><br>
      &nbsp;&nbsp;
      <br><br>
      <br>
    </p>

    <h3><a name="p_1">1 General Problems</a></h3>

    <p>
      General problems and notes applying to all releases:
    </p>

    <h4><a name="p_1_1">1.1 Linkage failure: cannot find -lXaw</a></h4>

    <p>
      <b>Platforms:</b> mostly LINUXLIBC6
    </p>

    <p>
      <b>Description:</b>
      Problems of this kind will arise if the linker cannot find the
      static standard libraries of the X systems. This will mostly be
      a problem on Linux systems, as almost all newer distributions
      tend to not install static libraries by default. A typical
      failure situation looks like this:
    </p>

    <pre>
&gt; === package /home/i8fs1/VERIF/usr/old/stow/cm3/current/m3-ui/formsedit ===
&gt;  +++ cm3 -build -override -DROOT=/home/i8fs1/VERIF/usr/old/stow/cm3/current  +++
&gt; --- building in LINUXLIBC6 ---
&gt; /home/i8fs1/VERIF/usr/old/stow/cm3/tmp/bin/m3bundle -name formseditBundle -F/tmp/qk
&gt; new source -&gt; compiling FormsEditVBT.i3
&gt; new source -&gt; compiling formseditBundle.i3
&gt; new source -&gt; compiling FormsEditVBT.m3
&gt; new source -&gt; compiling FormsEdit.m3
&gt; new source -&gt; compiling formseditBundle.m3
&gt;  -&gt; linking formsedit
&gt; /home/i8fs1/VERIF/usr/old/bin/ld: cannot find -lXaw
&gt; collect2: ld returned 1 exit status
    </pre>

    <p>
      <b>Solution:</b>
      Usually it is possible to install the missing libraries without
      much effort.
    </p>

    <h4><a name="p_1_2">1.2 Filenames with spaces</a></h4>

    <p>
      <b>Platforms:</b> all, especially WIN32
    </p>

    <p>
      <b>Description:</b>
      CM3 currently cannot handle filenames containing spaces very
      well. This will probably not be an issue on POSIX platforms, but
      it is very annoying on WIN32, as many standard installation path
      names contain spaces there.
    </p>

    <p>
      The problem cannot be easily resolved. This is due to the broken
      process creation interface on WIN32 platforms, which does not
      allow transparent passing of parameters, and some standard
      <tt>quake</tt> functions, which have to be replaced by more
      general equivalents, like <tt>exec, arglist</tt> (probably more).
    </p>

    <p>
      <b>Solution:</b>
      There is no easy solution to this problem. As a temporary
      work-around, the installer has been modified to replace pathnames
      with spaces by their 8.3 style equivalent on WIN32. If you
      cannot avoid using spaces in your CM3 projects, the 8.3 style
      short form should be a possible though ugly work-around for that,
      too. Voluntary contributions in this area are more than welcome.
      This work-around is incorporated in all installation programs
      since release 5.1.1.
    </p>

    <h4><a name="p_6_2">
      1.3 Unresolved X11 libraries on NetBSD</a>
    </h4>
    <p>
      <b>Platforms:</b> NetBSD
    </p>

    <p>
    <b>Description:</b> Running Modula3 programs, and hence building cm3, fails due to unresolved symbols to X11 libraries. Example error message: <i>Shared object &quot;libXaw.so.7&quot; not found</i>
    </p>

    <p>
    <b>Solution:</b> Add the <tt>/usr/X11R6/lib</tt> directory
    to <tt>/etc/ld.so.conf</tt>.
    </p>

    <!--
    <h4></h4>

    <p>
      <b>Platforms:</b> all
    </p>

    <p>
      <b>Description:</b>
    </p>

    <p>
      <b>Solution:</b>
    </p>
    -->

    <hr>
    <address><a href="mailto:m3-support{at}elego.de">m3-support{at}elego.de</a></address>
<!-- Created: Fri Mar  2 10:51:41 MET 2001 -->
  </body>
</html>