Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V2 1/2] tcl: add support for static builds
Date: Sat, 7 Mar 2015 16:05:17 +0100	[thread overview]
Message-ID: <54FB13AD.5080008@imgtec.com> (raw)
In-Reply-To: <20150307155634.605f5a68@free-electrons.com>

Dear Thomas Petazzoni,


On 07/03/15 15:56, Thomas Petazzoni wrote:
> Dear Vicente Olivert Riera,
> 
> On Sat, 7 Mar 2015 15:28:50 +0100, Vicente Olivert Riera wrote:
> 
>> I guess you could need tcl to build something that depends on it, and
>> link against libtcl8.6.a, for instance.
> 
> If you need tcl to build something, then it's the host tcl, not the
> target tcl.

uhm..., I'm sorry but I don't understand what you mean.

If you have a package that depends on tcl (it links against libtcl8.6.a,
for instance), then you will need the target tcl (actually the staging
one), which has the right architecture for your target, no? The host tcl
would have the same architecture as the host machine which may not be
the same as the target one.

Am I missing anything?

Regards,
--
Vincent


> Thomas
> 

  reply	other threads:[~2015-03-07 15:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07 13:22 [Buildroot] [PATCH V2 1/2] tcl: add support for static builds Vicente Olivert Riera
2015-03-07 13:22 ` [Buildroot] [PATCH V2 2/2] tcl: rename BR2_PACKAGE_TCL_SHLIB_ONLY to be more consistent Vicente Olivert Riera
2015-03-07 13:43   ` Thomas Petazzoni
2015-03-07 13:42 ` [Buildroot] [PATCH V2 1/2] tcl: add support for static builds Thomas Petazzoni
2015-03-07 14:28   ` Vicente Olivert Riera
2015-03-07 14:56     ` Thomas Petazzoni
2015-03-07 15:05       ` Vicente Olivert Riera [this message]
2015-03-07 15:35         ` Thomas Petazzoni
2015-03-07 16:12           ` Vicente Olivert Riera
2015-03-07 16:44   ` Arnout Vandecappelle

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=54FB13AD.5080008@imgtec.com \
    --to=vincent.riera@imgtec.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