Hi,

Honestly I don't know. Those errors are reported by the assembler, gcc probably generated some kind of opcodes it didn't recognize.

One idea I have is that glib has some inline assembly stuff in gatomic.h, so *maybe* that is the root cause. To confirm that you'll need to compare the offending lines in the generated assembly file to the functions in glib headers.

Glib probably attempts to detect which processor you have and uses an ifdef trickery to use the appropriate code fragment. I guess there's a generic implementation not using inline assembly. So you might try to force that by playing with glib configure options.

Bazsi

On Feb 7, 2016 1:45 PM, "Girish Kumar" <girish.kumar@al-enterprise.com> wrote:

Hi,

 

I have changed the syslog-ngd to syslog-ng

 

I am getting following error while compiling syslog-ng .  

My tool chain is perfectly fine. I have complied many other packages which are fine. With syslog-ng I am getting following error.

 

Could you please guide me on this. It would be great if you can give me some guidelines on how to compile  syslog-ng on armv7 arch on  linux platform

 

 

  CC     lib/lib_libsyslog_ng_la-mainloop-call.lo

/tmp/ccChQOWy.s: Assembler messages:

/tmp/ccChQOWy.s:260: Error: invalid operands (.text and *UND* sections) for `-'

/tmp/ccChQOWy.s:269: Error: invalid operands (.text and *UND* sections) for `-'

make[4]: *** [lib/lib_libsyslog_ng_la-mainloop-call.lo] Error 1

make[3]: *** [all-recursive] Error 1

make[2]: *** [all] Error 2

make[2]: Leaving directory `/home/gkuma020/PERFORCE/7.X.X.R01-gkuma020-gg/engr/sw/tps/objs/46/7.X.X.R01/armv7/syslog-ng'

make[2]: Entering directory `/home/gkuma020/PERFORCE/7.X.X.R01-gkuma020-gg/engr/sw/tps/objs/46/7.X.X.R01/armv7/syslog-ng'

make --no-print-directory install-recursive

  CC     lib/lib_libsyslog_ng_la-mainloop-call.lo

/tmp/cc0N5KS5.s: Assembler messages:

/tmp/cc0N5KS5.s:260: Error: invalid operands (.text and *UND* sections) for `-'

/tmp/cc0N5KS5.s:269: Error: invalid operands (.text and *UND* sections) for `-'

make[4]: *** [lib/lib_libsyslog_ng_la-mainloop-call.lo] Error 1

make[3]: *** [install-recursive] Error 1

make[2]: *** [install] Error 2

make[2]: Leaving directory `/home/gkuma020/PERFORCE/7.X.X.R01-gkuma020-gg/engr/sw/tps/objs/46/7.X.X.R01/armv7/syslog-ng'

make[1]: *** [/home/gkuma020/PERFORCE/7.X.X.R01-gkuma020-gg/engr/sw/tps/built/46/7.X.X.R01/armv7/sbin/syslog-ng] Error 2

make[1]: Leaving directory `/home/gkuma020/PERFORCE/7.X.X.R01-gkuma020-gg/engr/sw/tps'

make: *** [tps-build] Error 2

+ set +x

 

Regards,

Girish

 

From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Scheidler, Balázs
Sent: Sunday, February 07, 2016 2:30 AM
To: Syslog-ng users' and developers' mailing list
Subject: Re: [syslog-ng] compiling syslog-ng for armv7 platform on linux with TLS support

 

Sorry but I don't know the target environment so reviewing this is pretty impossible. If it compiles with these and at least the functest runs then it should be OK.

Do you have a specific reason to call syslog-ng binary as syslog-ngd? On other platforms it is syslog-ng.

On Feb 4, 2016 12:31 PM, "Girish Kumar" <girish.kumar@al-enterprise.com> wrote:

Hi All,

 

Presently I am compiling for armv7 platform on linux. Please let me know  whether following settings are fine

 

syslog-ng_deps = $(shell find $(LTOP)/syslog-ng-3.6.4 -type f)

$(OBJS)/syslog-ng/syslog-ng.configured: $(syslog-ng_deps) $(RAMDISK_LIB)/libssl.so.1.0.0 eventlog

    @rm -rf $(OBJS)/syslog-ng;

    @mkdir -p $(OBJS)/syslog-ng;

    @cd $(OBJS)/syslog-ng;\

    declare -x PATH=$(CCPATH):$(PATH);\

    declare -x CFLAGS="$(PLATFORM_CFLAGS) -I$(CROSSINCS) -I$(BUILT_INCLUDES)";\

    declare -x CPPFLAGS="$(PLATFORM_CPPFLAGS) -I$(CROSSINCS) -I$(BUILT_INCLUDES)";\

    declare -x LDFLAGS="$(PLATFORM_LDFLAGS) -L$(CROSSLIBS) -L$(BUILT_LIBS) -lcrypto -levtlog";\

    declare -x EVTLOG_CFLAGS="$(PLATFORM_CFLAGS) -I$(CROSSINCS) -I$(BUILT_INCLUDES) -I$(BUILT_INCLUDES)/eventlog";\

    declare -x EVTLOG_LIBS="$(PLATFORM_LDFLAGS) -L$(CROSSLIBS) -L$(BUILT_LIBS) -levtlog";\

    declare -x ac_cv_func_malloc_0_nonnull="yes";\

    declare -x ac_cv_func_realloc_0_nonnull="yes";\

    $(LTOP)/syslog-ng-3.6.4/configure --prefix=/ --host=$(CCPREFIX)\

        --enable-ssl --enable-glib &> $(OBJS)/syslog-ng/configure.out

    @touch $(OBJS)/syslog-ng/syslog-ng.configured

$(BUILT_BASE)/sbin/syslog-ngd: $(OBJS)/syslog-ng/syslog-ng.configured

    @cd $(OBJS)/syslog-ng;\

    declare -x PATH=$(CCPATH):$(PATH);\

    declare -x CFLAGS="$(PLATFORM_CFLAGS) -I$(CROSSINCS) -I$(BUILT_INCLUDES)";\

    declare -x CPPFLAGS="$(PLATFORM_CPPFLAGS) -I$(CROSSINCS) -I$(BUILT_INCLUDES)";\

    declare -x LDFLAGS="$(PLATFORM_LDFLAGS) -L$(CROSSLIBS) -L$(BUILT_LIBS) -lcrypto -levtlog";\

    declare -x EVTLOG_CFLAGS="$(PLATFORM_CFLAGS) -I$(CROSSINCS) -I$(BUILT_INCLUDES) -I$(BUILT_INCLUDES)/eventlog";\

    declare -x EVTLOG_LIBS="$(PLATFORM_LDFLAGS) -L$(CROSSLIBS) -L$(BUILT_LIBS) -levtlog";\

    $(MAKE) &> $(OBJS)/syslog-ng/make.out;\

    make install prefix=$(BUILT_BASE) &> $(OBJS)/syslog-ng/install.out

 

$(RAMDISK_SBIN)/syslog-ngd: $(BUILT_BASE)/sbin/syslog-ngd

    @cp -rf $(BUILT_BASE)/lib/syslog-ng $(RAMDISK_LIB)

   @cp -f $(BUILT_BASE)/sbin/syslog-ngd $(RAMDISK_SBIN)

    @echo "$(PLATFORM_DIR) syslog-ngd done"

 

syslog-ng: $(RAMDISK_SBIN)/syslog-ngd

 

Regards,

Girish


______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq


______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq