Cygwin

[ghost]

It says here:

http://wikipedia.org/wiki/Pkgsrc

that pkgsrc supports Cygwin - where can I find the pkg_add tool for Cygwin?

[iamleot]

Hello Steven, Steven Penny writes:

It says here: http://wikipedia.org/wiki/Pkgsrc that pkgsrc supports Cygwin - where can I find the `pkg_add` tool for Cygwin?

You will first need to fetch the pkgsrc tree and then bootstrap it. On the pkgsrc website the `bootstrap' and `build a package' section' describe a quickstart: <https://www.pkgsrc.org/> First chapters of `The pkgsrc guide' and `pkgsrc/bootstrap/README.Cygwin' should contains more helpful information but if you have any problem probably it's better to ask on pkgsrc-users@ mailing list.

[ghost]

@iamleot that seems rather large to download:

$ curl -I https://codeload.github.com/NetBSD/pkgsrc/tar.gz/trunk
HTTP/1.1 200 OK
Content-Length: 54675641

54 MB? Thats larger than the entirety of Autotools.

[iamleot]

Steven Penny writes:

@iamleot that seems rather large to download: ~~~ $ curl -I https://codeload.github.com/NetBSD/pkgsrc/zip/trunk HTTP/1.1 200 OK Content-Length: 87166577 ~~~ 87 MB?

