Mailinglist Archive: opensuse (1640 mails)

[G T Smith <grahamsmith@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Josef Wolf wrote:
> Thanks for your reply, Anders!
>
> On Fri, Aug 01, 2008 at 09:37:59AM +0200, Anders Johansson wrote:
> > Am Freitag 01 August 2008 08:45:06 schrieb Josef Wolf:

<snip>

> > By the way, your previous comment about having to compile locally on all 
> > machines is wrong. The remark in the man page you quoted is about using the 
> > same compiler flags as was used for perl. That doesn't mean it has to be 
> > rebuilt every time it is installed
>
> How can I be sure that debian/ubuntu/mandrake/redhat/whatever use the
> same compiler flags and linker flags as suse?  They can even change the
> flags between releases.  So I have to build and maintain a dist package
> for every release of every distro I want to support.  And I have to
> rebuild every time a distro ships a new release.  That would be even
> more pain than rebuild every time it is installed.

I doubt if you can...

I rather think you are asking this question in the wrong place. I would
suggest subscribing to the Perl developer lists which will probably will
give you better information than this list on how to deal with this issue.

As far as I can understand it you have an application in which you call
a Perl script from, rather than using something like Perl::Inline which
does the opposite. I have little knowledge personally of the former
approach.

Perl has a couple of tools for cross platform building of Perl modules
for the latter approach (Module::Build and ExtUtils::MakeMaker) without
which CPAN would probably be unworkable. Any C or C++ code in the Perl
Module is compiled on the installation and testing of the module.

But for the former creating a portable package would require that you
create suitable make script(s) and source package(s) that may need to
include the source code for the library you are missing. (Not having
compiler support on some of the host systems complicates matter
somewhat). The key here is to distribute with the instructions/scripts
to build your code.


- --
==============================================================================
I have always wished that my computer would be as easy to use as my
telephone.
My wish has come true. I no longer know how to use my telephone.

Bjarne Stroustrup
==============================================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFIlDHEasN0sSnLmgIRAj7WAKDRU6yMJmpI2PDCKtr90hqoWkkmRgCfagcM
F4yzlwynTAI1pHmIRjaAhZU=
=Jzgb
-----END PGP SIGNATURE-----
-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx