Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Building cdrkit on Solaris 8 generates a linker problem
Operating Systems Solaris Building cdrkit on Solaris 8 generates a linker problem Post 302269375 by dxk3355 on Wednesday 17th of December 2008 01:34:46 PM
Old 12-17-2008
Building cdrkit on Solaris 8 generates a linker problem
I'm trying to build cdrkit-1.1.9 but have the same problem with 1.1.6 as well. The reason I need cdrkit is that it has an extended Joilet that mkisofs doesn't have but if anyone has another program that can provide this that might be a work around I can use.

The problem I'm having is when I build cdrkit I get this output
Code:
make -C build  all
make[1]: Entering directory `/opt/XRXcps/users/xcps/cdrkit-1.1.9/build'
make[2]: Entering directory `/opt/XRXcps/users/xcps/cdrkit-1.1.9/build'
make[3]: Entering directory `/opt/XRXcps/users/xcps/cdrkit-1.1.9/build'
Linking C static library libunls.a
Error running link command: No such file or directory
make[3]: *** [libunls/libunls.a] Error 2
make[3]: Leaving directory `/opt/XRXcps/users/xcps/cdrkit-1.1.9/build'
make[2]: *** [libunls/CMakeFiles/unls.dir/all] Error 2
make[2]: Leaving directory `/opt/XRXcps/users/xcps/cdrkit-1.1.9/build'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/opt/XRXcps/users/xcps/cdrkit-1.1.9/build'
make: *** [all] Error 2

I built the same download in cygwin without a problem and I get past this when I built on a Solaris 10 machine (though I do run into a different error).

OS: SunOS 5.8, sparc
GCC: 3.4.6
CMake: 2.4.8
Gmake: 3.81
Last edited by dxk3355; 12-17-2008 at 02:59 PM..
 

8 More Discussions You Might Find Interesting

1. Programming

CC LInker Error UNIX Sun Solaris

Hi Together, while compiling my program with CC I get the following Error message from the Linker: Undefined first referenced symbol in file std::basic_string<char,std::char_traits<char>,std::allocator<char>... (2 Replies)
Discussion started by: nik
2 Replies

2. OS X (Apple)

Problem building graphserver

Problem building graphserver I've been trying to build this thing graphserver (Graphserver - Fine Open Source Itineraries) but I'm getting a build error on Mac OS X 1.4.11. I've tried using subversion and 0.5 release, both report the same problem. $ sudo ruby install.rb build Password:... (0 Replies)
Discussion started by: ollie saunders
0 Replies

3. OS X (Apple)

Problem building graphserver

I've been trying to build this thing graphserver (Graphserver - Fine Open Source Itineraries) but I'm getting a build error on Mac OS X 1.4.11. I've tried using subversion and 0.5 release, both report the same problem. $ sudo ruby install.rb build Password: checking for main() in... (0 Replies)
Discussion started by: ollie saunders
0 Replies

4. Solaris

Need help in building gcc on solaris.

We are moving from old solaris to new version of solaris. I have copied the gcc compiler installed on old server to new solaris server. But just copying didn't work. So I am trying to build it on the new server. The server version is sailfish@st-kvar02 -> uname -a SunOS st-kvar02 5.10... (7 Replies)
Discussion started by: nalina.hv
7 Replies

5. Solaris

gcc & linker question (Solaris 10)

Hi, I'm confused about the GCC & Linking process could somebody please briefly explain? I have GCC 3.4.6 installed from SunFreeware. Reading the narrative alongside the package states "It was compiled to use the SUN assembler and loader usually in /usr/ccs/bin if the SUNW developer packages... (1 Reply)
Discussion started by: Celtic_Monkey
1 Replies

6. Solaris

Problem building app

trying to run IPERF and i've downloaded and installed and screwed around with my path to get compilers and such available... log in as myself, go to /iperf-2.0.4 switch to su run ./configure seems to go fine, couple of no's but based on previous runs it seems to be ok... do make it goes... (3 Replies)
Discussion started by: jrich523
3 Replies

7. Solaris

Troubles building on solaris 9 and executing on solaris 10

Hi, I have to build an application on solaris 9 which is supposed to run on solaris 10 computers. I heard that solaris 9 builds should run on solaris 10 without any troubles. However, there is some trouble. Calling ldd on the programm reveals that "libgcc_s.so.1" and "libstdc++.so.6" are... (4 Replies)
Discussion started by: mikehammer80
4 Replies

8. Solaris

How to find out the script which generates the file in solaris/unix ?

Hi A file is generated/created/modified during installation (or) execution of a script. vice versa..How to find out which script is responsible for creating/modifying a file. Example:- ....An existing file ( hosts.ulcm ), this file is created or modified by running a script ( may be... (1 Reply)
Discussion started by: frintocf
1 Replies

LEARN ABOUT NETBSD

dh_auto_install

DH_AUTO_INSTALL(1)                                                   Debhelper                                                  DH_AUTO_INSTALL(1)

NAME

       dh_auto_install - automatically runs make install or similar

SYNOPSIS

       dh_auto_install [buildsystemoptions] [debhelperoptions] [--params]

DESCRIPTION

       dh_auto_install is a debhelper program that tries to automatically install built files. It does so by running the appropriate command for
       the build system it detects the package uses. For example, if there's a Makefile and it contains a install target, then this is done by
       running make (or MAKE, if the environment variable is set). If there is a setup.py or Build.PL, it is used. Note that the Ant build system
       does not support installation, so dh_auto_install will not install files built using Ant.

       Unless --destdir option is specified, the files are installed into debian/package/ if there is only one binary package. In the multiple
       binary package case, the files are instead installed into debian/tmp/, and should be moved from there to the appropriate package build
       directory using dh_install(1).

       DESTDIR is used to tell make where to install the files.  If the Makefile was generated by MakeMaker from a Makefile.PL, it will
       automatically set PREFIX=/usr too, since such Makefiles need that.

       This is intended to work for about 90% of packages. If it doesn't work, or tries to use the wrong install target, you're encouraged to skip
       using dh_auto_install at all, and just run make install manually.

OPTIONS

       See "BUILD SYSTEM OPTIONS" in debhelper(7) for a list of common build system selection and control options.

       --destdir=directory
           Install files into the specified directory. If this option is not specified, destination directory is determined automatically as
           described in the "DESCRIPTION" section.

       -- params
           Pass params to the program that is run, after the parameters that dh_auto_install usually passes.

SEE ALSO

       debhelper(7)

       This program is a part of debhelper.

AUTHOR

       Joey Hess <joeyh@debian.org>

11.1.6ubuntu2                                                       2018-05-10                                                  DH_AUTO_INSTALL(1)
All times are GMT -4. The time now is 11:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy