2011/3/16 Per Jessen <per@opensuse.org>:
Cristian Morales Vega wrote:
2011/3/16 Per Jessen <per@opensuse.org>:
Per Jessen wrote:
Marcus Meissner wrote:
error: File /usr/src/packages/SOURCES/nasm-2.09.07.tar.bz2: No such file or directory
nasm-2.09.07.tar.bz2 is the new tarball. What am I missing here?
adding it to the sources checkin...
osc add nasm-2.09.07.tar.bz2 osc ci
Ciao, Marcus
Duh! thanks.
Okay, next stumbling block:
my new nasm package built everywhere except SLE_10 :
gcc -c -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -O2 -W -Wall -std=c99 -pedantic -DHAVE_CONFIG_H -I. -I. -o ver.o ver.c ver.c:39: error: '__TIMESTAMP__' undeclared here (not in a function) make: *** [ver.o] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.45632 (%build)
What I don't understand is - ver.c wasn't changed, so how does/did the currently released nasm build on SLE_10?
Anyway you should patch/sed out that __TIMESTAMP__ to allow build-compare to do its work.
It's actually a __DATE__ and I can certainly get rid of it, but I'd like to understand _why_ before I do it. (Remember, I'm VERY new to this).
You want two builds from the same source to generate the same binary. This allows the user to verify the binary hasn't been corrupted/compromised. Also, the openSUE Build service rebuilds the package everytime a dependency changes, but after the build there is a script that checks if there is any important difference between the new build and the old one. If the two build are equal the new package is discarded, so the user doesn't needs to redownload a new package that is exactly equal to the one he already has. But __TIMESTAMP__, __DATE__ and __TIME__ macros make every build different since they add the build time to the binary. Usually you substitute the macro with the timestamp from the .changes file (using sed) to avoid the problem. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org