Date   

Re: Unable to extract tar file #dunfell #yocto

Vijay Rakesh Munganda
 

On Fri, Jan 8, 2021 at 04:09 AM, Quentin Schulz wrote:
On Fri, Jan 08, 2021 at 04:00:54AM -0800, Vijay Rakesh Munganda wrote:
On Fri, Jan 8, 2021 at 03:15 AM, Quentin Schulz wrote:


On Fri, Jan 08, 2021 at 03:07:43AM -0800, Vijay Rakesh Munganda wrote:

On Fri, Jan 8, 2021 at 01:26 AM, Quentin Schulz wrote:



Hi,

On Fri, Jan 08, 2021 at 01:19:51AM -0800, Vijay Rakesh Munganda wrote:


Hi Paul Barker,

No, ${WORKDIR}/tokbox directory is empty, it is not getting placed. I can
only see it in the downloads directory.
S = "${WORKDIR}/libopentok_linux_llvm_arm64"

This is the root directory of your archive and should be used for `S`

Cheers,
Quentin
By changing to S = "${WORKDIR}/libopentok_linux_llvm_arm64" error got
eliminated, thank you.

Now, how can I install the file under
opentok_linux_llvm_arm64/lib/libopentok.so into the rootfs?

I tried the below code but got an error as *install: cannot stat
'lib/libopentok.so': No such file or directory*.
If you go into ${WORKDIR} of your recipe (tmp/work/<arch>/<recipe name>),
what is the path to libopentok.*.so?
Do you have B set up somewhere in your recipe?
Otherwise try ${S}/lib/libopentok.so for the source path.

Quentin
Thank you! it worked.

Thanks,
Vijay Rakesh.


Re: insmod - huawei E3372h kernel module

Zoran
 

> Does it mean that it will never ever work?
> Could you please try this one? This might match your kernel version:
> https://elixir.bootlin.com/linux/v5.8.18/source/drivers/net/usb/huawei_cdc_ncm.c
>
> Zolee

[vuser@fedora33-ssd usb]$ kdiff3 huawei_cdc_ncm_5.8.18.c huawei_cdc_ncm.c
org.kde.kdiff3: "Loading A: /home/vuser/projects/kernel.bb/bb-kernel-5.8.18-bone24/KERNEL/drivers/net/usb/huawei_cdc_ncm_5.8.18.c"
"/proc/1715042/root"
org.kde.kdiff3: Loading B:  "/home/vuser/projects/kernel.bb/bb-kernel-5.8.18-bone24/KERNEL/drivers/net/usb/huawei_cdc_ncm.c"
[vuser@fedora33-ssd usb]$ diff huawei_cdc_ncm_5.8.18.c huawei_cdc_ncm.c
[vuser@fedora33-ssd usb]$ diff -c huawei_cdc_ncm_5.8.18.c huawei_cdc_ncm.c
[vuser@fedora33-ssd usb]$ diff -s huawei_cdc_ncm_5.8.18.c huawei_cdc_ncm.c
Files huawei_cdc_ncm_5.8.18.c and huawei_cdc_ncm.c are identical
[vuser@fedora33-ssd usb]$

This is the same modul. You need to try to built-in this one in the kernel.

Obviously, you need to load some basic module, this one is dependent upon (my best guess).

This one is missing. Maybe this one!

$ cat config-5.8.18-bone24 | grep HUAWEI
# CONFIG_NET_VENDOR_HUAWEI is not set
CONFIG_USB_NET_HUAWEI_CDC_NCM=m

Zee
_______


On Fri, Jan 8, 2021 at 1:29 PM Zoltan Kerenyi Nagy <kerenyi.nagy.zoltan@...> wrote:
Does it mean that it will never ever work?

Could you please try this one? This might match your kernel version:

https://elixir.bootlin.com/linux/v5.8.18/source/drivers/net/usb/huawei_cdc_ncm.c
--
Zolee



Re: insmod - huawei E3372h kernel module

Zoltan Kerenyi Nagy
 

I experimented with the latest and greatest source, this is my log during bitbake:

http://paste.ubuntu.com/p/R5PjtrtVYn/

