Many build systems add automatically detected `make` dependencies into the `.d` file.  In particular, for C/C++ source files they determine what `#include` files are required and automatically generate that information into the `.d` file.

The `.d` files are then included by the `makefile` so `make` is aware of that information.  If you look at the contents of those files they&#39;ll be make prerequisite statements, like:

    foo.o : foo.h bar.h biz.h

etc.

I am getting this warning while submitting app to the Apps store through organizer.

    

&gt; The app references non-public selectors in Payload/&lt;Appname&gt;.app/&lt;App
&gt; name&gt;: decoder

i know we get this warning if we use any Third Party API in our application. I have used [SOCKETIO-ObjC][1] library for chat functionality in application. Also used facebook iOS sdk for fb implementation.So i am not getting exactly what causes this warning.! Please find attached [ScreenShot][2] for better understanding


  [1]: https://github.com/pkyeck/socket.IO-objc
  [2]: http://i.stack.imgur.com/FayAJ.png

The app references non-public selectors in Payload/&lt;Appname&gt;.app/&lt;App name&gt;: decoder

Is it possible to query for a distinct/unique count of a field using Kibana? I am using elastic search as my backend to Kibana. 

If so, what is the syntax of the query? Heres a link to the Kibana interface I would like to make my query: http://demo.kibana.org/#/dashboard

I am parsing nginx access logs with logstash and storing the data into elastic search.  Then, I use Kibana to run queries and visualize my data in charts.  Specifically, I want to know the count of unique IP addresses for a specific time frame using Kibana.


How to retrieve unique count of a field using Kibana + Elastic Search

Sometimes, I find `.d` files for a given source file.
For instance, if I compile `test.c`, I&#39;ve got

    test.d, test.o

I understand that `test.o` is the object file but have no idea what is `test.d` for.
Could you give any hints or pointers?

what is .d file after building with make

<p>Sometimes, I find <code>.d</code> files for a given source file.
For instance, if I compile <code>test.c</code>, I've got</p>
<pre><code class="hljs">test.d, test.o
</code></pre>
<p>I understand that <code>test.o</code> is the object file but have no idea what is <code>test.d</code> for.
Could you give any hints or pointers?</p>


Can someone explain why I get exit code 141 from the below? 

    #!/usr/bin/bash

    set -o pipefail
    
    zfs list | grep tank
    echo a ${PIPESTATUS[@]}
    
    zfs list | grep -q tank
    echo b ${PIPESTATUS[@]}

    cat /etc/passwd | grep -q root
    echo c ${PIPESTATUS[@]}

I get

    ...
    a 0 0
    b 141 0
    c 0 0

From my understanding exit code 141 is a failure, but the line above gives zero, so it should be success, I would say.





Why exit code 141 with grep -q?

I am attempting to get cross-compiling for Raspberry Pi working on my Ubuntu machine. 

During my initial attempts I was using the arm-linux-gnueabi compiler, which is available in the Ubuntu repo. I got this working. I was able to build all my dependencies and use the cross-compiler in my cmake project.

However, I believe I should be using the hf version, so I switched to arm-linux-gnueabihf. Then I realized that this does not work with Raspberry Pi since it is armv6.

After some Googling, I then found the [pre-built toolchain from GitHub][1].

I downloaded the toolchain, but I don&#39;t really understand how to &quot;install&quot; it. I extracted the files to my home directory. The directory structure looks like this:

    /gcc-linearo-arm-linux-gnueabihf-raspbian
        /arm-linux-gnueabihf
            /bin
                (contains g++, gcc, etc)
            /lib
                (contains libstdc++ library)
        /bin
            (contains arm-linux-gnueabihf-g++, arm-linux-gnueabihf-...)
        /lib
            (gcc lib stuff)
       

If I change directory to the INNER bin folder I am able to compile a test program from the terminal without any problems.

    ~/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/
    arm-linux-gnueabihf/bin$ g++ test.cpp -o test

I then tried to compile a test program in the OUTER bin folder, which contains the prefixed versions of the tools.

     ~/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian/bin$ 
     arm-linux-gnueabihf-g++ test.cpp -o test

However, when I try to use the compiler now (from outside the inner bin directory), it is unable to find the libstdc++ shared library that comes with the toolchain:

    arm-linux-gnueabihf-gcc: error while loading shared libraries: 
    libstdc++.so.6: cannot open shared object file: No such file or directory.

