Re: Cannot build 21.4.16 under cygwin (gcc 3.3.3)

Henry, On Sun, Jan 09, 2005 at 03:28:11PM +, Henry S. Thompson wrote: > Now I had rebased those two by hand (because for reasons I can't now > figure out rebaseall didn't do them -- pbly because I installed GTK > 'by hand' as it were, not via the package mechanism), Bingo! Use rebaseall's "-

Re: Cannot build 21.4.16 under cygwin (gcc 3.3.3)

Vin Shelton writes: > [EMAIL PROTECTED] (Henry S. Thompson) writes: > >> >> But of course then I'm stuck with other code that won't run because of >> the two-different-bases problem. >> >> Anyway, thanks _very_ much for your help, it sounds like the xemacs >> folks are really where this needs to b

Re: Cannot build 21.4.16 under cygwin (gcc 3.3.3)

[EMAIL PROTECTED] (Henry S. Thompson) writes: > > But of course then I'm stuck with other code that won't run because of > the two-different-bases problem. > > Anyway, thanks _very_ much for your help, it sounds like the xemacs > folks are really where this needs to be solved. Point is, this is a

Re: Cannot build 21.4.16 under cygwin (gcc 3.3.3)

Jason Tishler writes: > On Thu, Jan 06, 2005 at 02:02:20PM +, Henry S. Thompson wrote: >> Jason Tishler writes: >> > If you get any errors due to DLLs being in-use or read-only, >> > then take the appropriate action and rerun rebaseall. >> > Otherwise, you run the risk of fork() fa

Re: Cannot build 21.4.16 under cygwin (gcc 3.3.3)

Henry, On Thu, Jan 06, 2005 at 02:02:20PM +, Henry S. Thompson wrote: > Jason Tishler writes: > > If you get any errors due to DLLs being in-use or read-only, > > then take the appropriate action and rerun rebaseall. > > Otherwise, you run the risk of fork() failing. > > /sur/bin/

Re: Cannot build 21.4.16 under cygwin (gcc 3.3.3)

Jason Tishler writes: > Henry, > > On Wed, Jan 05, 2005 at 11:10:26PM +, Henry S. Thompson wrote: >> Jason Tishler <[EMAIL PROTECTED]> writes: > > Sigh. More fodder for the spammers... :,( Damn. Sorry about that. > 1. shutdown all Cygwin processes > 2. start bash (do not us

Re: Cannot build 21.4.16 under cygwin (gcc 3.3.3)

Henry, On Wed, Jan 05, 2005 at 11:10:26PM +, Henry S. Thompson wrote: > Jason Tishler <[EMAIL PROTECTED]> writes: Sigh. More fodder for the spammers... :,( > > On Wed, Jan 05, 2005 at 05:22:48PM +, Henry S. Thompson wrote: > >> Ah, but rebasing cygwin1.dll _did_ fix the problem (once I

Re: Cannot build 21.4.16 under cygwin (gcc 3.3.3)

Jason Tishler <[EMAIL PROTECTED]> writes: > Henry, > > On Wed, Jan 05, 2005 at 05:22:48PM +, Henry S. Thompson wrote: >> > Suggestions? I tried using Jason Tishler's rebase on xemacs.exe, >> > but it refused. . . >> >> Ah, but rebasing cygwin1.dll _did_ fix the problem (once I had tracked >>

Re: Cannot build 21.4.16 under cygwin (gcc 3.3.3)

Henry, On Wed, Jan 05, 2005 at 05:22:48PM +, Henry S. Thompson wrote: > > Suggestions? I tried using Jason Tishler's rebase on xemacs.exe, > > but it refused. . . > > Ah, but rebasing cygwin1.dll _did_ fix the problem (once I had tracked > down cygserver and cygrunsrv in the Process Manager

Re: Cannot build 21.4.16 under cygwin (gcc 3.3.3)

[EMAIL PROTECTED] (Henry S. Thompson) writes: > [see subject] > Suggestions? I tried using Jason Tishler's rebase on xemacs.exe, but > it refused. . . Ah, but rebasing cygwin1.dll _did_ fix the problem (once I had tracked down cygserver and cygrunsrv in the Process Manager and nuked them). ht

Re: Cannot build 21.4.16 under cygwin (gcc 3.3.3)

For reasons I don't understand, the text content of the referenced message does not show up in my mailreader (gnus) or the archive [1], so here it is again. See the archive [1] for cygcheck output. > ./configure --without-x11 --pdump --with-modules=no . . . > make . . . ./xemacs -nd -batch -l