Trac is being migrated to new services! Issues can be found in our new
YouTrack instance and WIKI pages can be found on our
website.
- Timestamp:
-
Jul 18, 2008, 9:22:14 AM (16 years ago)
- Author:
-
kyrian
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v31
|
v32
|
|
84 | 84 | The requirement for the "avahi-glib-devel", and (possibly also) "libgpg-error-devel" packages to be installed are a bit of a curve ball that you might miss though? |
85 | 85 | |
86 | | The following commandline may prove useful for configuration: |
| 86 | Using the basic configure line from a .src.rpm of pidgin from Fedora (in /usr/src/redhat/SPECS/pidgin.spec) will get Pidgin to build, provided you have the pre-requisites. The mandatory parts of the FC spec file's configure line for pidgin are: |
| 87 | |
| 88 | ./configure --enable-gnutls=no --enable-nss=yes --enable-cyrus-sasl --enable-tcl --enable-tk --disable-schemas-install |
| 89 | |
| 90 | And then there are optional args which I am not so sure about. |
| 91 | |
| 92 | The following commandline may prove useful for configuration if you do it another way (that's as far as I really got): |
87 | 93 | |
88 | 94 | AVAHI_CFLAGS=-I/usr/include/avahi-glib ./configure --with-avahi-client-includes=/usr/include/avahi-client |
89 | 95 | |
90 | | However, it is probably more logical to download a .src.rpm of pidgin from Fedora and mimic at least part of its ./configure command from /usr/src/redhat/SPECS/pidgin.spec. The mandatory parts of the FC spec file's configure line for pidgin are: |
91 | | |
92 | | --enable-gnutls=no --enable-nss=yes --enable-cyrus-sasl --enable-tcl --enable-tk --disable-schemas-install |
93 | | |
94 | | And then there are optional args which I am not so sure about. |
95 | | |
96 | | [ More later. You *might* be able to just do "make && make install" after that, I am not sure ] |
| 96 | [ More later. I don't think the above compile will actually enable Maiku's code by default? Can't be *that* easy? ] |
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!