Hello,
i will compile php and apache on an aix 5.1. Configure works fine.
When i start the make the following error appears:
/usr/include/sys/context.h:155: parse error before "sigset64_t"
/usr/include/sys/context.h:158: parse error before '}' token
make: 1254-004 The error code from the... (1 Reply)
Hi, I'm trying to compile a Perl module for AIX 5.3. Now, Perl by default wants to use cc_r as compiler but I only have gcc installed on this system.
How can I get gcc to be thread safe? Or can I use gcc without any options and expect it to behave the same as cc_r? (0 Replies)
I try to compile Samba 3.0.27a under AIX with LDAP and KErberos.
The configure work fine:
CFLAGS:
-I/opt/pware/include -I/opt/pware/lib/ -I/opt/pware/open_ldap_exec/lib/ -I/software/samba/oldap/usr/lib -I/software/samba/oldap/usr/include
./configure --prefix=/opt/pware/samba/3.0.27a... (1 Reply)
Compiling samba 3.0.27a under AIX
I try to compile Samba 3.0.27a under AIX with LDAP and KErberos.
The configure work fine:
CFLAGS:
-I/opt/pware/include -I/opt/pware/lib/ -I/opt/pware/open_ldap_exec/lib/ -I/software/samba/oldap/usr/lib -I/software/samba/oldap/usr/include
./configure... (2 Replies)
Hi, i'm trying to work with a trial version of PurifyPlus 7 with fixpack 10 from Rational that needs to run over an AIX 5.3 platform, 64-bit. I had success on compiling and running the hello_world programs and even a hash test program i found over the net, but purify can achieve the same with the... (0 Replies)
Hello all. I have never had any issues like this when compiling applications from source. When I try to compile samba-3.5.0pre2, configure runs with no issues, but when the time comes to make, this happens:
make: make 1254-025 There must be an existing description file or specify a target.
... (4 Replies)
Hi everyone:
I have a server running AIX 6.1, I've upgraded the TL from 6100-0100 to 6100-04-02-1007, however since then all the executables I compile are 32-bit mode by default, how can I solve this?
I'm using VisualAge C/C++ 10.0
thanks in advance (4 Replies)
gcc --version
gcc (GCC) 3.4.3 20041212 (Red Hat 3.4.3-9.EL4)
Linux 2.6.9-5.ELsmp #1 SMP Wed Jan 5 19:30:39 EST 2005 i686 i686 i386 GNU/Linux
vsftpd built 3.0.2
I am seeing this error when I try to implement the steps outlined for installing vsftpd:
# make
gcc -c main.c -O2 -fPIE... (2 Replies)
:rolleyes:I am trying to setup all certificate based client-server environment in Linux using vsftpd and curl with openssl.
I would like to make a user access with vsftpd certificate and user own client certificate (self-signed) with private/public key.
I don't see google posts about the my plan... (4 Replies)
Hi
We meet errors while running configuration scripts to prepare compiling source code on AIX 7.2. This error does not happen on AIX5.3 and AIX6.1
With the “/usr/bin/sh” from AIX7.2, sometimes , the script runs sucessfully, sometimes not. It’s unstable, and I don’t know why.
When... (10 Replies)
Discussion started by: bobochacha29
10 Replies
LEARN ABOUT HPUX
unlink
unlink(2) System Calls Manual unlink(2)NAME
unlink - remove directory entry; delete file
SYNOPSIS DESCRIPTION
The system call removes the directory entry named by the path name pointed to by path.
When all links to a file have been removed and no process has the file open, the space occupied by the file is freed and the file ceases to
exist. If one or more processes have the file open when the last link is removed, only the directory entry is removed immediately so that
processes that do not already have the file open cannot access the file. After all processes close their references to the file, if there
are no more links to the file, the space occupied by the file is then freed and the file ceases to exist.
RETURN VALUE
returns the following values:
Successful completion.
Failure.
is set to indicate the error.
ERRORS
If fails, is set to one of the following values:
Search permission is denied for a component of the path prefix.
Write permission is denied on the directory containing the link to be removed.
The process does not have read/write access permission to the parent
directory.
The entry to be unlinked is the mount point for a mounted file system.
path points outside the process's allocated address space. The reliable detection of this error is implementation dependent.
Too many symbolic links were encountered in translating the path name.
The length of the specified path name exceeds
bytes, or the length of a component of the path name exceeds bytes while is in effect.
The named file does not exist (for example,
path is null or a component of path does not exist).
A component of the path prefix is not a directory.
The directory containing the file to be removed
has the sticky bit set and neither the containing directory nor the file to be removed are owned by the effective user ID.
The named file is a directory and
the effective user ID is not a user with appropriate privileges. Some file systems return this error whenever the named file
is a directory, regardless of the user ID.
The directory entry to be unlinked is part of a read-only file system.
The entry to be unlinked is the last link to a pure procedure
(shared text) file that is being executed.
WARNINGS
If is used on a directory that is not empty (contains files other than and the directory is unlinked, the files become orphans, and the
directory link count is left with an inaccurate value unless they are linked by some other directory.
If is used on a directory that is empty (contains only the files and the directory is unlinked, but the parent directory's link count is
left with an inaccurate value.
In either of the above cases, the file system should be checked using (see fsck(1M)). To avoid these types of problems, use instead (see
rmdir(2)).
SEE ALSO rm(1), close(2), link(2), open(2), rmdir(2), remove(3C), privileges(5).
STANDARDS CONFORMANCE unlink(2)