Clang error no input files

I had a file which I deleted and replaced with another file, somewhere else, of the same name. Despite cleaning, and trying this multiple times, I keep getting this error: clang: error: no such...

I had a file which I deleted and replaced with another file, somewhere else, of the same name.

Despite cleaning, and trying this multiple times, I keep getting this error:

clang: error: no such file or directory: ‘/Users/Andrew/App/Version 1.1/XCode/UIImage+Alpha.m’
clang: error: no input files

I can’t continue working on my app because of it. Any ideas?

Ajean's user avatar

Ajean

5,47814 gold badges48 silver badges69 bronze badges

asked Jul 5, 2012 at 21:00

Andrew's user avatar

1

The problem might be because your project > target > Build Phases > Compile Sources is trying to compile a file that doesn’t exist. It might be in there twice, like the below screen shot. My project contains UIImage+FFXtras, I can even remove it and re-add it and this won’t resolve the problem!

missing source file

I’m not sure how the project gets into this state — but I know it’s not obvious what is going wrong. Highlight the red problem one and remove it.

So have a look in compile sources phase for the file clang is complaining about.

answered Aug 31, 2012 at 15:30

bandejapaisa's user avatar

bandejapaisabandejapaisa

26.2k13 gold badges92 silver badges112 bronze badges

4

Got the similar troubles.

It seems XCode does not generate correct relative filepath when your project refer to an already existing source tree (relative path does not contain the .xcodeproj in the path of the file to be compiled).

There is a simple fix however: in the project explorer select the file or files files then look at the options in the file inspector. One of them is labeled «Location»; set it to absolut path and try again. This fixed the issue for me :)

enter image description here

answered Sep 28, 2015 at 21:03

TocToc's user avatar

TocTocTocToc

4,4894 gold badges29 silver badges34 bronze badges

2

Additional to all answers:

  1. delete derived data
  2. reboot
  3. delete derived data
  4. clean
  5. build
  6. Success!

Only this sequence works for me in my case.

answered Mar 4, 2016 at 19:23

WINSergey's user avatar

WINSergeyWINSergey

1,91926 silver badges39 bronze badges

I use quite a few cocoa pods and have just had this happen to me. A quick «pods update» sorted things out for me. -phil

answered Dec 30, 2014 at 3:47

phil's user avatar

philphil

9731 gold badge9 silver badges33 bronze badges

0

If you are using vs code and facing this issue which says

clang: error: no such file or directory: 'filename'
clang: error: no input files

Error while running files:

error while running files

I solved this issue by removing the space or replacing the space with underscore(_) in the filename .extension

bad_coder's user avatar

bad_coder

10.4k20 gold badges43 silver badges65 bronze badges

answered Aug 6, 2020 at 7:30

realironman101's user avatar

In case everything fails (i.e. first try bames53 suggestion)

Ok, this might be dangerous so make a copy of your whole project first:

  • close Xcode
  • locate the project file in the Finder
  • right click, choose «show package contents»
  • open project.pbxproj in a text editor of your choice, but not Xcode
  • search for your file
    • at the beginning of the line that shows up, you’ll see some id like 640450991409CF5C00B3B580. Search for this and delete any line you find.
    • pay attention, not to break the syntax (balance parenthesis and brackets, pay attention for commas)
  • when you are done, save the file and try to open the project in Xcode. Add the missing file via the Add file… dialog of Xcode. It is still in the folder of your project — if you added it successfully in the first place — you just got rid of all project references.
  • dont be surprised, if it doesnt work instantly — you have a copy. copy it again, new try.

And remember: make a copy of your whole project first — for every try. or copying the project.pbxproj might be enough.

answered Jul 5, 2012 at 21:26

vikingosegundo's user avatar

vikingosegundovikingosegundo

51.9k14 gold badges136 silver badges176 bronze badges

1

Add this line in your pod-file and run pod install:

use_frameworks!

loki's user avatar

loki

9,4567 gold badges55 silver badges80 bronze badges

answered Aug 30, 2016 at 9:45

sfg2k's user avatar