Furthermore, I want to be able to use the compiler without having to navigate to the bin directory. So I tried adding the OUTER bin directory (since I want the prefixed versions) and both lib directories to my PATH:

    export PATH=$PATH:~/tools/.../bin
    export PATH=$PATH:~/tools/.../lib
    export PATH=$PATH:~/tools/.../.../lib

However, this results in the same error. How should I &quot;install&quot; the toolchain so that I can use the toolchain from everywhere, just like I can when I use the cross-compilers from the Ubuntu repo?


  [1]: https://github.com/raspberrypi/tools

How to install the Raspberry Pi cross compiler on my Linux host machine?

I&#39;m trying to create a simple kernel using Ubuntu. In the terminal I typed 

    ld -Ttext 0x1000 -o kernel.bin loader.o main.o Video.o

But I got the following error message in return:

    ld: i386 architecture of input file `loader.o&#39; is incompatible with i386:x86-64 output
    ld: warning: cannot find entry symbol _start; defaulting to 0000000000001000



Architecture of i386 input file is incompatible with i386:x86-64

Why does the **C** preprocessor in **GCC** interpret the word `linux` (small letters) as the constant `1`?

**test.c:**

    #include &lt;stdio.h&gt;
    int main(void)
    {       
        int linux = 5;
        return 0;
    }


Result of `$ gcc -E test.c` (stop after the preprocessing stage):

    ....
    int main(void)
    {
        int 1 = 5;
        return 0;
    }

Which of course yields an error.

(BTW: There is no `#define linux` in the `stdio.h` file.)


Why does the C preprocessor interpret the word &quot;linux&quot; as the constant &quot;1&quot;?

I&#39;m trying to attach a program with gdb but it returns:

&gt; Attaching to process 29139  
&gt;     Could not attach to process.  If your uid matches the uid of the target
&gt;     process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
&gt;     again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf  
&gt;     ptrace: Operation not permitted.

gdb-debugger returns &quot;Failed to attach to process, please check privileges and try again.&quot;

strace returns &quot;attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted&quot;

I changed &quot;kernel.yama.ptrace_scope&quot; 1 to 0 and `/proc/sys/kernel/yama/ptrace_scope` 1 to 0 and tried `set environment LD_PRELOAD=./ptrace.so` with this:

    #include &lt;stdio.h&gt;
    int ptrace(int i, int j, int k, int l) {
        printf(&quot; ptrace(%i, %i, %i, %i), returning -1\n&quot;, i, j, k, l);
        return 0;
    }

But it still returns the same error. How can I attach it to debuggers?

How to solve &quot;ptrace operation not permitted&quot; when trying to attach GDB to a process?

I want to create a package in Go with tests and examples for the package as subdirectories to keep the workspace cleaner. Is this possible and if so how? 

All the documentation always puts the testing code in the same place as the other code, is this better in some way or just convention?

Golang tests in sub-directory

I am building a project through the command line and not inside Visual Studio 2013. Note, I had upgraded my project from Visual Studio 2012 to 2013. The project builds fine inside the IDE. Also, I completely uninstalled VS2012 first, rebooted, and installed VS2013. The only version of Visual Studio that I have is 2013 Ultimate.

    ValidateProjects:
        39&gt;path_to_project.csproj(245,3): error MSB4019: The imported project &quot;C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\WebApplications\Microsoft.WebApplication.targets&quot; was not found. Confirm that the path in the &lt;Import&gt; declaration is correct, and that the file exists on disk.
        39&gt;Done Building Project &quot;path_to_project.csproj&quot; (Clean target(s)) -- FAILED.

Here are the two lines in question:

    &lt;Import Project=&quot;$(VSToolsPath)\WebApplications\Microsoft.WebApplication.targets&quot; Condition=&quot;&#39;$(VSToolsPath)&#39; != &#39;&#39;&quot; /&gt;
    &lt;Import Project=&quot;$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v12.0\WebApplications\Microsoft.WebApplication.targets&quot; Condition=&quot;false&quot; /&gt;

The original second line was v10.0, but I manually changed that to v12.0.

$(VSToolsPath) elongates from what I see to the v11.0 (VS2012) folder, which obviously is not there anymore. The path should have been to v12.0.

    C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\WebApplications\

I tried specifying VSToolsPath in my system environment variables table, but the external build utility still uses v11.0. I tried searching through the registry and that came up with nothing.

Sadly, I do not see any easy way to get the exact command line used. I use a build tool.

Thoughts?

External VS2013 build error &quot;error MSB4019: The imported project &lt;path&gt; was not found&quot;

