public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Gordon McKay <gordon_mckay@btinternet.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: GCC fails to find headers under Ubuntu
Date: Fri, 13 Nov 2020 19:08:44 +0000	[thread overview]
Message-ID: <CAH6eHdQdEhYUDqq-4V6fDyJ-8rKG6Pon9-1541NPqsbnK-taLg@mail.gmail.com> (raw)
In-Reply-To: <5faeac7f.1c69fb81.b55df.57c2SMTPIN_ADDED_BROKEN@mx.google.com>

On Fri, 13 Nov 2020 at 15:55, Gordon McKay via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> Hi,
>
> I have a C project, star-charter, which is a straight clone from GitHub.
>
> From my $Home in Ubuntu I have a folder, Cprojects, where I keep all my C/C++ projects, each in a separate sub-folder.
>
> My start-charter GitHub clone is in the star-charter subfolder
>
> The makefile is in the star-charter subfolder
>
> All of the source is in the src sub folder of star-charter
>
> Main.c is in the src sub-folder.
>
> Various libraries and headers are in sub-folders of src, for eample the gsl headers
>
> When I attempt to compile main.c which refere to the gsl headers in INCLUDE statements with the sub-folder gsl and header name , a file not found error is thrown.

What is the exact command you are running, and the exact error?

We can't help without accurate information about exactly what you're
doing and what the error is.

       reply	other threads:[~2020-11-13 19:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5faeac7f.1c69fb81.b55df.57c2SMTPIN_ADDED_BROKEN@mx.google.com>
2020-11-13 19:08 ` Jonathan Wakely [this message]
2020-11-15 15:16   ` GORDON MCKAY
     [not found] <5faeabef.1c69fb81.3ead6.65e7SMTPIN_ADDED_BROKEN@mx.google.com>
2020-11-14  2:56 ` Jim Wilson
2020-11-13 15:53 Gordon McKay

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAH6eHdQdEhYUDqq-4V6fDyJ-8rKG6Pon9-1541NPqsbnK-taLg@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gordon_mckay@btinternet.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).