How to solve 'collect2: ld returned 1 exit status '?

velvetmist · 02-21-2018, 08:34 AM

Hi guys, today I wanted to start learning about programming, so I wanted to do that Hello World crap thinking it would be really easy, so I wrote the program:

Code:

#include<stdio.h>

#include<stdlib.h>

int main()

{

printf("\nHello World!");

return(0);

}

And for compiling it I wrote the command:

Code:

gcc -Wall -W -Werror helloworld.c -o helloworld

But it didn't work and I got:

Code:

collect2: ld returned 1 exit status

I googled for a solution but I didn't found anything, help me please, thx.

BW-userx · 02-21-2018, 08:51 AM

if your code is correct in how it is being presented here,then add spaces between your include and file

Code:

#include <stdio.h>
not
#include<stdio.h>

I just tested that theoy and well make a lair out of myself?

Code:

#include<stdio.h>

int main(void)
{
    printf("hello wOlrD\n");
return 0;
}

Code:

bash-4.3# nano mainhello.c
bash-4.3# gcc mainhello.c
bash-4.3# ./a.out
hello wOlrD

without errors.

Quote:

The exit status error just signals that the linking step in the build process encountered some errors.

just compile it like I did with default output and see what that does for you, your program will be named a.out

c++

Code:

#include <iostream>

using namespace std;

int main()
{
  cout<<"HEllO World"<<endl;

return 0;
}

Code:

bash-4.3# nano mainhello.cpp
bash-4.3# g++ mainhello.cpp
bash-4.3# ./a.out
HEllO World

BASH

Code:

bash-4.3# cat >> myhello 
#!/bin/bash
echo "HELLOS WOrld"
^D

bash-4.3# ls myhello
myhello

bash-4.3# chmod +x myhello
bash-4.3# ./myhello
HELLOS WOrld

Excuse me for being confused, because I am not getting the same error. in any of the three, BASH will not return that error, I just thought I'd add that for you benefit to show you BASH too.

You could run ldconfig on your system to see update your libs.
http://man7.org/linux/man-pages/man8/ldconfig.8.html
But I'd just try gcc helloworld.c first

velvetmist · 02-21-2018, 09:17 AM

[QUOTE=BW-userx;5822380]

Code:

bash-4.3# gcc mainhello.c

I tried it but it didn't work

When I write that command I get the same error.

michaelk · 02-21-2018, 09:45 AM

Quote:

collect2: ld returned 1 exit status

Is that the entire error/warning message displayed from the output of the gcc command? Please post the entire output.

As you have discovered the compiler does not care about spaces...

velvetmist · 02-21-2018, 10:06 AM

Quote:

Originally Posted by michaelk

Is that the entire error/warning message displayed from the output of the gcc command? Please post the entire output.

Code:

/usr/bin/ld: cannot open output file helloworld: Permission denied
collect2: error: ld returned 1 exit status

I also tried with: https://askubuntu.com/questions/4666...mission-denied
First with:

Code:

sudo chown -R "$USER:" /path/to/the/directory

it didn't worked so i tried with:

Code:

chmod -R 700 /path/to/the/directory

and then when I tried to cd to that directory it says:

Code:

bash: cd: /path/to/the/directory: Permission denied

BW-userx · 02-21-2018, 10:15 AM

where is it exacly? on your home/user why are you changing permissions?

755 read write execute user

Code:

Frequently used numeric parameters for chmod
755	The general preferred permissions for almost all the files on your disk
775	General files used when working as a Group (Others can only view/execute your files)
770	Important files used when working as a Group (Others cannot do anything with your files)

using -R changes every thing

Code:

echo $USER: <---- that colon is not suppose to be there

it screws it up

Code:

$ echo $USER:
userx:
userx@slackwhere101:~
$ echo $USER 
userx

there is no userx:
that might be it

Code:

userx@slackwhere101:~
$ touch permissions700
 
$ chmod 700 permissions700

$ ls -la permissions700
-rwx------ 1 userx users 23 Feb 21 10:22 permissions700

$ echo "in file permissions700" >> permissions700
 
$ cat permissions700
in file permissions700

when changing owner I usually add user group, but for whatever reasons you're just making it so no one but you can do anything to that dir and whats in it.

Code:

chown userx:users /path/to/dir -R

nevertheless, remove the : colon and redo it.

michaelk · 02-21-2018, 10:15 AM

Lets start from scratch.

What distribution/version are you running?

How did you create helloworld.c? What were the exact commands used. What directory is helloworld.c located.

velvetmist · 02-21-2018, 11:06 AM

Well, I tried to change the permissions, I mean I wrote the command:
sudo chmod 777 /path/to/my/folder
but when I put:
ls -l path/to/my/folder
I got
-rwx------ 1 root rooot 100

Quote:

What distribution/version are you running?

How did you create helloworld.c? What were the exact commands used. What directory is helloworld.c located.

I've got Debian.

I first wrote

Code:

sudo nano helloworld.c

Then the program I told you above, and then I tried to compilated it.

BW-userx · 02-21-2018, 11:30 AM

Quote:

Originally Posted by velvetmist

