public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ben <bkamen@benjammin.net>
To: cygwin@cygwin.com
Subject: Using ARM GNU GCC with Cygwin
Date: Sat, 4 Apr 2020 04:00:34 -0500	[thread overview]
Message-ID: <a63033db-7f0f-cf87-3de9-f544f4aa320b@benjammin.net> (raw)

Hey all,

  I've never used Cygwin much in the past for compiling let alone cross-compiling to another arch.

I've been playing with ARM GNU GCC and some examples from nordic semiconductor for some of their demo boards (The Thingy)

The make file that comes with the project includes source files using the (abspath ../main.c) (as one example) which GCC really seems to hate.

The output from GCC is the full path (/home/bkamen/workspace-nordic/.....) right down to the file and gcc tells me it can't find the file.

if I change the mail file to use a relative path, gcc can find that... but ultimately I'm trying to understand the issue than just patch around it.

I'm using the arm-gcc from the developer.arm.com website.

Is there something else I'm missing? What files can I offer (like the makefile) that can help determine the issue?

Thanks,

  -Ben



             reply	other threads:[~2020-04-04  9:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-04  9:00 Ben [this message]
2020-04-04 10:23 ` Eliot Moss
2020-04-04 18:15   ` Ben
2020-04-04 14:32 ` Kaz Kylheku
2020-04-04 18:18   ` Ben
2020-04-04 18:58   ` Åke Rehnman
2020-04-04 19:10     ` Ben
2020-04-04 20:39       ` Marco Atzeri
2020-04-08 20:50     ` Kaz Kylheku
2020-04-08 20:58       ` David Rothenberger
2020-04-08 21:13         ` Ben Kamen
2020-04-09  0:33           ` Kaz Kylheku
2020-04-09  0:17         ` Kaz Kylheku
2020-04-04 21:40   ` Andrey Repin
2020-04-04 21:56     ` Eliot Moss
2020-04-05  8:49     ` Csaba Raduly
2020-04-07 17:36       ` Ben
2020-04-04 19:11 ` Åke Rehnman
2020-04-04 19:31   ` Åke Rehnman

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=a63033db-7f0f-cf87-3de9-f544f4aa320b@benjammin.net \
    --to=bkamen@benjammin.net \
    --cc=cygwin@cygwin.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).