Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] Makefile: Symlink lib32 to lib for MIPS64/n32
Date: Thu, 11 Jul 2013 15:40:18 +0200	[thread overview]
Message-ID: <20130711154018.3ee37e86@skate> (raw)
In-Reply-To: <CAG2jQ8iHKiuRCGvMPOpgqmXdAuYgzJP6C4+CGq=dUz6p6JMTJw@mail.gmail.com>

Dear Markos Chandras,

On Thu, 11 Jul 2013 12:22:32 +0100, Markos Chandras wrote:

> > Are you experiencing this problem with a toolchain built via buildroot?
> > In my case, it is with an external toolchain, so package/gcc/gcc.mk
> > isn't used then.
> 
> Yeah you are correct. This problem is not specific to buildroot
> toolchains that's why I added
> the fix in the root Makefile.

So, it would be needed for both the internal toolchain backend and the
external toolchain backend?

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-07-11 13:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 13:06 [Buildroot] [PATCH v2] Makefile: Symlink lib32 to lib for MIPS64/n32 Markos Chandras
2013-07-09 10:26 ` Markos Chandras
2013-07-11  9:24 ` Thomas De Schampheleire
2013-07-11 10:59   ` Thomas Petazzoni
2013-07-11 11:08     ` Markos Chandras
2013-07-11 11:18       ` Thomas De Schampheleire
2013-07-11 11:22         ` Markos Chandras
2013-07-11 13:40           ` Thomas Petazzoni [this message]
2013-07-11 14:00             ` Markos Chandras
2013-07-11 14:07               ` Thomas Petazzoni
2013-07-11 14:30                 ` Markos Chandras
2013-07-11 14:19               ` Thomas De Schampheleire
2013-07-11 14:31                 ` Markos Chandras
2013-07-12  8:10                 ` Thomas Petazzoni
2013-07-14 22:07                   ` Markos Chandras
2013-07-20 10:27                     ` Markos Chandras

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=20130711154018.3ee37e86@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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