binutils: compilation error 'unknown pseudo-op: `.l`'

binutils: compilation error 'unknown pseudo-op: `.l`'

[Bryan Evenson]

All,

I have a AT91SAM9G25 based system that has been built and works using yocto-2.2 (morty).  I am in the process of upgrading my build tools to the latest.  The build image is a custom image that is based off of core-image-minimal with a few additional packages.  I'm using Ubuntu 18.04.06 LTS for my host environment.  I'm up to yocto-2.7.4 (warrior) and I hit some build issues that I'm looking for some help in solving.

Here is some build configuration details (with details I don't want spread over the internet removed):
Build Configuration:
BB_VERSION           = "1.42.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "arm-poky-linux-gnueabi"
MACHINE              = "at91sam9x5ek"
DISTRO_VERSION       = "2.7.4"
TUNE_FEATURES        = "arm armv5 thumb dsp"
TARGET_FPU           = "soft"
meta-bacnet          = "master:49ebde9269e8533a8e4ce9c335addced6bfb79b6"
meta-atmel           = "warrior:102d92bfc7bd772387ea89c149d33cc5ebf9179c"
meta-qt5             = "warrior:6310c5c17380ad5e3bdaf1938e025d713066e7ee"
meta                 
meta-poky            
meta-yocto-bsp       = "warrior:eb163bd6aa0911a9541702cd12a3df684fe5fbb1"
meta-oe              
meta-networking      
meta-python          = "warrior:a24acf94d48d635eca668ea34598c6e5c857e3f8"

I'm getting following error when the system is compiling binutils:

In file included from ../../gold/powerpc.cc:43:
../../gold/gc.h:375:1: note: parameter passing for argument of type 'std::vector<long long unsigned int>::iterator' {aka '__gnu_cxx::__normal_iterator<long long unsigned int*, std::vector<long long unsigned int> >'} changed in GCC 7.1
 }
 ^
