Skip Menu |
 

Date: Mon, 29 Mar 2004 14:19:01 -0500 (EST)
From: "Sean O'Malley" <omalleys@msu.edu>
To: <krb5-bugs@mit.edu>
Subject: 1.3.2 Build problems.
Download (untitled) / with headers
text/plain 1.3KiB
I will admit I only glanced at the bug-list but i didn't see these
problems reported. (i coudl be wrong)

I ran into two problems getting 1.3.2 to build correctly on SUSE 9.0/x86

The first is a telnet build problem, tgetent() is not being defined and
line 783 of src/appl/telnet/telnet/telnet.c chokes and 903 of
src/appl/telnet/telnetd.c is the same issue. changing tgetent() to
getent() in that line at least gets it to build. I don't know about
functionality. It wasn't my concern at that point.


The second is a simple Makefile problem. If you use
--prefix=/usr/local/krb5 for the prefix. You end up with the install
choking. If you change the line in src/kadmin/v5passwdd/Makefile from
ADMIN_MANDIR = $(KRB5MANROOT)/man8
to
ADMIN_MANDIR = $(prefix)/man8 it works.

make[2]: Entering directory `/root/krb5-1.3.2/src/kadmin/v5passwdd' for f
in v5passwd; do \
/usr/bin/install -c $f \
/usr/local/bin/`echo $f|sed 's,^,/usr/local/krb5,'`; \
/usr/bin/install -c -m 644 ./$f.M \
/usr/local/man/man1/`echo $f|sed 's,^,/usr/local/krb5,'`.1; \ done
/usr/bin/install: cannot create regular file
`/usr/local/bin//usr/local/krb5v5passwd': No such file or directory
/usr/bin/install: cannot create regular file
`/usr/local/man/man1//usr/local/krb5v5passwd.1': No such file or directory


I hope this helps or was enough information.

Sean
Date: Mon, 29 Mar 2004 16:20:11 -0500 (EST)
From: "Sean O'Malley" <omalleys@msu.edu>
To: krb5 <rt@krbdev.mit.edu>
Subject: Re: [krbdev.mit.edu #2519] AutoReply: 1.3.2 Build problems.
RT-Send-Cc:
Download (untitled) / with headers
text/plain 2.3KiB
one piece of misinformation.
I was using:
./configure --enable-shared --program-prefix=/usr/local/krb5

with the Makefile problem. Using --prefix seemed to work okay.
(which is what I wanted anyway).



--------------------------------------
Sean O'Malley, Information Technologist
Michigan State University
-------------------------------------

On Mon, 29 Mar 2004, krb5 wrote:

Show quoted text
>
> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
> "1.3.2 Build problems. ",
> a summary of which appears below.
>
> There is no need to reply to this message right now. Your ticket has been
> assigned an ID of [krbdev.mit.edu #2519].
>
> Please include the string:
>
> [krbdev.mit.edu #2519]
>
> in the subject line of all future correspondence about this issue. To do so,
> you may reply to this message.
>
> Thank you,
>
>
> -------------------------------------------------------------------------
> I will admit I only glanced at the bug-list but i didn't see these
> problems reported. (i coudl be wrong)
>
> I ran into two problems getting 1.3.2 to build correctly on SUSE 9.0/x86
>
> The first is a telnet build problem, tgetent() is not being defined and
> line 783 of src/appl/telnet/telnet/telnet.c chokes and 903 of
> src/appl/telnet/telnetd.c is the same issue. changing tgetent() to
> getent() in that line at least gets it to build. I don't know about
> functionality. It wasn't my concern at that point.
>
>
> The second is a simple Makefile problem. If you use
> --prefix=/usr/local/krb5 for the prefix. You end up with the install
> choking. If you change the line in src/kadmin/v5passwdd/Makefile from
> ADMIN_MANDIR = $(KRB5MANROOT)/man8
> to
> ADMIN_MANDIR = $(prefix)/man8 it works.
>
> make[2]: Entering directory `/root/krb5-1.3.2/src/kadmin/v5passwdd' for f
> in v5passwd; do \
> /usr/bin/install -c $f \
> /usr/local/bin/`echo $f|sed 's,^,/usr/local/krb5,'`; \
> /usr/bin/install -c -m 644 ./$f.M \
> /usr/local/man/man1/`echo $f|sed 's,^,/usr/local/krb5,'`.1; \ done
> /usr/bin/install: cannot create regular file
> `/usr/local/bin//usr/local/krb5v5passwd': No such file or directory
> /usr/bin/install: cannot create regular file
> `/usr/local/man/man1//usr/local/krb5v5passwd.1': No such file or directory
>
>
> I hope this helps or was enough information.
>
> Sean
>
>
To: rt@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #2519] 1.3.2 Build problems.
From: Tom Yu <tlyu@mit.edu>
Date: Fri, 02 Apr 2004 18:06:19 -0500
RT-Send-Cc:
Show quoted text
>>>>> "omalleys" == omalleys@msu edu via RT <rt-comment@krbdev.mit.edu> writes:

