Linked by Amjith Ramanujam on Tue 23rd Dec 2008 00:30 UTC
Thread beginning with comment 341159
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: A solution to the wrong problem
by sbergman27 on Tue 23rd Dec 2008 02:58
in reply to "RE[2]: A solution to the wrong problem"
Different GCC versions
Different GCC compilation options
Different GCC compilation options
Please be more specific about how reasonably current GCC versions and options affect binary portability.
Incompatible library APIs
Incompatible file formats
Incompatible file formats
Please be specific these incompatible library APIs and file formats.
Dependence on kernel functionality no longer supported
The kernel binary API has been frozen since Linux Kernel version 1.0, or so.
Dependence on kernel functionality specially compiled for a distro
If your package depends upon something that the vanilla kernel hasn't opted to merge, and distro support is still spotty, then yeah.
Dependence on specific distro-specific directory structures
Be specific, please. What variances from the FHS are significant here, and what can be done to correct that?
Dependence on specific distro-specific packages that no-one else supports
Again, please be more specific. What packages are we talking about?
RE[4]: A solution to the wrong problem
by Misogynist on Tue 23rd Dec 2008 05:14
in reply to "RE[3]: A solution to the wrong problem"
The FHS is a Linux-ism, and focusing more on Linux does us even less good in unifying software behavior in any meaningful way with OpenSolaris becoming more and more viable as an alternative. Many of the things advocated in the FHS are flat-out against the Solaris way of doing things.
RE[4]: A solution to the wrong problem
by chris_dk on Tue 23rd Dec 2008 09:58
in reply to "RE[3]: A solution to the wrong problem"
"Different GCC versions
Different GCC compilation options
Different GCC compilation options
Please be more specific about how reasonably current GCC versions and options affect binary portability.
"
Look at the autopackage page. They list all the problems related to binary compatibility.
Don't put your head in the sand.
RE[3]: A solution to the wrong problem
by AdamW on Tue 23rd Dec 2008 04:17
in reply to "RE[2]: A solution to the wrong problem"




Member since:
2005-07-09
Many reasons. Among which:
* Different GCC versions
* Different GCC compilation options
* Incompatible library APIs
* Incompatible file formats
* Dependence on kernel functionality no longer supported
* Dependence on kernel functionality specially compiled for a distro
* Dependence on specific distro-specific directory structures
* Dependence on specific distro-specific packages that no-one else supports