09-01-2011
[Solved] AIX server is compiling executables to 32-bits by default, how to change it?
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
Last edited by edgarvm; 09-01-2011 at 03:02 PM..
9 More Discussions You Might Find Interesting
1. AIX
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)
Discussion started by: n-may
1 Replies
2. AIX
There are quite many nifty little tricks, which can make life easier for the AIX administrator carrying out typical tasks in his job. I'll start the collection, suggestions will be highly welcome and added here when they are messaged to me. No, i don't claim to have found out myself what stands... (0 Replies)
Discussion started by: bakunin
0 Replies
3. UNIX and Linux Applications
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)
Discussion started by: BenediktS
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I try to use R through the Unix server in my university. When I want to install an R package, I don't have the permission to change the R library. So I installed another version of R under my user's folder on the server, which seems successful. However, when I try to run it, the default R on... (3 Replies)
Discussion started by: xuemin
3 Replies
5. AIX
Hi,
I am a newbie to AIX. We have 2 AIX5.3 servers in our environment, I need to transfer some files in Binary mode from one server to another and some files in ASCII mode from one server to another server. Could you please help me as to how I need to do that?
Thanks,
Rakesh (4 Replies)
Discussion started by: rakeshc.apps
4 Replies
6. AIX
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)
Discussion started by: raidzero
4 Replies
7. Programming
Hi Everyone,
I can ask what is the option to compile a 64 bits program using gcc. I have looked everywhere but can't find it. Before I used to use cc and the -q64 flag was the option to generate the 64 bits binary. Can anyone tell me what is the flags when using gcc. Thanks...... (3 Replies)
Discussion started by: arizah
3 Replies
8. AIX
Hi
I want to change password for around 100 users on an aix server.
I have the list of those 100 users with me.
instead of doing
# passwd username
for all the 100 users one by one, can you please help with a script through which we can change the password for all the 100 users in a... (2 Replies)
Discussion started by: newtoaixos
2 Replies
9. AIX
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 NETBSD
sticky
STICKY(7) BSD Miscellaneous Information Manual STICKY(7)
NAME
sticky -- Description of the `sticky' (S_ISVTX) bit functionality
DESCRIPTION
A special file mode, called the sticky bit (mode S_ISVTX), is used to indicate special treatment for directories. See chmod(2) or the file
/usr/include/sys/stat.h
Sticky files
For regular files, the use of mode S_ISVTX is reserved and can be set only by the super-user. NetBSD does not currently treat regular files
that have the sticky bit set specially, but this behavior might change in the future.
Sticky directories
A directory whose ``sticky bit'' is set becomes a directory in which the deletion of files is restricted. A file in a sticky directory may
only be removed or renamed by a user if the user has write permission for the directory and the user is the owner of the file, the owner of
the directory, or the super-user. This feature is usefully applied to directories such as /tmp which must be publicly writable but should
deny users the license to arbitrarily delete or rename each others' files.
Any user may create a sticky directory. See chmod(1) for details about modifying file modes.
HISTORY
The sticky bit first appeared in V7, and this manual page appeared in section 8. Its initial use was to mark sharable executables that were
frequently used so that they would stay in swap after the process exited. Sharable executables were compiled in a special way so their text
and read-only data could be shared amongst processes. vi(1) and sh(1) were such executables. This is where the term ``sticky'' comes from -
the program would stick around in swap, and it would not have to be fetched again from the file system. Of course as long as there was a
copy in the swap area, the file was marked busy so it could not be overwritten. On V7 this meant that the file could not be removed either,
because busy executables could not be removed, but this restriction was lifted in BSD releases.
To replace such executables was a cumbersome process. One had first to remove the sticky bit, then execute the binary so that the copy from
swap was flushed, overwrite the executable, and finally reset the sticky bit.
Later, on SunOS 4, the sticky bit got an additional meaning for files that had the bit set and were not executable: read and write operations
from and to those files would go directly to the disk and bypass the buffer cache. This was typically used on swap files for NFS clients on
an NFS server, so that swap I/O generated by the clients on the servers would not evict useful data from the server's buffer cache.
BUGS
Neither open(2) nor mkdir(2) will create a file with the sticky bit set.
BSD
May 10, 2011 BSD