I&#39;d like to add a new build configuration in Xcode 5, &quot;QA&quot;, to the other three we currently have (Debug, Distribution, Release). However, when I click &quot;Editor &gt; Add Configuration&quot;, everything is grayed out. I&#39;m not very familiar with Xcode in the first place, so I&#39;m not sure how to go about doing this.

Is there a reason it&#39;s grayed out? Is this this process to add a build configuration? Thanks.

Adding a build configuration in Xcode

I am trying to build [this project][1], which has CUDA as a dependency. But the cmake script cannot find the CUDA installation on the system:

    cls ~/workspace/gpucluster/cluster/build $ cmake ..
    -- The C compiler identification is GNU 4.7.1
    -- The CXX compiler identification is GNU 4.7.1
    -- Check for working C compiler: /usr/bin/gcc
    -- Check for working C compiler: /usr/bin/gcc -- works
    -- Detecting C compiler ABI info
    -- Detecting C compiler ABI info - done
    -- Check for working CXX compiler: /usr/bin/c++
    -- Check for working CXX compiler: /usr/bin/c++ -- works
    -- Detecting CXX compiler ABI info
    -- Detecting CXX compiler ABI info - done
    CMake Error at /usr/share/cmake/Modules/FindCUDA.cmake:488 (message):
      Specify CUDA_TOOLKIT_ROOT_DIR
    Call Stack (most recent call first):
      CMakeLists.txt:20 (find_package)


-- Configuring incomplete, errors occurred!


I&#39;ve tried adding it as an environment variable to `.bashrc`, to no effect:

    export CUDA_TOOLKIT_ROOT_DIR=/usr/local/cuda-5.5

How do I `Specify CUDA_TOOLKIT_ROOT_DIR` correctly?

  [1]: http://www.staff.science.uu.nl/~faggi101/gpucluster.tar.gz

How to let cmake find CUDA

Could someone tell me if it&#39;s possible to build only one of my different flavors through the command-line? 

At the moment I haven&#39;t seen the way to execute, for example:

    gradle buildDev 

when Dev is one of my different flavors. Indeed, I have to execute:

    gradle build

And all flavors are build. 

I&#39;d like to skip some flavors. 
is it possible?

Thanks

Gradle: How to Build different flavours of different built types?

I&#39;m developing a program in Qt. Its makefile is generated automatically from the .pro file. I need to use some code which need the -std=c++11 flag to be set up for g++. Where in .pro should I add this flag? (changing only the Makefile won&#39;t work since it gets overwritten by the newly generated one, each time I build the project).

C++ Qt - How to add &quot;-std=c++11&quot; to the makefile which is generated by qmake?

I am using `make` and `tar` to backup. When executing makefile, tar command shows `file changed as we read it`. In this case,

 - the tar package is ok when the warning comes up
 - but it stops the tar command for the following backup
 - the file showing the warning in fact doesn&#39;t change -- it is really strange that the warning comes up
 - the files showing the warning come up randomly, I mean, everytime I run my makefile, the files showing the warning are different
 - `--ignore-failed-read` doesn&#39;t help. I am using tar 1.23 in MinGW
 - I just changed my computer to WIN7 64 bit. The script works well in old WIN7 32 bit. But the tar version is not as new as the 1.23.

How can I stop the tar&#39;s warning to stop my backup following the warning?

-------------------------------------------------------------------
**Edit-2**: it might be the reason

As I said above, the bash shell script worked well in my old computer. Comparing with the old computer, the `msys` version is different. So is the version of tar command. In the old computer, tar is 1.13.19 and it is 1.23 in the new computer. I copied the old tar command without copying its dependency msys-1.0.dll to the new computer and renamed it tar_old. And I also updated the tar command in the shell script and run the script. Then everything is ok. So, it seemed that the problem is the tar command. I am sure that there is no any file changed when taring. Is it a bug for tar command in new version? I don&#39;t know.

-------------------------------------------------------------------
**Edit-1**: add more details

