Dependency Tree

Dependency Tree

[Jim Rucker]

[-- Attachment #1: Type: text/plain, Size: 315 bytes --]

I'm trying to build using the code sourcery external compiler and I noticed
that it's pulling in qemu. This brings up 2 questions-
1. Why? Qemu is not a prerequisite for building with GCC and shouldn't be a
prerequisite for building with CS.
2. How can I easily generate a dependency tree so I can 'fix' this?

[-- Attachment #2: Type: text/html, Size: 355 bytes --]

Re: Dependency Tree

[Khem Raj]

On Mon, Jun 18, 2012 at 11:58 AM, Jim Rucker <linux.mrjimorg@gmail.com> wrote:
> I'm trying to build using the code sourcery external compiler and I noticed
> that it's pulling in qemu. This brings up 2 questions-
> 1. Why? Qemu is not a prerequisite for building with GCC and shouldn't be a
> prerequisite for building with CS.

how did you conclude that its a prerequisite with external toolchain and not
with internal toolchain

> 2. How can I easily generate a dependency tree so I can 'fix' this?

bitbake -g <target>

>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

Re: Dependency Tree

[Paul Eggleton]

On Monday 18 June 2012 13:58:03 Jim Rucker wrote:
> I'm trying to build using the code sourcery external compiler and I noticed
> that it's pulling in qemu. This brings up 2 questions-
> 1. Why? Qemu is not a prerequisite for building with GCC and shouldn't be a
> prerequisite for building with CS.

What is your MACHINE set to? If you're building for a qemu* machine then that 
would explain it.

> 2. How can I easily generate a dependency tree so I can 'fix' this?

As Khem mentioned you can use -g -u depexp, or alternatively just -g to output 
dependency graphs in graphviz format which you can grep.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Dependency Tree

[Paul Eggleton]

On Wednesday 20 June 2012 16:28:02 Jim Rucker wrote:
> Thanks for the help
> "how did you conclude that its a prerequisite with external toolchain and
> not with internal toolchain?"
> Because this system doesn't have network access, so I have to transfer
> files to the system manually and use the PREMIRROR feature. When I build
> using the internal toolchain I never needed to grab qemu.
> Side note- after researching this it looks like qemu was needed for
> localization files required by eglibc, while the internal gcc uses a prebuilt
> localization file.

This is something that has apparently been fixed post-denzil. I think you just 
need to set the following:

GLIBC_INTERNAL_USE_BINARY_LOCALE = "precompiled"
ENABLE_BINARY_LOCALE_GENERATION = ""

> Although I'm able to build without network access on edison, I can't seem
> to get it to work on denzil. I seem to get pretty far, but when I get to a
> git repository, it doesn't seem to work. I have the file
> "git2_git.yoctoproject.org.prelink-cross.git.tar.gz", but it never seems to
> try to access it. Any suggestions?

So this suggests that you don't have the prelink-cross git archive in your 
local mirror (assuming PREMIRRORS is set up to also redirect git URIs); hence 
it is trying to go out to the internet to get it.

By the way, do you have BB_NO_NETWORK = "1" set? If not then you should set 
this in local.conf.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre