Re: [PATCH] kconfig: detect if -lintl is needed when linking conf,mconf

On Mon, Jan 30, 2006 at 01:26:47PM -0500, Robb, Sam wrote:
>   This patch attempts to correct the problem by detecting whether or not
> NLS support requires linking with libintl.
>

Sigh. Can everyone please stop assuming gcc can output to /dev/null? On 
several platforms, ld tries to lseek in the output file, and fails if it 
can't.

Is there any reason this problem can't be solved the same way it is
for libcurses in menuconfig, by using gcc -print-filename? Or perhaps
using tempfile?

Cheers,
	Kyle
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH] kconfig: detect if -lintl is needed when linking conf,mconf
  - From: Andrew Morton <[email protected]>

References:
- [PATCH] kconfig: detect if -lintl is needed when linking conf,mconf
  - From: "Robb, Sam" <[email protected]>

Prev by Date: Re: The issues for agreeing on a virtualization/namespaces implementation.
Next by Date: Re: [linux-pm] Re: [PATCH, RFC] [1/3] Generic in-kernel AC status
Previous by thread: [PATCH] kconfig: detect if -lintl is needed when linking conf,mconf
Next by thread: Re: [PATCH] kconfig: detect if -lintl is needed when linking conf,mconf
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]