Compiling Heimdal

Compiling Heimdal

[Henry S. Thompson]

Trying to build heimdal to debug other problem.  Installed sources,
installed missing dependency of gettext-devel, hit a previously known
problem (?):

  /usr/local/src/heimdal-1.5.3/heimdal-1.5.3-1/src/heimdal-1.5.3/lib/libedit/src/editline/readline.h:79:29: fatal error: sys/ttydefaults.h: No such file or directory
 #include <sys/ttydefaults.h>

This fixed it, maybe:

***
heimdal-1.5.3-1/src/heimdal-1.5.3/lib/libedit/src/editline/readline.h~
     2012-12-09 22:06:44.000000000 +0000
---
heimdal-1.5.3-1/src/heimdal-1.5.3/lib/libedit/src/editline/readline.h
     2014-04-09 16:47:29.174398900 +0100
***************
*** 75,81 ****

  #ifndef CTRL
  #include <sys/ioctl.h>
! #if !defined(__sun) && !defined(__hpux) && !defined(_AIX)
  #include <sys/ttydefaults.h>
  #endif
  #ifndef CTRL
--- 75,81 ----

  #ifndef CTRL
  #include <sys/ioctl.h>
! #if !defined(__sun) && !defined(__hpux) && !defined(_AIX) &&
!defined(__CYGWIN__)
  #include <sys/ttydefaults.h>
  #endif
  #ifndef CTRL

Next problem:

/usr/local/src/heimdal-1.5.3/heimdal-1.5.3-1/build/lib/sqlite/.libs/libheimsqlite.a(sqlite3.o):
In function `winFullPathname':
/usr/src/debug/heimdal-1.5.3-1/lib/sqlite/sqlite3.c:34367: undefined
reference to `cygwin_conv_to_full_win32_path'

This appears to be a well-known problem -- how did this stuff get
shipped?  How did the heimdal package maintainers manage to build this
with the patches as shipped?  I'm confused.

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Compiling Heimdal

[Yaakov (Cygwin/X)]

On 2014-04-09 10:59, Henry S. Thompson wrote:
> Trying to build heimdal to debug other problem.  Installed sources,
> installed missing dependency of gettext-devel, hit a previously known
> problem (?):

You are missing BRs, namely libedit-devel and libsqlite3-devel.


Yaakov



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Compiling Heimdal

[Henry S. Thompson]

Yaakov (Cygwin/X) writes:

> On 2014-04-09 10:59, Henry S. Thompson wrote:
>> Trying to build heimdal to debug other problem.  Installed sources,
>> installed missing dependency of gettext-devel, hit a previously known
>> problem (?):
>
> You are missing BRs, namely libedit-devel and libsqlite3-devel.

Thanks!  Help me not waste time (mine and others') again, please, by
telling me how I should have known that/been able to find that out?

Maybe same question -- acronym failure: BR ?

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Compiling Heimdal

[Achim Gratz]

Henry S. Thompson writes:
> Maybe same question -- acronym failure: BR ?

Build Requirement.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Compiling Heimdal

[Yaakov (Cygwin/X)]

On 2014-04-09 12:47, Henry S. Thompson wrote:
>> On 2014-04-09 10:59, Henry S. Thompson wrote:
>>> Trying to build heimdal to debug other problem.  Installed sources,
>>> installed missing dependency of gettext-devel, hit a previously known
>>> problem (?):
>>
>> You are missing BRs, namely libedit-devel and libsqlite3-devel.
>
> Thanks!  Help me not waste time (mine and others') again, please, by
> telling me how I should have known that/been able to find that out?

The --with-sqlite3=/usr --with-libedit=/usr configure flags.


Yaakov


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Compiling Heimdal

[Csaba Raduly]

On Wed, Apr 9, 2014 at 8:39 PM, Yaakov (Cygwin/X)  wrote:
> On 2014-04-09 12:47, Henry S. Thompson wrote:
>>>
>>> On 2014-04-09 10:59, Henry S. Thompson wrote:
>>>>
>>>> Trying to build heimdal to debug other problem.  Installed sources,
>>>> installed missing dependency of gettext-devel, hit a previously known
>>>> problem (?):
>>>
>>>
>>> You are missing BRs, namely libedit-devel and libsqlite3-devel.
>>
>>
>> Thanks!  Help me not waste time (mine and others') again, please, by
>> telling me how I should have known that/been able to find that out?
>
>
> The --with-sqlite3=/usr --with-libedit=/usr configure flags.

Would it make sense for heimdal-src to depend on libedit-devel and
libsqlite3-devel (and all the other -devel packages it needs) ?
This could help people who download -src packages to build them, at
the cost of annoying those who just merely want to look at them.

Csaba
-- 
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Compiling Heimdal

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]

On Apr 10 09:42, Csaba Raduly wrote:
> On Wed, Apr 9, 2014 at 8:39 PM, Yaakov (Cygwin/X)  wrote:
> > On 2014-04-09 12:47, Henry S. Thompson wrote:
> >>>
> >>> On 2014-04-09 10:59, Henry S. Thompson wrote:
> >>>>
> >>>> Trying to build heimdal to debug other problem.  Installed sources,
> >>>> installed missing dependency of gettext-devel, hit a previously known
> >>>> problem (?):
> >>>
> >>>
> >>> You are missing BRs, namely libedit-devel and libsqlite3-devel.
> >>
> >>
> >> Thanks!  Help me not waste time (mine and others') again, please, by
> >> telling me how I should have known that/been able to find that out?
> >
> >
> > The --with-sqlite3=/usr --with-libedit=/usr configure flags.
> 
> Would it make sense for heimdal-src to depend on libedit-devel and
> libsqlite3-devel (and all the other -devel packages it needs) ?
> This could help people who download -src packages to build them, at
> the cost of annoying those who just merely want to look at them.

The cygwin installer doesn't handle src dependencies, only binary
package dependencies.

I'm wondering, though, couldn't the cygport script contain something
like this to give warning that the so-and-so devel packages are required
before building?  Does cygport support this already, perhaps, and I just
missed it?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Compiling Heimdal

[Achim Gratz]

Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> I'm wondering, though, couldn't the cygport script contain something
> like this to give warning that the so-and-so devel packages are required
> before building?  Does cygport support this already, perhaps, and I just
> missed it?

Yes it can check for prerequisites and either warn or throw an error, but
you have to put that test into the cygport file by hand.


Regards,
Achim.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Compiling Heimdal

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 900 bytes --]

On Apr 10 11:18, Achim Gratz wrote:
> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> > I'm wondering, though, couldn't the cygport script contain something
> > like this to give warning that the so-and-so devel packages are required
> > before building?  Does cygport support this already, perhaps, and I just
> > missed it?
> 
> Yes it can check for prerequisites and either warn or throw an error, but
> you have to put that test into the cygport file by hand.

Rpm spec files also have to contain the build reqs explicitely, so
that's fine then, IMHO.  Maybe we should just urge ourselves to utilze
this more often :}

Skimming the cygport manual, I just can't find the keyword to specify
the build reqs.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Compiling Heimdal

[Achim Gratz]

Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> Skimming the cygport manual, I just can't find the keyword to specify
> the build reqs.

That would be the "Checks" section, note that you need to check for the
presence of specific headers, libs, programs or package configs (as well as
language / interpreter specific modules) and not Cygwin packages as they
might not be present during bootstrapping.  Nothing prevents you from
pointing to the Cygwin package in the error message or running cygcheck to
specifically test for installed packages, though.


Regards,
Achim.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Compiling Heimdal

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 840 bytes --]

On Apr 10 13:14, Achim Gratz wrote:
> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> > Skimming the cygport manual, I just can't find the keyword to specify
> > the build reqs.
> 
> That would be the "Checks" section, note that you need to check for the
> presence of specific headers, libs, programs or package configs (as well as
> language / interpreter specific modules) and not Cygwin packages as they
> might not be present during bootstrapping.  Nothing prevents you from
> pointing to the Cygwin package in the error message or running cygcheck to
> specifically test for installed packages, though.

Oh, right.  Thanks for pointing this out.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Compiling Heimdal

[Ken Brown]

On 4/10/2014 9:50 AM, Corinna Vinschen wrote:
> On Apr 10 13:14, Achim Gratz wrote:
>> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
>>> Skimming the cygport manual, I just can't find the keyword to specify
>>> the build reqs.
>>
>> That would be the "Checks" section, note that you need to check for the
>> presence of specific headers, libs, programs or package configs (as well as
>> language / interpreter specific modules) and not Cygwin packages as they
>> might not be present during bootstrapping.  Nothing prevents you from
>> pointing to the Cygwin package in the error message or running cygcheck to
>> specifically test for installed packages, though.
>
> Oh, right.  Thanks for pointing this out.

Actually I think what you're looking for is "DEPEND" 
(/usr/share/doc/cygport/manual.html#robo821).

Ken


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Compiling Heimdal

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

On Apr 10 10:01, Ken Brown wrote:
> On 4/10/2014 9:50 AM, Corinna Vinschen wrote:
> >On Apr 10 13:14, Achim Gratz wrote:
> >>Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> >>>Skimming the cygport manual, I just can't find the keyword to specify
> >>>the build reqs.
> >>
> >>That would be the "Checks" section, note that you need to check for the
> >>presence of specific headers, libs, programs or package configs (as well as
> >>language / interpreter specific modules) and not Cygwin packages as they
> >>might not be present during bootstrapping.  Nothing prevents you from
> >>pointing to the Cygwin package in the error message or running cygcheck to
> >>specifically test for installed packages, though.
> >
> >Oh, right.  Thanks for pointing this out.
> 
> Actually I think what you're looking for is "DEPEND"
> (/usr/share/doc/cygport/manual.html#robo821).

Oh, right #2.  I should relearn reading.  Seems to be a nice feature.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Compiling Heimdal

[Achim Gratz]

Ken Brown writes:
> Actually I think what you're looking for is "DEPEND"
> (/usr/share/doc/cygport/manual.html#robo821).

I've stopped using this one since it doesn't tell you which of the
potentially many dependencies failed and it just stops the compilation
cold.  The individual check_* functions aren't any more complicated to
use and you can be a bit more lenient with certain errors if you want.
That said, if its simply a single dependency or two it msy not matter
much.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple