[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: So, what's up with the XFree86 4.0 .debs?

On Sun, Mar 12, 2000 at 01:16:55PM -0500, Branden Robinson wrote:
> [1] The makedepend program gets stuck in an infinite loop when attempting
> to generate dependencies in xc/programs/xterm.  One of Tom Dickey's
> patches, #130 or #131, is probably the culprit since I think these are the
> only two changes that happened to the xterm sources between 3.9.18 and 4.0.


Just a little extra info - this is a mail I was composing before I read
your mail (obviously I realise that this is low priority till woody). 

I have two potato systems [Sys1 hasn't been updated for a while and
seems to have gone a little mouldy ;]

***X builds on Sys1***, but on Sys2 makedepend goes into an infinite 
loop when running in the xc/programs/xterm directory. [as you noted]

You've probably done this your self:

The end of a strace log gives:
[big snippage]
stat("./unctrl.h", 0xbffff67c)          = -1 ENOENT (No such file or[snip]
stat("/usr/local/lib/gcc-include/unctrl.h", 0xbffff67c) = -1 ENOENT[snip]
stat("/usr/include/unctrl.h", {st_mode=S_IFREG|0644, st_size=2957,...}) = 0
open("/usr/include/unctrl.h", O_RDONLY) = 5
fstat(5, {st_mode=S_IFREG|0644, st_size=2957, ...}) = 0
read(5, "/*******************************"..., 2957) = 2957
close(5)                                = 0
--- SIGINT (Interrupt) ---

Obviously, the -1 ENOENT's are fine - makedepend is just searching for
files in various paths. The infinite loop always occurs after unctrl.h.

Here are some diferences between my two systems. Let me know if you
want more info.

Pckg            Sys1(builds)    Sys2(fails)
~~~~            ~~~~~~~~~~~~    ~~~~~~~~~~~
libc6           2.1.3-4         2.1.3-7
libc6-dev       2.1.3-4         2.1.3-7
ncurses-base    5.0-4           5.0-6
libncurses5-dev 5.0-6*          5.0-6
gcc             2.95.2-6        2.95.2-7
make            3.78.1-6        3.78.1-7

* yes, there is a reason - I was forcing various -dev versions to see
if I could reproduce the error on Sys1...


Reply to: