search

ligzy / mp4v2

Automatically exported from code.google.com/p/mp4v2
Other
0 stars 0 forks source link

MP4V2 1.9.0 fails with GNU assembler 2.19.1 when -ggdb3 is in CFLAGS and/or CXXFLAGS #27

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Use GNU as 2.19.1 from binutils
2. Put -ggdb3 into CFLAGS and CXXFLAGS in your environment
3. Try to build MP4V2 1.9.0

What version of the product are you using? On what operating system?

MP4V2 1.9.0 release on Linux with GLIBC 2.10+, GCC 4.4+, BINUTILS 2.19+

libtool: compile:  i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I./include
-I./include -I. -I. -Wall -Wformat -march=native -O2 -pipe -ggdb3
-fvisibility=hidden -c src/bmff/typebmff.cpp  -fPIC -DPIC -o
src/bmff/.libs/typebmff.o
{standard input}: Assembler messages:
{standard input}:444: Error: file number 2 already allocated
libtool: compile:  i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I./include
-I./include -I. -I. -Wall -Wformat -march=native -O2 -pipe -ggdb3
-fvisibility=hidden -c src/itmf/CoverArtBox.cpp  -fPIC -DPIC -o
src/itmf/.libs/CoverArtBox.o
{standard input}: Assembler messages:
{standard input}:444: Error: file number 2 already allocated
make: *** [src/itmf/CoverArtBox.lo] Error 1
make: *** Waiting for unfinished jobs....
libtool: compile:  i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I./include
-I./include -I. -I. -Wall -Wformat -march=native -O2 -pipe -ggdb3
-fvisibility=hidden -c src/rtphint.cpp -o src/rtphint.o >/dev/null 2>&1
make: *** [src/bmff/typebmff.lo] Error 1

Please provide any additional information below.

See (downstream bug), http://bugs.gentoo.org/show_bug.cgi?id=277682

I'm the maintainer of this package for Gentoo, we are working around this
issue by replacing -ggdb3 with -ggdb2 to work around this "problem" inside
our build script -- It's not a problem in that sense anymore for us, but
just in case you want to really fix it.

Original issue reported on code.google.com by ssuomi...@unk.fi on 13 Jul 2009 at 6:21

GoogleCodeExporter commented 9 years ago 
Perhaps this patch.. ? Since sed was already used in the configure, I assumed 
it's
safe to use it plus if -ggdb3 is supported and present, we can assume -ggdb2 is 
there
as well

Original comment by ssuomi...@unk.fi on 13 Jul 2009 at 10:21

Attachments:

GoogleCodeExporter commented 9 years ago 
Fixed in 1.9.1, committed r368 for 1.9.1 and r369 for trunk

Original comment by eddygroe...@gmail.com on 13 Jul 2009 at 11:37