Hello
I have big compilation project when I run the top make file
I have problem to find the errors that acres in the sub directories because the make file keeps
Running the compilation. is there any way to perform summry of the errors when the Top
makefile done running ?
thanks (2 Replies)
Hi,
I'm in the process of compiling gnu gettext on a rs/6000 43p-260 running AIX 5.1 in 64bit-mode. The compilation itself runs fine as I understand it, however the installation itself fails like so:
I'm pretty much clueless about this relink stuff, so if anyone has suggestions, I'll try... (0 Replies)
Hello every one,
while compiling c++ modules.
i am getting the following 2 errors.
1)
/root/cc/unix-ce/root/subsys/cb/cdbh/include/cdbh_TransferFileHeader.h:111: error: âulong_tâ does not name a type
/root/cc/unix-ce/root/subsys/cb/cdbh/include/cdbh_TransferFileHeader.h:118: error: âulong_tâ... (0 Replies)
Hello,
Trying to compile xtrlock from source on a RHEL system. It has an Imakefile but not being familiar enough with that system getting errors running imake:
#! Imakefile for xtrlock - X Transparent Lock
#!
#! Copyright (C)1993,1994 Ian Jackson
#!
#! This is free software; you can... (1 Reply)
Hi all,
I tried to cross compile Ghostscript-8.54 source. I am getting some errors during cross compilation. I have pasted the errors below.
CC=arm-unknown-linux-gnu-gcc LD=arm-unknown-linux-gnu-ld ./configure --host=i686-pc-linux-gnu --target=arm-unknown-linux-gnu --without-x && make
... (2 Replies)
Hello everyone. I'm new to the boards, I hope I can get and possibly give some help through these forums.
I need some help.
I have two CSV files, let's call them File A and File B.
This is the structure for File A:
ID, VAR1, VAR2, VAR3 - VAR50 (where the VAR 1-VAR50 are either 0 or 1)
... (1 Reply)
Hi all! I am new to this forum. I have recently installed Cygwin and XEmacs on my
laptop running Windows Vista. I am studing at the moment and the code I am creating is mainly for that purpose.
I am trying to create the algorithm of Insertion sort. When I compile my code in XEmacs i get some... (1 Reply)
Dear all,
I have a file lik below: n of row=420, n of letters in each row=100000 like below: there is no space between the letters.
what I want is: the 75000th letter to the 85000th letter in each row.
how to do that? thanks a lot!
... (2 Replies)
Hello Unix experts,
I need a help to create a subset file. I know with cut comand, its very easy to select many different columns, or threshold. But here I have a bit problem as in my data file is big. And I don't want to identify the column numbers or names manually. I am trying to find any... (7 Replies)
Hi All,
We are planning to migrate from Solaris to AIX, and we have a requirement to move all files modified in last 7 days to AIX.
i found many helpful forums on this site but somehow the issue was still not solved:
Used the following command from the directory which we want to scan
... (6 Replies)
Discussion started by: nikhil8
6 Replies
LEARN ABOUT DEBIAN
apsfilter-bug
APSFILTER-BUG(1) BSD General Commands Manual APSFILTER-BUG(1)NAME
apsfilter-bug -- create a half-automatic bug report for apsfilter
SYNOPSIS
apsfilter-bug
OPTIONS
none
DESCRIPTION
With the apsfilter-bug script you can automatically create a bug report for apsfilter(1). A template report file is created which you can
edit with your favourite editor ( emacs(1) by default, or whatever is entered in the environment variable EDITOR ).
You will see a couple of lines starting with '#'; these lines will be removed before the report is sent. So if you want to use the '#' char-
acter at the beginning of a line, just indent it with a space.
A very important piece of the bug report is the debugging log created by aps2file(1), probably with a command like
aps2file -D -o /dev/null [-P...] [-Z...] [input] 2> log.txt
Unless you don't even have a chance to create a debugging log, it is crucial for serious bug hunting.
After you have filled in as much (useful) information as possible, you must save the file under its original name, then exit your editor.
If you invoked apsfilter-bug by accident, or if you need some additional system information to include into the bug report, just exit your
editor without saving the file.
NOTES
In addition to the stuff you've edited, some more information is appended to the bug report automatically:
apsfilter version 7.2.6-stable
ghostscript version (from 'gs --version')
system id (from 'uname -a')
configure options --prefix=/usr --sysconfdir=/etc --mandir=/usr/share/man --with-awk=/usr/bin/awk --with-sendmail=/usr/sbin/sendmail
shell executable /bin/bash
awk executable /usr/bin/awk
sendmail executable /usr/sbin/sendmail
FILES
/usr/bin/aps2file script to create debugging output
SEE ALSO apsfilter(1), aps2file(1)BUGS
See apsfilter software center - http://www.apsfilter.org/ - for new versions, bugfixes and known bugs.
Please use the new tool apsfilter-bug(1) to release bug- or problem reports. It automatically presents you a form in an editor window which
asks you some standard questions. If you save and quit the editor session, then this report is sent automatically via e-mail to the proper
apsfilter mailinglist.
If apsfilter fails to print something or prints it in a way you wouldn't expect and you want to report an apsfilter error then please save
the debugging output of one print session using the new aps2file(1) utility by typing aps2file -D -Z options file > /dev/null 2> file.debug
and including the debugging output in the file file.debug into the edit session of the apsfilter-bug utility, so that it is included into the
mail to the apsfilter mailinglist.
Please note that you need to run /bin/sh (Bourne Shell), bash or a compatible shell, so that the above mentioned output redirection works.
Under C-shell (/bin/csh) or tcsh it would't work. If you don't know, then simply make sure you use the Bournce shell by typing /bin/sh or
bash, then you should have no problems with redirection of stdout and stderr (> /dev/null 2> file.debug).
DOCUMENTATION
See official apsfilter homepage
http://www.apsfilter.org/handbook.html Apsfilter Handbook including the Frequently Asked Questions (FAQ)
USER FORUM
Please send questions to the official apsfilter help channel apsfilter-help@apsfilter.org. The above section BUGS and the file
HOWTO-BUGREPORTS tells you how to report bugs. If you want to know how to troubleshoot your apsfilter installation, please read the manpage
aps2file(1) and apsfilter-bug(1) as well as the Apsfilter Handbook carefully.
HISTORY
The apsfilter-bug manpage has been written by Michael LoBin <phallobst@web.de> and first appeared in apsfilter V 7.1.0.
BSD Dec 26, 2001 BSD