From: Ruben Louw <lfxciii@gmail.com>
To: Juergen Beisert <jbe@pengutronix.de>
Subject: Re: [ptxdist] Gdb debugging helper [PATCH]
Date: Fri, 11 Jan 2013 15:16:45 +0200 [thread overview]
Message-ID: <CAOP6b3imi2VmaEAYAwTxbNM=B+YoHhui420ZF9K_p9z1CNQpBg@mail.gmail.com> (raw)
In-Reply-To: <201301111412.37126.jbe@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1282 bytes --]
thanks Juergen
That was my problem, I removed the already built Toolchain that was in my
home directory. Now it wants to download everything.
Oh well, mental note to self, dont just remove stuff. I walk seems like a
great idea, would rather buy you, Tim and Michael a beer ;)
Thanks for all your help guys.
Regards
Ruben
On Fri, Jan 11, 2013 at 3:12 PM, Juergen Beisert <jbe@pengutronix.de> wrote:
> Hi Ruben,
>
> Ruben Louw wrote:
> > How do I partially rebuild the cross-gdb package?
>
> With the commands I mentioned. If you have kept your already built
> OSELAS.Toolchain-2012.12.0 build directory, with "ptxdist clean <package
> name>; ptxdist go" you can force the re-build of the package <package
> name>.
>
> > it keeps downloading stuff.
>
> ???
>
> > Should i remove the previous toolchain before rebuilding it, if so,
> > how do i remove it?
>
> If you really want to start from scratch:
>
> ~$ rm -rf /opt/OSELAS.Toolchain-2012.12.0/<your toolchain to remove>
> ~/OSELAS.Toolchain-2012.12.0$ ptxdist clean
> ~/OSELAS.Toolchain-2012.12.0$ ptxdist go
>
> And then go for a walk. :)
>
> Regards,
> Juergen
>
> --
> Pengutronix e.K. | Juergen Beisert
> |
> Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
>
[-- Attachment #1.2: Type: text/html, Size: 1878 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-01-11 13:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 7:30 [ptxdist] Gdb debugging helper Ruben Louw
2013-01-11 8:09 ` Juergen Beisert
2013-01-11 8:22 ` Ruben Louw
2013-01-11 8:40 ` Juergen Beisert
2013-01-11 8:47 ` Ruben Louw
2013-01-11 9:42 ` Michael Olbrich
2013-01-11 10:58 ` Ruben Louw
2013-01-11 9:42 ` [ptxdist] Gdb debugging helper [PATCH] Tim Sander
2013-01-11 10:57 ` Ruben Louw
2013-01-11 12:27 ` Tim Sander
2013-01-11 12:30 ` Ruben Louw
2013-01-11 12:45 ` Juergen Beisert
2013-01-11 12:57 ` Ruben Louw
2013-01-11 13:12 ` Juergen Beisert
2013-01-11 13:16 ` Ruben Louw [this message]
2013-01-11 13:25 ` Juergen Beisert
2013-01-11 13:33 ` Ruben Louw
2013-01-11 13:39 ` Ruben Louw
2013-01-11 13:49 ` Juergen Beisert
2013-01-11 12:30 ` Michael Olbrich
2013-01-11 12:37 ` Ruben Louw
2013-01-11 12:42 ` Ruben Louw
2013-01-11 13:00 ` Michael Olbrich
2013-01-11 13:02 ` Ruben Louw
2013-01-11 13:18 ` Michael Olbrich
2013-01-11 13:20 ` Ruben Louw
2013-01-11 13:21 ` Ruben Louw
2013-01-11 13:24 ` Tim Sander
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='CAOP6b3imi2VmaEAYAwTxbNM=B+YoHhui420ZF9K_p9z1CNQpBg@mail.gmail.com' \
--to=lfxciii@gmail.com \
--cc=jbe@pengutronix.de \
--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