On Wed, 22 Sep 2004, William Coleda wrote:

> Attached, find a patch that does a first pass of this.
[ . . . ]

>  # OTHER FILE GROUPS:
> @@ -412,6 +440,9 @@
>  .c$(O) :
>       @$(PERL) tools/dev/cc_flags.pl ./CFLAGS $(CC) "" $(CFLAGS) -I$(@D) 
> ${cc_o_out}$@ -c $<
> +%.pbc:%.imc
> +     @.${slash}$(TEST_PROG) -o $@ $<
> +

Is there any important reason for the leading '@' there?  When I tried
this patch, the result was the following (split to fix up the long
lines, and yes, all those mostly-useless -L options are doubled for
some unknown reason)

    src/nci_test.c
    cc -G -L/usr/lib -L/usr/ccs/lib -L/opt/SUNWspro/SC4.2/lib -L/usr/local/lib \
          -L/usr/lib -L/usr/ccs/lib -L/opt/SUNWspro/SC4.2/lib -L/usr/local/lib \
        -o runtime/parrot/dynext/libnci.so src/nci_test.o
    GNUmake: *** [runtime/parrot/library/libpcre.pbc] Segmentation Fault (core dumped)

More generally, I think the build process should generally avoid hiding
what's going on until we're *sure* that it works correctly nearly
everywhere, so while you're in that section of root.in, you probably ought
to remove the '@' before the preceeding rule as well.

-- 
    Andy Dougherty              [EMAIL PROTECTED]

Reply via email to