Well, I tried to change the permissions, I mean I wrote the command:
sudo chmod 777 /path/to/my/folder
but when I put:
ls -l path/to/my/folder
I got
-rwx------ 1 root rooot 100

I've got Debian.

I first wrote

Code:

sudo nano helloworld.c

Then the program I told you above, and then I tried to compilated it.

mmm why are you root?
programming is not system admin. Nonetheless, if you are logged in as root, which I don't think you'd be because Debain hides root account.
and you are an user and want to use that dir

Code:

sudo chown user:group  /path/to/dir -R
#to fix it so you can use it as a user, 
the group is a group you belong to, mostly your main group. 
then,

as I am in root account at the moment.

Code:

root@slackwhere101:~
# login userx
Password: 
Linux 4.4.14.
No mail.

The problem with the gene pool is that there is no lifeguard.


userx@slackwhere101:~$ mkdir ~/testdir

userx@slackwhere101:~$ ls -la ~/testdir
total 8
drwxr-xr-x  2 userx users 4096 Feb 21 11:35 ./
drwx--x--x 34 userx users 4096 Feb 21 11:35 ../

userx@slackwhere101:~$ sudo mkdir ~/testdir2
userx@slackwhere101:~$ ls -la ~/testdir2
total 8
drwxr-xr-x  2 root  root  4096 Feb 21 11:35 ./
drwx--x--x 35 userx users 4096 Feb 21 11:35 ../

userx@slackwhere101:~$ sudo chown userx:users ~/testdir2 -R
userx@slackwhere101:~$ ls -la ~/testdir2
total 8
drwxr-xr-x  2 userx users 4096 Feb 21 11:35 ./
drwx--x--x 35 userx users 4096 Feb 21 11:35 ../

userx@slackwhere101:~$ chmod 700 ~/testdir2
userx@slackwhere101:~$ ls -la ~/testdir2
total 8
drwx------  2 userx users 4096 Feb 21 11:35 ./
drwx--x--x 35 userx users 4096 Feb 21 11:35 ../

if you look at the command sudo and creating a dir who gets ownership of it, and whoever has ownership of the dir or file can do whatever they want to it. even changes permissions on it, no need to use sudo if user owns the dir.

michaelk · 02-21-2018, 11:55 AM

sudo allows a regular user elevated priveledges to run commands but it isn't necessarily for what you are doing.

As suggested run the chown command to change pemissions for your file.

astrogeek · 02-21-2018, 06:49 PM

I am coming in here a little late in the game, so let me recap and offer my own suggestions in addition to the excellent comments already posted.

First, when posting error messages, especially compiler messages, always include any lines which indicate error, failure, missing files or permission problems, etc. Very often the final error message is the result of something already reported, such as the file permission problem in this case. That will save time and effort and help others to more quickly understand what is happening.

I will defer to others to help with fixing the bad file permissions if they like, but please note that this is a separate, self-inflicted problem not actually part of your initial interest in building the hello world program. That resulted from unnecessary use of sudo and chmod, not from any normal code or compile problem - so knowing that I might suggest that you simply start over, without sudo, write, compile and run your hello world program. Then try to learn about file permissions, sudo, etc. as a separate and better focused task.

And as I am sure you will hear from others - often - never, ever try to fix a problem like this...

Quote:

Originally Posted by velvetmist

Well, I tried to change the permissions, I mean I wrote the command:
sudo chmod 777 /path/to/my/folder...

Doing so is always wrong, will mask other problems and dig yourself deeper into whatever hole you are stuck in at the moment!

Try to develop a reflexive "STOP!" response when told to chmod 777, and don't form that very bad habit! Instead, spend just a little time trying to understand the basic why and how of Unix/Linux file permissions. It is really pretty simple and well founded, and you will have to learn your way around it sooner or later - make it sooner!

A little time spent reading well written online references such as Rute User's Tutorial and Exposition, Bash Guide for Beginners, Advanced Linux Programming Book, and many others, will be well spent! And all of the will include some version of Hello World to help get you started!

Good luck!

michaelk · 02-21-2018, 07:05 PM

Quote:

I might suggest that you simply start over, without sudo, write, compile and run your hello world program. Then try to learn about file permissions, sudo, etc. as a separate and better focused task.

Exactly...

BW-userx · 02-21-2018, 07:12 PM

I have a bin and scripts in my home dir where I put my stuff in and sub dirs to try and keep it organized.

NevemTeve · 02-21-2018, 11:31 PM

@OP Go back to square 1 (delete the previous files), but this time forget su, sudo, chmod and alike. All you need is text-editor and gcc. And if you get some error messages quote all of them, not only the last line.
[Edit: I see it has been suggested again and again. You should actually do it.]

Delcaran · 02-22-2018, 02:26 AM

Bored at work so replying just for clarity. You should do as following:

Delete everything you have done.
As normal user, create a new directory.
In that directory, create helloworld.c. Beware of the spaces after #include: spaces aren't normaly an issue in code, but #include is a preprocessor directive and is not exatcly code...
Compile, link and execute.
Get yourself a copy of the Kernighan & Ritchie, the Bible for C programming.