Home
last modified time | relevance | path

Searched hist:cfe0a42b (Results 1 – 25 of 54) sorted by relevance

123

/dragonfly/gnu/usr.bin/gdb/libreadline/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/lib/libedit/readline/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/games/hunt/hunt/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/games/colorbars/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/usr.bin/tabs/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/gnu/usr.bin/gdb/kgdb/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/lib/libncurses/libpanel/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/usr.bin/tic/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/lib/libedit/libedit/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/lib/libncurses/libncurses/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/gnu/usr.bin/gdb/libgdb/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/
H A DMakefile_upgrade.inccfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/libexec/telnetd/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/sbin/vinum/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/usr.sbin/tzsetup/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/usr.sbin/watch/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/usr.bin/msgs/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/usr.bin/ncal/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/usr.bin/systat/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/usr.bin/talk/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/usr.bin/telnet/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/usr.bin/top/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/usr.bin/tput/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/usr.bin/tset/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon
/dragonfly/usr.bin/ul/
H A DMakefilecfe0a42b Thu Nov 17 20:46:24 GMT 2016 John Marino <draco@marino.st> Relocate readline and ncurses headers to /usr/include/priv

Having public headers for private libraries can cause confusion for
software that assumes the presence of headers leads to the availability
of the libraries.

Discussed-with: dillon

123