Ahh I figured it out!
Instead of using ~/pset1/hello/ $
go back to just the directory pset by using change directory
~/pset1/hello/ $ cd ~/pset1/
then add your ls command
~/pset1/ $ ls
~/pset1/ $ clang hello.c
adds the machine code to your directory and then you can execute!
My only questions now is about the hello/ . ...
Without seeing your code, no. But it's almost certain that you have a syntax error. Perhaps you put a semicolon on the end of the line int main(void), or something like that.
Take a close look at whatever code is just before the error.
Just check50 cs50/2018/x/hello, without mentioning hello.c (as it used to be years ago). The checker will get a list of files to upload.
according to my experience it takes a maximum of 2 weeks to get your pset submission graded. usually it is graded much faster. If you've been waiting for more than 2 weeks though,if you continue to have problems, you can submit the problem again or you may email Robert Bowden at firstname.lastname@example.org.
Are you working in the online IDE or in one of the downloaded environments like VMware? If you are working in VMware, the license expires at the end of the year, in a few days. It also raises another question. Are you signed up for the class that starts at the beginning of the year, or the one that ends Dec 31, 2015? There's simply not enough time to ...
Actually, you don't really have a problem. You just need a little instruction on a couple of nuances that you're tripping on.
First, make is saying up to date because the output of the compiler, file "hello", is current because hello.c has not been changed since the last time you ran "make hello". If you were to edit hello.c and make any changes,
to be able to use check50 make sure your appliance is up to date, by typing the command update50 in Terminal.
Also check the location of the file you should first cd the location for example:
cd Dropbox/pset1 , after you are in this directory try again.
If this is okay, check your print statement