<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Mark,</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
You could be missing a header file or maybe a flag to the linker/compiler for a particular library (e.g. -lm).</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
P.S. Here is a tip. For older Macs, like those running Lion, one often needs to add the following to the Portfile to ensure that the linker will link against stdc++:</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<blockquote style="margin-top:0;margin-bottom:0">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<b>configure.ldflags-append "-stdlib=${configure.cxx_stdlib}</b><br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
If you do not include it, one will often see the following when trying to build and link on the older Macs:</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<blockquote style="margin-top:0;margin-bottom:0">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<span style="color:rgb(32, 31, 30);font-family:"Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, "system-ui", Roboto, "Helvetica Neue", sans-serif;font-size:15px;background-color:rgb(255, 255, 255);display:inline !important">ld: symbol(s)
not found for architecture x86_64</span><br>
</div>
</blockquote>
</blockquote>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<span style="color:rgb(32, 31, 30);font-family:"Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, "system-ui", Roboto, "Helvetica Neue", sans-serif;font-size:15px;background-color:rgb(255, 255, 255);display:inline !important"><br>
</span></div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<span style="color:rgb(32, 31, 30);font-family:"Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, "system-ui", Roboto, "Helvetica Neue", sans-serif;font-size:15px;background-color:rgb(255, 255, 255);display:inline !important">Rob</span></div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Mark Brethen <mark.brethen@gmail.com><br>
<b>Sent:</b> August 2, 2022 3:00 PM<br>
<b>To:</b> Robert Kennedy <amtor@hotmail.com><br>
<b>Cc:</b> MacPorts Developers <macports-dev@lists.macports.org><br>
<b>Subject:</b> Re: include files for cgxCADTools</font>
<div> </div>
</div>
<div class="" style="word-wrap:break-word; line-break:after-white-space">I stripped those lines but there were some glitches in the build. First the Makefile only defines CC but the source is c++.
<div class=""><br class="">
</div>
<div class="">:info:build /opt/local/include/opencascade/Standard_Handle.hxx:75:19: warning: rvalue references are a C++11 extension [-Wc++11-extensions]</div>
<div class=""><br class="">
</div>
<div class="">Second, I’m missing an include somewhere.</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">:info:build plotTopology() in CadReader.o</div>
<div class="">:info:build std::__1::basic_stringstream<char, std::__1::char_traits<char>, std::__1::allocator<char> >::~basic_stringstream() in CadReader.o</div>
<div class="">:info:build ...</div>
<div class="">:info:build ld: symbol(s) not found for architecture x86_64</div>
<div class="">:info:build clang: error: linker command failed with exit code 1 (use -v to see invocation)</div>
<div class="">:info:build make: *** [tmain] Error 1</div>
</div>
<div class=""><br class="">
</div>
<div class="">
<div class=""><br class="">
</div>
<div class=""><a href="https://pastebin.com/9xYCd74R" class="">https://pastebin.com/9xYCd74R</a></div>
<div class="">
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<div class="">
<div class="">Mark Brethen</div>
<div class=""><a href="mailto:mark.brethen@gmail.com" class="">mark.brethen@gmail.com</a></div>
<div class=""><br class="">
</div>
<br class="x_Apple-interchange-newline">
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Aug 2, 2022, at 12:34 PM, Mark Brethen <<a href="mailto:mark.brethen@gmail.com" class="">mark.brethen@gmail.com</a>> wrote:</div>
<br class="x_Apple-interchange-newline">
<div class="">
<div class="" style="word-wrap:break-word; line-break:after-white-space">Rob,
<div class=""><br class="">
</div>
<div class="">There is the line '<span class="" style="font-family:Menlo; font-size:11px">.PHONY: depend clean</span>' but 'make all’ only calls $(MAIN). </div>
<div class="">
<div class=""></div>
</div>
</div>
<span id="x_cid:FD84E265-B15D-4BC0-8470-1BE1D271ED72"><Makefile></span>
<div class="" style="word-wrap:break-word; line-break:after-white-space">
<div class="">
<div class=""></div>
</div>
</div>
<span id="x_cid:625E843F-B49D-4283-A157-2C0F0E2ED761"><patch-CadReader-build.diff></span>
<div class="" style="word-wrap:break-word; line-break:after-white-space">
<div class="">
<div class=""></div>
<div class=""><br class="x_webkit-block-placeholder">
</div>
<div class="">
<div class="">Thanks,</div>
<div class="">Mark</div>
<div class=""><br class="">
</div>
<br class="x_Apple-interchange-newline">
</div>
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On Aug 2, 2022, at 9:34 AM, Robert Kennedy <<a href="mailto:amtor@hotmail.com" class="">amtor@hotmail.com</a>> wrote:</div>
<br class="x_Apple-interchange-newline">
<div class="">
<div class="x_elementToProof" style="font-style:normal; font-variant-caps:normal; font-weight:normal; letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
Mark,</div>
<div class="x_elementToProof" style="font-style:normal; font-variant-caps:normal; font-weight:normal; letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
<br class="">
</div>
<div class="x_elementToProof" style="font-style:normal; font-variant-caps:normal; font-weight:normal; letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
To be clear, I would first try patching the Makefile by deleting all the system header dependencies from the Makefile and then see if Macports will build the project. But make sure the Makefile lists the location of all the directories where the header files
are located. (I typically place them in $(INCLUDES)). And make sure the rules contain $(INCLUDES).</div>
<div class="x_elementToProof" style="font-style:normal; font-variant-caps:normal; font-weight:normal; letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
<br class="">
</div>
<div class="x_elementToProof" style="font-style:normal; font-variant-caps:normal; font-weight:normal; letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
<b class="" style="background-color:rgb(255,255,255)">You typically do not need to list the directories of the system header files<span class="x_Apple-converted-space"> </span></b><span class="" style="background-color:rgb(255,255,255); display:inline!important">because
the compiler typically knows where they are (which as you know may change from MacOS to MacOS).</span><br class="">
</div>
<div class="x_elementToProof" style="font-style:normal; font-variant-caps:normal; font-weight:normal; letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
<span class="" style="background-color:rgb(255,255,255); display:inline!important"><br class="">
</span></div>
<div class="x_elementToProof" style="font-style:normal; font-variant-caps:normal; font-weight:normal; letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
<span class="" style="background-color:rgb(255,255,255); display:inline!important">If you want to know why, keep reading....</span></div>
<div class="x_elementToProof" style="font-style:normal; font-variant-caps:normal; font-weight:normal; letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
<br class="">
</div>
<div class="x_elementToProof" style="font-style:normal; font-variant-caps:normal; font-weight:normal; letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
Typically "make" only needs to know the following to build the initial Project from scratch:</div>
<div class="x_elementToProof" style="font-style:normal; font-variant-caps:normal; font-weight:normal; letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
<div class="">
<ol class="">
<li class="" style=""><span class=""><span class=""> The rules that define what source code files are needed to build each object and a rule for linking the object files and <span class="" style="text-align:start; background-color:rgb(255,255,255); display:inline!important">the
location of the directories for the header files (e.g. main.h). </span></span><br class="">
</span></li></ol>
</div>
<blockquote class="" style="margin-top:0px; margin-bottom:0px">
<div class=""><span class="">e.g</span></div>
</blockquote>
<div class=""><span class=""><br class="">
</span></div>
<div class=""><span class=""><span class=""> <span class="" style="background-color:rgb(255,255,255); display:inline!important">INCLUDES := -I./ </span></span></span></div>
<blockquote class="" style="margin-top:0px; margin-bottom:0px">
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
<div class=""><span class=""><span class="">.PHONY all</span></span></div>
</blockquote>
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
<div class=""><span class=""><span class=""><span class=""> </span><span class=""> all: edit</span></span></span></div>
<div class=""><span class=""><span class=""><span class=""> </span><br class="">
</span></span></div>
<blockquote class="" style="margin-top:0px; margin-bottom:0px">
<div class=""><span class=""><span class="">edit: main.o kdb.o</span></span></div>
</blockquote>
<blockquote class="" style="margin-top:0px; margin-bottom:0px">
<blockquote class="" style="margin-top:0px; margin-bottom:0px">
<div class=""><span class="" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">$(CC) $(LDFLAGS) </span><span class="" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">-o main.o kbd.o</span></div>
</blockquote>
</blockquote>
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
<div class=""><span class=""><span class=""> </span></span><span class="" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">main.o: main.c myfunc.c</span></div>
<blockquote class="" style="margin-top:0px; margin-bottom:0px">
<blockquote class="" style="margin-top:0px; margin-bottom:0px">
<div class=""><span class="" style="font-size:12pt; font-family:Calibri,Helvetica,sans-serif">$(CC) $(CFLAGS) $(INCLUDES)</span><span class="" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt"><span class="x_Apple-converted-space"> </span>-c
main.c myfunc.c</span></div>
<div class=""><span class="" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt"><br class="">
</span></div>
</blockquote>
<div class=""><span class="" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">kbd.o: kbd.c</span></div>
<blockquote class="" style="margin-top:0px; margin-bottom:0px">
<div class=""><span class="" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">$(CC) $(CFLAGS) $(INCLUDES)</span><span class="" style="font-size:12pt; font-family:Calibri,Helvetica,sans-serif"> -c kbd.c</span></div>
</blockquote>
</blockquote>
<blockquote class="" style="margin-top:0px; margin-bottom:0px">
<div class=""><br class="">
</div>
</blockquote>
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
<div class=""><span class=""><span class="">In the example above, the directories of the header files are in listed in $(INCLUDES).</span></span> </div>
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
<div class=""><span class=""><b class="">You do not need to list the directories of the system header files in $(INCLUDES)</b><span class="x_Apple-converted-space"> </span>because the compiler knows where they are (which as you know may change from MacOS to
MacOS).</span></div>
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
<div class=""><span class=""><span class="">Ideally, if you know that a particular header is a dependency for an object, it is better to list it in the rule (e.g. main.o: main.c myfunc.c main.h) OR create a separate rule for the header dependency:</span></span></div>
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
<blockquote class="" style="margin-top:0px; margin-bottom:0px">
<div class=""><span class=""><span class="">main.o: main.h</span></span></div>
</blockquote>
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
<div class=""><b class="">But these header dependency rules are typically not needed to build the initial project from scratch!</b> These rules exist so "make" will only<span class="x_Apple-converted-space"> </span><b class=""><u class="">rebuild</u></b><span class="x_Apple-converted-space"> </span>the
minimum number of objects when a header file has changed.</div>
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
<div class=""><span class=""><span class="">E.g. If I change header.h and then run "make all" again in the above example, make will only recompile main.o and then it will link main.o with the previously built kbd.o. kbd.o does not need to be recompiled.
This saves time. Great for development!</span></span></div>
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
<div class=""><span class=""><span class=""><span class="" style="background-color:rgb(255,255,255); display:inline!important">Macports does not do this. It typically will rebuild the whole project from scratch. (i.e. build all the objects and then link them
into the final product).</span></span></span></div>
<div class=""><span class=""><span class=""><span class="" style="background-color:rgb(255,255,255); display:inline!important"><br class="">
</span></span></span></div>
<div class=""><span class=""><span class=""><span class="" style="background-color:rgb(255,255,255); display:inline!important">In my view, Macports was not designed for development but for building a finished project and making a binary package. (i.e. package
management)</span></span></span></div>
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
<div class=""><span class=""><span class="">If you are still having problems, please EMAIL me the Makefile and I will take a look.</span></span></div>
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
<div class=""><span class=""><span class="">RobK88</span></span></div>
</div>
<div id="x_appendonsend" class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-variant-caps:normal; font-weight:normal; letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none">
</div>
<hr tabindex="-1" class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-variant-caps:normal; font-weight:normal; letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; display:inline-block; width:354.75px">
<span class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-variant-caps:normal; font-weight:normal; letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none; float:none; display:inline!important"></span>
<div id="x_divRplyFwdMsg" dir="ltr" class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-variant-caps:normal; font-weight:normal; letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none">
<font face="Calibri, sans-serif" class="" style="font-size:11pt"><b class="">From:</b><span class="x_Apple-converted-space"> </span>macports-dev <<a href="mailto:macports-dev-bounces@lists.macports.org" class="">macports-dev-bounces@lists.macports.org</a>>
on behalf of Robert Kennedy <<a href="mailto:amtor@hotmail.com" class="">amtor@hotmail.com</a>><br class="">
<b class="">Sent:</b><span class="x_Apple-converted-space"> </span>August 2, 2022 8:10 AM<br class="">
<b class="">To:</b><span class="x_Apple-converted-space"> </span>Mark Brethen <<a href="mailto:mark.brethen@gmail.com" class="">mark.brethen@gmail.com</a>>; MacPorts Developers <<a href="mailto:macports-dev@lists.macports.org" class="">macports-dev@lists.macports.org</a>><br class="">
<b class="">Subject:</b><span class="x_Apple-converted-space"> </span>Re: include files for cgxCADTools</font>
<div class=""> </div>
</div>
<div dir="ltr" class="" style="font-family:Helvetica; font-size:12px; font-style:normal; font-variant-caps:normal; font-weight:normal; letter-spacing:normal; text-align:start; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0px; text-decoration:none">
<div class="x_x_elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
Mark,</div>
<div class="x_x_elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
<br class="">
</div>
<div class="x_x_elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
I agree with Josh, these headers look like they were automatically generated using something like "make depends". </div>
<div class="x_x_elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
<br class="">
</div>
<div class="x_x_elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
When creating a Makefile, it is GOOD practice to include these lines as it will ensure that the Project will rebuild the correct files when a header file was changed. Since it is a REAL pain to create them manually. Many developers use something like "make
depends".</div>
<div class="x_x_elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
<br class="">
</div>
<div class="x_x_elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
If there is a "depends:" target in the Makefile, you could patch the Makefile and add "depends" as the first Phony target to the "all:" target. e.g. </div>
<div class="x_x_elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
<br class="">
</div>
<div class="x_x_elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
all: depends main etc etc</div>
<div class="x_x_elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
<br class="">
</div>
<div class="x_x_elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
Alternatively, you could try just patching the Makefile by removing all these lines (and any other line where a system header is the ONLY dependency in the rule). <span class="x_Apple-converted-space"> </span><b class="">The vast majority of time, they are
NOT needed to build the initial project.</b> (They are needed if you want to use "make" to rebuild your project properly on subsequent runs where the developer has changed one of more of these system header files. This is not a normal scenario if one is
using Macports to build the project).</div>
<div class="x_x_elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
<br class="">
</div>
<div class="x_x_elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
The most important rules are the rules involving the source code files (which must be kept). </div>
<div class="x_x_elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
e.g. $(OBJDIR-MAIN)/%.o: %.c<br class="">
<blockquote class="" style="margin-top:0px; margin-bottom:0px"> $(CC) $(CFLAGS) $(INCLUDES) -c $< -o $@</blockquote>
<div class=""><br class="">
</div>
<div class="">Make sure the Makfile has an "INCLUDES:" that lists the location of all the header files. If it does, make will find them and build the initial project!</div>
<div class=""><br class="">
</div>
</div>
<div class="x_x_elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
e.g. I am working on a new port where I converted an Xcode project to one using a Makefile. I used "make depends" to generate these dependencies, Macports built the code just fine when I either:</div>
<div class="x_x_elementToProof" style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt">
<ol class="">
<li class=""><span class="">Deleted all the lines below "# DO NOT DELETE THIS LINE -- make depend needs it"; or</span></li><li class=""><span class="">Added "depends" as the first phony target to the all: phoney target </span></li></ol>
<blockquote class="" style="margin-top:0px; margin-bottom:0px">
<blockquote class="" style="margin-top:0px; margin-bottom:0px">
<div class="">e.g. all: depends utils altivec mpeg2enc main $(PRODUCT)</div>
<div class=""><br class="">
</div>
</blockquote>
<div class="">You could even patch the Makefile and add another target called "macports" and tell Macports to build that:</div>
</blockquote>
<div class=""><br class="">
</div>
<blockquote class="" style="margin-top:0px; margin-bottom:0px">
<div class=""><span class=""> macports: depends all</span><br class="">
</div>
</blockquote>
<div class=""><span class=""><br class="">
</span></div>
<div class=""><span class=""> <span class=""> And in the portfile, you would add:</span></span></div>
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
<blockquote class="" style="margin-top:0px; margin-bottom:0px">
<div class=""><span class=""><span class="">build.target macports<br class="">
</span></span></div>
</blockquote>
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
<div class="">Good luck,<br class="">
</div>
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
<div class=""><span class=""><span class="">Rob</span></span></div>
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
<div class=""><span class=""><span class=""><br class="">
</span></span></div>
</div>
<div id="x_x_appendonsend" class=""></div>
<hr tabindex="-1" class="" style="display:inline-block; width:354.75px">
<div id="x_x_divRplyFwdMsg" dir="ltr" class=""><font face="Calibri, sans-serif" class="" style="font-size:11pt"><b class="">From:</b><span class="x_Apple-converted-space"> </span>macports-dev <<a href="mailto:macports-dev-bounces@lists.macports.org" class="">macports-dev-bounces@lists.macports.org</a>>
on behalf of Mark Brethen <<a href="mailto:mark.brethen@gmail.com" class="">mark.brethen@gmail.com</a>><br class="">
<b class="">Sent:</b><span class="x_Apple-converted-space"> </span>August 1, 2022 8:51 PM<br class="">
<b class="">To:</b><span class="x_Apple-converted-space"> </span>MacPorts Developers <<a href="mailto:macports-dev@lists.macports.org" class="">macports-dev@lists.macports.org</a>><br class="">
<b class="">Subject:</b><span class="x_Apple-converted-space"> </span>Re: include files for cgxCADTools</font>
<div class=""> </div>
</div>
<div class="x_x_BodyFragment"><font size="2" class=""><span class="" style="font-size:11pt">
<div class="x_x_PlainText">I’ll ask the developer<br class="">
<br class="">
Sent from my iPhone<br class="">
<br class="">
> On Aug 1, 2022, at 4:53 PM, Joshua Root <<a href="mailto:jmr@macports.org" class="">jmr@macports.org</a>> wrote:<br class="">
><span class="x_Apple-converted-space"> </span><br class="">
> A lot of them aren't even standard headers; I believe the ones under bits/ are glibc implementation details. I would suspect this part of the Makefile was not hand-written but generated with one of the compiler's -M options. To work correctly in that case,
it would need to be regenerated for each new system the software is built on.<br class="">
><span class="x_Apple-converted-space"> </span><br class="">
> - Josh<br class="">
><span class="x_Apple-converted-space"> </span><br class="">
>> On 2022-8-2 05:23 , Chris Jones wrote:<br class="">
>> The makefile here is very poorly written. You should never directly reference standard headers like that…<br class="">
>>>> On 1 Aug 2022, at 4:52 pm, Mark Brethen <<a href="mailto:mark.brethen@gmail.com" class="">mark.brethen@gmail.com</a>> wrote:<br class="">
>>><span class="x_Apple-converted-space"> </span><br class="">
>>> This Makefile has the following lines:<br class="">
>>><span class="x_Apple-converted-space"> </span><br class="">
>>> CadReader.o: /usr/include/stdlib.h /usr/include/bits/libc-header-start.h<br class="">
>>> CadReader.o: /usr/include/features.h /usr/include/stdc-predef.h<br class="">
>>> CadReader.o: /usr/include/sys/cdefs.h /usr/include/bits/wordsize.h<br class="">
>>> CadReader.o: /usr/include/bits/long-double.h /usr/include/gnu/stubs.h<br class="">
>>> CadReader.o: /usr/include/bits/waitflags.h /usr/include/bits/waitstatus.h<br class="">
>>> CadReader.o: /usr/include/bits/floatn.h /usr/include/sys/types.h<br class="">
>>> CadReader.o: /usr/include/bits/types.h /usr/include/bits/typesizes.h<br class="">
>>> CadReader.o: /usr/include/bits/types/clock_t.h<br class="">
>>> CadReader.o: /usr/include/bits/types/clockid_t.h<br class="">
>>> CadReader.o: /usr/include/bits/types/time_t.h<br class="">
>>> CadReader.o: /usr/include/bits/types/timer_t.h<br class="">
>>> CadReader.o: /usr/include/bits/stdint-intn.h /usr/include/endian.h<br class="">
>>> CadReader.o: /usr/include/bits/endian.h /usr/include/bits/byteswap.h<br class="">
>>> CadReader.o: /usr/include/bits/byteswap-16.h<br class="">
>>> CadReader.o: /usr/include/bits/uintn-identity.h /usr/include/sys/select.h<br class="">
>>> CadReader.o: /usr/include/bits/select.h /usr/include/bits/types/sigset_t.h<br class="">
>>> CadReader.o: /usr/include/bits/types/__sigset_t.h<br class="">
>>> CadReader.o: /usr/include/bits/types/struct_timeval.h<br class="">
>>> CadReader.o: /usr/include/bits/types/struct_timespec.h<br class="">
>>> CadReader.o: /usr/include/sys/sysmacros.h /usr/include/bits/sysmacros.h<br class="">
>>> CadReader.o: /usr/include/bits/pthreadtypes.h<br class="">
>>> CadReader.o: /usr/include/bits/thread-shared-types.h<br class="">
>>> CadReader.o: /usr/include/bits/pthreadtypes-arch.h /usr/include/alloca.h<br class="">
>>> CadReader.o: /usr/include/bits/stdlib-float.h<br class="">
>>><span class="x_Apple-converted-space"> </span><br class="">
>>> /usr/include doesn’t exist on Big Sure (I assume its deprecated?) however, they can be found at<br class="">
>>><span class="x_Apple-converted-space"> </span><br class="">
>>> ~ $ xcrun --sdk macosx --show-sdk-path<br class="">
>>> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.1.sdk<br class="">
>>><span class="x_Apple-converted-space"> </span><br class="">
>>> although I don’t see a ‘bits’ subdirectory. Has it been relocated?<br class="">
>>><span class="x_Apple-converted-space"> </span><br class="">
>>> Thanks,<br class="">
>>> Mark<br class="">
>>><span class="x_Apple-converted-space"> </span><br class="">
>>><span class="x_Apple-converted-space"> </span><br class="">
>>><span class="x_Apple-converted-space"> </span><br class="">
><span class="x_Apple-converted-space"> </span></div>
</span></font></div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</div>
</body>
</html>