> If there are problems building a new package, the first resource is LFS
> or BLFS of course, what else? So besides LFS is missing some basic
> Cygwin packages it is already the best guide available when building new
> packages. Just rename it;)
Hehehe, precisely what I do, too. I figure they'
> Maybe a better question would be, "Why do you feel it would not be
> possible?" Every Cygwin binary package is compiled from source by the
> maintainer (obviously) and includes a -src package that should build
> cleanly, else there's a packaging problem. So in that sense you can
> build everyth
> Dunno what you're up to but I'm running syslog from inetutils just
> fine. Cygwin tries to syslog on /dev/log if it's available (it's
> usually created by syslog) and there's also a /dev/kmsg pipe which
> would be utilized for kernel messages ... *if* Cygwin would have
> anything like kernel mes
Just a random thought: as a long time Linux from Scratch user, I'm
intrigued about the possibility of building a Cygwin "distribution"
from scratch. Typically when I build an LFS install, I take a lot of
time building each package to make sure every possible feature is
available (for example, curr
I've seen lots of people who got syslog-ng working on their cygwin
boxes. Latest version compiles just fine out of the box, but not sure
what I should put in for a source in the syslog-ng.conf? Default for
Linux is to use /proc/kmesg, but we don't have one under Cygwin. Are
Cygwin installs limit
> This is the wrong approach, use the linking flag -no-undefined instead.
I've been searching for a couple of days now for how you're supposed
to do that. Set LDFLAGS?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Docume
> > net use z: share\\fs2 password /USER:qadomain\\Administrator
> > /PERSISTENT:No
Change that to /persistent:yes
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:
Crossposted from Apache-users:
For the last couple of days, I've been trying to get Apache 2.0.54 to
compile in a Cygwin environment. Depending various config options, I
receive various levels of success. The configure line I'm using is:
./configure --enable-module=so --prefix=/usr
--enable-mo
8 matches
Mail list logo
