[bug #25713] Please note CPPFLAGS required to build on Tru64

Follow-up Comment #10, bug #25713 (project make): Paul, I just tried 3.81.91 with the same build environment as before, and everything builds successfully. "make check" yields a couple of anomalies, however: targets/ONESHELL ok (5 passed) targets/PH

[bug #25713] Please note CPPFLAGS required to build on Tru64

Update of bug #25713 (project make): Item Group: Documentation => Build/Install Status:None => Fixed Assigned to:None => psmith Open/Closed:

[bug #25713] Please note CPPFLAGS required to build on Tru64

Follow-up Comment #8, bug #25713 (project make): I believe bsd_signal() is detected because the configure script checks whether the function links, not whether the headers provide a prototype. The bsd_signal() check itself, as recorded in config.log, is pretty perfunctory: configure:7340: chec

[bug #25713] Please note CPPFLAGS required to build on Tru64

Follow-up Comment #7, bug #25713 (project make): OK, the problem seems to be that in config.h, we have HAVE_BSD_SIGNAL set. But, in the output of the preprocessor for main.c that function is not defined anywhere. So, the C compiler gives it the default prototype where it returns int, instead of

[bug #25713] Please note CPPFLAGS required to build on Tru64

Follow-up Comment #6, bug #25713 (project make): I'm attaching a copy of config.h, the bsd_signal() man page, and the preprocessed form of main.c. (I'm using the vendor's compiler, so it's just straight "cc -E", but hopefully that'll show what you need.) Relevant tidbits: #define HAVE_BSD_SI

[bug #25713] Please note CPPFLAGS required to build on Tru64

Follow-up Comment #5, bug #25713 (project make): Hm, that's interesting. Can you check the status of HAVE_BSD_SIGNAL and HAVE_SIGACTION in config.h? Attaching it would be very helpful. Can you check your system to see if there's a man page for bsd_signal() and if so, what it says the calling a

[bug #25713] Please note CPPFLAGS required to build on Tru64

Follow-up Comment #4, bug #25713 (project make): Okay, I pulled down make-3.81.90 and built on the Tru64 system without setting any flags. It looks like only one file is failing now, albeit with a similar error to what I saw before. Here's the output from a second pass of "make -i": make all-re

[bug #25713] Please note CPPFLAGS required to build on Tru64

Follow-up Comment #3, bug #25713 (project make): A log would be helpful. The problem is that from what you say, it's not that functions are missing. It seems more like there are errors in the system headers; for example if u_long is not available when compiling getloadavg.c then why not? I can

[bug #25713] Please note CPPFLAGS required to build on Tru64

Follow-up Comment #2, bug #25713 (project make): config.guess returns "alphaev56-dec-osf4.0g". I would add checks for the missing functions to the configure script, and if not have logic that automatically tries the feature test macros in case the functions aren't found, then at least a note ale

[bug #25713] Please note CPPFLAGS required to build on Tru64

Follow-up Comment #1, bug #25713 (project make): I'm not sure the best way to handle this. What's the triplet printed by running "config.guess" on your system? ___ Reply to this item at: _

[bug #25713] Please note CPPFLAGS required to build on Tru64

URL: Summary: Please note CPPFLAGS required to build on Tru64 Project: make Submitted by: iskunk Submitted on: Thu 26 Feb 2009 05:08:14 AM GMT Severity: 3 - Normal Item