[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to tell the compiler NOT to assume cpu provides atomic instructions




On Mon, Mar 7, 2011 at 7:38 PM, brian m. carlson <sandals@crustytoothpaste.net> wrote:
Hi.  *Please* do not CC me; I'm subscribed to the list.

Sorry, the default on my gmail is "Reply All" and usually I remove relevant parties from the To/Cc: headers, guess missed it this time. Wasn't intentional.
 
> umm sorry if this is a stupid question but I don't know what other output to
> provide other than what I provided above which was from the 'make' command.
> The beginning of that is:

Normally, make will print the actual command line of the command it is
running.  In this case, Asterisk upstream has hidden this and printed
something else instead.

> # make
> CC="cc" CXX="" LD="" AR="" RANLIB="" CFLAGS="" make -C menuselect
> CONFIGURE_SILENT="--silent" makeopts

Using --silent as an argument to make will prevent it from printing the commands as they are executed.  You should probably ask Asterisk 
upstream how to get the commands printed as they are executed.  I need to see the compilation command line (probably starting "cc" or "gcc") so
that I know what flags are being used.  The command line used for linking would also be useful.

Ok, I'll leave an email in the Asterisk list but in the meantime, this is what I found from the make output (just posting the relevant lines):

CC="cc" CXX="" LD="" AR="" RANLIB="" CFLAGS="" make -C menuselect CONFIGURE_SILENT="--silent" menuselect
make[1]: Entering directory `/usr/src/asterisk-1.8.3/menuselect'
gcc -g -c -D_GNU_SOURCE -Wall   -c -o menuselect.o menuselect.c
gcc -g -c -D_GNU_SOURCE -Wall   -c -o strcompat.o strcompat.c
gcc -g -c -D_GNU_SOURCE -Wall   -c -o menuselect_stub.o menuselect_stub.c
make[2]: Entering directory `/usr/src/asterisk-1.8.3/menuselect/mxml'
gcc -Os -g -Wall   -c mxml-attr.c
gcc -Os -g -Wall   -c mxml-entity.c
gcc -Os -g -Wall   -c mxml-file.c
gcc -Os -g -Wall   -c mxml-index.c
gcc -Os -g -Wall   -c mxml-node.c
gcc -Os -g -Wall   -c mxml-search.c
gcc -Os -g -Wall   -c mxml-set.c
gcc -Os -g -Wall   -c mxml-private.c
gcc -Os -g -Wall   -c mxml-string.c
/bin/rm -f libmxml.a
/usr/bin/ar crvs libmxml.a mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o                  mxml-private.o mxml-string.o
a - mxml-attr.o
a - mxml-entity.o
a - mxml-file.o
a - mxml-index.o
a - mxml-node.o
a - mxml-search.o
a - mxml-set.o
a - mxml-private.o
a - mxml-string.o
ranlib libmxml.a
make[2]: Leaving directory `/usr/src/asterisk-1.8.3/menuselect/mxml'
gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a

...and this might be even more relevant?

checking for gcc... gcc
checking whether the C compiler (gcc -pthread -I../..//include -I/usr/include/libxml2 -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -g3 -mtune=ultrasparc -mcpu=v8 -fomit-frame-pointer -O6    ) works                 ... yes
checking whether the C compiler (gcc -pthread -I../..//include -I/usr/include/libxml2 -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -g3 -mtune=ultrasparc -mcpu=v8 -fomit-frame-pointer -O6    ) is a                  cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking for mawk... mawk
checking host system type... sparc64-unknown-linux-gnu
checking for a BSD compatible install... /usr/bin/install -c
checking for ranlib... ranlib
checking for ar... /usr/bin/ar
checking for tgetent in -ltermcap... yes
checking for termcap.h... yes
checking for sys/cdefs.h... yes
checking for vis.h... no
checking for issetugid... no
checking for fgetln... no
checking for strvis... no
checking for strunvis... no
checking for strlcpy... no
checking for strlcat... no

HTH



Reply to: