I don't know when those errors started to appear, but I think they started after I updated GIT today.
The errors are in my build log and look like this:
cd /opt/trinity/bin && ./tdelfeditor -m /dev/shm/arts.build/soundserver/artswrapper "artswrapper" "" "" "" "" "Trinity Desktop Environment" "" "" "01/19/2012 19:33:11" "artswrapper" "" || true /bin/sh: line 0: cd: /opt/trinity/bin: No such file or directory
The problem is /opt/trinity/bin does not yet exist. Hence the errors.
I built qt3 and tqtinterface to build to /usr. Everything else I am building to install to /opt/trinity.
The errors occurred while building arts, the third package in the core series of packages.
I can eliminate the messages with mkdir -p /opt/trinity/bin, but I think there should be a test that /opt/trinity/bin exists. Of course, /opt/trinity/bin gets created after I install the arts package. Thereafter the errors will not occur.
I suspect the errors are harmless, but I always search my build logs for "No such file or directory" errors. That is one way I catch problems. Not having those errors in the build logs helps reduce clutter. :)
Darrell
I don't know when those errors started to appear, but I think they started after I updated GIT today.
The errors are in my build log and look like this:
cd /opt/trinity/bin && ./tdelfeditor -m /dev/shm/arts.build/soundserver/artswrapper "artswrapper" "" "" "" "" "Trinity Desktop Environment" "" "" "01/19/2012 19:33:11" "artswrapper" "" || true /bin/sh: line 0: cd: /opt/trinity/bin: No such file or directory
The problem is /opt/trinity/bin does not yet exist. Hence the errors.
<snip>
Try the attached patch.
Tim
The errors are in my build log and look like this:
cd /opt/trinity/bin && ./tdelfeditor -m /dev/shm/arts.build/soundserver/artswrapper
"artswrapper" "" "" "" ""
"Trinity Desktop Environment" "" "" "01/19/2012
19:33:11" "artswrapper" ""
|| true /bin/sh: line 0: cd: /opt/trinity/bin: No such file or
directory
The problem is /opt/trinity/bin does not yet exist.
Hence the errors.
<snip>
Try the attached patch.
You da man!
No more "No such file or directory" errors from tdelfeditor.
But I ran into a strange quirk. :(
I receive build failures with this error message:
cd /dev/shm/arts.build/soundserver && if [[ -e /opt/trinity/bin/tdelfeditor ]]; then /opt/trinity/bin/tdelfeditor -m /dev/shm/arts.build/soundserver/artswrapper "artswrapper" "" "" "" "" "Trinity Desktop Environment" "" "" "01/19/2012 22:01:43" "artswrapper" "" || true fi /bin/sh: -c: line 1: syntax error: unexpected end of file make[2]: *** [soundserver/artswrapper] Error 1
Notice the missing semi-colon at the end. Seems the semi-colon between the true and fi disappears into thin air.
After the configure and before the make I need to run the following:
find arts.build -name build.make -exec sed -i 's: || true fi: || true; fi:' {} ;
What is tdelfeditor anyway?
Darrell
The errors are in my build log and look like this:
<snip>
Final patch attached--the others were preliminary test patches. If this one works it will go straight into GIT.
What is tdelfeditor anyway?
The TDE ELF information editor--basically it is called during the build process to add metadata to TDE executables.
Tim
Final patch attached--the others were preliminary test patches. If this one works it will go straight into GIT.
No error messages for arts.
Looks like the same fix is needed for other packages too. My dbus-1-tqt and tdelibs build logs show the following similar errors:
cd /opt/trinity/bin && ./tdelfeditor -m /dev/shm/tdelibs.build/dcop/dcopserver_shutdown "dcopserver_shutdown" "" "" "" "" "Trinity Desktop Environment" "" "" "01/19/2012 22:20:19" "dcopserver_shutdown" "" || true /bin/sh: ./tdelfeditor: No such file or directory cd /opt/trinity/bin && ./tdelfeditor -e /dev/shm/tdelibs.build/dcop/dcopserver_shutdown || true /bin/sh: ./tdelfeditor: No such file or directory cd /opt/trinity/bin && ./tdelfeditor -t /dev/shm/tdelibs.build/dcop/dcopserver_shutdown dcopserver_shutdown || true /bin/sh: ./tdelfeditor: No such file or directory make[2]: Leaving directory `/dev/shm/tdelibs.build'
What is tdelfeditor anyway?
The TDE ELF information editor--basically it is called during the build process to add metadata to TDE executables.
Oh. Ok. Um, how do we use that?
Darrell
-
Darrell Anderson -
Timothy Pearson