Thank you for your efforts!
--
Zolee


Re: insmod - huawei E3372h kernel module

Zoltan Kerenyi Nagy
 

Does it mean that it will never ever work?

Could you please try this one? This might match your kernel version:

https://elixir.bootlin.com/linux/v5.8.18/source/drivers/net/usb/huawei_cdc_ncm.c
--
Zolee


Re: Unable to extract tar file #dunfell #yocto

Quentin Schulz
 

On Fri, Jan 08, 2021 at 04:00:54AM -0800, Vijay Rakesh Munganda wrote:
On Fri, Jan 8, 2021 at 03:15 AM, Quentin Schulz wrote:


On Fri, Jan 08, 2021 at 03:07:43AM -0800, Vijay Rakesh Munganda wrote:

On Fri, Jan 8, 2021 at 01:26 AM, Quentin Schulz wrote:



Hi,

On Fri, Jan 08, 2021 at 01:19:51AM -0800, Vijay Rakesh Munganda wrote:


Hi Paul Barker,

No, ${WORKDIR}/tokbox directory is empty, it is not getting placed. I can
only see it in the downloads directory.
S = "${WORKDIR}/libopentok_linux_llvm_arm64"

This is the root directory of your archive and should be used for `S`

Cheers,
Quentin
By changing to S = "${WORKDIR}/libopentok_linux_llvm_arm64" error got
eliminated, thank you.

Now, how can I install the file under
opentok_linux_llvm_arm64/lib/libopentok.so into the rootfs?

I tried the below code but got an error as *install: cannot stat
'lib/libopentok.so': No such file or directory*.
If you go into ${WORKDIR} of your recipe (tmp/work/<arch>/<recipe name>),
what is the path to libopentok.*.so?
Do you have B set up somewhere in your recipe?
Otherwise try ${S}/lib/libopentok.so for the source path.

Quentin


Re: Unable to extract tar file #dunfell #yocto

Vijay Rakesh Munganda
 

On Fri, Jan 8, 2021 at 03:15 AM, Quentin Schulz wrote:
On Fri, Jan 08, 2021 at 03:07:43AM -0800, Vijay Rakesh Munganda wrote:
On Fri, Jan 8, 2021 at 01:26 AM, Quentin Schulz wrote:


Hi,

On Fri, Jan 08, 2021 at 01:19:51AM -0800, Vijay Rakesh Munganda wrote:

Hi Paul Barker,

No, ${WORKDIR}/tokbox directory is empty, it is not getting placed. I can
only see it in the downloads directory.
S = "${WORKDIR}/libopentok_linux_llvm_arm64"

This is the root directory of your archive and should be used for `S`

Cheers,
Quentin
By changing to S = "${WORKDIR}/libopentok_linux_llvm_arm64" error got eliminated, thank you.

Now, how can I install the file under opentok_linux_llvm_arm64/lib/libopentok.so into the rootfs?

I tried the below code but got an error as *install: cannot stat 'lib/libopentok.so': No such file or directory*.
If you go into ${WORKDIR} of your recipe (tmp/work/<arch>/<recipe name>),
what is the path to libopentok.*.so?

Quentin
This is the path to libopentok.so tmp/work/aarch64-poky-linux/tokbox/1.0-r0/libopentok_linux_llvm_arm64/lib/

Thanks,
Vijay Rakesh.


Re: insmod - huawei E3372h kernel module

Zoran
 

> insmod /lib/modules/4.10.0/extra/huawei_cdc_ncm.ko
> insmod: can't insert '/lib/modules/4.10.0/extra/huawei_cdc_ncm.ko': unknown symbol in module, or unknown parameter


On my target (Pocket Bone):

debian@arm:/lib/modules/5.8.18-bone24/kernel$ find . -name huawei_cdc_ncm*
./drivers/net/usb/huawei_cdc_ncm.ko.xz
debian@arm:/lib/modules/5.8.18-bone24/kernel$ cd ./drivers/net/usb/
debian@arm:/lib/modules/5.8.18-bone24/kernel/drivers/net/sudo insmod huawei_cdc_ncm.ko.xz
[ 6554.826591] huawei_cdc_ncm: Unknown symbol cdc_ncm_tx_fixup (err -2)
[ 6554.833115] huawei_cdc_ncm: Unknown symbol cdc_ncm_bind_common (err -2)
[ 6554.841745] huawei_cdc_ncm: Unknown symbol usb_cdc_wdm_register (err -2)
[ 6554.849680] huawei_cdc_ncm: Unknown symbol cdc_ncm_unbind (err -2)
[ 6554.857042] huawei_cdc_ncm: Unknown symbol cdc_ncm_rx_fixup (err -2)
insmod: ERROR: could not insert module huawei_cdc_ncm.ko.xz: Unknown symbol in module

debian@arm:/lib/modules/5.8.18-bone24/kernel/drivers/net/usb$ uname -a
Linux arm 5.8.18-bone24 #1 PREEMPT Sun Dec 13 19:15:04 CET 2020 armv7l GNU/Linux
debian@arm:/lib/modules/5.8.18-bone24/kernel/drivers/net/usb$ cat /etc/debian_version
10.7
debian@arm:/lib/modules/5.8.18-bone24/kernel/drivers/net/usb$

Good Luck!
Zoran
_______


