Daniel Jacobowitz <[EMAIL PROTECTED]> writes:

|> SIGRTMIN has changed behavior recently in 2.3; at the same time as:
|> 
|> 2002-09-18  Ulrich Drepper  <[EMAIL PROTECTED]>
|> 
|>         * signal/allocrtsig.c: Move to...
|>         * sysdeps/generic/allocrtsig.c: ...here.  New file.
|> 
|> as far as I can tell.
|> 
|> The problem is something I ran into in GDB today: the location of a
|> source file overrides the normal search path.  If a file in
|> sysdeps/generic/ includes a header using "", the copy in
|> sysdeps/generic/ will win.  So we get sysdeps/generic/testrtsig.h
|> instead of the sysdeps/unix/sysv/linux/testrtsig.h, and
|> kernel_has_rtsig always returns 0.

The right fix is probably to change "..." to <...>.  Could you try that
please?

Andreas.

-- 
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 N�rnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to