* Basile STARYNKEVITCH wrote on Fri, Jul 03, 2009 at 03:51:00PM CEST:
>
> The patch below solves the issue, but the generated gtype-input.list
> contains too much empty blank lines. Any suggestions on how to solve
> this?
> +## compute the realpath of above GTFILES - keeping language tags as befo
On Fri, 2009-07-03 at 13:47 -0500, Joel Sherrill wrote:
> Hi,
>
> Apparently no one has hit this case. RTEMS does
> not have two error codes that g-socket.adb
> maps back. From s-oscons.ads:
>
>ESHUTDOWN : constant := -1; -- Cannot send once
> shutdown
>ESOCKTNOSUPPO
Eli Zaretskii writes:
> Some of the -print-* command-line switches either don't work as
> advertised or their documentation should be made more clear.
>
> All of the examples below are with the following version of GCC:
>
> gcc (GCC) 4.0.3 (Ubuntu 4.0.3-1ubuntu5)
> Copyright (C) 2006 Free
Basile STARYNKEVITCH writes:
>@: $(call write_entries_to_file,$(realpath $(GTFILES)),tmp-gi.list)
>$(SHELL) $(srcdir)/../move-if-change tmp-gi.list gtyp-input.list
>$(STAMP) s-gtyp-input
In general, one should try to avoid changing a user specified relative
path to an absolute path.
Ian Lance Taylor wrote:
> Eli Zaretskii > 3. -print-prog-name: Works only for some programs; manual text
>> misleading.
>>
>> The manual says:
>>
>> `-print-prog-name=PROGRAM'
>> Like `-print-file-name', but searches for a program such as `cpp'.
>>
>> It fails to say what pro
> Date: Sun, 05 Jul 2009 00:33:44 +0100
> From: Dave Korn
> CC: Eli Zaretskii , gcc@gcc.gnu.org
>
> >> e...@fencepost:~$ gcc -print-prog-name=cpp
> >> cpp
> >
> > Yeah, that's a clear doc bug. It used to work with "cpp", but not with
> > current gcc releases.
> >
> >> Similarly
Ian Lance Taylor wrote:
Basile STARYNKEVITCH writes:
@: $(call write_entries_to_file,$(realpath $(GTFILES)),tmp-gi.list)
$(SHELL) $(srcdir)/../move-if-change tmp-gi.list gtyp-input.list
$(STAMP) s-gtyp-input
In general, one should try to avoid changing a user specified relat
