Launchpad itself

Difference between binary built locally and on launchpad

Asked by lucio messina

H, I'm Lucio, I'm Italian and I don't speak English very well.

My problem is that I can build misqui (https://launchpad.net/~lucio-messina-w/+archive/ppa/+packages) from sources, using sudo make install.
But when I download the package and install it the program won't work.

I think it's because the file into debian packages aren't recompiled, but only copied in filesystem.
So, are there any differences between binary build in launchpad machines and ones build on my computer?
Should binary build in launchpad's machines work correctly on my computer?

I think yes...
The two binaries are also different, I checked with the "readelf -a" command.

Can I force debian package recompiling sources instead of just copying files?
Or there is another way?

Thanks in advance.
Lucio

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
lucio messina
Solved:
Last query:
Last reply:
Revision history for this message
William Grant (wgrant) said : 		#1

What do you mean when you say "the program won't work"?

Launchpad just does whatever debian/rules tells it to do. Try using https://wiki.ubuntu.com/PbuilderHowto to do a test build locally, hopefully letting you identify the issue there.

Revision history for this message
lucio messina (lucio-messina-w) said : 		#2

Hi William.
Thanks for the reply.

Actually, I'm building packages using bzr and debhelper.
I discovered that the binary build with

dh_auto_build

doesn't work itself.
So, when I put it in the package it doesn't work too.

Also the sizes of the two binary are different.
It is strange because dh_auto_build calls

$(MAKE) build.

When I call make build manually the program works fine, but the binary build by dh_auto_build crashes with an output:

*** stack smashing detected ***: ./misqui terminated

Can you tell me why?
Thank you a lot again.

Revision history for this message
William Grant (wgrant) said : 		#3

It may be building with additional compiler security flags. Compare the build logs and see if the gcc stack protector flags differ.

Revision history for this message
lucio messina (lucio-messina-w) said : 		#4

Ok, I'll try

Revision history for this message
lucio messina (lucio-messina-w) said : 		#5

I checked the buildlog, and the flag compilation are the same.

Even in my computer the binary build with "dh_auto_build" doesn't work.
I read about "stack smashing detected", and I'm trying to discover the error in the code (I hope it is somwthing stupid).

Thank you a lot, I'll mark this question as solved if I fix the bug.

Revision history for this message
lucio messina (lucio-messina-w) said : 		#6

Ok, I solved the problem (it was a bug in the code).
Now it builds and run without any error.

Thank you a lot again