01-23-2003
Ok when I run make I run into this problem
ar[2]: Entering directory `/usr/scott/m4-1.4/lib'
ar[2]: *** No rule to make target `cru'. Stop.
ar[2]: Leaving directory `/usr/scott/m4-1.4/lib'
make[1]: *** [libm4.a] Error 2
make[1]: Leaving directory `/usr/scott/m4-1.4/lib
make: *** [all] Error 1
What is this 'cru'??
10 More Discussions You Might Find Interesting
1. Programming
Hi All,
I m very new to unix.
I have a basic doubt ..
In unix I m seeing that there is a * at the end of by executable name (exe1*)..
Wht is the significance of that
Thanks a lot in advance (2 Replies)
Discussion started by: binums
2 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I have written a shell script for automating some of our repetitive activities. I want all my colleagues to use my script and do the activities automatically by just running the script.
But I do not want them to see the code. Is there a way we can generate something like an executable... (16 Replies)
Discussion started by: lokachari
16 Replies
3. HP-UX
Hi
I have locally compiled and installed gcc-4.1.2 in directory /usr/local/pkg/gcc/4.1.2/bin/gcc
I want to compile beecrypt using this new compiler , So i have done
setenv CC usr/local/pkg/gcc/4.1.2/bin/gcc ( Note this configuration is running properly with older version of... (1 Reply)
Discussion started by: vasanthan
1 Replies
4. Programming
Hi - I have two complex (for me at least) make files. The older one creates a succesful executable. The later one uses if statements to conditionally make different versions of the executable. The 2nd produces an executable that fails. I have "eyeballed" the differences in the Make files and run... (18 Replies)
Discussion started by: BrighterLater
18 Replies
5. Solaris
Hi,
I'm trying to compile Apache2.2 (I know it is available as a package) on a fresh install of Solaris Express 11. I've installed gcc-3 and gnu-bintutils via pkg. The config.log is attached (as config.txt). I don't see what I'm missing.
Thanks,
Doug (1 Reply)
Discussion started by: Doug_M
1 Replies
6. Linux
Hello everyone,
I am trying to re-install quantum espresso-4.3 on the University's LINUX interface (because of a recent crash and I lost most of my files).
when I " ./configure ", It is giving an error stating that :
checking building system type... x86_64-unknown-linux-gnu
checking... (7 Replies)
Discussion started by: Physicslad78
7 Replies
7. Shell Programming and Scripting
Hello Unix users, this is my first post here. :)
I want to search a directory (and subdirectories) for executable files (files with rwx------ permission) and move them to a different folder. What Unix commands can accomplish this? (2 Replies)
Discussion started by: Sagan_Radiation
2 Replies
8. Shell Programming and Scripting
CROSS_COMPILE?=
LIBDIR_APP_LOADER?=../../../../app_loader/lib
INCDIR_APP_LOADER?=../../../../app_loader/include
BINDIR?=../../bin
CFLAGS+= -Wall -I$(INCDIR_APP_LOADER) -D__DEBUG -O2 -mtune=cortex-a8 -march=armv7-a -std=gnu99
LDFLAGS+=-L$(LIBDIR_APP_LOADER) -lprussdrv -lpthread
OBJDIR=obj... (1 Reply)
Discussion started by: bpetersen
1 Replies
9. Shell Programming and Scripting
Hi everyone,
I am working with an executable (let's say work) in bash shell. When I run this work
executable it asks the following information;
1- choose task a or b
2- input file
3- output file
4- some operational choices
after it reads the given input file, does some algebraic... (17 Replies)
Discussion started by: hayreter
17 Replies
10. Ubuntu
https://www.unix.com/302461112-post1.html
Thank you. It's still in Linux Mint 17 (3 Replies)
Discussion started by: jgt
3 Replies
LEARN ABOUT NETBSD
compat_30
COMPAT_30(8) BSD System Manager's Manual COMPAT_30(8)
NAME
compat_30 -- setup procedure for backward compatibility on post-3.0 releases
SYNOPSIS
options COMPAT_30
DESCRIPTION
The compat_30 module allows NetBSD to run NetBSD 3.0 executables.
The support is present if the kernel was built with option COMPAT_30. It is not available as a loadable module.
Static executables typically need no additional setup. Dynamic binaries may require shared libraries whose major version number changed
since NetBSD 3.0, which are listed below. A shadow directory under /emul is not used; the libraries can be obtained from a NetBSD 3.0 dis-
tribution and installed in the original directories shown, as the major version number in the file name will prevent conflicts. If an
upgrade installation from NetBSD 3.0 has been done and these libraries are still present, nothing more need be done.
Libraries needed from 3.0
/lib/libcrypto.so.2.1 /lib/libcrypto.so.2
/usr/lib/libcrypto.so.2.1 /usr/lib/libcrypto.so.2
/lib/libevent.so.0.2 /lib/libevent.so.0
/usr/lib/libevent.so.0.2 /usr/lib/libevent.so.0
/usr/lib/libg2c.so.2.0 /usr/lib/libg2c.so.2
/usr/lib/libkadm.so.5.0 /usr/lib/libkadm.so.5
/usr/lib/libkafs.so.6.0 /usr/lib/libkafs.so.6
/usr/lib/libkdb.so.5.0 /usr/lib/libkdb.so.5
/usr/lib/libkrb5.so.19.1 /usr/lib/libkrb5.so.19
/usr/lib/libkrb.so.6.0 /usr/lib/libkrb.so.6
/usr/lib/libkstream.so.2.0 /usr/lib/libkstream.so.2
/usr/lib/libmagic.so.0.1 /usr/lib/libmagic.so.0
/usr/lib/libpcap.so.1.4 /usr/lib/libpcap.so.1
/lib/libradius.so.0.0 /lib/libradius.so.0
/usr/lib/libradius.so.0.0 /usr/lib/libradius.so.0
/usr/lib/libssh.so.1.0 /usr/lib/libssh.so.1
/usr/lib/libssl.so.3.0 /usr/lib/libssl.so.3
/usr/lib/libstdc++.so.5.0 /usr/lib/libstdc++.so.5
/lib/libz.so.0.4 /lib/libz.so.0
/usr/lib/libz.so.0.4 /usr/lib/libz.so.0
/usr/lib/libamu.so.2.1 /usr/lib/libamu.so.2
IMPLEMENTATION NOTES
COMPAT_30 enables the NetBSD 3.0 versions of the following system calls, whose syscall numbers and argument structures were changed after the
3.0 release to accommodate 64-bit filesystems: fhstat(2), fstat(2), getdents(2), lstat(2), stat(2).
The filehandle structure (formerly fhandle_t) was made opaque to userland and variable-sized. A fh_size argument was added to related
syscalls: fhstat(2), fhstatvfs(2), fhstatvfs1(2), fhopen(2), getfh(2). This changes the API and ABI of those syscalls, COMPAT_30 enables
binary compatibility with the old ABI. Source compatibility is not provided, as use of those syscalls is supposed to be rare.
The error code from the socket(2) syscall changed from EPROTONOSUPPORT to EAFNOSUPPORT in the case of an unsupported address family.
COMPAT_30 enables binary compatibility with the old ABI. Source compatiblility is not provided.
The struct ntptimeval used by ntp_gettime(2) changed with the implementation of timecounters.
SEE ALSO
config(1), fhstat(2), fstat(2), getdents(2), lstat(2), stat(2), options(4)
HISTORY
NetBSD offers back-compatibility options back to NetBSD 0.9, but the first to be documented with a manual page is compat_30.
BUGS
The compatible getdents(2) is unable to see directory entries beneath the top layer of a union, even though the real 3.0 getdents() did not
have that problem.
SECURITY CONSIDERATIONS
Programs with security impact that receive incorrect directory contents from getdents() may behave improperly, as when they are unable to
find, or find the wrong versions of, important files.
BSD
December 15, 2007 BSD