Hello,

I now can build Curl off of the daily CVS snapshot on VMS resulting in:

EAGLE> curl --version
curl 7.19.6-20090619 (alpha-dec-vms) libcurl/7.19.6-20090619
OpenSSL/0.9.7e zlib/1.2.3
Protocols: tftp ftp telnet dict ldap http file https ftps
Features: GSS-Negotiate IPv6 Largefile NTLM SSL libz

The procedures result in building a binary distribution kit. The PCSI
file is the kit and the PCSI$COMPRESS is a compressed version of the
kit. These are the Native VMS product installer kit format.

Directory STAGE_ROOT:[kit]

JEM-AXPVMS-CURL-D0719-6-1.PCSI;1
JEM-AXPVMS-CURL-D0719-6-1.PCSI$COMPRESSED;1

The build and kitting procedures required an additional 32 files. The
readme. file in that list has been updated for building using the GNV
package.

The GNV (GNU is not VMS) package is a toolkit that provides a more Unix
like build environment.

EAGLE> dir vms_root:[--...]/exclude=*.dir

Directory VMS_ROOT:[curl-7^.19^.6-daily.packages.vms]

backup_gnv_project_sources.com Build_gnv_curl.com
build_gnv_curl_pcsi_desc.com build_gnv_curl_pcsi_text.com
build_gnv_curl_release_notes.com clean_gnv_curl.com
curl_gnv_build_steps.txt curl_release_note_start.txt
curl_startup.com gnv$conftest.c_first
gnv$conftest.opt gnv$curl.opt
gnv$first_include.h gnv$getenv.c_first
gnv$homedir.c_first gnv$netrc.c_first
gnv_curl_configure.sh gnv_libcurl_symbols.opt
    gnv_link_curl.com gnv_template_linker.opt

make_debug_gnv_curl.sh make_gnv_curl.sh
make_gnv_curl_check.sh make_gnv_curl_install.sh
make_pcsi_curl_kit_name.com PCSI_GNV_CURL_FILE_LIST.TXT
pcsi_product_gnv_curl.com readme
setup_gnv_curl_build.com vms_crtl_init.c

Total of 30 files.

Directory VMS_ROOT:[curl-7^.19^.6-daily.packages.vms.contrib]

curl_daily_cvs_update.com replace_curl_daily_cvs.sh
setup_curl_daily_build.com

Total of 3 files.

Grand total of 2 directories, 33 files.

Is it possible to get these into the CVS repository?

If so, what would be the best way for me to post them?

Regards,
-John
wb8tyw_at_qsl.network
Personal Opinion Only
Received on 2009-06-20