[Buildroot] fakeroot patch

[Buildroot] fakeroot patch

[J. Spence]

Did that last patch to the fakeroot package break anyone else's build?  The debian server that the patch now points to is responding 404 when the build system tries to get the fakeroot tarball.

[Buildroot] fakeroot patch

[Hamish Moffatt]

On Wed, Mar 12, 2008 at 06:50:41PM -0700, J. Spence wrote:
> Did that last patch to the fakeroot package break anyone else's build?  The debian server that the patch now points to is responding 404 when the build system tries to get the fakeroot tarball.

Yes the patch was wrong:

http://buildroot.uclibc.org/cgi-bin/viewcvs.cgi/trunk/buildroot/package/fakeroot/fakeroot.mk?rev=21316&r1=21289&r2=21316

-FAKEROOT_SOURCE:=fakeroot_$(FAKEROOT_VERSION).tar.gz
+FAKEROOT_SOURCE:=fakeroot-$(FAKEROOT_VERSION).tar.gz

This didn't need changing.

Please all, test your commits.

Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

[Buildroot] fakeroot patch

[Peter Korsgaard]

>>>>> "Hamish" == Hamish Moffatt <hamish@cloud.net.au> writes:

Hi,

 Hamish> -FAKEROOT_SOURCE:=fakeroot_$(FAKEROOT_VERSION).tar.gz
 Hamish> +FAKEROOT_SOURCE:=fakeroot-$(FAKEROOT_VERSION).tar.gz

 Hamish> This didn't need changing.

Thanks - Fixed.

 Hamish> Please all, test your commits.

Yes, please.

-- 
Bye, Peter Korsgaard

[Buildroot] fakeroot patch

[Peter Korsgaard]

>>>>> "Jeff" == Jeff Bailey <jeffbailey@google.com> writes:

 > Hi! ?Your patch at?http://git.buildroot.net/buildroot/commit/?id=
 > f18c33b4cc9c344c6ac8e28bfac5ae42befc8b1c is confusing.

 > Why did you drop the fakeroot patch? ?I do use powerpc64le to build.

So your build machine (the one you run Buildroot on, not the one you are
cross compiling for) is a powerpc64le machine?

-- 
Bye, Peter Korsgaard 

[Buildroot] fakeroot patch

[Jeff Bailey]

Correct.  While most of our builds happen on x86 targeting ppc64le, when
doing development I use the ppc64le system natively to speed up build/test
iterations.

Tks,
Jeff Bailey

On Thu Jul 10 2014 at 12:12:31 PM, Peter Korsgaard <peter@korsgaard.com>
wrote:

> >>>>> "Jeff" == Jeff Bailey <jeffbailey@google.com> writes:
>
>  > Hi!  Your patch at http://git.buildroot.net/buildroot/commit/?id=
>  > f18c33b4cc9c344c6ac8e28bfac5ae42befc8b1c is confusing.
>
>  > Why did you drop the fakeroot patch?  I do use powerpc64le to build.
>
> So your build machine (the one you run Buildroot on, not the one you are
> cross compiling for) is a powerpc64le machine?
>
> --
> Bye, Peter Korsgaard
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140710/ee54b97a/attachment.html>

[Buildroot] fakeroot patch

[Peter Korsgaard]

>>>>> "Jeff" == Jeff Bailey <jeffbailey@google.com> writes:

 > Correct. ?While most of our builds happen on x86 targeting ppc64le, when doing
 > development I use the ppc64le system natively to speed up build/test
 > iterations.

Ok, and you still use Buildroot for that? Buildroot is really a system for cross
compilation. Do you do ppc64le->ppc64le cross compilation? How does that
speed up development?

-- 
Bye, Peter Korsgaard 

[Buildroot] fakeroot patch

[Yann E. MORIN]

Jeff, Peter, All,

On 2014-07-10 21:29 +0200, Peter Korsgaard spake thusly:
> >>>>> "Jeff" == Jeff Bailey <jeffbailey@google.com> writes:
>  > Correct. ?While most of our builds happen on x86 targeting ppc64le, when doing
>  > development I use the ppc64le system natively to speed up build/test
>  > iterations.
> 
> Ok, and you still use Buildroot for that? Buildroot is really a system for cross
> compilation. Do you do ppc64le->ppc64le cross compilation? How does that
> speed up development?

Also, I'd be very interested to know if all the quirks we're going to
make cross-compilation work effectively on x86, and especially x86->x86,
such as ebnsuring the host devel files do not interfere, are still
working OK on anything else than an x86 as build host.

If at least for that reason, having someone do real-life tests on a
non-x86 build host is very nice, since we can discover bugs that do not
occur on an x86 build host.

I know you, Peter, are running a PPC autobuilder, but that's not really
the same as actually using a PPC machien as a devel machine in a real
project.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] fakeroot patch

[Jeff Bailey]

On Thu Jul 10 2014 at 12:29:37 PM, Peter Korsgaard <peter@korsgaard.com>
wrote:

> >>>>> "Jeff" == Jeff Bailey <jeffbailey@google.com> writes:
>
>  > Correct.  While most of our builds happen on x86 targeting ppc64le,
> when doing
>  > development I use the ppc64le system natively to speed up build/test
>  > iterations.
>
> Ok, and you still use Buildroot for that? Buildroot is really a system for
> cross
> compilation. Do you do ppc64le->ppc64le cross compilation? How does that
> speed up development?
>

So today's case is that I have patches that apply to petitboot and friends.
 I've tested them out locally.  Now I need to make sure that the buildroot
setup hasn't rotted (I haven't looked since May).  At this point I'd build
it locally to make sure the configuration had all the right dependencies
and such and that the result was chrootable.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140710/48b045bc/attachment.html>