On Fri, Jan 8, 2021 at 12:22 PM Zoltan Kerenyi Nagy <kerenyi.nagy.zoltan@...> wrote:
No success :-(

insmod /lib/modules/4.10.0/extra/huawei_cdc_ncm.ko
insmod: can't insert '/lib/modules/4.10.0/extra/huawei_cdc_ncm.ko': unknown symbol in module, or unknown parameter

--
Zolee



Re: insmod - huawei E3372h kernel module

Zoltan Kerenyi Nagy
 

No success :-(

insmod /lib/modules/4.10.0/extra/huawei_cdc_ncm.ko
insmod: can't insert '/lib/modules/4.10.0/extra/huawei_cdc_ncm.ko': unknown symbol in module, or unknown parameter

--
Zolee


rebuild issues using sstate mirror

Markus Volk
 

Hi Folks,
i did some research on building a custom yocto image using gatesgarth branch. The testcase was building an image on one machine and rebuild it on another using sstate mirror.
I encountered two issues witch i was able to fix in a way that may also be interesting upstream.
 
The first error:
| /home/flk/yocto/build/poky-3.2/hd51/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/gobject-introspection/1.64.1-r0/recipe-sysroot-native/usr/bin/bison: error while loading shared libraries: libreadline.so.7: cannot open shared object file: No such file or directory
 
the solution for me was to add 'readline'  to DEPENDS in bison_3.7.2.bb .
 
configure log for bison-native changed from:
 checking for readline... no
checking readline/readline.h usability... no
checking readline/readline.h presence... no
checking for readline/readline.h... no
checking readline/history.h usability... no
checking readline/history.h presence... no
checking for readline/history.h... no
 
to:
checking for readline... yes
checking how to link with libreadline... /home/flk/yocto/build/poky-3.2/hd51/tmp/work/x86_64-linux/bison-native/3.7.2-r0/recipe-sysroot-native/usr/lib/libreadline.so -Wl,-rpath -Wl,/home/flk/yocto/build/poky-3.2/hd51/tmp/work/x86_64-linux/bison-native/3.7.2-r0/recipe-sysroot-native/usr/lib
checking readline/readline.h usability... yes
checking readline/readline.h presence... yes
checking for readline/readline.h... yes
checking readline/history.h usability... yes
checking readline/history.h presence... yes
checking for readline/history.h... yes
 
and the error disappeared
 
The second error:
 
ERROR: neutrino-image-1.0-r0 do_rootfs: Unable to update the package index files. Command '/home/flk/yocto/build/poky-3.2/hd60/tmp/work/hd60-oe-linux-gnueabi/neutrino-image/1.0-r0/recipe-sysroot-native/usr/bin/opkg --volatile-cache -f /home/flk/yocto/build/poky-3.2/hd60/tmp/work/hd60-oe-linux-gnueabi/neutrino-image/1.0-r0/opkg.conf -t /home/flk/yocto/build/poky-3.2/hd60/tmp/work/hd60-oe-linux-gnueabi/neutrino-image/1.0-r0/temp/ipktemp/ -o /home/flk/yocto/build/poky-3.2/hd60/tmp/work/hd60-oe-linux-gnueabi/neutrino-image/1.0-r0/rootfs  --force_postinstall --prefer-arch-to-version   update' returned 127:
/home/flk/yocto/build/poky-3.2/hd60/tmp/work/hd60-oe-linux-gnueabi/neutrino-image/1.0-r0/recipe-sysroot-native/usr/bin/opkg: error while loading shared libraries: libcharset.so.1: cannot open shared object file: No such file or directory
 
after some research why libiconv libs are  being used (which i didn't have installed on the rebuild machine) i found this in libarchive:
configure.ac
 
and was able to avoid the error by including 'gettext' to the inherit line in libarchive_3.4.3.bb

Kind regards


Re: Unable to extract tar file #dunfell #yocto

Quentin Schulz
 

On Fri, Jan 08, 2021 at 03:07:43AM -0800, Vijay Rakesh Munganda wrote:
On Fri, Jan 8, 2021 at 01:26 AM, Quentin Schulz wrote:


Hi,

On Fri, Jan 08, 2021 at 01:19:51AM -0800, Vijay Rakesh Munganda wrote:

Hi Paul Barker,

No, ${WORKDIR}/tokbox directory is empty, it is not getting placed. I can
only see it in the downloads directory.
S = "${WORKDIR}/libopentok_linux_llvm_arm64"

This is the root directory of your archive and should be used for `S`

Cheers,
Quentin
By changing to S = "${WORKDIR}/libopentok_linux_llvm_arm64" error got eliminated, thank you.

Now, how can I install the file under opentok_linux_llvm_arm64/lib/libopentok.so into the rootfs?

I tried the below code but got an error as *install: cannot stat 'lib/libopentok.so': No such file or directory*.
If you go into ${WORKDIR} of your recipe (tmp/work/<arch>/<recipe name>),
what is the path to libopentok.*.so?

Quentin


Re: Unable to extract tar file #dunfell #yocto

Vijay Rakesh Munganda
 

On Fri, Jan 8, 2021 at 01:26 AM, Quentin Schulz wrote:
Hi,

On Fri, Jan 08, 2021 at 01:19:51AM -0800, Vijay Rakesh Munganda wrote:
Hi Paul Barker,

No, ${WORKDIR}/tokbox directory is empty, it is not getting placed. I can only see it in the downloads directory.
S = "${WORKDIR}/libopentok_linux_llvm_arm64"

This is the root directory of your archive and should be used for `S`

Cheers,
Quentin
By changing to S = "${WORKDIR}/libopentok_linux_llvm_arm64" error got eliminated, thank you.

Now, how can I install the file under opentok_linux_llvm_arm64/lib/libopentok.so into the rootfs?

I tried the below code but got an error as install: cannot stat 'lib/libopentok.so': No such file or directory.

do_install() {
         install -d ${D}${libdir}
         install -m 0755 lib/libopentok.so ${D}${libdir}
}
Thanks,
Vijay Rakesh.


Re: Unable to extract tar file #dunfell #yocto

Vijay Rakesh Munganda
 

On Fri, Jan 8, 2021 at 01:28 AM, Paul Barker wrote:
Hi Paul Barker,

No, ${WORKDIR}/tokbox directory is empty, it is not getting placed. I can only see it in the downloads directory.

I'm Yocto Project Dunfell version.
What I mean is, do you see the file
"libopentok_linux_llvm_arm64-2.18.1.tgz" itself under ${WORKDIR}? i.e.
has it been copied instead of extracted?

Also, please quote the email you're replying to for the benefit of
others on the mailing list. Replying inline like this is preferred.

Thanks,

--
Paul Barker
Konsulko Group
I figured out URL is hyperlinked with another URL. When I use a hyperlinked URL it is getting copied and extracted into the working directory. Thanks.

Thanks,
Vijay Rakesh.


Re: insmod - huawei E3372h kernel module

Zoltan Kerenyi Nagy
 

Hi,

I managed to bitbake with these:

http://paste.ubuntu.com/p/4W2525MQDj/

http://paste.ubuntu.com/p/VT3zyhy7h2/

I'm very curious how it behaves on the hardware

--
Zolee


Re: insmod - huawei E3372h kernel module

Zoltan Kerenyi Nagy
 

Hi,

Makefile:
huawei_cdc_ncm-y :=    huawei_cdc_ncm.o   
obj-m += huawei_cdc_ncm.o
KDIR ?= /lib/modules/`uname -r`/build
all:
    make -C $(KDIR) M=$(PWD) modules
clean:
    make -C $(KDIR) M=$(PWD) clean
install:
    cp *.ko /lib/modules/$(shell uname -r)/kernel/drivers/misc/
    depmod -a


This one doesnt work:
DEBUG: Executing shell function do_compile
NOTE: make -j 8 KERNEL_SRC=/home/kerenyiz/oe-core/build/tmp-glibc/work-shared/barix-ipam400/kernel-source KERNEL_PATH=/home/kerenyiz/oe-core/build/tmp-glibc/work-shared/barix-ipam400/kernel-source KERNEL_VERSION=4.10.0 CC=arm-oe-linux-gnueabi-gcc   -fuse-ld=bfd LD=arm-oe-linux-gnueabi-ld.bfd   AR=arm-oe-linux-gnueabi-ar  O=/home/kerenyiz/oe-core/build/tmp-glibc/work-shared/barix-ipam400/kernel-build-artifacts KBUILD_EXTRA_SYMBOLS=
ERROR: oe_runmake failed
make -C /lib/modules/`uname -r`/build M=/home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0 modules
make[1]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
make[1]: Entering directory '/usr/src/linux-headers-4.15.0-88-generic'
make[2]: Entering directory '/home/kerenyiz/oe-core/build/tmp-glibc/work-shared/barix-ipam400/kernel-build-artifacts'
make[3]: Circular /home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0/huawei_cdc_ncm.o <- /home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0/huawei_cdc_ncm.o dependency dropped.
  LD [M]  /home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0/huawei_cdc_ncm.o
arm-oe-linux-gnueabi-ld.bfd: no input files
/usr/src/linux-headers-4.15.0-88-generic/scripts/Makefile.build:578: recipe for target '/home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0/huawei_cdc_ncm.o' failed
make[3]: *** [/home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0/huawei_cdc_ncm.o] Error 1
/usr/src/linux-headers-4.15.0-88-generic/Makefile:1577: recipe for target '_module_/home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0' failed
make[2]: *** [_module_/home/kerenyiz/oe-core/build/tmp-glibc/work/barix_ipam400-oe-linux-gnueabi/huawei/1.1-r0] Error 2
make[2]: Leaving directory '/home/kerenyiz/oe-core/build/tmp-glibc/work-shared/barix-ipam400/kernel-build-artifacts'
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.15.0-88-generic'
Makefile:25: recipe for target 'all' failed
make: *** [all] Error 2
ERROR: F
--
Zolee


Re: Unable to extract tar file #dunfell #yocto

 

On Fri, 8 Jan 2021 at 09:20, Vijay Rakesh Munganda
<vijayrakeshmunganda@gmail.com> wrote:

Hi Paul Barker,

No, ${WORKDIR}/tokbox directory is empty, it is not getting placed. I can only see it in the downloads directory.

I'm Yocto Project Dunfell version.
What I mean is, do you see the file
"libopentok_linux_llvm_arm64-2.18.1.tgz" itself under ${WORKDIR}? i.e.
has it been copied instead of extracted?

Also, please quote the email you're replying to for the benefit of
others on the mailing list. Replying inline like this is preferred.

Thanks,

--
Paul Barker
Konsulko Group


Re: Unable to extract tar file #dunfell #yocto

Quentin Schulz
 

Hi,

On Fri, Jan 08, 2021 at 01:19:51AM -0800, Vijay Rakesh Munganda wrote:
Hi Paul Barker,

No, ${WORKDIR}/tokbox directory is empty, it is not getting placed. I can only see it in the downloads directory.
S = "${WORKDIR}/libopentok_linux_llvm_arm64"

This is the root directory of your archive and should be used for `S`

Cheers,
Quentin


Re: Unable to extract tar file #dunfell #yocto

Vijay Rakesh Munganda
 

Hi Paul Barker,

No,
${WORKDIR}/tokbox directory is empty, it is not getting placed. I can only see it in the downloads directory.

I'm Yocto Project Dunfell version.

Thanks,
Vijay Rakesh.


Re: Unable to extract tar file #dunfell #yocto

 

On Fri, 8 Jan 2021 at 08:49, Vijay Rakesh Munganda
<vijayrakeshmunganda@gmail.com> wrote:

Hi Zoran,

Thanks for the reply. The reason behind CMakeLists.txt does not appear is because tgz file is getting extracted into the source folder, it is empty when I checked. My recipe is unable to extract the tgz file which is download in the downloads directory. Do I need to write something specifically for extracting tgz file in the recipe?
Does the .tgz file get placed in ${WORKDIR} without being extracted?

Also, which Yocto Project version/branch are you using?

Thanks,

--
Paul Barker
Konsulko Group


Re: How to select Linux kernel version?

Quentin Schulz
 

Hi Jupiter,

On Fri, Jan 08, 2021 at 02:03:47PM +1100, Jupiter wrote:
Thanks Quentin, here are results:

So we can stop half guessing and help you can you give us the output of:
bitbake -e virtual/kernel | grep -e "^PREFERRED_PROVIDER_"
$ bitbake -e virtual/kernel | grep -e "^PREFERRED_PROVIDER_"
[...]
PREFERRED_PROVIDER_virtual/kernel="linux-yocto"
[...]

bitbake -e virtual/kernel | grep -e "^PREFERRED_VERSION_"
$ bitbake -e virtual/kernel | grep -e "^PREFERRED_VERSION_"
PREFERRED_VERSION_linux-libc-headers="5.2%"
PREFERRED_VERSION_linux-yocto="5.10.%"
Not sure this will fly nicely (the kernel headers being older than your
kernel).

Otherwise ok.


bitbake -e virtual/kernel | grep -e "^OVERRIDES="
$ bitbake -e virtual/kernel | grep -e "^OVERRIDES="
OVERRIDES="linux:i686:pn-linux-yocto:x86:qemuall:qemux86:solar-distro:class-target:libc-glibc:forcevariable"

bitbake-layers show-recipes linux-yocto linux-fslc
$ bitbake-layers show-recipes linux-yocto linux-fslc
NOTE: Starting bitbake server...
Loading cache: 100% |############################################| Time: 0:00:00
Loaded 1473 entries from dependency cache.
Parsing recipes: 100% |##########################################| Time: 0:00:02
Parsing of 922 .bb files complete (920 cached, 2 parsed). 1475
targets, 295 skipped, 0 masked, 0 errors.
=== Matching recipes: ===
linux-fslc:
meta-freescale 5.1 (skipped)
linux-yocto:
meta 5.2.28+gitAUTOINC+dd6019025c_992280855e
meta 4.19.87+gitAUTOINC+4f5d761316_b44ad1b1e7
And here we have the winner :)

You don't have a 5.10 linux-yocto recipe so obviously bitbake can't
compile it.

Now, I don't know why 4.19 is taken and not 5.2. I quickly looked into
both recipes and didn't find a DEFAULT_PREFERENCE
(c.f. https://docs.yoctoproject.org/ref-manual/variables.html?highlight=preference#term-DEFAULT_PREFERENCE).

So, can you tell us how you created your 5.10 recipe and where you put
it (the filename, the path in the layer, is it in a new layer? if yes,
did you add it to bblayers.conf? etc...).

Quentin


Re: Unable to extract tar file #dunfell #yocto

Vijay Rakesh Munganda
 

Hi Zoran,

Thanks for the reply. The reason behind CMakeLists.txt does not appear is because tgz file is getting extracted into the source folder, it is empty when I checked. My recipe is unable to extract the tgz file which is download in the downloads directory. Do I need to write something specifically for extracting tgz file in the recipe?

Thanks,
Vijay Rakesh.

1561 - 1580 of 53484