09-30-2004
attach that make file please, otherwise nobody could help
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I often encounter make errors. Many a times, a corresponding error code is also shown, like
make: Error 56 (ignored)
make: Error 91 (ignored)
make: Error 96 (ignored)
et al.
I tried google'ing as well as searching this forum for what these error codes mean.
I know, make... (1 Reply)
Discussion started by: vino
1 Replies
2. UNIX for Dummies Questions & Answers
My system is ubuntu, can I use PMake ? (0 Replies)
Discussion started by: meili100
0 Replies
3. Programming
Is this possible? Right now I'm developing some code for Linux, Windows and OS X. To build on each of the systems I've currently got separate build targets for each platform. Ideally I'd like to set up a single make rule that can detect the appropriate target and build it.
I know this is... (2 Replies)
Discussion started by: G_Morgan
2 Replies
4. SCO
Installed GNU make and the GNU C/C++ compiler on SCO Openserver 5.0.7 recently.
Only a normal user is able to run make and compile programs - root is not able to.
Under root, make do run, but root can't access the compiler at all, even tho I set root's path to point to the compiler.... (0 Replies)
Discussion started by: The_Librarian
0 Replies
5. Programming
Hello everybody,
Currently I'm learning how to build projects (C programming) with GNU make. I have a problem with one Makefile and I would appreciate if you could kindly give me a hand. Here is the environment:
OS: Redhat linux 5
compiler: gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-44)... (2 Replies)
Discussion started by: dariyoosh
2 Replies
6. AIX
Hi team,
I am new to unix,and need your advice on the below.
I am using aix5.3 and have installed make-3.82 on the server.
I need to use gmake for configuring and installing a package ,but it is giving error at the below
root@sapsrp:/usr/tmp/xymon-4.3.2
# ./configure.server
... (7 Replies)
Discussion started by: sonal kumar
7 Replies
7. Shell Programming and Scripting
It's been a while since I had to write a Makefile, but I've managed to clobber this together:
SRC=module1.c module2.c
OBJS=$(SRC:%.c=%.o)
HDR=include1.h include2.h
CC=gcc
CFLAGS=-Wall -ggdb -D_XOPEN_SOURCE -I. -ansi
all: program
program: $(OBJS)
$(CC) $(CFLAGS) -o $@ $(OBJS)
... (3 Replies)
Discussion started by: pludi
3 Replies
8. Shell Programming and Scripting
Hi,
I do "touch poub.mlc"
Download my Makefile,
But when I try : make -f Makefile.txt(.txt in order my file to be accepted for upload), it says:"no rule for poub.mlo target"
What is wrong in my Makefile(test yourself please before posting)? (1 Reply)
Discussion started by: synhedionn
1 Replies
9. OS X (Apple)
As you may already know, Apple has integrated all the GNU developer tools into their own graphical development environment so you can no longer use them from the command line. This means that open source software that is distributed as source is inaccessible to users of newer versions of Mac OS X,... (4 Replies)
Discussion started by: Ultrix
4 Replies
10. Programming
I need some help.
I use variables and conditionals to build with or without specic libraries. I set
USEAL ?= 1 # get value from cmd, defaults to 1
(see comment)
the conditional is:
ifeq ($(USEAL),1)
LIBS = <any libs>
else
LIBS =
endif
Its amazing that this works when invoked... (4 Replies)
Discussion started by: dodona
4 Replies
usoc(7D) Devices usoc(7D)
NAME
usoc - universal serial optical controller for Fibre Channel arbitrated loop (SOC+) device driver
DESCRIPTION
The Fibre Channel adapter is an SBus card that implements two full duplex Fibre Channel interfaces. Each interface can connect to a Fibre
Channel arbitrated loop (FC-AL). The usoc device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL.
FILES
/kernel/drv/usoc
32-bit ELF kernel module
/kernel/drv/sparcv9/usoc
64-bit ELF kernel module
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC |
+-----------------------------+-----------------------------+
|Interface stability |Unknown |
+-----------------------------+-----------------------------+
|Availability |SUNWusoc |
+-----------------------------+-----------------------------+
SEE ALSO
fctl(7D), sbus(4), fcp(7D), fp(7D), ssd(7D)
Writing Device Drivers
Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994
Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996
Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998
Fabric Channel Loop Attachment (FC-FLA), NCITS TR-20:1998
DIAGNOSTICS
The following messages are logged and may also appear on the system console. On the console these messages are preceded by:
usoc%d:
where
usoc%d:
is the per-port instance number of the usoc controller.
Fibre Channel is ONLINE
The Fibre Channel loop is now online.
Fibre Channel Loop is ONLINE
The Fibre Channel loop is now online.
Fibre Channel Loop is OFFLINE
The Fibre Channel loop is now offline.
attach failed: device in slave-only slot.
Move soc+ card to another slot.
attach failed: alloc soft state.
Driver did not attach, devices will be inaccessible.
attach failed: bad soft state.
Driver did not attach, devices will be inaccessible.
attach failed: unable to map eeprom
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to map XRAM
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to map registers
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to access status register
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to install interrupt handler
Driver was not able to add the interrupt routine to the kernel. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to access host adapter XRAM
Driver was unable to access device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to write host adapter XRAM
Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: read/write mismatch in XRAM
Driver was unable to verify device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
SunOS 5.10 20 Jul 1999 usoc(7D)