Show quoted text
omalleys> one piece of misinformation.
omalleys> I was using:
omalleys> ./configure --enable-shared --program-prefix=/usr/local/krb5

Show quoted text
omalleys> with the Makefile problem. Using --prefix seemed to work okay.
omalleys> (which is what I wanted anyway).

Don't use --program-prefix for that purpose; it affects
program_tranform_name, which is probably not what you want.

---Tom
Date: Sun, 4 Apr 2004 17:09:44 -0400 (EDT)
From: "Sean O'Malley" <omalleys@msu.edu>
To: Tom Yu via RT <rt-comment@krbdev.mit.edu>
Cc: <krb5-prs@mit.edu>
Subject: Re: [krbdev.mit.edu #2519] 1.3.2 Build problems.
RT-Send-Cc:
Download (untitled) / with headers
text/plain 1.2KiB
It still didn't build. Shouldn't it still compile even if I used
that flag?

I used the wrong flag for what I was -intending-, but the fact remains
it didn't build with that particular flag or do the build scripts have
some sort of mind-reading capabilities? If so, why wouldn't they want
to tell me i am a moron in the configure script before I tried to build
it? like "configure failed! You are being a moron and either you want to
use --flag with the --program-prefix flag or you really want the --prefix
instead. RTFM!"

This is a non-issue for me because of the aforementioned OE. But I thought
I would be nice and point it out.

Sean

--------------------------------------
Sean O'Malley, Information Technologist
Michigan State University
-------------------------------------

On Fri, 2 Apr 2004, Tom Yu via RT wrote:

Show quoted text
> >>>>> "omalleys" == omalleys@msu edu via RT <rt-comment@krbdev.mit.edu> writes:
>
> omalleys> one piece of misinformation.
> omalleys> I was using:
> omalleys> ./configure --enable-shared --program-prefix=/usr/local/krb5
>
> omalleys> with the Makefile problem. Using --prefix seemed to work okay.
> omalleys> (which is what I wanted anyway).
>
> Don't use --program-prefix for that purpose; it affects
> program_tranform_name, which is probably not what you want.
>
> ---Tom
>
To: rt-comment@krbdev.mit.edu
Cc: krb5-prs@mit.edu
Subject: Re: [krbdev.mit.edu #2519] 1.3.2 Build problems.
From: Sam Hartman <hartmans@mit.edu>
Date: Sun, 04 Apr 2004 17:25:12 -0400
RT-Send-Cc:
Show quoted text
>>>>> "omalleys@msu" == omalleys@msu edu via RT <rt-comment@krbdev.mit.edu> writes:

omalleys@msu> It still didn't build. Shouldn't it still compile
omalleys@msu> even if I used that flag?

omalleys@msu> I used the wrong flag for what I was -intending-,
omalleys@msu> but the fact remains it didn't build with that
omalleys@msu> particular flag or do the build scripts have some
omalleys@msu> sort of mind-reading capabilities? If so, why
omalleys@msu> wouldn't they want to tell me i am a moron in the
omalleys@msu> configure script before I tried to build it? like
omalleys@msu> "configure failed! You are being a moron and either
omalleys@msu> you want to use --flag with the --program-prefix
omalleys@msu> flag or you really want the --prefix instead. RTFM!"

I think you misunderstand what that flag does. The program-prefix is
added in front of every program name. If it contains slash, things
won't work very well. The flag you may have been looking for is
bindir, which specifies where the programs get installed to.