public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Or Goshen <oberonc@gmail.com>
To: crossgcc@sourceware.org
Subject: Missing c_nano.a and g_nano.a in arm-unknown-eabi
Date: Sat, 12 Oct 2019 11:51:00 -0000	[thread overview]
Message-ID: <CAKx3Guz3TP7b9N3YWtQ9Uq-Gh2+tiuXFYsqMpwfH-tWWDoVktQ@mail.gmail.com> (raw)

Hi,

I'm creating a cross compile toolchain for Nordic nRf52840 (build and host
are my desktop).
After "ct-ng build" finish (release 1.24.0) I try to make an example from
Nordic SDK (15.3.0) and I get the following error:









*bash-4.4$ make VERBOSE=1Linking target: _build/nrf52840_xxaa.out"make" -s
--no-print-directory -f "../../../../../../components/toolchain/gcc/dump.mk
<http://dump.mk>" VARIABLE=CONTENT_TO_DUMP > _build/nrf52840_xxaa.in
<http://nrf52840_xxaa.in>'/home/[my
username]/x-tools/arm-unknown-eabi/bin/arm-unknown-eabi-gcc' -O3 -g3
-mthumb -mabi=aapcs -L../../../../../../modules/nrfx/mdk
-Tusbd_audio_gcc_nrf52.ld -mcpu=cortex-m4 -mfloat-abi=hard
-mfpu=fpv4-sp-d16 -Wl,--gc-sections --specs=nano.specs
@_build/nrf52840_xxaa.in <http://nrf52840_xxaa.in>
-Wl,-Map=_build/nrf52840_xxaa.map -o
_build/nrf52840_xxaa.out/home/oberon/x-tools/arm-unknown-eabi/lib/gcc/arm-unknown-eabi/8.3.0/../../../../arm-unknown-eabi/bin/ld:
cannot find
-lc_nano/home/oberon/x-tools/arm-unknown-eabi/lib/gcc/arm-unknown-eabi/8.3.0/../../../../arm-unknown-eabi/bin/ld:
cannot find
-lg_nano/home/oberon/x-tools/arm-unknown-eabi/lib/gcc/arm-unknown-eabi/8.3.0/../../../../arm-unknown-eabi/bin/ld:
cannot find -lc_nanocollect2: error: ld returned 1 exit statusmake: ***
[../../../../../../components/toolchain/gcc/Makefile.common:294:
_build/nrf52840_xxaa.out] Error 1*

This is actually the same as this issue
<https://github.com/crosstool-ng/crosstool-ng/issues/1203>

Was this solved ?
Is there a quick fix ?

Thanks,

Or

                 reply	other threads:[~2019-10-12 11:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAKx3Guz3TP7b9N3YWtQ9Uq-Gh2+tiuXFYsqMpwfH-tWWDoVktQ@mail.gmail.com \
    --to=oberonc@gmail.com \
    --cc=crossgcc@sourceware.org \
    /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).