mjy@sdti.UUCP (Michael J. Young) (11/01/88)
Whenever I try to run 'make' on a makefile that contains nested
'make' commands, I get a core dump. Has anyone else observed this
behavior? Setting SHELL=/bin/sh doesn't seem to make any difference.
Is this a bug in 'make'? What am I missing?
--
Mike Young
Software Development Technologies, Inc., Sudbury MA Tel: +1 508 443 5779
Internet: mjy@sdti.sdti.com UUCP: {harvard,mit-eddie}!sdti!mjybill@ssbn.WLK.COM (Bill Kennedy) (11/02/88)
In article <322@sdti.UUCP> mjy@sdti.UUCP (Michael J. Young) writes: | |Whenever I try to run 'make' on a makefile that contains nested |'make' commands, I get a core dump. Has anyone else observed this I get the same thing. If you just visit the directory where the next level make is and make again it works OK. It's repeatable and it doesn't exist in AT&T for the PC 6300 PLUS. If anyone has a workaround I'd sure like to hear about it. -- Bill Kennedy usenet {killer,att,rutgers,sun!daver,uunet!bigtex}!ssbn!bill internet bill@ssbn.WLK.COM
misko@abhg.UUCP (William Miskovetz) (11/02/88)
In article <322@sdti.UUCP>, mjy@sdti.UUCP (Michael J. Young) writes: > > Whenever I try to run 'make' on a makefile that contains nested > 'make' commands, I get a core dump. Has anyone else observed this > behavior? I also have this problem. Another problem I have with make which causes a core dump is running make as root. If I am root, attempting to run make always coredumps. This is V/AT Version 1.3 of the Software Developement. Bill Miskovetz {uunet!lll-winken, lll-lcc, pyramid}!abhg!misko
" Maynard) (11/02/88)
In article <322@sdti.UUCP> mjy@sdti.UUCP (Michael J. Young) writes: >Whenever I try to run 'make' on a makefile that contains nested >'make' commands, I get a core dump. Has anyone else observed this >behavior? Setting SHELL=/bin/sh doesn't seem to make any difference. >Is this a bug in 'make'? What am I missing? Good question. I think this is the cause of the failure I mentioned to John Plocher a few days ago, where I can't get news 3.0 to compile - it uses nested makes, in part to make the makefile for a subsequent make. It's really slick, but SV/AT 2.3 throws up all over it (that is, when my system doesn't double panic first). -- Jay Maynard, EMT-P, K5ZC, PP-ASEL | Never ascribe to malice that which can uucp: uunet!nuchat! (eieio)| adequately be explained by stupidity. hoptoad!academ!uhnix1!splut!jay +---------------------------------------- {killer,bellcore}!tness1! | "Dukakis" is just Greek for "Mondale".
friedl@vsi.COM (Stephen J. Friedl) (11/03/88)
> > Whenever I try to run 'make' on a makefile that contains nested > > 'make' commands, I get a core dump. Has anyone else observed this > > behavior? > > I also have this problem. Another problem I have with make which causes > a core dump is running make as root. If I am root, attempting to run > make always coredumps. This is V/AT Version 1.3 of the Software Developement. Hi Folks, We had the second problem too, and tracked down to a bug in make that was triggered by Aspen ksh. ksh exports the _ environment variable, and when make is looking at the env for variables, it croaks on the non-alphanum character. A short-term fix should be to make a wrapper program that scans the environment, drops the _ variable, and then calls the real make. This bug, along with the source-code fix, was sent to uport in early May. Steve -- Steve Friedl V-Systems, Inc. +1 714 545 6442 3B2-kind-of-guy friedl@vsi.com {backbones}!vsi.com!friedl attmail!vsi!friedl ----Nancy Reagan on 120MB SCSI cartridge tape: "Just say *now*"----
mjy@sdti.UUCP (Michael J. Young) (11/09/88)
In article <927@vsi.COM> friedl@vsi.COM (Stephen J. Friedl) writes: >> > Whenever I try to run 'make' on a makefile that contains nested >> > 'make' commands, I get a core dump. Has anyone else observed this >> > behavior? > We had the second problem too, and tracked down to a bug in >make that was triggered by Aspen ksh. ksh exports the _ >environment variable, and when make is looking at the env for >variables, it croaks on the non-alphanum character. Yup, turns out that was my problem as well. I've been running ksh for a while now. I thought just setting SHELL=/bin/sh and maybe invoking /bin/sh as a subshell would do the trick, but it didn't. When I change my login shell to /bin/sh, make works fine. Will Microport be supplying a fixed make on the bbs anytime soon? Please? -- Mike Young Software Development Technologies, Inc., Sudbury MA Tel: +1 508 443 5779 Internet: mjy@sdti.sdti.com UUCP: {harvard,mit-eddie}!sdti!mjy
rick@pcrat.UUCP (Rick Richardson) (11/11/88)
In article <327@sdti.UUCP> mjy@sdti.UUCP (0006-Michael J. Young) writes: >Yup, turns out that was my problem as well. I've been running ksh for >a while now. I thought just setting SHELL=/bin/sh and maybe invoking >/bin/sh as a subshell would do the trick, but it didn't. When I change >my login shell to /bin/sh, make works fine. No need to change your login shell, just $ sh $ unset <offending variable name> $ SHELL=/bin/sh; export SHELL $ exec make <any args you need> Obviously, you can wrap make with a suitable shell script that does the same. -- Rick Richardson | JetRoff "di"-troff to LaserJet Postprocessor|uunet!pcrat!dry2 PC Research,Inc.| Mail: uunet!pcrat!jetroff; For anon uucp do:|for Dhrystone 2 uunet!pcrat!rick| uucp jetroff!~jetuucp/file_list ~nuucp/. |submission forms. jetroff Wk2200-0300,Sa,Su ACU {2400,PEP19200} 12013898963 "" \r ogin: jetuucp