[Buildroot] showstopper 404 problem ...

[Buildroot] showstopper 404 problem ...

[g4 at novadsp.com]

I am not sure if this is due to general ignorance or a real problem. TVMIA
for any pointers.

 

My .config (created by menuconfig) has 

 

BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="4.0.4"

BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git://git.ti.com/ti-linux-kernel/ti-linux-
kernel.git"

 

Once the repo is finally cloned I get this showstopper error. Re-running
make starts the git clone all over again. 

 

Have I simply go the kernel name/label wrong?  A manual wget fails so I
assume the latter is a strong possibility.

 

----------------------------------------------------------------------------
--

moi at acermint ~/buildroot $ make

/usr/bin/make -j1  HOSTCC="/usr/bin/gcc" HOSTCXX="/usr/bin/g++"
silentoldconfig

make[1]: Entering directory `/home/moi/buildroot'

BR2_DEFCONFIG=''
KCONFIG_AUTOCONFIG=/home/moi/buildroot/output/build/buildroot-config/auto.co
nf KCONFIG_AUTOHEADE

R=/home/moi/buildroot/output/build/buildroot-config/autoconf.h
KCONFIG_TRISTATE=/home/moi/buildroot/output/bui

ld/buildroot-config/tristate.config BR2_CONFIG=/home/moi/buildroot/.config
BR2_EXTERNAL=support/dummy-external /h

ome/moi/buildroot/output/build/buildroot-config/conf --silentoldconfig
Config.in

make[1]: Leaving directory `/home/moi/buildroot'

>>> linux 4.0.4 Downloading

Doing full clone

Cloning into bare repository 'linux-4.0.4'...

remote: Counting objects: 4872908, done.

remote: Compressing objects: 100% (723616/723616), done.

Receiving objects:  33% (1609811/4872908), 526.36 MiB | 218.00 K

remote: Total 4872908 (delta 4123401), reused 4863877 (delta 4114759)

Receiving objects: 100% (4872908/4872908), 944.23 MiB | 204.00 KiB/s, done.

Resolving deltas: 100% (4123401/4123401), done.

Checking connectivity... done.

fatal: Not a valid object name

--2015-05-25 18:36:02--  http://sources.buildroot.net/linux-4.0.4.tar.gz

Resolving sources.buildroot.net (sources.buildroot.net)... 176.9.16.109

Connecting to sources.buildroot.net
(sources.buildroot.net)|176.9.16.109|:80... connected.

HTTP request sent, awaiting response... 404 Not Found

2015-05-25 18:36:02 ERROR 404: Not Found.

 

make: *** [/home/moi/buildroot/output/build/linux-4.0.4/.stamp_downloaded]
Error 1

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150525/95c62f37/attachment.html>

[Buildroot] showstopper 404 problem ...

[Thomas Petazzoni]

Hello,

On Mon, 25 May 2015 19:52:44 +0100, g4 at novadsp.com wrote:

> BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="4.0.4"
> 
> BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git://git.ti.com/ti-linux-kernel/ti-linux-
> kernel.git"

As explained by Yegor, use the mainline kernel, not TI's fork.


> fatal: Not a valid object name

This means there is no 4.0.4 tag in the Git kernel tree you're pointing
to.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] showstopper 404 problem ...

[g4 at novadsp.com]

Hello Thomas and thanks

> > BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="4.0.4"
> >
> > BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git://git.ti.com/ti-linux-
> kernel/ti-
> > linux-
> > kernel.git"
> 
> As explained by Yegor, use the mainline kernel, not TI's fork.
> 

As in kernel.org? An example or the canonical repo would be really handy.

TIA.

[Buildroot] showstopper 404 problem ...

[Gergely Imreh]

On 26 May 2015 at 03:50,  <g4@novadsp.com> wrote:
> Hello Thomas and thanks
>
>> > BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="4.0.4"
>> >
>> > BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git://git.ti.com/ti-linux-
>> kernel/ti-
>> > linux-
>> > kernel.git"
>>
>> As explained by Yegor, use the mainline kernel, not TI's fork.
>>
>
> As in kernel.org? An example or the canonical repo would be really handy.

I'd guess Thomas means that for the mainline kernel you don't need any
custom repo, just use the default kernel version (it's already 4.0.4
in the current Buildroot). Much simpler and quicker that way.

If for whatever reason you want to use the git version of the tree,
you can find the clone URLs at the bottom of this page:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/
The https://git.kernel.org/cgit/ has all the various kernel repos that
you will never have to use directly. Just FYI.

Cheers,
   Greg

>
> TIA.
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

[Buildroot] showstopper 404 problem ...

[g4 at novadsp.com]

Hi Gergely and thanks.

> 
> I'd guess Thomas means that for the mainline kernel you don't need any
> custom repo, just use the default kernel version (it's already 4.0.4 in the
> current Buildroot). Much simpler and quicker that way.
> 

I've been using 2015.02 stable which seems to stop at 3.18 hence my latest round of questions :)

Is RC3 stable enough for use?

TVMIA.

Jerry

[Buildroot] showstopper 404 problem ...

[Peter Korsgaard]

>>>>>   <g4@novadsp.com> writes:

 > Hi Gergely and thanks.
 >> 
 >> I'd guess Thomas means that for the mainline kernel you don't need any
 >> custom repo, just use the default kernel version (it's already 4.0.4 in the
 >> current Buildroot). Much simpler and quicker that way.
 >> 

 > I've been using 2015.02 stable which seems to stop at 3.18 hence my latest round of questions :)

 > Is RC3 stable enough for use?

Yes, expect the final 2015.05 release by this weekend.

-- 
Bye, Peter Korsgaard

[Buildroot] showstopper 404 problem ...

[g4 at novadsp.com]

Thank you Peter.

> 
> Yes, expect the final 2015.05 release by this weekend.
> 

I am trying rc3 now.

I'm still confused by the Toolchain >> Kernel headers and Kernel >> Linux
kernel >> Kernel version settings. Why are these independent?  

TVMIA.

[Buildroot] showstopper 404 problem ...

[Peter Korsgaard]

>>>>>   <g4@novadsp.com> writes:

 > Thank you Peter.
 >> 
 >> Yes, expect the final 2015.05 release by this weekend.
 >> 

 > I am trying rc3 now.

 > I'm still confused by the Toolchain >> Kernel headers and Kernel >> Linux
 > kernel >> Kernel version settings. Why are these independent?  

because you can build a toolchain without building a kernel or reuse an
existing toolchain to build a kernel.

If you do build both, then the versions should match.

-- 
Venlig hilsen,
Peter Korsgaard