Searched refs:working (Results 51 - 75 of 90) sorted by relevance

1234

/openbsd-current/gnu/usr.bin/perl/cpan/Test-Simple/lib/Test/Builder/
H A DTester.pm375 result. This is very useful for working out the correct text of
/openbsd-current/gnu/usr.bin/perl/cpan/autodie/lib/autodie/
H A Dexception.pm227 hand side, but in future Perls that is likely to stop working.
/openbsd-current/gnu/usr.bin/perl/dist/ExtUtils-ParseXS/lib/ExtUtils/ParseXS/
H A DUtilities.pm256 List of two elements: C<typemap> element from C<%args>; current working
/openbsd-current/gnu/usr.bin/perl/cpan/Encode/bin/
H A Denc2xs1232 how large your encoding is. Unless you are working on something big
/openbsd-current/gnu/usr.bin/perl/cpan/CPAN/lib/
H A DCPAN.pm829 CPAN.pm working directory. I could not create this directory due
854 Your configuration suggests that CPAN.pm should use a working
1721 being executed within the distribution file's working directory.
2033 The typical usage case is for private modules or working copies of
2358 CPAN.pm changes the current working directory often and needs to
2359 determine its own current working directory. By default it uses
3563 that are not networked at all, you should consider working with C<file:>
4052 minimal prerequisites working on older perls. It is close to
4053 impossible to get the whole Bundle::CPAN working there. If you're in
/openbsd-current/gnu/usr.bin/binutils/gprof/
H A Dconfigure939 echo $ac_n "checking for working aclocal""... $ac_c" 1>&6
940 echo "configure:941: checking for working aclocal" >&5
952 echo $ac_n "checking for working autoconf""... $ac_c" 1>&6
953 echo "configure:954: checking for working autoconf" >&5
965 echo $ac_n "checking for working automake""... $ac_c" 1>&6
966 echo "configure:967: checking for working automake" >&5
978 echo $ac_n "checking for working autoheader""... $ac_c" 1>&6
979 echo "configure:980: checking for working autoheader" >&5
991 echo $ac_n "checking for working makeinfo""... $ac_c" 1>&6
992 echo "configure:993: checking for working makeinf
[all...]
/openbsd-current/gnu/usr.bin/perl/cpan/Term-ReadKey/
H A DConfigure.pm697 and it may simply not be capable of working on some systems.
/openbsd-current/gnu/usr.bin/perl/regen/
H A Dreentr.pl130 * As of OpenBSD 3.7, reentrant functions are now working, they just are
/openbsd-current/usr.sbin/pkg_add/OpenBSD/
H A DPkgCreate.pm1186 $state->progress->working(2048)
/openbsd-current/gnu/usr.bin/cvs/
H A Dconfigure2459 echo $ac_n "checking for working const""... $ac_c" 1>&6
2460 echo "configure:2461: checking for working const" >&5
3028 echo $ac_n "checking for working vfork""... $ac_c" 1>&6
3029 echo "configure:3030: checking for working vfork" >&5
3442 echo $ac_n "checking for working fnmatch""... $ac_c" 1>&6
3443 echo "configure:3444: checking for working fnmatch" >&5
/openbsd-current/gnu/usr.bin/perl/ext/File-Find/lib/File/
H A DFind.pm841 preorder traversal, working from the bottom of the directory tree up
/openbsd-current/gnu/usr.bin/perl/utils/
H A Dperlbug.PL387 which will help the volunteers working to improve perl to categorize
514 might be relevant or might help the volunteers working to improve
/openbsd-current/gnu/usr.bin/perl/cpan/Digest-SHA/lib/Digest/
H A DSHA.pm636 before processing. This ensures consistent digest values when working
/openbsd-current/gnu/usr.bin/binutils/gdb/
H A Dconfigure1407 echo $ac_n "checking for working const""... $ac_c" 1>&6
1408 echo "configure:1409: checking for working const" >&5
1590 echo $ac_n "checking for working alloca.h""... $ac_c" 1>&6
1591 echo "configure:1592: checking for working alloca.h" >&5
1917 echo $ac_n "checking for working mmap""... $ac_c" 1>&6
1918 echo "configure:1919: checking for working mmap" >&5
5736 echo $ac_n "checking for working const""... $ac_c" 1>&6
5737 echo "configure:5738: checking for working const" >&5
5858 echo $ac_n "checking for working alloca.h""... $ac_c" 1>&6
5859 echo "configure:5860: checking for working alloc
[all...]
/openbsd-current/gnu/usr.bin/perl/Porting/
H A Dbisect-runner.pl200 # When did this code stop working in blead with these modules?
219 Which commit caused this example code to start working?
248 use it with a file outside of the working checkout, for example to test a
270 your working checkout is called F<perl>, a simple solution is to make a
613 on your computer while you're working, you can do something like
2718 # The trick is not to break *working* probes by
3350 # relate to getting make_patchnum.sh working,
3479 # default to searching for a working perl binary
/openbsd-current/gnu/usr.bin/binutils/ld/
H A Dconfigure947 echo $ac_n "checking for working aclocal""... $ac_c" 1>&6
948 echo "configure:949: checking for working aclocal" >&5
960 echo $ac_n "checking for working autoconf""... $ac_c" 1>&6
961 echo "configure:962: checking for working autoconf" >&5
973 echo $ac_n "checking for working automake""... $ac_c" 1>&6
974 echo "configure:975: checking for working automake" >&5
986 echo $ac_n "checking for working autoheader""... $ac_c" 1>&6
987 echo "configure:988: checking for working autoheader" >&5
999 echo $ac_n "checking for working makeinfo""... $ac_c" 1>&6
1000 echo "configure:1001: checking for working makeinf
[all...]
/openbsd-current/gnu/usr.bin/binutils/opcodes/
H A Dconfigure951 echo $ac_n "checking for working aclocal""... $ac_c" 1>&6
952 echo "configure:953: checking for working aclocal" >&5
964 echo $ac_n "checking for working autoconf""... $ac_c" 1>&6
965 echo "configure:966: checking for working autoconf" >&5
977 echo $ac_n "checking for working automake""... $ac_c" 1>&6
978 echo "configure:979: checking for working automake" >&5
990 echo $ac_n "checking for working autoheader""... $ac_c" 1>&6
991 echo "configure:992: checking for working autoheader" >&5
1003 echo $ac_n "checking for working makeinfo""... $ac_c" 1>&6
1004 echo "configure:1005: checking for working makeinf
[all...]
/openbsd-current/gnu/usr.bin/perl/cpan/Encode/
H A DEncode.pm798 Old byte-oriented programs should magically start working on the new
/openbsd-current/gnu/usr.bin/perl/lib/
H A Dwarnings.pm859 If you are used to working with a version of Perl prior to the
H A Doverload.t2370 'no overload "fallback" does not stop overload from working';
/openbsd-current/gnu/usr.bin/perl/cpan/Pod-Usage/lib/Pod/
H A DUsage.pm874 I<and> the script itself changes the current working directory
/openbsd-current/gnu/usr.bin/perl/cpan/IO-Compress/lib/IO/Compress/
H A DZip.pm1445 Also note that you should set the C<Efs> option to true if you are working
1543 C<Zip64> will be automatically set, as needed, if working with the one-shot
/openbsd-current/gnu/usr.bin/perl/
H A DConfigure15 # called "metaconfig". Rather than working with this copy of Configure,
2765 echo "Uh-oh, the C compiler '$cc' doesn't seem to be working." >&4
2779 echo "You seem to have a working gcc, though." >&4
2838 echo "Uh-oh, the C compiler '$cc' doesn't seem to be working." >&4
2841 You need to find a working C compiler.
4608 echo " Your C compiler \"$cc\" doesn't seem to be working!" >&4
10359 3) echo "Your long double math functions are working correctly." >&4 ;;
13530 3) echo "Hmm... non-blocking I/O does not seem to be working!";;
14247 : check for a working futimes
14250 echo "Checking if you have a working futime
[all...]
/openbsd-current/gnu/usr.bin/binutils/bfd/
H A Dconfigure938 echo $ac_n "checking for working aclocal-${am__api_version}""... $ac_c" 1>&6
939 echo "configure:940: checking for working aclocal-${am__api_version}" >&5
951 echo $ac_n "checking for working autoconf""... $ac_c" 1>&6
952 echo "configure:953: checking for working autoconf" >&5
964 echo $ac_n "checking for working automake-${am__api_version}""... $ac_c" 1>&6
965 echo "configure:966: checking for working automake-${am__api_version}" >&5
977 echo $ac_n "checking for working autoheader""... $ac_c" 1>&6
978 echo "configure:979: checking for working autoheader" >&5
990 echo $ac_n "checking for working makeinfo""... $ac_c" 1>&6
991 echo "configure:992: checking for working makeinf
[all...]
/openbsd-current/gnu/usr.bin/perl/win32/bin/
H A Dsearch.pl1633 you might consider copying the above, and then working from there.

Completed in 537 milliseconds

1234