From: Marc Kleine-Budde <mkl@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Javier Fileiv <javier.fileiv@gmail.com>
Subject: Re: [ptxdist] Problem adding new package.
Date: Wed, 09 Oct 2013 13:11:17 +0200 [thread overview]
Message-ID: <525539D5.3060400@pengutronix.de> (raw)
In-Reply-To: <CABvwO2DtA3Vu_QxyrhJxx2V4QC1_8P1LbHPtcb7Qi-VxG+4g=g@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1113 bytes --]
Hello Javier,
please don't top-post.
On 10/09/2013 09:27 AM, Javier Fileiv wrote:
> One question...the patch you sent me>..I don't know which file I have to
> apply it to... I couldnt find the gcc_defaults.mak
It's in speech_tools-2.1-release.tar.gz
You have to create a patches dir in your BSP, named after you package.
To figure out use:
ptxdist print SPEECH_TOOLS
The output is probably "speech_tools-2.1-release". So create a dir
"patches/speech_tools-2.1-release" and place the attached patch there.
Create a series file in that directory, too:
ls 0* > series
Then add:
<YOUR_NEW_PACKGE>_MAKE_OPT := $(CROSS_ENV_CC)
to rules/<your_new_pacakge>.make Then rebuild:
ptxdist clean <your_new_pacakge>
ptxdist targetinstall <your_new_pacakge>
Everything totally untested,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.1.2: 0001-gcc_defaults-HACK-build-system-to-make-CC-and-CXX-ov.patch --]
[-- Type: text/x-diff; name="0001-gcc_defaults-HACK-build-system-to-make-CC-and-CXX-ov.patch", Size: 826 bytes --]
From a86bf6be627f876c370c9fafcaf304f1e85a0f17 Mon Sep 17 00:00:00 2001
From: Marc Kleine-Budde <mkl@pengutronix.de>
Date: Wed, 9 Oct 2013 09:30:38 +0200
Subject: [PATCH] gcc_defaults: HACK build system to make CC and CXX
overwriteable
---
config/compilers/gcc_defaults.mak | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/config/compilers/gcc_defaults.mak b/config/compilers/gcc_defaults.mak
index a885266..7240ab3 100644
--- a/config/compilers/gcc_defaults.mak
+++ b/config/compilers/gcc_defaults.mak
@@ -38,8 +38,8 @@
## ##
###########################################################################
-CC=gcc
-CXX=gcc
+CC=$(CC)
+CXX=$(CC)
ifeq ($(OSTYPE),Darwin)
CXX=g++
endif
--
1.8.4.rc3
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-10-09 11:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 18:14 Javier Fileiv
2013-10-05 18:27 ` Marc Kleine-Budde
2013-10-06 8:56 ` Javier Fileiv
[not found] ` <CABvwO2D==XqM_d06=kA8PZPTQdtNPWdHwOnBXrexGb6HZwZh2w@mail.gmail.com>
2013-10-06 9:59 ` [ptxdist] Fwd: " Javier Fileiv
2013-10-06 10:04 ` [ptxdist] " Marc Kleine-Budde
2013-10-09 7:22 ` Javier Fileiv
2013-10-09 7:27 ` Javier Fileiv
2013-10-09 11:11 ` Marc Kleine-Budde [this message]
2013-10-09 18:50 ` Javier Fileiv
2013-10-09 19:21 ` Marc Kleine-Budde
2013-10-10 19:53 ` Javier Fileiv
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=525539D5.3060400@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=javier.fileiv@gmail.com \
--cc=ptxdist@pengutronix.de \
/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