../../gold/gc.h:375:1: note: parameter passing for argument of type 'std::vector<long long unsigned int>::iterator' {aka '__gnu_cxx::__normal_iterator<long long unsigned int*, std::vector<long long unsigned int> >'} changed in GCC 7.1
{standard input}: Assembler messages:
{standard input}:347600: Warning: end of file not at end of a line; newline inserted
{standard input}:347687: Error: unknown pseudo-op: `.l'
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
arm-poky-linux-gnueabi-g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
Makefile:1137: recipe for target 'powerpc.o' failed

I have looked through the Git log for meta/recipes-devtools/binutils up through master HEAD, and I don't see any references to a problem similar to this one.  Has anyone seen a problem like this before?  If so, does anyone know how to fix it?

Thanks,
Bryan

Re: [OE-core] binutils: compilation error 'unknown pseudo-op: `.l`'

[Khem Raj]

On Tue, Sep 28, 2021 at 8:11 AM Bryan Evenson <bevenson@melinkcorp.com> wrote:
>
> All,
>
> I have a AT91SAM9G25 based system that has been built and works using yocto-2.2 (morty).  I am in the process of upgrading my build tools to the latest.  The build image is a custom image that is based off of core-image-minimal with a few additional packages.  I'm using Ubuntu 18.04.06 LTS for my host environment.  I'm up to yocto-2.7.4 (warrior) and I hit some build issues that I'm looking for some help in solving.
>
> Here is some build configuration details (with details I don't want spread over the internet removed):
> Build Configuration:
> BB_VERSION           = "1.42.0"
> BUILD_SYS            = "x86_64-linux"
> NATIVELSBSTRING      = "universal"
> TARGET_SYS           = "arm-poky-linux-gnueabi"
> MACHINE              = "at91sam9x5ek"
> DISTRO_VERSION       = "2.7.4"
> TUNE_FEATURES        = "arm armv5 thumb dsp"
> TARGET_FPU           = "soft"
> meta-bacnet          = "master:49ebde9269e8533a8e4ce9c335addced6bfb79b6"
> meta-atmel           = "warrior:102d92bfc7bd772387ea89c149d33cc5ebf9179c"
> meta-qt5             = "warrior:6310c5c17380ad5e3bdaf1938e025d713066e7ee"
> meta
> meta-poky
> meta-yocto-bsp       = "warrior:eb163bd6aa0911a9541702cd12a3df684fe5fbb1"
> meta-oe
> meta-networking
> meta-python          = "warrior:a24acf94d48d635eca668ea34598c6e5c857e3f8"
>
> I'm getting following error when the system is compiling binutils:
>
> In file included from ../../gold/powerpc.cc:43:
> ../../gold/gc.h:375:1: note: parameter passing for argument of type 'std::vector<long long unsigned int>::iterator' {aka '__gnu_cxx::__normal_iterator<long long unsigned int*, std::vector<long long unsigned int> >'} changed in GCC 7.1
>  }
>  ^
> ../../gold/gc.h:375:1: note: parameter passing for argument of type 'std::vector<long long unsigned int>::iterator' {aka '__gnu_cxx::__normal_iterator<long long unsigned int*, std::vector<long long unsigned int> >'} changed in GCC 7.1
> {standard input}: Assembler messages:
> {standard input}:347600: Warning: end of file not at end of a line; newline inserted
> {standard input}:347687: Error: unknown pseudo-op: `.l'
> {standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
> arm-poky-linux-gnueabi-g++: fatal error: Killed signal terminated program cc1plus
> compilation terminated.
> Makefile:1137: recipe for target 'powerpc.o' failed
>
> I have looked through the Git log for meta/recipes-devtools/binutils up through master HEAD, and I don't see any references to a problem similar to this one.  Has anyone seen a problem like this before?  If so, does anyone know how to fix it?
>

it seems compiler is out of memory.

> Thanks,
> Bryan
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#156424): https://lists.openembedded.org/g/openembedded-core/message/156424
> Mute This Topic: https://lists.openembedded.org/mt/85926755/1997914
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

RE: [OE-core] binutils: compilation error 'unknown pseudo-op: `.l`'

[Bryan Evenson]

Khem,

> -----Original Message-----
> From: Khem Raj <raj.khem@gmail.com>
> Sent: Tuesday, September 28, 2021 2:41 PM
> To: Bryan Evenson <bevenson@melinkcorp.com>
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] binutils: compilation error 'unknown pseudo-op: `.l`'
> 
> On Tue, Sep 28, 2021 at 8:11 AM Bryan Evenson
> <bevenson@melinkcorp.com> wrote:
> >
> > All,
> >
> > I have a AT91SAM9G25 based system that has been built and works using
> yocto-2.2 (morty).  I am in the process of upgrading my build tools to the
> latest.  The build image is a custom image that is based off of core-image-
> minimal with a few additional packages.  I'm using Ubuntu 18.04.06 LTS for my
> host environment.  I'm up to yocto-2.7.4 (warrior) and I hit some build issues
> that I'm looking for some help in solving.
> >
> > Here is some build configuration details (with details I don't want spread
> over the internet removed):
> > Build Configuration:
> > BB_VERSION           = "1.42.0"
> > BUILD_SYS            = "x86_64-linux"
> > NATIVELSBSTRING      = "universal"
> > TARGET_SYS           = "arm-poky-linux-gnueabi"
> > MACHINE              = "at91sam9x5ek"
> > DISTRO_VERSION       = "2.7.4"
> > TUNE_FEATURES        = "arm armv5 thumb dsp"
> > TARGET_FPU           = "soft"
> > meta-bacnet          =
> "master:49ebde9269e8533a8e4ce9c335addced6bfb79b6"
> > meta-atmel           = "warrior:102d92bfc7bd772387ea89c149d33cc5ebf9179c"
> > meta-qt5             = "warrior:6310c5c17380ad5e3bdaf1938e025d713066e7ee"
> > meta
> > meta-poky
> > meta-yocto-bsp       =
> "warrior:eb163bd6aa0911a9541702cd12a3df684fe5fbb1"
> > meta-oe
> > meta-networking
> > meta-python          =
> "warrior:a24acf94d48d635eca668ea34598c6e5c857e3f8"
> >
> > I'm getting following error when the system is compiling binutils:
> >
> > In file included from ../../gold/powerpc.cc:43:
> > ../../gold/gc.h:375:1: note: parameter passing for argument of type
> > 'std::vector<long long unsigned int>::iterator' {aka
> > '__gnu_cxx::__normal_iterator<long long unsigned int*,
> > std::vector<long long unsigned int> >'} changed in GCC 7.1  }  ^
> > ../../gold/gc.h:375:1: note: parameter passing for argument of type
> > 'std::vector<long long unsigned int>::iterator' {aka
> '__gnu_cxx::__normal_iterator<long long unsigned int*, std::vector<long
> long unsigned int> >'} changed in GCC 7.1 {standard input}: Assembler
> messages:
> > {standard input}:347600: Warning: end of file not at end of a line;
> > newline inserted {standard input}:347687: Error: unknown pseudo-op: `.l'
> > {standard input}: Error: open CFI at the end of file; missing
> > .cfi_endproc directive
> > arm-poky-linux-gnueabi-g++: fatal error: Killed signal terminated
> > arm-poky-linux-gnueabi-g++program cc1plus
> > compilation terminated.
> > Makefile:1137: recipe for target 'powerpc.o' failed
> >
> > I have looked through the Git log for meta/recipes-devtools/binutils up
> through master HEAD, and I don't see any references to a problem similar to
> this one.  Has anyone seen a problem like this before?  If so, does anyone
> know how to fix it?
> >
> 
> it seems compiler is out of memory.

That may be what happened.  I tried rebuilding a few times and I kept getting the same error.  I read through the release notes for the other releases and I saw that I would eventually need to add 'ptest' to my DISTRO_FEATURES_remove list.  I did that and rebuilt the image, and it built without issues.

If I see this again in the future, I may need to change the parallel build settings so there is less building at the same time.

Thanks,
Bryan

> 
> > Thanks,
> > Bryan
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#156424):
> > https://lists.openembedded.org/g/openembedded-core/message/156424
> > Mute This Topic: https://lists.openembedded.org/mt/85926755/1997914
> > Group Owner: openembedded-core+owner@lists.openembedded.org
> > Unsubscribe: https://lists.openembedded.org/g/openembedded-
> core/unsub
> > [raj.khem@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >