[Q] 'require during byte-compilation
24 years, 3 months
Didier Verna
Didier Verna
It seems that a (require 'something) line in a file is executed during
byte-compilation. That seems wrong to me, since if that is really what you
want, you can 'eval-and-compile it.
Is it a bug or am I missing something ?
--
/ / _ _ Didier Verna http://www.inf.enst.fr/~verna/
- / / - / / /_/ / EPITA / LRDE mailto:didier＠lrde.epita.fr
/_/ / /_/ / /__ / 14-16 rue Voltaire Tel. +33 (1) 53 14 59 47
94276 Kremlin-Bicê…
[View More]tre cedex Fax. +33 (1) 44 08 01 99
[View Less]
- 4 participants
- 6 comments
add ansi-color.el to XEmacs?
24 years, 3 months
Alex Schroeder
Alex Schroeder
Hi XEmacs Team,
Maybe you want to add ansi-color.el to XEmacs? It is already part of
Emacs.
Alex.
;;; ansi-color.el --- translate ANSI escape sequences into faces
;; Copyright (C) 1999, 2000 Free Software Foundation, Inc.
;; Author: Alex Schroeder <alex(a)gnu.org>
;; Maintainer: Alex Schroeder <alex(a)gnu.org>
;; Version: 3.4.0
;; Keywords: comm processes
;; This file is part of GNU Emacs.
;; GNU Emacs is free software; you can redistribute it and/or modify it
;; under the …
[View More]terms of the GNU General Public License as published by the
;; Free Software Foundation; either version 2, or (at your option) any
;; later version.
;;
;; GNU Emacs is distributed in the hope that it will be useful, but
;; WITHOUT ANY WARRANTY; without even the implied warranty of
;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
;; General Public License for more details.
;;
;; You should have received a copy of the GNU General Public License
;; along with GNU Emacs; see the file COPYING. If not, write to the
;; Free Software Foundation, Inc., 59 Temple Place - Suite 330,
;; Boston, MA 02111-1307, USA.
;;; Commentary:
;; This file provides a function that takes a string or a region
;; containing Select Graphic Rendition (SGR) control sequences (formerly
;; known as ANSI escape sequences) and tries to translate these into
;; faces.
;;
;; This allows you to run ls --color=yes in shell-mode. In order to
;; test this, proceed as follows:
;;
;; 1. start a shell: M-x shell
;; 2. load this file: M-x load-library RET ansi-color RET
;; 3. activate ansi-color: M-x ansi-color-for-comint-mode-on
;; 4. test ls --color=yes in the *shell* buffer
;;
;; Note that starting your shell from within Emacs might set the TERM
;; environment variable. The new setting might disable the output of
;; SGR control sequences. Using ls --color=yes forces ls to produce
;; these.
;;
;; If you decide you like this, add the following to your .emacs file:
;;
;; (autoload 'ansi-color-for-comint-mode-on "ansi-color" nil t)
;; (add-hook 'shell-mode-hook 'ansi-color-for-comint-mode-on)
;;
;; SGR control sequences are defined in section 3.8.117 of the ECMA-48
;; standard (identical to ISO/IEC 6429), which is freely available as a
;; PDF file <URL:http://www.ecma.ch/ecma1/STAND/ECMA-048.HTM>. The
;; "Graphic Rendition Combination Mode (GRCM)" implemented is
;; "cumulative mode" as defined in section 7.2.8. Cumulative mode means
;; that whenever possible, SGR control sequences are combined (ie. blue
;; and bold).
;; The basic functions are:
;;
;; `ansi-color-apply' to colorize a string containing SGR control
;; sequences.
;;
;; `ansi-color-filter-apply' to filter SGR control sequences from a
;; string.
;;
;; `ansi-color-apply-on-region' to colorize a region containing SGR
;; control sequences.
;;
;; `ansi-color-filter-region' to filter SGR control sequences from a
;; region.
;;; Thanks
;; Georges Brun-Cottan <gbruncot(a)emc.com> for improving ansi-color.el
;; substantially by adding the code needed to cope with arbitrary chunks
;; of output and the filter functions.
;;
;; Markus Kuhn <Markus.Kuhn(a)cl.cam.ac.uk> for pointing me to ECMA-48.
;;
;; Stefan Monnier <foo(a)acm.com> explaing obscure font-lock stuff and
;; code suggestions.
;;; Code:
;; Customization
(defgroup ansi-colors nil
"Translating SGR control sequences to faces.
This translation effectively colorizes strings and regions based upon
SGR control sequences embedded in the text. SGR (Select Graphic
Rendition) control sequences are defined in section 3.8.117 of the
ECMA-48 standard \(identical to ISO/IEC 6429), which is freely available
as a PDF file <URL:http://www.ecma.ch/ecma1/STAND/ECMA-048.HTM>."
:version "20.7"
:group 'processes)
(defcustom ansi-color-faces-vector
[default bold default italic underline bold bold-italic modeline]
"Faces used for SGR control sequences determining a face.
This vector holds the faces used for SGR control sequence parameters 0
to 7.
Parameter Description Face used by default
0 default default
1 bold bold
2 faint default
3 italic italic
4 underlined underline
5 slowly blinking bold
6 rapidly blinking bold-italic
7 negative image modeline
Note that the symbol `default' is special: It will not be combined
with the current face.
This vector is used by `ansi-color-make-color-map' to create a color
map. This color map is stored in the variable `ansi-color-map'."
:type '(vector face face face face face face face face)
:set 'ansi-color-map-update
:initialize 'custom-initialize-default
:group 'ansi-colors)
(defcustom ansi-color-names-vector
["black" "red" "green" "yellow" "blue" "magenta" "cyan" "white"]
"Colors used for SGR control sequences determining a color.
This vector holds the colors used for SGR control sequences parameters
30 to 37 \(foreground colors) and 40 to 47 (background colors).
Parameter Color
30 40 black
31 41 red
32 42 green
33 43 yellow
34 44 blue
35 45 magenta
36 46 cyan
37 47 white
This vector is used by `ansi-color-make-color-map' to create a color
map. This color map is stored in the variable `ansi-color-map'."
:type '(vector string string string string string string string string)
:set 'ansi-color-map-update
:initialize 'custom-initialize-default
:group 'ansi-colors)
(defconst ansi-color-regexp "\033\\[\\([0-9;]*\\)m"
"Regexp that matches SGR control sequences.")
(defconst ansi-color-parameter-regexp "\\([0-9]*\\)[m;]"
"Regexp that matches SGR control sequence parameters.")
;; Convenience functions for comint modes (eg. shell-mode)
(defcustom ansi-color-for-comint-mode nil
"Determines what to do with comint output.
If nil, do nothing.
If the symbol `filter', then filter all SGR control sequences.
If anything else (such as t), then translate SGR control sequences
into text-properties.
In order for this to have any effect, `ansi-color-process-output' must
be in `comint-output-filter-functions'.
This can be used to enable colorized ls --color=yes output
in shell buffers. You set this variable by calling one of:
\\[ansi-color-for-comint-mode-on]
\\[ansi-color-for-comint-mode-off]
\\[ansi-color-for-comint-mode-filter]"
:version "20.8"
:type '(choice (const :tag "Do nothing" nil)
(const :tag "Filter" filter)
(const :tag "Translate" t))
:group 'ansi-colors)
(defun ansi-color-for-comint-mode-on ()
"Set `ansi-color-for-comint-mode' to t."
(interactive)
(setq ansi-color-for-comint-mode t))
(defun ansi-color-for-comint-mode-off ()
"Set `ansi-color-for-comint-mode' to nil."
(interactive)
(setq ansi-color-for-comint-mode nil))
(defun ansi-color-for-comint-mode-filter ()
"Set `ansi-color-for-comint-mode' to symbol `filter'."
(interactive)
(setq ansi-color-for-comint-mode 'filter))
(defun ansi-color-process-output (string)
"Maybe translate SGR control sequences of comint output into text-properties.
Depending on variable `ansi-color-for-comint-mode' the comint output is
either not processed, SGR control sequences are filtered using
`ansi-color-filter-region', or SGR control sequences are translated into
text-properties using `ansi-color-apply-on-region'.
The comint output is assumed to lie between the marker
`comint-last-output-start' and the process-mark.
This is a good function to put in `comint-output-filter-functions'."
(let ((start-marker (or comint-last-output-start
(point-min-marker)))
(end-marker (process-mark (get-buffer-process (current-buffer)))))
(cond ((eq ansi-color-for-comint-mode nil))
((eq ansi-color-for-comint-mode 'filter)
(ansi-color-filter-region start-marker end-marker))
(t
(ansi-color-apply-on-region start-marker end-marker)))))
(add-hook 'comint-output-filter-functions
'ansi-color-process-output)
;; Alternative font-lock-unfontify-region-function
(eval-when-compile
;; We use this to preserve or protect things when modifying text
;; properties. Stolen from lazy-lock and font-lock. Ugly!!!
;; Probably most of this is not needed?
(defmacro save-buffer-state (varlist &rest body)
"Bind variables according to VARLIST and eval BODY restoring buffer state."
(` (let* ((,＠ (append varlist
'((modified (buffer-modified-p)) (buffer-undo-list t)
(inhibit-read-only t) (inhibit-point-motion-hooks t)
before-change-functions after-change-functions
deactivate-mark buffer-file-name buffer-file-truename))))
(,＠ body)
(when (and (not modified) (buffer-modified-p))
(set-buffer-modified-p nil)))))
(put 'save-buffer-state 'lisp-indent-function 1))
(defun ansi-color-unfontify-region (beg end &rest xemacs-stuff)
"Replacement function for `font-lock-default-unfontify-region'.
When font-lock is active in a buffer, you cannot simply add face
text-properties to the buffer. Font-lock will remove the face
text-property using `font-lock-unfontify-region-function'. If you want
to insert the strings returned by `ansi-color-apply' into such buffers,
you must set `font-lock-unfontify-region-function' to
`ansi-color-unfontify-region'. This function will not remove all face
text-properties unconditionally. It will keep the face text-properties
if the property `ansi-color' is set.
The region from BEG to END is unfontified. XEMACS-STUFF is ignored.
A possible way to install this would be:
\(add-hook 'font-lock-mode-hook
\(function (lambda ()
\(setq font-lock-unfontify-region-function
'ansi-color-unfontify-region))))"
;; save-buffer-state is a macro in font-lock.el!
(save-buffer-state nil
(when (boundp 'font-lock-syntactic-keywords)
(remove-text-properties beg end '(syntax-table nil)))
;; instead of just using (remove-text-properties beg end '(face
;; nil)), we find regions with a non-nil face test-property, skip
;; positions with the ansi-color property set, and remove the
;; remaining face test-properties.
(while (setq beg (text-property-not-all beg end 'face nil))
(setq beg (or (text-property-not-all beg end 'ansi-color t) end))
(when (get-text-property beg 'face)
(let ((end-face (or (text-property-any beg end 'face nil)
end)))
(remove-text-properties beg end-face '(face nil))
(setq beg end-face))))))
;; Working with strings
(defvar ansi-color-context nil
"Context saved between two calls to `ansi-color-apply'.
This is a list of the form (FACES FRAGMENT) or nil. FACES is a list of
faces the last call to `ansi-color-apply' ended with, and FRAGMENT is a
string starting with an escape sequence, possibly the start of a new
escape sequence.")
(make-variable-buffer-local 'ansi-color-context)
(defun ansi-color-filter-apply (string)
"Filter out all SGR control sequences from STRING.
Every call to this function will set and use the buffer-local variable
`ansi-color-context' to save partial escape sequences. This information
will be used for the next call to `ansi-color-apply'. Set
`ansi-color-context' to nil if you don't want this.
This function can be added to `comint-preoutput-filter-functions'."
(let ((start 0) end result)
;; if context was saved and is a string, prepend it
(if (cadr ansi-color-context)
(setq string (concat (cadr ansi-color-context) string)
ansi-color-context nil))
;; find the next escape sequence
(while (setq end (string-match ansi-color-regexp string start))
(setq result (concat result (substring string start end))
start (match-end 0)))
;; save context, add the remainder of the string to the result
(let (fragment)
(if (string-match "\033" string start)
(let ((pos (match-beginning 0)))
(setq fragment (substring string pos)
result (concat result (substring string start pos))))
(setq result (concat result (substring string start))))
(if fragment
(setq ansi-color-context (list nil fragment))
(setq ansi-color-context nil)))
result))
(defun ansi-color-apply (string)
"Translates SGR control sequences into text-properties.
Applies SGR control sequences setting foreground and background colors
to STRING using text-properties and returns the result. The colors used
are given in `ansi-color-faces-vector' and `ansi-color-names-vector'.
See function `ansi-color-apply-sequence' for details.
Every call to this function will set and use the buffer-local variable
`ansi-color-context' to save partial escape sequences and current face.
This information will be used for the next call to `ansi-color-apply'.
Set `ansi-color-context' to nil if you don't want this.
This function can be added to `comint-preoutput-filter-functions'.
You cannot insert the strings returned into buffers using font-lock.
See `ansi-color-unfontify-region' for a way around this."
(let ((face (car ansi-color-context))
(start 0) end escape-sequence result)
;; if context was saved and is a string, prepend it
(if (cadr ansi-color-context)
(setq string (concat (cadr ansi-color-context) string)
ansi-color-context nil))
;; find the next escape sequence
(while (setq end (string-match ansi-color-regexp string start))
;; store escape sequence
(setq escape-sequence (match-string 1 string))
;; colorize the old block from start to end using old face
(when face
(put-text-property start end 'ansi-color t string)
(put-text-property start end 'face face string))
(setq result (concat result (substring string start end))
start (match-end 0))
;; create new face by applying all the parameters in the escape
;; sequence
(setq face (ansi-color-apply-sequence escape-sequence face)))
;; if the rest of the string should have a face, put it there
(when face
(put-text-property start (length string) 'ansi-color t string)
(put-text-property start (length string) 'face face string))
;; save context, add the remainder of the string to the result
(let (fragment)
(if (string-match "\033" string start)
(let ((pos (match-beginning 0)))
(setq fragment (substring string pos)
result (concat result (substring string start pos))))
(setq result (concat result (substring string start))))
(if (or face fragment)
(setq ansi-color-context (list face fragment))
(setq ansi-color-context nil)))
result))
;; Working with regions
(defvar ansi-color-context-region nil
"Context saved between two calls to `ansi-color-apply-on-region'.
This is a list of the form (FACES MARKER) or nil. FACES is a list of
faces the last call to `ansi-color-apply-on-region' ended with, and
MARKER is a buffer position within an escape sequence or the last
position processed.")
(make-variable-buffer-local 'ansi-color-context-region)
(defun ansi-color-filter-region (begin end)
"Filter out all SGR control sequences from region BEGIN to END.
Every call to this function will set and use the buffer-local variable
`ansi-color-context-region' to save position. This information will be
used for the next call to `ansi-color-apply-on-region'. Specifically,
it will override BEGIN, the start of the region. Set
`ansi-color-context-region' to nil if you don't want this."
(let ((end-marker (copy-marker end))
(start (or (cadr ansi-color-context-region) begin)))
(save-excursion
(goto-char start)
;; find the next escape sequence
(while (re-search-forward ansi-color-regexp end-marker t)
;; delete the escape sequence
(replace-match ""))
;; save context, add the remainder of the string to the result
(if (re-search-forward "\033" end-marker t)
(setq ansi-color-context-region (list nil (match-beginning 0)))
(setq ansi-color-context-region nil)))))
(defun ansi-color-apply-on-region (begin end)
"Translates SGR control sequences into overlays or extents.
Applies SGR control sequences setting foreground and background colors
to text in region between BEGIN and END using extents or overlays.
Emacs will use overlays, XEmacs will use extents. The colors used are
given in `ansi-color-faces-vector' and `ansi-color-names-vector'. See
function `ansi-color-apply-sequence' for details.
Every call to this function will set and use the buffer-local variable
`ansi-color-context-region' to save position and current face. This
information will be used for the next call to
`ansi-color-apply-on-region'. Specifically, it will override BEGIN, the
start of the region and set the face with which to start. Set
`ansi-color-context-region' to nil if you don't want this."
(let ((face (car ansi-color-context-region))
(start-marker (or (cadr ansi-color-context-region)
(copy-marker begin)))
(end-marker (copy-marker end))
escape-sequence)
(save-excursion
(goto-char start-marker)
;; find the next escape sequence
(while (re-search-forward ansi-color-regexp end-marker t)
;; colorize the old block from start to end using old face
(when face
(ansi-color-set-extent-face
(ansi-color-make-extent start-marker (match-beginning 0))
face))
;; store escape sequence and new start position
(setq escape-sequence (match-string 1)
start-marker (copy-marker (match-end 0)))
;; delete the escape sequence
(replace-match "")
;; create new face by applying all the parameters in the escape
;; sequence
(setq face (ansi-color-apply-sequence escape-sequence face)))
;; search for the possible start of a new escape sequence
(if (re-search-forward "\033" end-marker t)
(progn
;; if the rest of the region should have a face, put it there
(when face
(ansi-color-set-extent-face
(ansi-color-make-extent start-marker (point))
face))
;; save face and point
(setq ansi-color-context-region
(list face (copy-marker (match-beginning 0)))))
;; if the rest of the region should have a face, put it there
(if face
(progn
(ansi-color-set-extent-face
(ansi-color-make-extent start-marker end-marker)
face)
(setq ansi-color-context-region (list face)))
;; reset context
(setq ansi-color-context-region nil))))))
;; This function helps you look for overlapping overlays. This is
;; usefull in comint-buffers. Overlapping overlays should not happen!
;; A possible cause for bugs are the markers. If you create an overlay
;; up to the end of the region, then that end might coincide with the
;; process-mark. As text is added BEFORE the process-mark, the overlay
;; will keep growing. Therefore, as more overlays are created later on,
;; there will be TWO OR MORE overlays covering the buffer at that point.
;; This function helps you check your buffer for these situations.
; (defun ansi-color-debug-overlays ()
; (interactive)
; (let ((pos (point-min)))
; (while (< pos (point-max))
; (if (<= 2 (length (overlays-at pos)))
; (progn
; (goto-char pos)
; (error "%d overlays at %d" (length (overlays-at pos)) pos))
; (let (message-log-max)
; (message "Reached %d." pos)))
; (setq pos (next-overlay-change pos)))))
;; Emacs/XEmacs compatibility layer
(defun ansi-color-make-face (property color)
"Return a face with PROPERTY set to COLOR.
PROPERTY can be either symbol `foreground' or symbol `background'.
For Emacs, we just return the cons cell \(PROPERTY . COLOR).
For XEmacs, we create a temporary face and return it."
(if (featurep 'xemacs)
(let ((face (make-face (intern (concat color "-" (symbol-name property)))
"Temporary face created by ansi-color."
t)))
(set-face-property face property color)
face)
(cond ((eq property 'foreground)
(cons 'foreground-color color))
((eq property 'background)
(cons 'background-color color))
(t
(cons property color)))))
(defun ansi-color-make-extent (from to &optional object)
"Make an extent for the range [FROM, TO) in OBJECT.
OBJECT defaults to the current buffer. XEmacs uses `make-extent', Emacs
uses `make-overlay'. XEmacs can use a buffer or a string for OBJECT,
Emacs requires OBJECT to be a buffer."
(if (functionp 'make-extent)
(make-extent from to object)
;; In Emacs, the overlay might end at the process-mark in comint
;; buffers. In that case, new text will be inserted before the
;; process-mark, ie. inside the overlay (using insert-before-marks).
;; In order to avoid this, we use the `insert-behind-hooks' overlay
;; property to make sure it works.
(let ((overlay (make-overlay from to object)))
(overlay-put overlay 'modification-hooks '(ansi-color-freeze-overlay))
overlay)))
(defun ansi-color-freeze-overlay (overlay is-after begin end &optional len)
"Prevent OVERLAY from being extended.
This function can be used for the `modification-hooks' overlay
property."
;; if stuff was inserted at the end of the overlay
(when (and is-after
(= 0 len)
(= end (overlay-end overlay)))
;; reset the end of the overlay
(move-overlay overlay (overlay-start overlay) begin)))
(defun ansi-color-set-extent-face (extent face)
"Set the `face' property of EXTENT to FACE.
XEmacs uses `set-extent-face', Emacs uses `overlay-put'."
(if (functionp 'set-extent-face)
(set-extent-face extent face)
(overlay-put extent 'face face)))
;; Helper functions
(defun ansi-color-apply-sequence (escape-sequence faces)
"Apply ESCAPE-SEQ to FACES and return the new list of faces.
ESCAPE-SEQ is an escape sequences parsed by `ansi-color-get-face'.
If the new faces start with the symbol `default', then the new
faces are returned. If the faces start with something else,
they are appended to the front of the FACES list, and the new
list of faces is returned.
If `ansi-color-get-face' returns nil, then we either got a
null-sequence, or we stumbled upon some garbage. In either
case we return nil."
(let ((new-faces (ansi-color-get-face escape-sequence)))
(cond ((null new-faces)
nil)
((eq (car new-faces) 'default)
(cdr new-faces))
(t
(append new-faces face)))))
(defun ansi-color-make-color-map ()
"Creates a vector of face definitions and returns it.
The index into the vector is an ANSI code. See the documentation of
`ansi-color-map' for an example.
The face definitions are based upon the variables
`ansi-color-faces-vector' and `ansi-color-names-vector'."
(let ((ansi-color-map (make-vector 50 nil))
(index 0))
;; miscellaneous attributes
(mapcar
(function (lambda (e)
(aset ansi-color-map index e)
(setq index (1+ index)) ))
ansi-color-faces-vector)
;; foreground attributes
(setq index 30)
(mapcar
(function (lambda (e)
(aset ansi-color-map index
(ansi-color-make-face 'foreground e))
(setq index (1+ index)) ))
ansi-color-names-vector)
;; background attributes
(setq index 40)
(mapcar
(function (lambda (e)
(aset ansi-color-map index
(ansi-color-make-face 'background e))
(setq index (1+ index)) ))
ansi-color-names-vector)
ansi-color-map))
(defvar ansi-color-map (ansi-color-make-color-map)
"A brand new color map suitable for `ansi-color-get-face'.
The value of this variable is usually constructed by
`ansi-color-make-color-map'. The values in the array are such that the
numbers included in an SGR control sequences point to the correct
foreground or background colors.
Example: The sequence \033[34m specifies a blue foreground. Therefore:
(aref ansi-color-map 34)
=> \(foreground-color . \"blue\")")
(defun ansi-color-map-update (symbol value)
"Update `ansi-color-map'.
Whenever the vectors used to construct `ansi-color-map' are changed,
this function is called. Therefore this function is listed as the :set
property of `ansi-color-faces-vector' and `ansi-color-names-vector'."
(set-default symbol value)
(setq ansi-color-map (ansi-color-make-color-map)))
(defun ansi-color-get-face-1 (ansi-code)
"Get face definition from `ansi-color-map'.
ANSI-CODE is used as an index into the vector."
(condition-case nil
(aref ansi-color-map ansi-code)
('args-out-of-range nil)))
(defun ansi-color-get-face (escape-seq)
"Create a new face by applying all the parameters in ESCAPE-SEQ.
Should any of the parameters result in the default face (usually this is
the parameter 0), then the effect of all previous parameters is cancelled.
ESCAPE-SEQ is a SGR control sequences such as \\033[34m. The parameter
34 is used by `ansi-color-get-face-1' to return a face definition."
(let ((ansi-color-r "[0-9][0-9]?")
(i 0)
f val)
(while (string-match ansi-color-r escape-seq i)
(setq i (match-end 0)
val (ansi-color-get-face-1
(string-to-int (match-string 0 escape-seq) 10)))
(cond ((not val))
((eq val 'default)
(setq f (list val)))
(t
(add-to-list 'f val))))
f))
(provide 'ansi-color)
;;; ansi-color.el ends here
[View Less]
- 3 participants
- 2 comments
[Success] XEmacs 21.2-b40 "Persephone", i586-pc-win32
24 years, 3 months
Adrian Aichner
Adrian Aichner
builds fine from latest, post b40, CVS.
make check
and
make check-temacs
both cause a crash when clearcase.el is required and ClearCase is not
online.
See
*** Error
below.
Best regards,
Adrian
> XEmacs Build Report generated by emacs-version
> 21.1 (patch 12) "Channel Islands" XEmacs Lucid
> with system-configuration
> i386-pc-win32
> follows:
> Contents of d:\tmp\21.2\xemacs\Installation:
> (Output from most recent run of ./configure)
OS: Windows_NT
XEmacs 21.2-b40 …
[View More]\"Persephone\" configured for `i586-pc-win32'.
Building XEmacs in \"d:\\tmp\\21.2\\xemacs\\nt\".
Using compiler \"cl -nologo -W3 -O2 -G5 -MD\".
Installing XEmacs in \"c:\\XEmacs\\XEmacs-21.2-b40\".
Package path is \"~\\.xemacs;;c:\\XEmacs\\site-packages;c:\\XEmacs\\xemacs-packages\".
Compiling in support for Microsoft Windows native GUI.
Compiling in support for XPM images.
Compiling in support for GIF images.
Compiling in support for PNG images.
Compiling in support for TIFF images.
Compiling in support for JPEG images.
Compiling in support for X-Face message headers.
Compiling in support for toolbars.
Compiling in support for dialogs.
Compiling in support for widgets.
Compiling in support for native sounds.
Compiling in fast dired implementation.
Using minimal tagbits.
Using indexed lrecord implementation.
Using portable dumper.
Using system malloc.
Using DLL version of C runtime library
> Contents of d:\tmp\21.2\xemacs\nt\xemacs-make-install.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+"
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:"
cd d:\tmp\21.2\xemacs\nt\
nmake /f xemacs.mak INSTALL_DIR="c:\XEmacs\XEmacs-$(XEMACS_VERSION_STRING)" JPEG_DIR="d:\tmp\libs4xemacs\jpeg-6b" MAKEINFO="d:\tmp\texinfo-4.0\makeinfo\makeinfo.exe" PACKAGE_PREFIX="c:\XEmacs" PNG_DIR="d:\tmp\libs4xemacs\libpng-1.0.2" TIFF_DIR="d:\tmp\libs4xemacs\tiff-v3.4" USE_PORTABLE_DUMPER="1" XPM_DIR="d:\tmp\libs4xemacs\xpm-3.4k" ZLIB_DIR="d:\tmp\libs4xemacs\zlib" install
Compilation started at Tue Jan 09 23:02:33 2001
WARNING: Compiling without dependency information.
Installing XEmacs in \"c:\\XEmacs\\XEmacs-21.2-b40\".
1 file(s) copied.
1 file(s) copied.
1 file(s) copied.
d:\tmp\21.2\xemacs\nt\..\src\nt.c(1424) : warning C4244: '=' : conversion from 'unsigned long ' to 'short ', possible loss of data
d:\tmp\21.2\xemacs\nt\..\src\nt.c(1435) : warning C4244: '=' : conversion from 'unsigned long ' to 'unsigned short ', possible loss of data
d:\tmp\21.2\xemacs\nt\..\src\nt.c(1437) : warning C4244: '=' : conversion from 'unsigned long ' to 'unsigned short ', possible loss of data
d:\tmp\21.2\xemacs\nt\..\src\search.c(1558) : warning C4244: '=' : conversion from 'long ' to 'unsigned char ', possible loss of data
d:\tmp\21.2\xemacs\nt\..\src\search.c(1643) : warning C4244: '=' : conversion from 'long ' to 'unsigned char ', possible loss of data
WARNING: Compiling without dependency information.
Using load-path (d:\tmp\21.2\xemacs\lisp)
Using module-load-path (d:\tmp\21.2\xemacs\modules)
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\code-cmds.el:
** the function coding-system-category is not known to be defined.
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\coding.el:
** The following functions are not known to be defined:
set-console-tty-input-coding-system,
set-console-tty-output-coding-system
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\toolbar-items.el:
** The following functions are not known to be defined:
pending-delete-pre-hook, x-init-specifier-from-resources
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\dragdrop.el:
** the function mime/viewer-mode is not known to be defined.
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\scrollbar.el:
** the function x-init-scrollbar-from-resources is not known to be defined.
While compiling mouse-consolidated-yank in file d:\tmp\21.2\xemacs\lisp\mouse.el:
** reference to free variable gpm-minor-mode
While compiling the end of the data:
** the function x-store-cutbuffer is not known to be defined.
While compiling find-space-insertable-point in file d:\tmp\21.2\xemacs\lisp\fill.el:
** reference to free variable space-insertable
While compiling the end of the data:
** The following functions are not known to be defined:
kinsoku-process-extend, kinsoku-process
While compiling isearch-help-or-delete-char in file d:\tmp\21.2\xemacs\lisp\isearch-mode.el:
** reference to free variable tty-erase-char
While compiling the end of the data:
** the function x-keysym-on-keyboard-sans-modifiers-p is not known to be defined.
While compiling read-library-internal in file d:\tmp\21.2\xemacs\lisp\lib-complete.el:
** reference to free variable read-library-internal-search-path
While compiling read-library-name:
** variable read-library-internal-search-path bound but not referenced
While compiling set-visited-file-name in file d:\tmp\21.2\xemacs\lisp\files.el:
** reference to free variable vc-mode
While compiling find-backup-file-name:
** variable bv-length bound but not referenced
While compiling save-some-buffers-1:
** assignment to free variable view-exit-action
While compiling the end of the data:
** The following functions are not known to be defined:
vc-after-save, dired-get-filename, dired-expunge-deletions,
ange-ftp-ftp-path
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\help.el:
** the function compiled-function-annotation is not known to be defined.
While compiling command-line-early in file d:\tmp\21.2\xemacs\lisp\startup.el:
** init-file-user is an obsolete variable; use load-user-init-file-p instead.
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\modeline.el:
** the function vc-toggle-read-only is not known to be defined.
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\minibuf.el:
** The following functions are not known to be defined:
ange-ftp-ftp-path, user-name-all-completions,
user-name-completion-1, tty-color-list
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\simple.el:
** The following functions are not known to be defined:
x-keysym-on-keyboard-sans-modifiers-p, kinsoku-process
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\frame.el:
** the function console-tty-controlling-process is not known to be defined.
While compiling set-face-stipple in file d:\tmp\21.2\xemacs\lisp\faces.el:
** reference to free variable x-bitmap-file-path
While compiling the end of the data:
** The following functions are not known to be defined:
x-init-face-from-resources, x-init-device-faces,
x-init-frame-faces, x-init-global-faces
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\console.el:
** the function console-tty-controlling-process is not known to be defined.
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\syntax.el:
** The following functions are not known to be defined:
charset-name, char-charset
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\custom.el:
** the function custom-theme-reset-internal-face is not known to be defined.
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\cl-extra.el:
** The following functions are not known to be defined:
overlay-lists, overlay-start, overlay-end, overlays-at,
next-overlay-change
Using load-path (d:\tmp\21.2\xemacs\lisp)
Using module-load-path (d:\tmp\21.2\xemacs\modules)
Note: Strange doc (not fboundp) for function user-name-completion-1 ＠ 610617
Note: Strange doc (not fboundp) for function user-name-all-completions ＠ 610941
While compiling toplevel forms in file d:\tmp\21.2\xemacs\lisp\apropos.el:
** reference to free variable font-lock-keyword-face
** reference to free variable font-lock-string-face
** reference to free variable font-lock-comment-face
** reference to free variable font-lock-variable-name-face
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\font-lock.el:
** The following functions are not known to be defined:
fast-lock-after-fontify-buffer, lazy-lock-after-fontify-buffer
While compiling toplevel forms in file d:\tmp\21.2\xemacs\lisp\font.el:
** reference to free variable global-face-data
While compiling font-properties-from-style:
** variable style bound but not referenced
While compiling toplevel forms:
** reference to free variable x-font-regexp
** variable weight bound but not referenced
** variable slant bound but not referenced
While compiling x-font-create-object:
** reference to free variable x-font-regexp-foundry-and-family
** variable style bound but not referenced
While compiling x-font-create-name:
** variable style bound but not referenced
While compiling ns-font-create-name:
** variable registry bound but not referenced
** variable encoding bound but not referenced
While compiling mswindows-font-create-name:
** variable style bound but not referenced
While compiling font-update-device-fonts:
** variable font bound but not referenced
While compiling font-update-one-face:
** variable font bound but not referenced
While compiling the end of the data:
** The following functions are not known to be defined:
x-list-fonts, mswindows-list-fonts, ns-list-fonts, internal-facep,
fontsetp, get-font-info, get-fontset-info,
mswindows-define-rgb-color, cancel-function-timers
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\gpm.el:
** The following functions are not known to be defined:
gpm-enable, console-tty-terminal-type
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\ldap.el:
** The following functions are not known to be defined: ldapp,
ldap-open, ldap-close, ldap-add, ldap-modify, ldap-delete
While compiling lm-report-bug in file d:\tmp\21.2\xemacs\lisp\lisp-mnt.el:
** reference to free variable report-emacs-bug-beta-address
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\msw-font-menu.el:
** the function charset-registry is not known to be defined.
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\multicast.el:
** the function open-multicast-group-internal is not known to be defined.
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\mwheel.el:
** The following functions are not known to be defined:
event-basic-type, posn-window, event-start, mwheel-event-window,
mwheel-event-button
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\package-get.el:
** the function mc-pgp-verify-region is not known to be defined.
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\symbols.el:
** the function set-magic-variable-handler is not known to be defined.
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\tty-init.el:
** The following functions are not known to be defined:
register-tty-color, init-mule-tty-win
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\wid-browse.el:
** the function pp-to-string is not known to be defined.
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\x-faces.el:
** The following functions are not known to be defined:
x-get-resource-and-maybe-bogosity-check, x-get-resource,
x-init-pointer-shape
While compiling x-reset-device-font-menus in file d:\tmp\21.2\xemacs\lisp\x-font-menu.el:
** reference to free variable x-font-regexp
** reference to free variable x-font-regexp-foundry-and-family
** reference to free variable x-font-regexp-spacing
While compiling the end of the data:
** the function charset-registry is not known to be defined.
While compiling init-x-win in file d:\tmp\21.2\xemacs\lisp\x-init.el:
** assignment to free variable x-initial-argv-list
** reference to free variable x-initial-argv-list
While compiling the end of the data:
** The following functions are not known to be defined:
x-keysym-on-keyboard-p, x-server-vendor,
x-init-specifier-from-resources, init-mule-x-win
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\x-misc.el:
** the function x-get-resource is not known to be defined.
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\x-mouse.el:
** The following functions are not known to be defined:
x-store-cutbuffer, x-get-resource
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\x-scrollbar.el:
** The following functions are not known to be defined:
x-init-specifier-from-resources, x-get-resource
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\x-select.el:
** The following functions are not known to be defined:
x-get-cutbuffer-internal, x-rotate-cutbuffers-internal,
x-store-cutbuffer-internal
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\x-win-sun.el:
** the function x-keysym-on-keyboard-sans-modifiers-p is not known to be defined.
While compiling the end of the data in file d:\tmp\21.2\xemacs\lisp\x-win-xfree86.el:
** The following functions are not known to be defined:
x-keysym-on-keyboard-p, x-keysym-on-keyboard-sans-modifiers-p
Installing in c:\XEmacs\XEmacs-21.2-b40 ...
1 File(s) copied
1 File(s) copied
10 File(s) copied
1 file(s) copied.
1 file(s) copied.
1 file(s) copied.
423 File(s) copied
130 File(s) copied
464 File(s) copied
1 File(s) copied
1 File(s) copied
1 File(s) copied
Compilation finished at Tue Jan 09 23:22:09
> Contents of d:\tmp\21.2\xemacs\nt\xemacs-make-check-temacs.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+"
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:"
cd d:\tmp\21.2\xemacs\nt\
nmake /f xemacs.mak INSTALL_DIR="c:\XEmacs\XEmacs-$(XEMACS_VERSION_STRING)" JPEG_DIR="d:\tmp\libs4xemacs\jpeg-6b" MAKEINFO="d:\tmp\texinfo-4.0\makeinfo\makeinfo.exe" PACKAGE_PREFIX="c:\XEmacs" PNG_DIR="d:\tmp\libs4xemacs\libpng-1.0.2" TIFF_DIR="d:\tmp\libs4xemacs\tiff-v3.4" USE_PORTABLE_DUMPER="1" XPM_DIR="d:\tmp\libs4xemacs\xpm-3.4k" ZLIB_DIR="d:\tmp\libs4xemacs\zlib" check-temacs
Compilation started at Tue Jan 09 23:22:25 2001
WARNING: Compiling without dependency information.
Using load-path (d:\tmp\21.2\xemacs\lisp)
Using module-load-path (d:\tmp\21.2\xemacs\modules)
Note: Strange doc (not fboundp) for function user-name-completion-1 ＠ 610617
Note: Strange doc (not fboundp) for function user-name-all-completions ＠ 610941
base64-tests.el: 1232 of 1232 (100%) tests successful.
byte-compiler-tests.el: 102 of 102 (100%) tests successful.
c-tests.el: No tests run
case-tests.el: 1118 of 1118 (100%) tests successful.
ccl-tests.el: No tests run
database-tests.el: No tests run
hash-table-tests.el: 9866 of 9866 (100%) tests successful.
lisp-tests.el: 3572 of 3588 (99%) tests successful.
md5-tests.el: 56 of 56 (100%) tests successful.
mule-tests.el: 2 of 2 (100%) tests successful.
regexp-tests.el: 118 of 118 (100%) tests successful.
symbol-tests.el: 264 of 264 (100%) tests successful.
syntax-tests.el: 56 of 56 (100%) tests successful.
Fatal error.
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
If you have access to the PROBLEMS file that came with your
version of XEmacs, please check to see if your crash is described
there, as there may be a workaround available.
Otherwise, please report this bug by running the send-pr
script included with XEmacs, or selecting `Send Bug Report'
from the help menu.
As a last resort send ordinary email to `crashes(a)xemacs.org'.
*MAKE SURE* to include the information in the command
M-x describe-installation.
*** Error in XEmacs initialization
(invalid-operation "Cannot send signal to process" #<process "lsregion" pid 456 state:run>)
*** Backtrace
really-early-error-handler((invalid-operation "Cannot send signal to process" #<process "lsregion" pid 456 state:run>))
*** Killing XEmacs
> Contents of d:\tmp\21.2\xemacs\nt\xemacs-make-check.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+"
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:"
cd d:\tmp\21.2\xemacs\nt\
nmake /f xemacs.mak INSTALL_DIR="c:\XEmacs\XEmacs-$(XEMACS_VERSION_STRING)" JPEG_DIR="d:\tmp\libs4xemacs\jpeg-6b" MAKEINFO="d:\tmp\texinfo-4.0\makeinfo\makeinfo.exe" PACKAGE_PREFIX="c:\XEmacs" PNG_DIR="d:\tmp\libs4xemacs\libpng-1.0.2" TIFF_DIR="d:\tmp\libs4xemacs\tiff-v3.4" USE_PORTABLE_DUMPER="1" XPM_DIR="d:\tmp\libs4xemacs\xpm-3.4k" ZLIB_DIR="d:\tmp\libs4xemacs\zlib" check
Compilation started at Tue Jan 09 23:27:11 2001
WARNING: Compiling without dependency information.
base64-tests.el: 1232 of 1232 (100%) tests successful.
byte-compiler-tests.el: 102 of 102 (100%) tests successful.
c-tests.el: No tests run
case-tests.el: 1118 of 1118 (100%) tests successful.
ccl-tests.el: No tests run
database-tests.el: No tests run
hash-table-tests.el: 9866 of 9866 (100%) tests successful.
lisp-tests.el: 3572 of 3588 (99%) tests successful.
md5-tests.el: 56 of 56 (100%) tests successful.
mule-tests.el: 2 of 2 (100%) tests successful.
regexp-tests.el: 118 of 118 (100%) tests successful.
symbol-tests.el: 264 of 264 (100%) tests successful.
syntax-tests.el: 56 of 56 (100%) tests successful.
*** Error in XEmacs initialization
(invalid-operation "Cannot send signal to process" #<process "lsregion" pid 301 state:run>)
*** Backtrace
really-early-error-handler((invalid-operation "Cannot send signal to process" #<process "lsregion" pid 301 state:run>))
*** Killing XEmacs
--
Adrian Aichner <adrian(a)xemacs.org>
[View Less]
- 1 participants
- 0 comments
Re: Background pixmaps do not change properly
24 years, 3 months
Dmitry Yaitskov
Dmitry Yaitskov
"Kilian A. Foth" <foth(a)informatik.uni-hamburg.de> wrote:
> In XEmacs 21.2 (beta38) "Peisino,Ak(B" [Lucid]
> (sparc-sun-solaris2.8, Mule) of Fri Dec 29 2000 on nats21 configured
> using `configure --with-mule --with-xpm --with-site-lisp=yes
> --package-path=/opt/lib/xemacs-21.2-b38/'
>
> Please describe exactly what actions triggered the bug
> and the precise symptoms of the bug:
>
> Doing
>
> (set-face-background-pixmap 'default "/my/pretty/…
[View More]file1.jpeg")
>
> correctly sets the background pixmap the image in file1, but
> following up with
>
> (set-face-background-pixmap 'default "/my/pretty/file2.jpeg")
>
> displays the same image again, not the second one as under 21.1.
>
<snip>
I also have this problem, both with beta 38 and now beta 40. I am
using a cygwin XEmacs under w2k. FWIW, it also happens when using
customize-face.
--
Cheers,
-Dima.
[View Less]
- 1 participants
- 0 comments
Re: Anyone using b39 non-Solaris + SIGIO + widgets + Motif?
24 years, 3 months
Raymond Toy
Raymond Toy
>>>>> "Andy" == Andy Piper <andyp(a)bea.com> writes:
Andy> At 15:55 08/01/01 -0500, Raymond Toy wrote:
>>
>>
>> Would it help you if I built without Motif?
Andy> As a datapoint probably
Done. It works quite nicely without my having to wiggle the mouse
pointer around the window. I rather like it bettern than the Motif
version. (I like the growing bar instead of the moving slider
thingie.)
I guess it's a Motif problem. But …
[View More]I have a whacked out system here
with both X11R6.4 and openwin. I try to compile and link with just
openwin, but sometimes I forgot to set that all up. And my
LD_LIBRARY_PATH oftentimes points to X11R6.4 so xemacs gets that too.
Ray
[View Less]
- 1 participants
- 0 comments
RE: Problems building netinstall in 21.2.40 with missing header f iles .
24 years, 3 months
Andy Piper
Andy Piper
At 12:09 09/01/01 -0500, Bush, David wrote:
>Is the Mingw build of zlib available on line?
No idea. I have a personal version :)
andy
--------------------------------------------------------------
Dr Andy Piper
Principal Consultant, BEA Systems Ltd
- 1 participants
- 0 comments
RE: Problems building netinstall in 21.2.40 with missing header f iles .
24 years, 3 months
Bush, David
Bush, David
Is the Mingw build of zlib available on line?
> -----Original Message-----
> From: Andy Piper [mailto:andyp＠bea.com]
> Sent: Tuesday, January 09, 2001 11:20 AM
> To: Bush, David; xemacs-beta(a)xemacs.org
> Subject: Re: Problems building netinstall in 21.2.40 with
> missing header
> files .
>
>
> At 10:22 09/01/01 -0500, Bush, David wrote:
> >I downloaded and build 21.2.40 as the first 21.2 build on
> >this system. I had trouble in netinstall …
[View More]because four header
> >files were not visible in the Mingw build:
> >zconf.h
> >zlib.h
> >cygwin/version.h
> >sys/mount.h
>
> I have fixed these in my local version. You still need a
> mingw build of
> zlib for things to function correctly.
>
> >Is this because I failed to download a package necessary
> >for the Mingw build or is there a bug I should be hunting?
>
> Bug which is fixed.
>
> andy
> --------------------------------------------------------------
> Dr Andy Piper
> Principal Consultant, BEA Systems Ltd
>
[View Less]
- 1 participants
- 0 comments
Re: Problems building netinstall in 21.2.40 with missing header files .
24 years, 3 months
Andy Piper
Andy Piper
At 10:22 09/01/01 -0500, Bush, David wrote:
>I downloaded and build 21.2.40 as the first 21.2 build on
>this system. I had trouble in netinstall because four header
>files were not visible in the Mingw build:
>zconf.h
>zlib.h
>cygwin/version.h
>sys/mount.h
I have fixed these in my local version. You still need a mingw build of
zlib for things to function correctly.
>Is this because I failed to download a package necessary
>for the Mingw build or is there a bug I …
[View More]should be hunting?
Bug which is fixed.
andy
--------------------------------------------------------------
Dr Andy Piper
Principal Consultant, BEA Systems Ltd
[View Less]
- 1 participants
- 0 comments
outstanding issues
24 years, 3 months
John A. Turner
John A. Turner
I'm not sure what the schedule for a 21.2 release is, but I thought I'd
mention a couple of things that I see as outstanding issues - everything is
as of b36, possibly slightly more recent
they're pretty minor
o the dired customize prob reported here remains:
http://www.xemacs.org/list-archives/xemacs-beta/200002/msg00139.html
o I believe others have mentioned the problems with focus being lost
after pressing Done in a Customize buffer - oddly, the only thing I
could find in the …
[View More]archives was this msg from Kirill with a patch
ostensibly fixing the prob on win32 - but I still see the problem on
both Irix and win32 - I do use focus-follows-mouse
http://www.xemacs.org/list-archives/xemacs-beta/200001/msg00202.html
o the weirdness in Motif buttons, both in dialogs and in Customize buffers
- best report was this one, which has pics:
http://www.xemacs.org/list-archives/xemacs-beta/200010/msg00241.html
I have to admit that I've been working w/o gutters turned on recently -
maybe I should turn them back on and work them out a bit...
--
John A. Turner, Ph.D. Senior Research Associate
Blue Sky Studios, 44 S. Broadway, White Plains, NY 10601
http://www.blueskystudios.com/ (914) 259-6319
[View Less]
- 7 participants
- 18 comments
Problems building netinstall in 21.2.40 with missing header files .
24 years, 3 months
Bush, David
Bush, David
I downloaded and build 21.2.40 as the first 21.2 build on
this system. I had trouble in netinstall because four header
files were not visible in the Mingw build:
zconf.h
zlib.h
cygwin/version.h
sys/mount.h
Is this because I failed to download a package necessary
for the Mingw build or is there a bug I should be hunting?
thanks,
david
David Bush
Software Engineer
Dialogic, an Intel Company
Phone: (703) 633-3384
Fax: (703) 633-3319
mailto:David.Bush＠Dialogic.com
http://www.dialogic.com
- 1 participants
- 0 comments