If you tell us what it actually did, maybe we can actually help you. But my crystal ball is still in for maintenance so I can't tell you why those errors were happening, or what they even were. "some header file dependency problem" doesn't cut it. There might be reasons you're missing a specific header. I can't tell you why you might be missing any random header.
Please don't throw random symlinks into /usr/include. Take out the ones you put before you forget where they are. They'll come back to haunt you later.
Thank you for reply
symlinks from /usr/include is removed.
I recently loaded SuSE on my intel comp.
I am presently taking a walk down memory lane from my days at UofT.
I was fiddling round with cc and the gcc compilers.
I wrote a basic basic basic program .
I tried to compile it as I remember doing in Uni. The problem is that it can't find the header... (5 Replies)
would anyone know of a good online tutorial on compiling and installing tarballs? i'm looking for one that assumes that you know very little to nothing about unix. (3 Replies)
i am trying to compile and install free qt for x11 2.2.4 in order to use kde 2.1. i'm using freebsd 4.3
i currently have XFree86 installed and working.
i followed these instructions:
ftp://ftp.trolltech.com/qt/source/INSTALL
i get through the unpacking fine and i set my .profile.
--... (2 Replies)
I am new to unix so please forgive ignorance. I am running openbsd-2.9 and need some help. All the software I run was added via the package system openbsd has. There have been times when I need an app. But it was not in the openbsd ports and or packages system. I usually just wait for it to show up... (1 Reply)
I have a problem.
How can I be sure that the binary currently in production is the binary originally produced by the compiler? I ask because recompiling the sources (ALL sources + stripping away the metadata: strip ...) does not give the same result.
I am pretty sure that I wasn't hacked!
... (5 Replies)
I was trying to compile a proc code. All steps when fine, except the last step which threw an error -
I was just trying to compile it manually. Any ideas what this error means. Does it mean I am using the wrong library? (3 Replies)
Hi guys.
I have a header file: unp.h like this:
#ifndef _UNP_H_
#define _UNP_H_
extern ssize_t readn(int filedes, void *buff, size_t nbytes);
extern ssize_t writen(int filedes, const void *buff, size_t nbytes);
extern void err_quit(const char *msg);
#define TRUE 1
#define FALSE 0
... (2 Replies)
Discussion started by: majid.merkava
2 Replies
LEARN ABOUT FREEBSD
uniq
UNIQ(1) BSD General Commands Manual UNIQ(1)NAME
uniq -- report or filter out repeated lines in a file
SYNOPSIS
uniq [-c | -d | -u] [-i] [-f num] [-s chars] [input_file [output_file]]
DESCRIPTION
The uniq utility reads the specified input_file comparing adjacent lines, and writes a copy of each unique input line to the output_file. If
input_file is a single dash ('-') or absent, the standard input is read. If output_file is absent, standard output is used for output. The
second and succeeding copies of identical adjacent input lines are not written. Repeated lines in the input will not be detected if they are
not adjacent, so it may be necessary to sort the files first.
The following options are available:
-c Precede each output line with the count of the number of times the line occurred in the input, followed by a single space.
-d Only output lines that are repeated in the input.
-f num Ignore the first num fields in each input line when doing comparisons. A field is a string of non-blank characters separated from
adjacent fields by blanks. Field numbers are one based, i.e., the first field is field one.
-s chars
Ignore the first chars characters in each input line when doing comparisons. If specified in conjunction with the -f option, the
first chars characters after the first num fields will be ignored. Character numbers are one based, i.e., the first character is
character one.
-u Only output lines that are not repeated in the input.
-i Case insensitive comparison of lines.
ENVIRONMENT
The LANG, LC_ALL, LC_COLLATE and LC_CTYPE environment variables affect the execution of uniq as described in environ(7).
EXIT STATUS
The uniq utility exits 0 on success, and >0 if an error occurs.
COMPATIBILITY
The historic +number and -number options have been deprecated but are still supported in this implementation.
SEE ALSO sort(1)STANDARDS
The uniq utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'') as amended by Cor. 1-2002.
HISTORY
A uniq command appeared in Version 3 AT&T UNIX.
BSD December 17, 2009 BSD