Changes between Initial Version and Version 1 of Ticket #38582, comment 6


Ignore:
Timestamp:
Jul 30, 2013, 7:49:42 PM (11 years ago)
Author:
cooljeanius (Eric Gallager)
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #38582, comment 6

    initial v1  
    11I don't think any of these macros can actually fail, so I don't see why they'd need fallback code. They're just for adding more information about the user's system to their `config.log` and to their `config.h` (which I guess MacPorts doesn't use, but it could do so easily...). Also it looks like a lot of the macros currently in `configure.ac` were originally added with an older version of `autoscan`, this would be just updating those to a more recent version. Anyway I'm planning on editing a table into this post showing more about these macros:
    2 ||= Macro =||= contents of line `autoscan` is referring to when it says a file wants this macro =||= context (how the line is used) =||= human explanation for how adding the macro will be useful =||
    3 ||= `AC_CHECK_FUNCS([dup2])` =||= =||= =||= =||
     2||= Macro =||= line of file `autoscan` wants it for =||= contents of line from previous column =||= context (how the line is used) =||= human explanation for how adding the macro will be useful (i.e. relevant comments) =||
     3||= `AC_CHECK_FUNCS([dup2])` =||= `src/darwintracelib1.0/darwintrace.c:1100` =||= `int dup2(int filedes, int filedes2) {` =||= new function declaration =||= `/* if darwintrace has been initialized, trap attempts to dup2 over our file descriptor */` (this function would only be useful if calls are being made to `dup2` in the first place, so check for it) =||
     4||= `AC_CHECK_FUNCS([getcwd])` =||= `src/darwintracelib1.0/darwintrace.c:642` =||= `if (!getcwd(somepath, sizeof(somepath))) {` =||= condition for an error message =||= In a path-sending function. Checking for `getcwd` would ensure that this function works. =||
     5||= `AC_CHECK_FUNCS([lchown])` =||=
    46
    57(coming back to this later...)