Date: Mon, 18 May 2015 08:59:02 -0400 From: "John D. Hendrickson" <johnandsara2@cox.net> To: "Julian H. Stacey" <jhs@berklix.com> Cc: x11@freebsd.org Subject: Re: ports/devel/gccmakedep Message-ID: <5559E216.8090602@cox.net> In-Reply-To: <VPyW1q00W2X408g01PyXTm> References: <VPyW1q00W2X408g01PyXTm>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian H. Stacey wrote:
> x11@freebsd.org is MAINTAINER= for this ...
>
> with current src & ports:
> /usr/ports/devel/gccmakedep cat ../../.ctm*
> ports-cur 10906
> 11.0-CURRENT /dev/pts/6 jhs 11 lapr/usr/ports/devel/gccmakedep cat ../../.svn*
> 386470
> 11.0-CURRENT /dev/pts/6 jhs 12 lapr/usr/ports/devel/gccmakedep
>
> cd /usr/ports/devel/gccmakedep ; make
> ===> Applying FreeBSD patches for gccmakedep-1.0.3
> File to patch: ^D
> No file found--skip this patch? [n] y
> 1 out of 1 hunks ignored--saving rejects to Oops.rej
> => Patch patch-gccmdep.cpp failed to apply cleanly.
>
> It should not patch
> gccmdep.cpp
> but patch
> gccmakedep.in
>
> The patch content is also obsolete, there is no
> CC=CCCMD
> but is a
> CC="@CC@"
>
> I append a new patch file, which builds.
> BUT I have Not bothered to analyse what what CC is supposed to be doing,
> sufficient for me that it no longer breaks.
> Others should please review this.
>
> ---------
> *** gccmakedep.in.orig Wed May 21 20:20:00 2014
> --- gccmakedep.in Mon May 18 13:49:16 2015
> ***************
> *** 9,15 ****
> #
>
> TMP=mdep$$.tmp
> ! CC="@CC@"
> RM="rm -f"
> LN="ln"
> MV="mv"
> --- 9,16 ----
> #
>
> TMP=mdep$$.tmp
> ! # CC="@CC@"
> ! CC=${CC:-CCCMD}
> RM="rm -f"
> LN="ln"
> MV="mv"
> --------
>
> Cheers,
> Julian
> --
> Julian Stacey, BSD Linux Unix C Sys Eng Consultant Munich http://berklix.com
> Indent previous with "> ". Reply Below as a play script.
> Send plain text, Not quoted-printable, HTML, or base64.
> _______________________________________________
> freebsd-x11@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-x11
> To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org"
>
i'm unhappy with a microsoft friendly win32 team hacking gcc etc
after much preparation (gcc glibc etc compiling chain setup) and what i
thought was compiling on one host, i now get this when running on a new
LFS (linux from scratch):
coreutils-8.5)
# configure message:
# <wchar.h> cannot be used with this compiler
# a known problem of glibc <= 2.5 with gcc >= 4.3 in
# ls.c: In function 'abmon_init':
# ls.c:1048: error: 'for' loop initial declarations are only allowed
in C99 mo
# ls.c:1048: note: use option -std=c99 or -std=gnu99 to compile your code
# i check for header damage: but no, headers are diff good
The above had worked before i have no idea how: gnu89 is broken so is
gnu99 using gcc-4.4.5 (though 3.5 was on the system - i beleived it not
in use)
they hacked ls(1)
abmon_init(void) {
...
/* int i; */
for (int i=0; i<12; ++i)
WHICH WAS THE ONLY thing holding up the build (other fixes aside) (until
install). i think it's absolutely criminal they take what works (ls.c)
and break it so there is not chance of it working without delay.
i also had to do this (also set allot of environment and compile
options) to even start.
[ ! -f coreutils-8.5/src/Makefile.in.old.old ] && {
cp coreutils-8.5/src/Makefile.in coreutils-8.5/src/Makefile.in.old.old
cat << EOF | ed -s
r coreutils-8.5/src/Makefile.in
/cu_install_program = ..ginstall/
.,.s/ = .*/ = @INSTALL_PROGRAM@/
w coreutils-8.5/src/Makefile.in
q
EOF
}
i'm wishing to try BSD sometime - problem is time :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5559E216.8090602>