Yes, sounds right! (it's the entire pkgsrc tree with all the package Makefile-s and the pkgsrc infrastructure)

[krytarowski]

Is this solved?

[ghost]

need link to binary download - no full source repository

[jsonn]

Noone provides binary packages for cygwin.

[krytarowski]

Cygwin (and all other handled OSes) are community driven and the project can promise only source repository. Everything else what comes in a binary format is a matter of downstream vendor to build and distribute binary packages.

If that vendor takes part in the community, it can put the packages on shared ftp.

http://cdn.netbsd.org/pub/pkgsrc/packages/

Right now nobody is actively collaborating from the Cygwin community so we cannot do much beyond shipping with source form.

The source distribution of pkgsrc might not be the proper place for prompt for binary packages, at least it probably won't get much traction here.

[michaeldexter]

I tried pkgsrc on Cygwin today and while it works, it is poorly documented and many packages fail to build, notably, devel/libtool-base, which is needed by devel/flex, which is needed by several packages I tried. I can install the same version of libtool in Cygwin but I do not know how to force use of it.

A few tips:

At a minimum you will want to install the gcc-core and libgcc1 packages in Cygwin.

From the command line: ./setup-x86.exe -q -P gcc-core libgcc1

Download and extract the pkgsrc tree as per the documentation and run the bootstrap script. I suggest you save the output with the script(1) command.

You will want to add these paths to /etc/profile (one is for Cygwin itself):

if [ ${CYGWIN_NOWINPATH-addwinpath} = "addwinpath" ] ; then
PATH="/usr/pkg/bin:/usr/pkg/sbin:/usr/local/sbin:/usr/local/bin:/usr/bin${PATH:+:${PATH}}"
else
PATH="/usr/pkg/bin:/usr/pkg/sbin:/usr/local/sbin:/usr/local/bin:/usr/bin"
fi

Log in again to receive the correct paths and you should be able to enter a specific package and type "bmake", rather than the traditional "make" and note that make from Cygwin will fail.

That said, could someone please look at building devel/libtool-base ?

Thanks!

[sskras]

@michaeldexter commented on Jun 20, 2019:

many packages fail to build, notably, devel/libtool-base
...
That said, could someone please look at building devel/libtool-base ?

pkgsrc-2022Q1 still fails, the commit e4e229c7b64 to be exact:

$ bmake -C devel/libtool-base
=> Bootstrap dependency digest>=20211023: found digest-20220214
===> Skipping vulnerability checks.
WARNING: No /home/saukrs/pkg/pkgdb/pkg-vulnerabilities file found.
WARNING: To fix run: `/home/saukrs/pkg/sbin/pkg_admin -K /home/saukrs/pkg/pkgdb fetch-pkg-vulnerabilities'.
===> Configuring for libtool-base-2.4.6nb3
=> Modifying GNU configure scripts to avoid --recheck
=> Replacing config-guess with pkgsrc versions
=> Replacing config-sub with pkgsrc versions
=> Replacing install-sh with pkgsrc version
## ------------------------- ##
## Configuring libtool 2.4.6 ##
## ------------------------- ##

checking for GNU M4 that supports accurate traces... /home/saukrs/pkg/bin/gm4
checking whether /home/saukrs/pkg/bin/gm4 accepts --gnu... yes
checking how m4 supports trace files... --debugfile
checking for a BSD-compatible install... /bin/install -c -o saukrs -g None
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /home/saukrs/src/pkgsrc/devel/libtool-base/work/.tools/bin/mkdir -p
checking for gawk... /bin/awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking build system type... x86_64-pc-cygwin
checking host system type... x86_64-pc-cygwin
configure: autobuild project... GNU Libtool
configure: autobuild revision... 2.4.6
configure: autobuild hostname... DESKTOP-O7JE7JE
configure: autobuild mode... default
configure: autobuild timestamp... 20220502T191655Z
checking for x86_64-pc-cygwin-gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.exe
checking for suffix of executables... .exe
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... (cached) /bin/grep
checking for egrep... (cached) /bin/egrep
checking for Minix Amsterdam compiler... no
checking for x86_64-pc-cygwin-ar... no
checking for ar... ar
checking how to run the C preprocessor... gcc -E
checking how to print strings... printf
checking for a sed that does not truncate output... /home/saukrs/pkg/bin/nbsed
checking for fgrep... /bin/grep -F
checking for ld used by gcc... (cached) ld
checking if the linker (ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... (cached) nm
checking the name lister (nm) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... (cached) 262144
checking how to convert x86_64-pc-cygwin file names to x86_64-pc-cygwin format... func_convert_file_noop
checking how to convert x86_64-pc-cygwin file names to toolchain format... func_convert_file_noop
checking for ld option to reload object files... -r
checking for x86_64-pc-cygwin-objdump... no
checking for objdump... objdump
checking how to recognize dependent libraries... file_magic ^x86 archive import|^x86 DLL
checking for x86_64-pc-cygwin-dlltool... no
checking for dlltool... dlltool
checking how to associate runtime and link libraries... func_cygming_dll_for_implib
checking for x86_64-pc-cygwin-ar... ar
checking for archiver @FILE support... @
checking for x86_64-pc-cygwin-strip... no
checking for strip... strip
checking for x86_64-pc-cygwin-ranlib... ranlib
checking command to parse nm output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for x86_64-pc-cygwin-mt... no
checking for mt... no
checking if : is a manifest tool... no
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for x86_64-pc-cygwin-as... no
checking for as... as
checking for x86_64-pc-cygwin-dlltool... dlltool
checking for x86_64-pc-cygwin-objdump... objdump
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -DDLL_EXPORT -DPIC
checking if gcc PIC flag -DDLL_EXPORT -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... yes
checking dynamic linker characteristics... Win32 ld.exe
checking how to hardcode library paths into programs... immediate
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... yes
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking what extension is used for runtime loadable modules... .dll
checking what variable specifies run-time module search path... PATH
checking for the default library search path... /lib /usr/lib
checking for library containing dlopen... none required
checking for dlerror... yes
checking for shl_load... no
checking for shl_load in -ldld... no
checking whether cygwin_conv_path is declared... yes
checking for dld_link in -ldld... no
checking for _ prefix in compiled symbols... no
checking whether deplibs are loaded by dlopen... unknown
checking for argz.h... yes
checking for error_t... yes
checking for argz_add... yes
checking for argz_append... yes
checking for argz_count... yes
checking for argz_create_sep... yes
checking for argz_insert... yes
checking for argz_next... yes
checking for argz_stringify... yes
checking if argz actually works... yes
checking whether libtool supports -dlopen/-dlpreopen... yes
checking for unistd.h... (cached) yes
checking for dl.h... no
checking for sys/dl.h... no
checking for dld.h... no
checking for mach-o/dyld.h... no
checking for dirent.h... yes
checking for closedir... yes
checking for opendir... yes
checking for readdir... yes
checking for strlcat... yes
checking for strlcpy... yes
checking whether we are using the GNU C++ compiler... no
checking whether c++ accepts -g... no
checking dependency style of c++... none
checking how to run the C++ preprocessor... /lib/cpp
configure: error: in `/home/saukrs/src/pkgsrc/devel/libtool-base/work/libtool-2.4.6':
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details
*** Error code 1

Stop.
bmake[1]: stopped in /home/saukrs/src/pkgsrc/devel/libtool-base
*** Error code 1

Stop.
bmake: stopped in /home/saukrs/src/pkgsrc/devel/libtool-base

It's 64-bit Cygwin v3.3.3:

$ uname -srmo
CYGWIN_NT-10.0 3.3.3(0.341/5/3) x86_64 Cygwin

[sskras]

Can this be reopened or should I add this into a new report?