Ok, I've fixed up my package a bit so that lintian doesn't complain
about the conffiles anymore and I made the gnome support optional.
I'd like somebody to sponsor this package so that I can get underway
with becoming a new maintainer. What my package contains is a gtk based
app that keeps
On Tue, Mar 19, 2002 at 07:22:56PM +, David H. Askew wrote:
I realize that it is basically a debian policy to seperate documentation
and binarys into seperate packages, so that people who don't want the
documentation don't have to install it. However, the policy manual as I
understood
Is it valid to compile an executable with -fPIC?
Can anyone tell me which architectures require -fPIC?
Thanks,
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Wednesday 20 Mar 2002 11:00 pm, Michel LESPINASSE wrote:
I'd like to add that some architectures (including x86) do not actualy
require that you use -fPIC for shared libraries. If you choose to do
that, the benefits are that you dont pay the overhead of -fPIC code,
the drawbacks however
Hi!
On Wed, Mar 20, 2002 at 11:38:43PM +0100, Martin Eitzenberger wrote:
I want to make a simple debian package (I never made one before)
Only startup-script, docu and depends. But I don't understand how.
Could anyone help me?
First of all, you should read the New Maintainers' Guide (at
On Wed, 20 Mar 2002 23:38:43 +0100
Martin Eitzenberger [EMAIL PROTECTED] wrote:
Hi!
I want to make a simple debian package (I never made one before)
Only startup-script, docu and depends. But I don't understand how.
Could anyone help me?
read the new maintainers guide... you should have
On Wed, Mar 20, 2002 at 11:11:10PM +, Will Newton wrote:
On Wednesday 20 Mar 2002 11:00 pm, Michel LESPINASSE wrote:
I'd like to add that some architectures (including x86) do not actualy
require that you use -fPIC for shared libraries. If you choose to do
that, the benefits are that
Matt Zimmerman [EMAIL PROTECTED] writes:
On Sun, Mar 17, 2002 at 02:56:29PM -0500, Colin Walters wrote:
On Sun, 2002-03-17 at 11:41, Chris AtLee wrote:
Hi there,
I've written a small program that I'd like to package and have included
in the debian archive. It's a gnome applet
Ok, I've fixed up my package a bit so that lintian doesn't complain
about the conffiles anymore and I made the gnome support optional.
I'd like somebody to sponsor this package so that I can get underway
with becoming a new maintainer. What my package contains is a gtk based
app that keeps track
On Tue, Mar 19, 2002 at 06:28:23AM +0100, J?rgen H?gg wrote:
But lintian does not like this:
W: ham-server: executable-not-elf-or-script ./usr/lib/ham/Ham/Sched.pm
[...]
But the modules are not executable, it's -rw-r--r--.
What version of lintian are you using? Have you checked the
On Tue, Mar 19, 2002 at 07:22:56PM +, David H. Askew wrote:
I realize that it is basically a debian policy to seperate documentation
and binarys into seperate packages, so that people who don't want the
documentation don't have to install it. However, the policy manual as I
understood it
Is it valid to compile an executable with -fPIC?
Can anyone tell me which architectures require -fPIC?
Thanks,
--
Terry Churchill : http://www.doc-linux.co.uk
I was going to compile a list of innovations that could be attributed
to Microsoft. Once I realized that Ctrl-Alt-Del was handled in the
BIOS, I found that there aren't any.
Hi,
on Wed, 20 Mar 2002, Will Newton wrote:
Is it valid to compile an executable with -fPIC?
Can anyone tell me which architectures require -fPIC?
In general, you need to compile everything that could be mapped at
arbitrary addresses (in the process's virtual address space) with the
-fPIC
On Wednesday 20 Mar 2002 5:46 pm, Simon Richter wrote:
In general, you need to compile everything that could be mapped at
arbitrary addresses (in the process's virtual address space) with the
-fPIC option to make it position independent (whatever that means for the
target platform). Programs
Hi, I wan't to get our companys software packages in Debian. We've already
had our own apt-source for them about a year now and I think its time for
the world to learn about our LGPL:ed product.
I read [ http://www.debian.org/devel/join/nm-step1 ] and identified mailing
you guys as the very first
[cc: me, for I'm not on debian-mentors, thanks]
Hello!
I'm NM and only waiting for DAM Aproval. Since if been waiting for
about 3 months now, I will try too get my packages in via a sponsor.
So. If you are interested:
http://silverlock.dgim.crc.ca/remstats/
for the homepage
On Wed, Mar 20, 2002 at 06:46:19PM +0100, Tobias Bengtsson wrote:
Hi, I wan't to get our companys software packages in Debian. We've already
had our own apt-source for them about a year now and I think its time for
the world to learn about our LGPL:ed product.
Heh, I went to your site and
--
-- PSIplus [EMAIL PROTECTED]
-- ICQ... 57749465
-- Site... www.psiplus.org
-- Board... www.netphoenix.at
-- GnuPG Public Key... www.netphoenix.at/0/?loc=11
--
Hi!
I want to make a simple debian package (I never made one before)
Only startup-script, docu and depends. But I don't understand how.
Could anyone help me?
Martin
--
-- Martin Eitzenberger - PSIplus [EMAIL PROTECTED]
-- ICQ... 57749465
-- Site... www.psiplus.org
-- Board...
On Wed, Mar 20, 2002 at 06:00:35PM +, Will Newton wrote:
I understand the need for PIC, but I was asking whether or not compiling
whole binaries with PIC unnecesarily might be a bad thing. e.g. if I cannot
control the granularity of compiler options easily in a build system and I
build
On tor, mar 21, 2002 at 08:25:42 +1100, Craig Small wrote:
Here is a scan of my swedish ID-card:
http://www.tobbe.nu/images/id.jpg (337Kb)
Several things wrong with that:
- the photo ID must be in a signed email to your application manager
- that form of ID is only used if there is
On Wednesday 20 Mar 2002 11:00 pm, Michel LESPINASSE wrote:
I'd like to add that some architectures (including x86) do not actualy
require that you use -fPIC for shared libraries. If you choose to do
that, the benefits are that you dont pay the overhead of -fPIC code,
the drawbacks however
Hi!
On Wed, Mar 20, 2002 at 11:38:43PM +0100, Martin Eitzenberger wrote:
I want to make a simple debian package (I never made one before)
Only startup-script, docu and depends. But I don't understand how.
Could anyone help me?
First of all, you should read the New Maintainers' Guide (at
On Wed, 20 Mar 2002 23:38:43 +0100
Martin Eitzenberger [EMAIL PROTECTED] wrote:
Hi!
I want to make a simple debian package (I never made one before)
Only startup-script, docu and depends. But I don't understand how.
Could anyone help me?
read the new maintainers guide... you should have a
On Wed, Mar 20, 2002 at 11:11:10PM +, Will Newton wrote:
On Wednesday 20 Mar 2002 11:00 pm, Michel LESPINASSE wrote:
I'd like to add that some architectures (including x86) do not actualy
require that you use -fPIC for shared libraries. If you choose to do
that, the benefits are that
On Thursday 21 Mar 2002 1:07 am, Michel LESPINASSE wrote:
For debian shared libraries, yes.
For programs and static libraries, you should avoid using -fPIC.
Thanks, I appreciate the advice. It makes my life a bit easier too. :)
Matt Zimmerman [EMAIL PROTECTED] writes:
On Sun, Mar 17, 2002 at 02:56:29PM -0500, Colin Walters wrote:
On Sun, 2002-03-17 at 11:41, Chris AtLee wrote:
Hi there,
I've written a small program that I'd like to package and have included
in the debian archive. It's a gnome applet
28 matches
Mail list logo
