| Summary: | media-tv/mythtv/mythtv-0.21_p16658 fails to build - red_eye error | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Matthew Schultz <mattsch> |
| Component: | New packages | Assignee: | Television related Applications in Gentoo's Portage <media-tv> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build.log
my only mythtv.eclass |
||
|
Description
Matthew Schultz
2008-03-23 16:41:48 UTC
Created attachment 147022 [details]
build.log
mythtv build.log with error
<snip> make[3]: Leaving directory `/var/tmp/portage/portage/media-tv/mythtv-0.21_p16658/work/mythtv-0.21/bindings/perl' -o perl -L/usr/qt/3/lib64 -L/usr/X11R6/lib64 -lqt-mt -lXext -lX11 -lm make[2]: Leaving directory `/var/tmp/portage/portage/media-tv/mythtv-0.21_p16658/work/mythtv-0.21/bindings/perl' make[1]: Leaving directory `/var/tmp/portage/portage/media-tv/mythtv-0.21_p16658/work/mythtv-0.21/bindings' cd config && make -f Makefile make[1]: Entering directory `/var/tmp/portage/portage/media-tv/mythtv-0.21_p16658/work/mythtv-0.21/config' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/var/tmp/portage/portage/media-tv/mythtv-0.21_p16658/work/mythtv-0.21/config' x86_64-pc-linux-gnu-gcc: red_eye.c: No such file or directory x86_64-pc-linux-gnu-gcc: no input files </snip> *** This bug has been marked as a duplicate of bug 213093 *** Do you have the following file? ls -l /usr/portage/distfiles/svn-src/mythtv/mythtv/contrib/chan nel_changers/red_eye.c (In reply to comment #3) > Do you have the following file? > > ls -l /usr/portage/distfiles/svn-src/mythtv/mythtv/contrib/chan > nel_changers/red_eye.c > I was just looking at the this line in the ebuild and it's wrong: $(tc-getCC) ${CFLAGS} ${CPPFLAGS} -o ../../red_eye red_eye.c ${LDFLAGS} || cd "${S}"/contrib/channel_changers ls -l: drwxr-sr-x 3 root portage 120 2008-03-23 08:49 6200ch drwxr-sr-x 3 root portage 152 2008-03-23 08:49 change-channel-lirc drwxr-sr-x 3 root portage 128 2008-03-23 08:49 d10control drwxr-sr-x 3 root portage 160 2008-03-23 08:50 dct2000serial drwxr-sr-x 3 root portage 552 2008-03-23 08:49 dct-channel drwxr-sr-x 3 root portage 128 2008-03-23 08:51 red_eye drwxr-sr-x 3 root portage 128 2008-03-23 08:49 sa3250ch You shouldn't be using ../../ since you're already in the directory with the red_eye directory in it. Path for the red_eye.c file: /usr/portage/distfiles/svn-src/mythtv/mythtv/contrib/channel_changers/red_eye/red_eye.c (In reply to comment #4) > (In reply to comment #3) > > Do you have the following file? > > > > ls -l /usr/portage/distfiles/svn-src/mythtv/mythtv/contrib/chan > > nel_changers/red_eye.c > > > > I was just looking at the this line in the ebuild and it's wrong: > > $(tc-getCC) ${CFLAGS} ${CPPFLAGS} -o ../../red_eye red_eye.c ${LDFLAGS} || -o means output file. Since we're in ${S}/contrib/channel_changers it means we're putting the resultant binary from what we compiled in ${S}. So that's proper. > > > > cd "${S}"/contrib/channel_changers > > ls -l: > > drwxr-sr-x 3 root portage 120 2008-03-23 08:49 6200ch > drwxr-sr-x 3 root portage 152 2008-03-23 08:49 change-channel-lirc > drwxr-sr-x 3 root portage 128 2008-03-23 08:49 d10control > drwxr-sr-x 3 root portage 160 2008-03-23 08:50 dct2000serial > drwxr-sr-x 3 root portage 552 2008-03-23 08:49 dct-channel > drwxr-sr-x 3 root portage 128 2008-03-23 08:51 red_eye > drwxr-sr-x 3 root portage 128 2008-03-23 08:49 sa3250ch That's not what my SVN checkout looks like for 0.21 and upstream's repo, http://svn.mythtv.org/trac/browser/branches/release-0-21-fixes/mythtv/contrib/channel_changers agrees with me. You pasted the layout of the 0.22 trunk. > > > You shouldn't be using ../../ since you're already in the directory with the > red_eye directory in it. It's -o ../../red_eye which is building the result file and that's not a reference to the source file. > > Path for the red_eye.c file: > > /usr/portage/distfiles/svn-src/mythtv/mythtv/contrib/channel_changers/red_eye/red_eye.c > it's /usr/portage/distfiles/svn-src/mythtv/mythtv/contrib/channel_changers/red_eye.c for 0.21 You most likely have an overlay with a mythtv.eclass in it and aren't using the Portage version. (In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > Do you have the following file? > > > > > > ls -l /usr/portage/distfiles/svn-src/mythtv/mythtv/contrib/chan > > > nel_changers/red_eye.c > > > > > > > I was just looking at the this line in the ebuild and it's wrong: > > > > $(tc-getCC) ${CFLAGS} ${CPPFLAGS} -o ../../red_eye red_eye.c ${LDFLAGS} || > > -o means output file. Since we're in ${S}/contrib/channel_changers it means > we're putting the resultant binary from what we compiled in ${S}. So that's > proper. > > > > > > > > > cd "${S}"/contrib/channel_changers > > > > ls -l: > > > > drwxr-sr-x 3 root portage 120 2008-03-23 08:49 6200ch > > drwxr-sr-x 3 root portage 152 2008-03-23 08:49 change-channel-lirc > > drwxr-sr-x 3 root portage 128 2008-03-23 08:49 d10control > > drwxr-sr-x 3 root portage 160 2008-03-23 08:50 dct2000serial > > drwxr-sr-x 3 root portage 552 2008-03-23 08:49 dct-channel > > drwxr-sr-x 3 root portage 128 2008-03-23 08:51 red_eye > > drwxr-sr-x 3 root portage 128 2008-03-23 08:49 sa3250ch > > That's not what my SVN checkout looks like for 0.21 and upstream's repo, > http://svn.mythtv.org/trac/browser/branches/release-0-21-fixes/mythtv/contrib/channel_changers > agrees with me. > > You pasted the layout of the 0.22 trunk. > > > > > > > You shouldn't be using ../../ since you're already in the directory with the > > red_eye directory in it. > > It's -o ../../red_eye which is building the result file and that's not a > reference to the source file. > > > > > Path for the red_eye.c file: > > > > /usr/portage/distfiles/svn-src/mythtv/mythtv/contrib/channel_changers/red_eye/red_eye.c > > > > it's > /usr/portage/distfiles/svn-src/mythtv/mythtv/contrib/channel_changers/red_eye.c > for 0.21 > > You most likely have an overlay with a mythtv.eclass in it and aren't using the > Portage version. > I was wondering about that. It was compiling fine on my other two computers running gentoo but not the one. I think it's because I was using 0.22. 0.21 used to be masked and 0.22 appeared one day and it just went to emerge that. Then I deleted the unmask and now it's trying to emerge 0.21 but it's failing. This doesn't really make much sense since svn should update to the specified version in the repo right? (In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) > > > (In reply to comment #3) > > > > Do you have the following file? > > > > > > > > ls -l /usr/portage/distfiles/svn-src/mythtv/mythtv/contrib/chan > > > > nel_changers/red_eye.c > > > > > > > > > > I was just looking at the this line in the ebuild and it's wrong: > > > > > > $(tc-getCC) ${CFLAGS} ${CPPFLAGS} -o ../../red_eye red_eye.c ${LDFLAGS} || > > > > -o means output file. Since we're in ${S}/contrib/channel_changers it means > > we're putting the resultant binary from what we compiled in ${S}. So that's > > proper. > > > > > > > > > > > > > > cd "${S}"/contrib/channel_changers > > > > > > ls -l: > > > > > > drwxr-sr-x 3 root portage 120 2008-03-23 08:49 6200ch > > > drwxr-sr-x 3 root portage 152 2008-03-23 08:49 change-channel-lirc > > > drwxr-sr-x 3 root portage 128 2008-03-23 08:49 d10control > > > drwxr-sr-x 3 root portage 160 2008-03-23 08:50 dct2000serial > > > drwxr-sr-x 3 root portage 552 2008-03-23 08:49 dct-channel > > > drwxr-sr-x 3 root portage 128 2008-03-23 08:51 red_eye > > > drwxr-sr-x 3 root portage 128 2008-03-23 08:49 sa3250ch > > > > That's not what my SVN checkout looks like for 0.21 and upstream's repo, > > http://svn.mythtv.org/trac/browser/branches/release-0-21-fixes/mythtv/contrib/channel_changers > > agrees with me. > > > > You pasted the layout of the 0.22 trunk. > > > > > > > > > > > You shouldn't be using ../../ since you're already in the directory with the > > > red_eye directory in it. > > > > It's -o ../../red_eye which is building the result file and that's not a > > reference to the source file. > > > > > > > > Path for the red_eye.c file: > > > > > > /usr/portage/distfiles/svn-src/mythtv/mythtv/contrib/channel_changers/red_eye/red_eye.c > > > > > > > it's > > /usr/portage/distfiles/svn-src/mythtv/mythtv/contrib/channel_changers/red_eye.c > > for 0.21 > > > > You most likely have an overlay with a mythtv.eclass in it and aren't using the > > Portage version. > > > > I was wondering about that. It was compiling fine on my other two computers > running gentoo but not the one. I think it's because I was using 0.22. 0.21 > used to be masked and 0.22 appeared one day and it just went to emerge that. > Then I deleted the unmask and now it's trying to emerge 0.21 but it's failing. > This doesn't really make much sense since svn should update to the specified > version in the repo right? > The build.log I attached specifies 0.21 as you can see. Is not possible to go back to 0.21 after I updated to 0.22 in svn? Works fine for me. Like I said, I think you have a mythtv.eclass in one of your overlays that's overriding some stuff from the Portage version of that eclass. Created attachment 147212 [details]
my only mythtv.eclass
I don't have mythtv in any my overlay:
gandalf svn-src # updatedb
gandalf svn-src # locate mythtv.eclass
/usr/portage/eclass/mythtv.eclass
(In reply to comment #8) > Works fine for me. Like I said, I think you have a mythtv.eclass in one of your > overlays that's overriding some stuff from the Portage version of that eclass. > Should I just rm -rf svn-src and re-emerge? You could try that. However, svn up http://svn.mythtv.org/svn/branches/release-0-21-fixes/mythtv@16658 is what the eclass should be running for you and it'll do the right thing. You can go into the /usr/portage/distfiles/svn-src/mythtv/mythtv directory and run that command and then run svn status and paste that result here. (In reply to comment #11) > You could try that. However, svn up > http://svn.mythtv.org/svn/branches/release-0-21-fixes/mythtv@16658 is what the > eclass should be running for you and it'll do the right thing. You can go into > the /usr/portage/distfiles/svn-src/mythtv/mythtv directory and run that command > and then run svn status and paste that result here. > Well I tried to run svn up http://svn.mythtv.org/svn/branches/release-0-21-fixes/mythtv@16658 but it said there was nothing to do. So I took a more drastic approach and rm -rf mythtv directory. Then so it didn't have to do a checkout again, I tarred a checkout of the same rev off one of my other gentoo boxes and untarred it on that box. It emerged fine without errors after that. (In reply to comment #12) > Well I tried to run svn up > http://svn.mythtv.org/svn/branches/release-0-21-fixes/mythtv@16658 but it said > there was nothing to do. So I took a more drastic approach and rm -rf mythtv > directory. Then so it didn't have to do a checkout again, I tarred a checkout > of the same rev off one of my other gentoo boxes and untarred it on that box. > It emerged fine without errors after that. Cool, thanks Matthew. Closing as INVALID. |
