On Thu, 18 Jun 1998, Troy Hanson wrote:
> Duh. Okay. I missed that step after getting confused from the whole thing
> not compiling alone. A thousand pardons for the static.
>
> I added the lines to dirs, and it finishes now, but this brings up the
> final question:
> Are the manual pages
Duh. Okay. I missed that step after getting confused from the whole thing
not compiling alone. A thousand pardons for the static.
I added the lines to dirs, and it finishes now, but this brings up the
final question:
Are the manual pages changed to executable normally? How do I avoid this?
I checked and I am linking with -lc. But the -Wl thing. Is it in
addition to the -Wl,-Bsymbolic I've already got or should it replace it?
i.e.
-shared, -Wl,-Bsymbolic -Wl,soname,libtwin.so.3.2 -D_REENTRANT
or
-shared -Wl,soname,libtwin.so.3.2 -D_REENTRANT
Thanks for your help.
--
Jaldhar
Do you have a line that says
usr/man/man1
in your dirs file? It looks like that directory is not being created in
debian/TMP. Also make sure there isn't a leading / before usr.
And btw instead of chown/chgrp/chmod you might want to look into using
install(1) to move files around.
--
Jaldhar
Okay, I now have the build program, and started over on the project. (I did
miss the package with build in it). I still get the failure when it tries
to copy the man pages before making the directories under
(srcdir)/debian/tmp/usr
For the #linux problem, I am just leaving the #define LINUX ri
You have everything right so far. You need to make sure that it links
with "-lc" (libc) and that it sets the soname. This is done w/
-Wl,soname,libfoo.so.. This makes it so that multiple libs can
co-exist. Like libc5 and libc6 do.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
I'm packaging the Windows emulator TWIN. It's my first library package
and the experience has been very educational (though in retrospect I think
I should have picked something a little smaller.) I have a a nice -dev
package. I have nice static libraries. I'm still getting problems with
shared
debmake doesn't make the build script it is include in the debmake
package. Or was. I forget exactly when but somewhere down the line build
and other scripts were moved into their own package called devscripts.
(The current version of "Creating a package with debmake" mentions you
need devscript
Hi! I am working on a package called 'heyu' for X-10 control. I am
trying to follow The New-Maintainer's Debian Packaging Howto and Creating a
Package using Debmake files, but they refer to things that aren't happening
on my system. :(
I had it built into a .deb file fine with deb-make under 1.
On Thu, Jun 18, 1998 at 10:58:07AM +0100, James Troup wrote:
> Eh? The use of .orig.tar.gz pre-dates the use of pristine source
> significantly. Often there is no way to make certain alterations to
> the upstream source other than to alter the .orig.tar.gz (i.e. if you
> want to mass-remove or a
"Marcelo E. Magallon" <[EMAIL PROTECTED]> writes:
> On Tue, Jun 16, 1998 at 06:51:11PM +0100, James Troup wrote:
> > tmancill <[EMAIL PROTECTED]> writes:
> >
> > > Put another way: "Am I going to mess up any of the automated
> > > scripts processing the archive if I make changes to the
> > > .ori
On Tue, Jun 16, 1998 at 06:51:11PM +0100, James Troup wrote:
> tmancill <[EMAIL PROTECTED]> writes:
>
> > Put another way: "Am I going to mess up any of the automated scripts
> > processing the archive if I make changes to the .orig.tar.gz without
> > giving it a new name?"
>
> No.
James is ri
12 matches
Mail list logo
