Bug 180545 - app-accessibility/epos-2.5.37 does not compile
|
Bug#:
180545
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: accessibility@gentoo.org
|
Reported By: kavol@email.cz
|
|
Component: Applications
|
|
|
URL:
|
|
Summary: app-accessibility/epos-2.5.37 does not compile
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2007-06-01 12:37 0000
|
hi,
there is some problem with epos compilation - the interesting lines are:
/bin/sh ../../libtool --tag=CXX --mode=compile g++ c++ cc++ gcc cc
-DHAVE_CONFIG_H -I. -I../.. -I./.. -w -DEPOS -ggdb -DBASE_DIR=/usr/share/epos
-Os -march=athlon-tbird -pipe -fomit-frame-pointer -c -o matrix.lo matrix.cc
mkdir .libs
g++ c++ cc++ gcc cc -DHAVE_CONFIG_H -I. -I../.. -I./.. -w -DEPOS -ggdb
-DBASE_DIR=/usr/share/epos -Os -march=athlon-tbird -pipe -fomit-frame-pointer
-c matrix.cc -DPIC
g++ c++ cc++ gcc cc -DHAVE_CONFIG_H -I. -I../.. -I./.. -w -DEPOS -ggdb
-DBASE_DIR=/usr/share/epos -Os -march=athlon-tbird -pipe -fomit-frame-pointer
-c map.cc -DPIC
g++ c++ cc++ gcc cc -DHAVE_CONFIG_H -I. -I../.. -I./.. -w -DEPOS -ggdb
-DBASE_DIR=/usr/share/epos -Os -march=athlon-tbird -pipe -fomit-frame-pointer
-c enumstring.cc -DPIC
distcc[19535] ERROR: compile (null) on localhost failed
distcc[19525] ERROR: compile (null) on localhost failed
g++: c++: No such file or directory
g++: cc++: No such file or directory
g++: gcc: No such file or directory
g++: cc: No such file or directory
- as we see, it uses wrong compiler name
this comes from some strange varible in configure.ac:
CCC="g++ c++ cc++ gcc cc"
after commenting out that variable, the configure process and the compilation
go fine; for testing purposes, to filter the variable "CCC" out I've added a
simple sed to the ebuild in the function src_unpack() after epatch - and it
works_for_me(tm)
Reproducible: Always
(In reply to comment #0)
> hi,
>
> there is some problem with epos compilation - the interesting lines are:
>
> /bin/sh ../../libtool --tag=CXX --mode=compile g++ c++ cc++ gcc cc
> -DHAVE_CONFIG_H -I. -I../.. -I./.. -w -DEPOS -ggdb -DBASE_DIR=/usr/share/epos
> -Os -march=athlon-tbird -pipe -fomit-frame-pointer -c -o matrix.lo matrix.cc
> mkdir .libs
> g++ c++ cc++ gcc cc -DHAVE_CONFIG_H -I. -I../.. -I./.. -w -DEPOS -ggdb
> -DBASE_DIR=/usr/share/epos -Os -march=athlon-tbird -pipe -fomit-frame-pointer
> -c matrix.cc -DPIC
> g++ c++ cc++ gcc cc -DHAVE_CONFIG_H -I. -I../.. -I./.. -w -DEPOS -ggdb
> -DBASE_DIR=/usr/share/epos -Os -march=athlon-tbird -pipe -fomit-frame-pointer
> -c map.cc -DPIC
> g++ c++ cc++ gcc cc -DHAVE_CONFIG_H -I. -I../.. -I./.. -w -DEPOS -ggdb
> -DBASE_DIR=/usr/share/epos -Os -march=athlon-tbird -pipe -fomit-frame-pointer
> -c enumstring.cc -DPIC
> distcc[19535] ERROR: compile (null) on localhost failed
> distcc[19525] ERROR: compile (null) on localhost failed
> g++: c++: No such file or directory
> g++: cc++: No such file or directory
> g++: gcc: No such file or directory
> g++: cc: No such file or directory
>
>
> - as we see, it uses wrong compiler name
>
> this comes from some strange varible in configure.ac:
> CCC="g++ c++ cc++ gcc cc"
>
> after commenting out that variable, the configure process and the compilation
> go fine; for testing purposes, to filter the variable "CCC" out I've added a
> simple sed to the ebuild in the function src_unpack() after epatch - and it
> works_for_me(tm)
>
> Reproducible: Always
>
I am having the same issue, are there any updates or test ebuilds for this
problem?
Can you please submit a patch for the ebuild that adds this sed call so that it
can be tested? Thanks much.
(In reply to comment #2)
> Can you please submit a patch for the ebuild that adds this sed call so that it
> can be tested? Thanks much.
--- epos-2.5.37.ebuild 2007-04-28 17:35:23.000000000 +0000
+++ epos-2.5.37-r1.ebuild 2007-08-11 16:52:42.000000000 +0000
@@ -29,6 +29,7 @@
cd "${S}"
epatch "${FILESDIR}/${PN}-2.5.35-sysportaudio.patch"
+ sed -i "s/CCC/#CCC/" configure.ac
eautoreconf
}
I am having the same issue :-( can you add to portage patch? Thanks
This has been fixed in portage. Thanks for your patience. :-)