sfg2ksfg2k

1291 silver badge10 bronze badges

I had this error in monodevelop. I just went to edit>preferences
and changed the default location of the program files. It was set to the monodevelop default they give you when you open a file and not the folder i changed it too.
Likely, you need to adjust the settings of xcode, where you stored your files.

answered Apr 14, 2017 at 22:59

l.grant's user avatar

I was seeing this while setting up a React Native project. Solved it using:

sudo xcode-select --switch /Applications/Xcode.app

Source

answered Oct 29, 2020 at 10:07

Nelu's user avatar

NeluNelu

15.5k10 gold badges77 silver badges87 bronze badges

Comment Quoted from another site was the issue is resolved for me

hmm that’s strange. Try this — click on the name of your project on the list of files/folders on the left in Xcode (at the very top of the list). Look at the «Targets» section on the left-hand side of the window to the right. Likely, there’s two listed with the second being a «test» item. Right-click on that item and select «delete». Then try to run the project again. See screenshot below for a visual cue.

ArtKorchagin's user avatar

ArtKorchagin

4,73113 gold badges41 silver badges58 bronze badges

answered Dec 13, 2015 at 16:37

Rakan Bushnaq's user avatar

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account


Closed

gitdudek opened this issue

Jun 26, 2019

· 11 comments


Closed

clang error c++ on mac in vscode

#2821

gitdudek opened this issue

Jun 26, 2019

· 11 comments

Assignees

@mikeblome

Comments

@gitdudek

Hello, i’m trying to use clang to work with c++ in vscode on my mac and followed every step of the tutorial (https://code.visualstudio.com/docs/cpp/config-clang-mac).

When I build the ‘helloworld.cpp’ file I get the following errors in my console:

`Executing task: clang++ -std=c++17 -stdlib=libc++ helloworld.cpp -o helloworld.out —debug <

clang: error: no such file or directory: ‘helloworld.cpp’
clang: error: no input files
The terminal process terminated with exit code: 1`

@mikeblome

@gitdudek sorry to hear you are having problems. I just verified that the exact instructions work for me. Can you see your helloworld.cpp file in Finder in the expected location?

@gitdudek

@mikeblome the ‘.vscode’ directory is hidden but I can see the helloworld.cpp file in my finder as you can see on the screenshot.
screen

@mikeblome

@gitdudek thanks for that image! Move helloworld.cpp up one level. Only the .json files should be in the .vscode folder.

@gitdudek

@rmcclain31

Found this old thread that helped me with the same problem. Thank you!

Do you happen to know what we’re supposed to do if we want to put source files into sub-directories? Is there a way to tell vscode where we’ve stored .cpp, .lib, .h files?

@tdserapio

@realironman101

If you are using vs code and facing this issue which says clang: error: no such file or directory: ‘filename’
clang: error: no input files.error while running files

I solved this issue by removing the space or replacing the space with underscore(_)in the filename .extension

Hope this works for you also

realironman101, alibabaintelligence, keshav1sharma, neelad3110, mikekenn, Jessica765, Peterrr11, shashankrustagiiiitdelhi, LilTurkProdigy, moafkaljabi, and rohhitrz reacted with thumbs up emoji
realironman101 and shashankrustagiiiitdelhi reacted with laugh emoji
realironman101 and shashankrustagiiiitdelhi reacted with hooray emoji
realironman101, shashankrustagiiiitdelhi, and rohhitrz reacted with heart emoji
realironman101 and shashankrustagiiiitdelhi reacted with rocket emoji
realironman101 and shashankrustagiiiitdelhi reacted with eyes emoji

@LilTurkProdigy

If you are using vs code and facing this issue which says clang: error: no such file or directory: ‘filename’ clang: error: no input files.error while running files

I solved this issue by removing the space or replacing the space with underscore(_)in the filename .extension

Hope this works for you also

Thank you so much I’ve been looking for a solution to this problem I was having

@jackromo888

@Aryan1405

my named c files show —
clang: error: no such file or directory: ‘Case’
clang: error: no such file or directory: ‘2’
clang: error: no such file or directory: ‘2’
clang: error: no input files

all the named files are not working even with the fresh code just because they are named . any tips?

@Aryan1405

If you are using vs code and facing this issue which says clang: error: no such file or directory: ‘filename’ clang: error: no input files.error while running files
I solved this issue by removing the space or replacing the space with underscore(_)in the filename .extension
Hope this works for you also

Thank you so much I’ve been looking for a solution to this problem I was having

now working thnx

Содержание

  1. clang error c++ on mac in vscode #2821
  2. Comments
  3. suma / config.log

clang error c++ on mac in vscode #2821

Hello, i’m trying to use clang to work with c++ in vscode on my mac and followed every step of the tutorial (https://code.visualstudio.com/docs/cpp/config-clang-mac).

When I build the ‘helloworld.cpp’ file I get the following errors in my console:

`Executing task: clang++ -std=c++17 -stdlib=libc++ helloworld.cpp -o helloworld.out —debug

The text was updated successfully, but these errors were encountered:

@gitdudek sorry to hear you are having problems. I just verified that the exact instructions work for me. Can you see your helloworld.cpp file in Finder in the expected location?

@mikeblome the ‘.vscode’ directory is hidden but I can see the helloworld.cpp file in my finder as you can see on the screenshot.

@gitdudek thanks for that image! Move helloworld.cpp up one level. Only the .json files should be in the .vscode folder.

@mikeblome thanks a lot. Now it’s working.

Found this old thread that helped me with the same problem. Thank you!

Do you happen to know what we’re supposed to do if we want to put source files into sub-directories? Is there a way to tell vscode where we’ve stored .cpp, .lib, .h files?

If you are using vs code and facing this issue which says clang: error: no such file or directory: ‘filename’
clang: error: no input files.error while running files

I solved this issue by removing the space or replacing the space with underscore(_)in the filename .extension

Hope this works for you also

If you are using vs code and facing this issue which says clang: error: no such file or directory: ‘filename’ clang: error: no input files.error while running files

I solved this issue by removing the space or replacing the space with underscore(_)in the filename .extension

Hope this works for you also

Thank you so much I’ve been looking for a solution to this problem I was having

my named c files show —
clang: error: no such file or directory: ‘Case’
clang: error: no such file or directory: ‘2’
clang: error: no such file or directory: ‘2’
clang: error: no input files

all the named files are not working even with the fresh code just because they are named . any tips?

If you are using vs code and facing this issue which says clang: error: no such file or directory: ‘filename’ clang: error: no input files.error while running files
I solved this issue by removing the space or replacing the space with underscore(_)in the filename .extension
Hope this works for you also

Thank you so much I’ve been looking for a solution to this problem I was having

Источник

suma / config.log

This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure, which was
generated by GNU Autoconf 2.69. Invocation command line was
$ ./configure
## ——— ##
## Platform. ##
## ——— ##
hostname = debian-sid-suma
uname -m = x86_64
uname -r = 3.2.0-4-amd64
uname -s = Linux
uname -v = #1 SMP Debian 3.2.35-2
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/local/bin
PATH: /usr/bin
PATH: /bin
PATH: /usr/local/games
PATH: /usr/games
PATH: /home/suma/.cabal/bin
## ———— ##
## Core tests. ##
## ———— ##
configure:2377: checking build system type
configure:2391: result: x86_64-unknown-linux-gnu
configure:2411: checking host system type
configure:2424: result: x86_64-unknown-linux-gnu
configure:2444: checking target system type
configure:2457: result: x86_64-unknown-linux-gnu
configure:2500: checking for a BSD-compatible install
configure:2568: result: /usr/bin/install -c
configure:2579: checking whether build environment is sane
configure:2629: result: yes
configure:2770: checking for a thread-safe mkdir -p
configure:2809: result: /bin/mkdir -p
configure:2822: checking for gawk
configure:2852: result: no
configure:2822: checking for mawk
configure:2838: found /usr/bin/mawk
configure:2849: result: mawk
configure:2860: checking whether make sets $(MAKE)
configure:2882: result: yes
configure:3021: checking for gcc
configure:3048: result: clang
configure:3277: checking for C compiler version
configure:3286: clang —version >&5
Debian clang version 3.0-6 (tags/RELEASE_30/final) (based on LLVM 3.0)
Target: x86_64-pc-linux-gnu
Thread model: posix
configure:3297: $? = 0
configure:3286: clang -v >&5
Debian clang version 3.0-6 (tags/RELEASE_30/final) (based on LLVM 3.0)
Target: x86_64-pc-linux-gnu
Thread model: posix
configure:3297: $? = 0
configure:3286: clang -V >&5
clang: error: argument to ‘-V’ is missing (expected 1 value)
clang: error: no input files
configure:3297: $? = 1
configure:3286: clang -qversion >&5
clang: error: no input files
configure:3297: $? = 1
configure:3317: checking whether the C compiler works
configure:3339: clang -O4 -Wall conftest.c >&5
/tmp/conftest-Fx0fuT.o: file not recognized: File format not recognized
clang: error: linker command failed with exit code 1 (use -v to see invocation)
configure:3343: $? = 1
configure:3381: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME «»
| #define PACKAGE_TARNAME «»
| #define PACKAGE_VERSION «»
| #define PACKAGE_STRING «»
| #define PACKAGE_BUGREPORT «»
| #define PACKAGE_URL «»
| #define PACKAGE «jubatus_mpio»
| #define VERSION «0.4.0»
| /* end confdefs.h. */
|
| int
| main ()
| <
|
| ;
| return 0;
| >
configure:3386: error: in `/home/suma/repos/jubatus-mpio’:
configure:3388: error: C compiler cannot create executables
See `config.log’ for more details
## —————- ##
## Cache variables. ##
## —————- ##
ac_cv_build=x86_64-unknown-linux-gnu
ac_cv_env_CCASFLAGS_set=
ac_cv_env_CCASFLAGS_value=
ac_cv_env_CCAS_set=
ac_cv_env_CCAS_value=
ac_cv_env_CCC_set=
ac_cv_env_CCC_value=
ac_cv_env_CC_set=set
ac_cv_env_CC_value=clang
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_CXX_set=set
ac_cv_env_CXX_value=clang++
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_host=x86_64-unknown-linux-gnu
ac_cv_path_install=’/usr/bin/install -c’
ac_cv_path_mkdir=/bin/mkdir
ac_cv_prog_AWK=mawk
ac_cv_prog_ac_ct_CC=clang
ac_cv_prog_make_make_set=yes
ac_cv_target=x86_64-unknown-linux-gnu
## —————— ##
## Output variables. ##
## —————— ##
ACLOCAL=’$ /home/suma/repos/jubatus-mpio/ac/missing —run aclocal-1.11′
AMDEPBACKSLASH=»
AMDEP_FALSE=»
AMDEP_TRUE=»
AMTAR=’$$‘
AR=»
AUTOCONF=’$ /home/suma/repos/jubatus-mpio/ac/missing —run autoconf’
AUTOHEADER=’$ /home/suma/repos/jubatus-mpio/ac/missing —run autoheader’
AUTOMAKE=’$ /home/suma/repos/jubatus-mpio/ac/missing —run automake-1.11′
AWK=’mawk’
CC=’clang’
CCAS=»
CCASDEPMODE=»
CCASFLAGS=»
CCDEPMODE=»
CFLAGS=’-O4 -Wall ‘
CPP=»
CPPFLAGS=»
CXX=’clang++’
CXXCPP=»
CXXDEPMODE=»
CXXFLAGS=’-O4 -Wall ‘
CYGPATH_W=’echo’
DEFS=»
DEPDIR=»
DLLTOOL=»
DSYMUTIL=»
DUMPBIN=»
ECHO_C=»
ECHO_N=’-n’
ECHO_T=»
EGREP=»
EXEEXT=»
FGREP=»
GREP=»
INSTALL_DATA=’$ -m 644′
INSTALL_PROGRAM=’$‘
INSTALL_SCRIPT=’$‘
INSTALL_STRIP_PROGRAM=’$(install_sh) -c -s’
LD=»
LDFLAGS=»
LIBOBJS=»
LIBS=»
LIBTOOL=»
LIPO=»
LN_S=»
LTLIBOBJS=»
MAKEINFO=’$ /home/suma/repos/jubatus-mpio/ac/missing —run makeinfo’
MANIFEST_TOOL=»
MKDIR_P=’/bin/mkdir -p’
NM=»
NMEDIT=»
OBJDUMP=»
OBJEXT=»
OTOOL64=»
OTOOL=»
PACKAGE=’jubatus_mpio’
PACKAGE_BUGREPORT=»
PACKAGE_NAME=»
PACKAGE_STRING=»
PACKAGE_TARNAME=»
PACKAGE_URL=»
PACKAGE_VERSION=»
PATH_SEPARATOR=’:’
RANLIB=»
SED=»
SET_MAKE=»
SHELL=’/bin/bash’
STRIP=»
VERSION=’0.4.0′
ac_ct_AR=»
ac_ct_CC=’clang’
ac_ct_CXX=»
ac_ct_DUMPBIN=»
am__EXEEXT_FALSE=»
am__EXEEXT_TRUE=»
am__fastdepCCAS_FALSE=»
am__fastdepCCAS_TRUE=»
am__fastdepCC_FALSE=»
am__fastdepCC_TRUE=»
am__fastdepCXX_FALSE=»
am__fastdepCXX_TRUE=»
am__include=»
am__isrc=»
am__leading_dot=’.’
am__nodep=»
am__quote=»
am__tar=’$$ chof — «$$tardir»‘
am__untar=’$$ xf -‘
bindir=’$/bin’
build=’x86_64-unknown-linux-gnu’
build_alias=»
build_cpu=’x86_64′
build_os=’linux-gnu’
build_vendor=’unknown’
datadir=’$‘
datarootdir=’$/share’
docdir=’$/doc/$‘
dvidir=’$‘
exec_prefix=’NONE’
host=’x86_64-unknown-linux-gnu’
host_alias=»
host_cpu=’x86_64′
host_os=’linux-gnu’
host_vendor=’unknown’
htmldir=’$‘
includedir=’$/include’
infodir=’$/info’
install_sh=’$ /home/suma/repos/jubatus-mpio/ac/install-sh’
libdir=’$/lib’
libexecdir=’$/libexec’
localedir=’$/locale’
localstatedir=’$/var’
mandir=’$/man’
mkdir_p=’/bin/mkdir -p’
oldincludedir=’/usr/include’
pdfdir=’$‘
prefix=’NONE’
program_transform_name=’s,x,x,’
psdir=’$‘
sbindir=’$/sbin’
sharedstatedir=’$/com’
sysconfdir=’$/etc’
target=’x86_64-unknown-linux-gnu’
target_alias=»
target_cpu=’x86_64′
target_os=’linux-gnu’
target_vendor=’unknown’
## ———— ##
## confdefs.h. ##
## ———— ##
/* confdefs.h */
#define PACKAGE_NAME «»
#define PACKAGE_TARNAME «»
#define PACKAGE_VERSION «»
#define PACKAGE_STRING «»
#define PACKAGE_BUGREPORT «»
#define PACKAGE_URL «»
#define PACKAGE «jubatus_mpio»
#define VERSION «0.4.0»
configure: exit 77

This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters

Источник

Hi,

i want to create a Makefile to simplify the compilation of my C++ programs.
It should recursively collect all source files in a parent src directory and automatically create dependency files.

I found an example here but if i try to use it, clang++ complains:

Code:

[xxx@xxx ~/development]$ make
mkdir -p ./build
clang++ -Wfatal-errors -Wall -Wextra -Wpedantic -Wconversion -Wshadow  -o ./build/mybin
clang++: fatal error: no input files
*** Error code 1

Stop.
make: stopped in /home/xxx/development

I understand that the Makefile fails to append the sources to the clang++ command.
Is this because i use

shells/bash

as my shell? How can i make the Makefile work?

Makefile

Code:

CXX = clang++
CXX_FLAGS = -Wfatal-errors -Wall -Wextra -Wpedantic -Wconversion -Wshadow

# Final binary
BIN = mybin
# Put all auto generated stuff to this build dir.
BUILD_DIR = ./build

# List of all .cpp source files.
CPP = $(wildcard src/*.cpp)

# All .o files go to build dir.
OBJ = $(CPP:%.cpp=$(BUILD_DIR)/%.o)
# Gcc/Clang will create these .d files containing dependencies.
DEP = $(OBJ:%.o=%.d)

# Default target named after the binary.
$(BIN) : $(BUILD_DIR)/$(BIN)

# Actual target of the binary - depends on all .o files.
$(BUILD_DIR)/$(BIN) : $(OBJ)
    # Create build directories - same structure as sources.
    mkdir -p $(@D)
    # Just link all the object files.
    $(CXX) $(CXX_FLAGS) $^ -o $@

# Include all .d files
-include $(DEP)

# Build target for every single object file.
# The potential dependency on header files is covered
# by calling `-include $(DEP)`.
$(BUILD_DIR)/%.o : %.cpp
    mkdir -p $(@D)
    # The -MMD flags additionaly creates a .d file with
    # the same name as the .o file.
    $(CXX) $(CXX_FLAGS) -MMD -c $< -o $@

.PHONY : clean
clean :
    # This should remove all generated files.
    -rm $(BUILD_DIR)/$(BIN) $(OBJ) $(DEP)

src/main.cpp

Code:

#include <iostream>

int main(int argc, char* argv[])
{
    std::cout << "HElloe" << std::endl;
    return 0;
}

Thanks.

suma / config.log

This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure, which was
generated by GNU Autoconf 2.69. Invocation command line was
$ ./configure
## ——— ##
## Platform. ##
## ——— ##
hostname = debian-sid-suma
uname -m = x86_64
uname -r = 3.2.0-4-amd64
uname -s = Linux
uname -v = #1 SMP Debian 3.2.35-2
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/local/bin
PATH: /usr/bin
PATH: /bin
PATH: /usr/local/games
PATH: /usr/games
PATH: /home/suma/.cabal/bin
## ———— ##
## Core tests. ##
## ———— ##
configure:2377: checking build system type
configure:2391: result: x86_64-unknown-linux-gnu
configure:2411: checking host system type
configure:2424: result: x86_64-unknown-linux-gnu
configure:2444: checking target system type
configure:2457: result: x86_64-unknown-linux-gnu
configure:2500: checking for a BSD-compatible install
configure:2568: result: /usr/bin/install -c
configure:2579: checking whether build environment is sane
configure:2629: result: yes
configure:2770: checking for a thread-safe mkdir -p
configure:2809: result: /bin/mkdir -p
configure:2822: checking for gawk
configure:2852: result: no
configure:2822: checking for mawk
configure:2838: found /usr/bin/mawk
configure:2849: result: mawk
configure:2860: checking whether make sets $(MAKE)
configure:2882: result: yes
configure:3021: checking for gcc
configure:3048: result: clang
configure:3277: checking for C compiler version
configure:3286: clang —version >&5
Debian clang version 3.0-6 (tags/RELEASE_30/final) (based on LLVM 3.0)
Target: x86_64-pc-linux-gnu
Thread model: posix
configure:3297: $? = 0
configure:3286: clang -v >&5
Debian clang version 3.0-6 (tags/RELEASE_30/final) (based on LLVM 3.0)
Target: x86_64-pc-linux-gnu
Thread model: posix
configure:3297: $? = 0
configure:3286: clang -V >&5
clang: error: argument to ‘-V’ is missing (expected 1 value)
clang: error: no input files
configure:3297: $? = 1
configure:3286: clang -qversion >&5
clang: error: no input files
configure:3297: $? = 1
configure:3317: checking whether the C compiler works
configure:3339: clang -O4 -Wall conftest.c >&5
/tmp/conftest-Fx0fuT.o: file not recognized: File format not recognized
clang: error: linker command failed with exit code 1 (use -v to see invocation)
configure:3343: $? = 1
configure:3381: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME «»
| #define PACKAGE_TARNAME «»
| #define PACKAGE_VERSION «»
| #define PACKAGE_STRING «»
| #define PACKAGE_BUGREPORT «»
| #define PACKAGE_URL «»
| #define PACKAGE «jubatus_mpio»
| #define VERSION «0.4.0»
| /* end confdefs.h. */
|
| int
| main ()
| <
|
| ;
| return 0;
| >
configure:3386: error: in `/home/suma/repos/jubatus-mpio’:
configure:3388: error: C compiler cannot create executables
See `config.log’ for more details
## —————- ##
## Cache variables. ##
## —————- ##
ac_cv_build=x86_64-unknown-linux-gnu
ac_cv_env_CCASFLAGS_set=
ac_cv_env_CCASFLAGS_value=
ac_cv_env_CCAS_set=
ac_cv_env_CCAS_value=
ac_cv_env_CCC_set=
ac_cv_env_CCC_value=
ac_cv_env_CC_set=set
ac_cv_env_CC_value=clang
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_CXX_set=set
ac_cv_env_CXX_value=clang++
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_host=x86_64-unknown-linux-gnu
ac_cv_path_install=’/usr/bin/install -c’
ac_cv_path_mkdir=/bin/mkdir
ac_cv_prog_AWK=mawk
ac_cv_prog_ac_ct_CC=clang
ac_cv_prog_make_make_set=yes
ac_cv_target=x86_64-unknown-linux-gnu
## —————— ##
## Output variables. ##
## —————— ##
ACLOCAL=’$ /home/suma/repos/jubatus-mpio/ac/missing —run aclocal-1.11′
AMDEPBACKSLASH=»
AMDEP_FALSE=»
AMDEP_TRUE=»
AMTAR=’$$‘
AR=»
AUTOCONF=’$ /home/suma/repos/jubatus-mpio/ac/missing —run autoconf’
AUTOHEADER=’$ /home/suma/repos/jubatus-mpio/ac/missing —run autoheader’
AUTOMAKE=’$ /home/suma/repos/jubatus-mpio/ac/missing —run automake-1.11′
AWK=’mawk’
CC=’clang’
CCAS=»
CCASDEPMODE=»
CCASFLAGS=»
CCDEPMODE=»
CFLAGS=’-O4 -Wall ‘
CPP=»
CPPFLAGS=»
CXX=’clang++’
CXXCPP=»
CXXDEPMODE=»
CXXFLAGS=’-O4 -Wall ‘
CYGPATH_W=’echo’
DEFS=»
DEPDIR=»
DLLTOOL=»
DSYMUTIL=»
DUMPBIN=»
ECHO_C=»
ECHO_N=’-n’
ECHO_T=»
EGREP=»
EXEEXT=»
FGREP=»
GREP=»
INSTALL_DATA=’$ -m 644′
INSTALL_PROGRAM=’$‘
INSTALL_SCRIPT=’$‘
INSTALL_STRIP_PROGRAM=’$(install_sh) -c -s’
LD=»
LDFLAGS=»
LIBOBJS=»
LIBS=»
LIBTOOL=»
LIPO=»
LN_S=»
LTLIBOBJS=»
MAKEINFO=’$ /home/suma/repos/jubatus-mpio/ac/missing —run makeinfo’
MANIFEST_TOOL=»
MKDIR_P=’/bin/mkdir -p’
NM=»
NMEDIT=»
OBJDUMP=»
OBJEXT=»
OTOOL64=»
OTOOL=»
PACKAGE=’jubatus_mpio’
PACKAGE_BUGREPORT=»
PACKAGE_NAME=»
PACKAGE_STRING=»
PACKAGE_TARNAME=»
PACKAGE_URL=»
PACKAGE_VERSION=»
PATH_SEPARATOR=’:’
RANLIB=»
SED=»
SET_MAKE=»
SHELL=’/bin/bash’
STRIP=»
VERSION=’0.4.0′
ac_ct_AR=»
ac_ct_CC=’clang’
ac_ct_CXX=»
ac_ct_DUMPBIN=»
am__EXEEXT_FALSE=»
am__EXEEXT_TRUE=»
am__fastdepCCAS_FALSE=»
am__fastdepCCAS_TRUE=»
am__fastdepCC_FALSE=»
am__fastdepCC_TRUE=»
am__fastdepCXX_FALSE=»
am__fastdepCXX_TRUE=»
am__include=»
am__isrc=»
am__leading_dot=’.’
am__nodep=»
am__quote=»
am__tar=’$$ chof — «$$tardir»‘
am__untar=’$$ xf -‘
bindir=’$/bin’
build=’x86_64-unknown-linux-gnu’
build_alias=»
build_cpu=’x86_64′
build_os=’linux-gnu’
build_vendor=’unknown’
datadir=’$‘
datarootdir=’$/share’
docdir=’$/doc/$‘
dvidir=’$‘
exec_prefix=’NONE’
host=’x86_64-unknown-linux-gnu’
host_alias=»
host_cpu=’x86_64′
host_os=’linux-gnu’
host_vendor=’unknown’
htmldir=’$‘
includedir=’$/include’
infodir=’$/info’
install_sh=’$ /home/suma/repos/jubatus-mpio/ac/install-sh’
libdir=’$/lib’
libexecdir=’$/libexec’
localedir=’$/locale’
localstatedir=’$/var’
mandir=’$/man’
mkdir_p=’/bin/mkdir -p’
oldincludedir=’/usr/include’
pdfdir=’$‘
prefix=’NONE’
program_transform_name=’s,x,x,’
psdir=’$‘
sbindir=’$/sbin’
sharedstatedir=’$/com’
sysconfdir=’$/etc’
target=’x86_64-unknown-linux-gnu’
target_alias=»
target_cpu=’x86_64′
target_os=’linux-gnu’
target_vendor=’unknown’
## ———— ##
## confdefs.h. ##
## ———— ##
/* confdefs.h */
#define PACKAGE_NAME «»
#define PACKAGE_TARNAME «»
#define PACKAGE_VERSION «»
#define PACKAGE_STRING «»
#define PACKAGE_BUGREPORT «»
#define PACKAGE_URL «»
#define PACKAGE «jubatus_mpio»
#define VERSION «0.4.0»
configure: exit 77

This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters

Источник

g++: fatal error: no input files #243

Comments

Haghrah commented Nov 6, 2018 •

I am trying to compile and run a simple hello world c++ code. g++ says no input files:

g++: fatal error: no input files
compilation terminated.

It seems that the g++ is not running in the same directory which c++ file is placed or maybe file path is not correct in compilation command. How to solve the problem?

The text was updated successfully, but these errors were encountered:

Godsgrav3 commented Nov 28, 2018

hi @Haghrah Do you still have this issue? If so check if g++ is in your PATH variables by opening CMD and entering the following: «gcc —version» and «g++ —version». if you do not see information check you my issue #132

LiamInfoSec commented May 17, 2019

I have the same problem when I run «g++ —version»;

g++ (MinGW.org GCC-8.2.0-3) 8.2.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

michael-rishi commented Jun 8, 2019 •

in my terminal i am trying to run a welcome.cpp file that’s code is

# include
using namespace std;
int main()
<
cout >> «Hello What’s your name »
char name = «»
cin > msg >> endl
cout >> «» >> endl
>

and when I type «g++ -o welcome.cpp» then enter this is what comes up

Godsgrav3 commented Jun 8, 2019 •

for one, your code will not compile, you have multiple fatal errors in your code.
#include is not used, is necessary for cout.
cout doesn’t use >>, but

Источник

Понравилась статья? Поделить с друзьями:
  • Clamav ошибка обновления
  • Clamav scanning error 8 init error
  • Clack ошибка 103
  • Clack ошибка 102
  • Clack ошибка 101