The backup is invoked by a bash shell script. It scans the target directory and builds makefile then invokes make to use tar command for backup. Followed is a typical makefile built by the bash shell script.

    #--------------------------------------------
    # backup VC
    #--------------------------------------------
    # the program for packing
    PACK_TOOL=tar
    
    # the option for packing tool
    PACK_OPTION=cjvf
    
    # M$: C driver
    WIN_C_DIR=c:
    
    # M$: D driver
    WIN_D_DIR=d:
    
    # M$: where the software is
    WIN_PRG_DIR=wuyu/tools
    # WIN_PRG_DIR=
    
    # where to save the backup files
    BAKDIR=/home/Wu.Y/MS_bak_MSYS
    
    VC_FRAMEWORK=/home/Wu.Y/MS_bak_MSYS/tools/VC/VC_framework.tar.bz2
    VC_2010=/home/Wu.Y/MS_bak_MSYS/tools/VC/VC_2010.tar.bz2
    
    .PHONY: all
    
    all: $(VC_FRAMEWORK) $(VC_2010)
    
    $(VC_FRAMEWORK): $(WIN_C_DIR)/$(WIN_PRG_DIR)/VC/Framework/*
    	@$(PACK_TOOL) $(PACK_OPTION) &quot;$@&quot; --ignore-failed-read /c/$(WIN_PRG_DIR)/VC/Framework
    $(VC_2010): $(WIN_C_DIR)/$(WIN_PRG_DIR)/VC/VS2010/*
    	@$(PACK_TOOL) $(PACK_OPTION) &quot;$@&quot; --ignore-failed-read /c/$(WIN_PRG_DIR)/VC/VS2010

As you can see, the tar package is stored in ~/MS_bak_MSYS/tools/VC/VC_2010.tar.bz2. I run the script in ~/qqaa. `~/MS_bak_MSYS` is excluded from tar command. So, the tar file I am creating is not inside a directory I am trying to put into tar file. This is why I felt it strange that the warning came up.

 

tar: file changed as we read it

In his [answer][1] @Grundlefleck explains how to check whether a directory exists or not. I tried some to use this inside a `makefile` as follow:

    foo.bak: foo.bar
    	echo &quot;foo&quot;
    	if [ -d &quot;~/Dropbox&quot; ]; then
    		echo &quot;Dir exists&quot;
    	fi

Running `make foo.bak` (given that `foo.bar` exists) yields the following error:

    echo &quot;foo&quot;
    foo
    if [ -d &quot;~/Dropbox&quot; ]; then
    /bin/sh: -c: line 1: syntax error: unexpected end of file
    make: *** [foo.bak] Error 2

The workaround I made was to have a standalone bash script where the test is implemented and I called the script from the `makefile`. This, however, sounds very cumbersome. Is there a nicer way to check whether a directory exists from within a `makefile`?

  [1]: https://stackoverflow.com/a/59839/671013

Test whether a directory exists inside a makefile

I&#39;m trying to build:
https://github.com/kanzure/nanoengineer

But it looks like it errors out on:

    gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include/python2.7   -std=c99 x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -MT libstructcompare_a-structcompare.o -MD -MP -MF .deps/libstructcompare_a-structcompare.Tpo -c -o libstructcompare_a-structcompare.o `test -f &#39;structcompare.c&#39; || echo &#39;./&#39;`structcompare.c
    gcc: error: x86_64-linux-gnu-gcc: No such file or directory

`x86_64-linux-gnu-gcc` definitely exists in */usr/bin* (It&#39;s a symlink) and the target definitely exists as well. It looks to me like the Makefile wasn&#39;t generated correctly, perhaps there is a flag that should be passed before specifying x86_64-linux-gnu-gcc? I am unsure as well what specifying `x86_64-linux-gnu-gcc` is supposed to accomplish.

Finally, this makefile was generated by configure, so once we narrow down the cause of the error, I&#39;ll have to figure out what files to modify in order to fix this. (I&#39;m a CMake kind of guy myself, but of course I didn&#39;t choose the build system for this project.) My OS is Debian.

I&#39;ve tried building this branch as well:
https://github.com/kanzure/nanoengineer/branches/kirka-updates

If you can try getting this to build on your system, I would greatly appreciate it! Thanks!

Debugging the error &quot;gcc: error: x86_64-linux-gnu-gcc: No such file or directory&quot;

Just out of curiosity, how does Makefile know that a file changed (and then recompile it)? Is it up to `make`? Is it up to the compiler? If so, is it language dependent?

Content Type	Original Author	Original Content on Stackoverflow
Question	jaeyong	View Question on Stackoverflow
Solution 1 - Linux	MadScientist	View Answer on Stackoverflow

what is .d file after building with make

Linux Problem Overview

Linux Solutions

Solution 1 - Linux

How to retrieve unique count of a field using Kibana + Elastic Search

The app references non-public selectors in Payload/<Appname>.app/<App name>: decoder

Attributions