cc1 binary in final rootfs even when no reference to it


Marek Belisko
 

Hello,

on dunfell images I start seeing that cc1 binary (checked by buildhistory):
files-in-image.txt:-rwxr-xr-x root root 17674124
./usr/libexec/gcc/arm-poky-linux-gnueabi/9.3.0/cc1

is present in the final image. I check taskexp but cannot find any
reference which pointes to it.
Any ideas how to check or it's a common problem?

Thanks and regards,

marek

--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com


Khem Raj
 

this file comes from cpp output package. Can you check if somehow cpp
is being pulled into your image

On Wed, Mar 3, 2021 at 6:10 AM Marek Belisko <marek.belisko@gmail.com> wrote:

Hello,

on dunfell images I start seeing that cc1 binary (checked by buildhistory):
files-in-image.txt:-rwxr-xr-x root root 17674124
./usr/libexec/gcc/arm-poky-linux-gnueabi/9.3.0/cc1

is present in the final image. I check taskexp but cannot find any
reference which pointes to it.
Any ideas how to check or it's a common problem?

Thanks and regards,

marek

--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com



Marek Belisko
 

On Wed, Mar 3, 2021 at 6:31 PM Khem Raj <raj.khem@gmail.com> wrote:

this file comes from cpp output package. Can you check if somehow cpp
is being pulled into your image
It turns out that cpp + cpp-symlinks is pulled by python3-pycparser.
It is really necessary to be as runtime dependency in recipe?

On Wed, Mar 3, 2021 at 6:10 AM Marek Belisko <marek.belisko@gmail.com> wrote:

Hello,

on dunfell images I start seeing that cc1 binary (checked by buildhistory):
files-in-image.txt:-rwxr-xr-x root root 17674124
./usr/libexec/gcc/arm-poky-linux-gnueabi/9.3.0/cc1

is present in the final image. I check taskexp but cannot find any
reference which pointes to it.
Any ideas how to check or it's a common problem?

Thanks and regards,

marek

--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com




--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com


Khem Raj
 

On 3/3/21 11:29 AM, Belisko Marek wrote:
On Wed, Mar 3, 2021 at 6:31 PM Khem Raj <raj.khem@gmail.com> wrote:

this file comes from cpp output package. Can you check if somehow cpp
is being pulled into your image
It turns out that cpp + cpp-symlinks is pulled by python3-pycparser.
It is really necessary to be as runtime dependency in recipe?
it a parser for C language written in python, so my initial thoughts will be no. but there might be some dependencies on cpp, you might have to dive a bit deeper.


On Wed, Mar 3, 2021 at 6:10 AM Marek Belisko <marek.belisko@gmail.com> wrote:

Hello,

on dunfell images I start seeing that cc1 binary (checked by buildhistory):
files-in-image.txt:-rwxr-xr-x root root 17674124
./usr/libexec/gcc/arm-poky-linux-gnueabi/9.3.0/cc1

is present in the final image. I check taskexp but cannot find any
reference which pointes to it.
Any ideas how to check or it's a common problem?

Thanks and regards,

marek

--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com


Anders Montonen
 

On 4.3.2021 2.06, Khem Raj wrote:
On 3/3/21 11:29 AM, Belisko Marek wrote:
On Wed, Mar 3, 2021 at 6:31 PM Khem Raj <raj.khem@gmail.com> wrote:

this file comes from cpp output package. Can you check if somehow cpp
is being pulled into your image
It turns out that cpp + cpp-symlinks is pulled by python3-pycparser.
It is really necessary to be as runtime dependency in recipe?
it a parser for C language written in python, so my initial thoughts will be no. but there might be some dependencies on cpp, you might have to dive a bit deeper.

I've run into this, and from memory cpp is needed if you intend to run the parser, but since the dependency is added through RDEPENDS_${PN}_class-target it gets installed even if you're only running the parser on the host. I ended up removing the target dependency due to license conflicts, and didn't encounter any problems.

-anders


Khem Raj
 

On Thu, Mar 4, 2021 at 10:04 AM Anders Montonen <Anders.Montonen@iki.fi> wrote:

On 4.3.2021 2.06, Khem Raj wrote:
On 3/3/21 11:29 AM, Belisko Marek wrote:
On Wed, Mar 3, 2021 at 6:31 PM Khem Raj <raj.khem@gmail.com> wrote:

this file comes from cpp output package. Can you check if somehow cpp
is being pulled into your image
It turns out that cpp + cpp-symlinks is pulled by python3-pycparser.
It is really necessary to be as runtime dependency in recipe?
it a parser for C language written in python, so my initial thoughts
will be no. but there might be some dependencies on cpp, you might
have to dive a bit deeper.

I've run into this, and from memory cpp is needed if you intend to run
the parser, but since the dependency is added through
RDEPENDS_${PN}_class-target it gets installed even if you're only
running the parser on the host. I ended up removing the target
dependency due to license conflicts, and didn't encounter any problems.
right perhaps its fine to drop this and maybe add it as rsuggests or something

-anders