Sponsored Content
Full Discussion: pkgadd woes
Operating Systems Solaris pkgadd woes Post 302232279 by jlliagre on Thursday 4th of September 2008 07:45:25 AM
Old 09-04-2008
The package name is SUNWlibC (case dependant).
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

CDROM Woes

Have a Sun CDROM connected to a Ultra machine . Problem is it is not recognizing the drive being connected to it ... When i put the CD in the drive it accepts the CD and zooms initially then quitens out .. The devices drivers are also not created for it ... Any ideas anyone ... I am... (4 Replies)
Discussion started by: Jai
4 Replies

2. IP Networking

source address woes

I have checkpoint firewall-1 running on a solaris 7 sparc box with two physical working networks interface cards hme0, qfe0, (please note these are false addresses) qfe0 = 195.111.222.178 internet ISP hme0 = 172.19.12.58 /24 internal Lan which has a router to france on it I want to... (3 Replies)
Discussion started by: hcclnoodles
3 Replies

3. Solaris

Remote CD woes

Good Day, I've remotely mounted a cdrom (no problems theere). The kicker is I can see the directories on the remote CD bout I can't see the files. What am I doing wrong? I'm logged in as root on both systems. All the permissions seem okay - what am I missing? Thanks (2 Replies)
Discussion started by: greg69
2 Replies

4. Solaris

Solaris 10 Jumpstart woes

Hi All I have a Solaris 10 jumpstart boot/config server set up on a subnet, and am trying to use it to build a client (the only other machine on the network). Things start out just fine, with the client booting into the Solaris Installation program, but then it just coredumps just as it's... (4 Replies)
Discussion started by: rickedwards44
4 Replies

5. UNIX for Dummies Questions & Answers

Mksysb and Savevg woes

hi, i'm having a little trouble with an AIX 5.2 script that i have written and i was wondering if anyone could please offer me some advice on how to append a savevg backup to a mksysb tape, or more importantly where i'm going wrong? i've been trying to get this to work on and off for about a... (1 Reply)
Discussion started by: boredazfcuk
1 Replies

6. AIX

IVM vs. HMC woes

I have a running VIO server that was managed via IVM. We made the (apparent) mistake of trying to connect a HMC server to it. Other than making a connection, no work has been done via HMC. We've since decided we don't want to use HMC and it's been powered off for a couple of weeks. However,... (1 Reply)
Discussion started by: cjs226
1 Replies

7. Solaris

SSH woes

version of solaris: SunOS 5.8 Generic-117350-39 sun4u sparc SUNW,Netra-240 version of SSH: OpenSSH_4.4p1, OpenSSL 0.9.8d 28 Sep 2006 Task: I need to have another Machine ssh into my machine, by either RSA authentication or username/pass authentication. History: In the begining my... (4 Replies)
Discussion started by: EWTGPAC
4 Replies

8. Solaris

Locale woes

Greetings Forumers! I've been fighting a locale problem on a v490 running Solaris 10 u4 (8/07). When I login to the system, I get several "locale" error messages: user1's password: Last login: Wed May 26 2010 09:14:13 -0400 from system1 You have mail. couldn't set locale correctly couldn't... (0 Replies)
Discussion started by: bluescreen
0 Replies

9. Solaris

Jumpstart woes

Hey, I have been battling with jumpstart for the past few days. Interface nxge0 is set on a vlan: nxge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 0.0.0.0 netmask ff000000 ether 0:21:28:3c:a0:6 nxge998000:... (0 Replies)
Discussion started by: stantonnet
0 Replies

10. AIX

Samba Woes

Hi all With the recent virus attacks we have been tasked with upgrading Samba to a "secure" version. Currently running 3.0.29a and looking to put the latest version down 4.6.5. Being a lazy bod I have only ever installed this, a long time ago, when you could get it in BFF filesets. Have... (6 Replies)
Discussion started by: splattty
6 Replies
Tcl_StaticPackage(3)                                          Tcl Library Procedures                                          Tcl_StaticPackage(3)

__________________________________________________________________________________________________________________________________________________

NAME
Tcl_StaticPackage - make a statically linked package available via the 'load' command SYNOPSIS
#include <tcl.h> Tcl_StaticPackage(interp, pkgName, initProc, safeInitProc) ARGUMENTS
Tcl_Interp *interp (in) If not NULL, points to an interpreter into which the package has already been loaded (i.e., the caller has already invoked the appropriate initialization procedure). NULL means the package has not yet been incorporated into any interpreter. const char *pkgName (in) Name of the package; should be properly capitalized (first letter upper-case, all others lower-case). Tcl_PackageInitProc *initProc (in) Procedure to invoke to incorporate this package into a trusted interpreter. Tcl_PackageInitProc *safeInitProc (in) Procedure to call to incorporate this package into a safe interpreter (one that will exe- cute untrusted scripts). NULL means the package cannot be used in safe interpreters. _________________________________________________________________ DESCRIPTION
This procedure may be invoked to announce that a package has been linked statically with a Tcl application and, optionally, that it has already been loaded into an interpreter. Once Tcl_StaticPackage has been invoked for a package, it may be loaded into interpreters using the load command. Tcl_StaticPackage is normally invoked only by the Tcl_AppInit procedure for the application, not by packages for them- selves (Tcl_StaticPackage should only be invoked for statically loaded packages, and code in the package itself should not need to know whether the package is dynamically or statically loaded). When the load command is used later to load the package into an interpreter, one of initProc and safeInitProc will be invoked, depending on whether the target interpreter is safe or not. initProc and safeInitProc must both match the following prototype: typedef int Tcl_PackageInitProc(Tcl_Interp *interp); The interp argument identifies the interpreter in which the package is to be loaded. The initialization procedure must return TCL_OK or TCL_ERROR to indicate whether or not it completed successfully; in the event of an error it should set the interpreter's result to point to an error message. The result or error from the initialization procedure will be returned as the result of the load command that caused the initialization procedure to be invoked. KEYWORDS
initialization procedure, package, static linking Tcl 7.5 Tcl_StaticPackage(3)
All times are GMT -4. The time now is 05:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy