01-05-2005
I'm definitely using a 64bit system. I suspect the software I'm trying to install is supposing it is on a 32bit system and throws an error when it tries to access a 64bit library. Is there a way of figuring that out?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am running mandrake 8.2 and when booting I get the message:
e2fschk: Bad magic number in super-block while trying to open /dev/hda8.
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and really contains a valid an ext2 filesystem (and... (1 Reply)
Discussion started by: Jay
1 Replies
2. Filesystems, Disks and Memory
Dear All,
i have a SCSI hard disk drive i'm installing on it solaris 5 and the workstation is sun sparc, i made an image of this H.D using Norton Ghost 6, so i took off the SCSI H.D from the sun workstation and put it on a Compaq server then i booted the server from the Norton Ghost floppy disk... (0 Replies)
Discussion started by: wesweshahaha
0 Replies
3. UNIX for Advanced & Expert Users
Hello All,
(RHEL4)
Few weeks ago I had posted a message in this forum about the problem I had when I replaced my two scsi disks and tried rebuild raid1 array.
I somehow managed to up the system with working raid1 array.
But the main problem persisted..
i.e when I reboot the system, mounting... (0 Replies)
Discussion started by: ravinandan
0 Replies
4. Solaris
Hello All,
I m very new to this forum.
i m having SUN NETRA X1 server with 40 GB HDD (Seagate) & 128 MB RAM.
i m trying this server for SUN 10 Practise.
As i m installing SUN 9 /10 with CD ,its giving me error after OK propmt
***************************
#boot cdrom
or
#boot cdrom... (16 Replies)
Discussion started by: amrut_k
16 Replies
5. Solaris
Hi guys, I have a big problem wiht my old Netra T1 200. I want to install OpenSolaris 2009 but there's a problem, I burned the ISO image on a CD-RW and then I tryied to install it on netra, but the setup won't to start and the error is that in the attached image.
Thanks for the support and sorry... (5 Replies)
Discussion started by: Ducati87
5 Replies
6. Solaris
I'll keep it fairly straight forward. I work with a Solaris server and magically today it decided to take a dump on me. At first it give a long list of files that couldn't be acessed before terminating the boot process and returning to the 'ok' prompt. Booting in single-user mode allowed me to run... (4 Replies)
Discussion started by: Aon
4 Replies
7. Solaris
Hi,
i got the following error while unpacking the archive file.
cpio -icvd < as_sun_x86_101202_disk2.cpio
Disk2/stage/Components/oracle.webdb.wwdoc/10.1.2.0.1/1/DataFiles/wwdoc.jar
Disk2/stage/Components/oracle.webdb.wwdoc/10.1.2.0.1/1/DataFiles... (2 Replies)
Discussion started by: malikshahid85
2 Replies
8. Filesystems, Disks and Memory
Hello all,
I have a hard drive that I can't repair.
The drive is WD15EARS - Filesystem ext4 ( not 100% sure )
It's used in a Synology DS110j NAS.
I try to run fsck -p /dev/sdb on the HD and I get this:
Bad magic number in super-block while trying to open /dev/sdb
/dev/sdb:
The superblock... (4 Replies)
Discussion started by: dallasw1983
4 Replies
9. Solaris
So we have a new to us v240 server with no OS installed. It has an outdated version of OB and ALOM so before we install the OS we want to update both. We have a DVD with the latest OB patch burned on it.
We do the boot cdrom command but receive the Bad Magic Number Error. Does an OS need to... (2 Replies)
Discussion started by: dunkpancakes
2 Replies
10. Solaris
This is first time post...found this forum when looking for possible solution to fix my sun pc. Just one day can't boot it already showing the following:
Boot device: disk File args:
Bad magic number in disk label
Can't open disk label package
Evaluating: boot
Can't open boot device... (40 Replies)
Discussion started by: SHuKoSuGi
40 Replies
LEARN ABOUT DEBIAN
iverilog-vpi
iverilog-vpi(1) Version 0.9.5 iverilog-vpi(1)
NAME
iverilog-vpi - Compile front end for VPI modules
SYNOPSIS
iverilog-vpi [--name=name] sourcefile...
DESCRIPTION
iverilog-vpi is a tool to simplify the compilation of VPI modules for use with Icarus Verilog. It takes on the command line a list of C or
C++ source files, and generates as output a linked VPI module. See the vvp(1) man page for a description of how the linked module is loaded
by a simulation.
The output is named after the first source file. For example, if the first source file is named foo.c, the output becomes foo.vpi.
OPTIONS
iverilog-vpi accepts the following options:
-llibrary
Include the named library in the link of the VPI module. This allows VPI modules to further reference external libraries.
-Idirectory
Add directory to the list of directories that will be search for header files.
-Ddefine
Define a macro named define.
--name=name
Normally, the output VPI module will be named after the first source file passed to the command. This flag sets the name (without
the .vpi suffix) of the output vpi module.
--install-dir
This flag causes the program to print the install directory for VPI modules, then exit. It is a convenience for makefiles or auto-
mated plug-in installers.
--cflags, --ldflags and -ldlibs
These flags provide compile time information.
PC-ONLY OPTIONS
The PC port of iverilog-vpi includes two special flags needed to support the more intractable development environment. These flags help the
program locate parts that it needs.
-mingw=path
Tell the program the root of the Mingw compiler tool suite. The vvp runtime is compiled with this compiler, and this is the com-
piler that iverilog-vpi expects to use to compile your source code. This is normally not needed, and if you do use it, it is only
needed once. The compiler will save the path in the registry for use later.
-ivl=path
Set for the use during compilation the root if the Icarus Verilog install. This is the place where you installed Icarus Verilog
when you ran the installer. This flag is also only needed once, and the path is stored in the registry for future use.
UNIX-ONLY OPTIONS
The UNIX version of iverilog-vpi includes additional flags to let Makefile gurus peek at the configuration of the iverilog installation.
This way, Makefiles can be written that handle complex VPI builds natively, and without hard-coding values that depend on the system and
installation. If used at all, these options must be used one at a time, and without any other options or directives.
--cflags
Print the compiler flags (CFLAGS or CXXFLAGS) needed to compile source code destined for a VPI module.
--ldflags
Print the linker flags (LDFLAGS) needed to link a VPI module.
--ldlibs
Print the libraries (LDLIBS) needed to link a VPI module.
-m32 On 64bit systems that support it (and support vvp32) this flag requests a 32bit vpi binary instead of the default 64bit binary.
Example GNU makefile that takes advantage of these flags:
CFLAGS = -Wall -O $(CFLAGS_$@)
VPI_CFLAGS := $(shell iverilog-vpi --cflags)
CFLAGS_messagev.o = $(VPI_CFLAGS)
CFLAGS_fifo.o = $(VPI_CFLAGS)
messagev.o fifo.o: transport.h
messagev.vpi: messagev.o fifo.o
iverilog-vpi $^
AUTHOR
Steve Williams (steve@icarus.com)
SEE ALSO
iverilog(1), vvp(1), <http://www.icarus.com/eda/verilog/>, <http://www.mingw.org>,
COPYRIGHT
Copyright (C) 2002-2009 Stephen Williams
This document can be freely redistributed according to the terms of the
GNU General Public License version 2.0
April 17th, 2009 iverilog-vpi(1)