Re: glib compile problem

Jeremy Messenger wrote:
> On Wed, 04 Jul 2007 03:02:09 -0500, Ganbold <ganbold_at_micom.mng.net> 
> wrote:
>
>> Replying to myself, it seems like it required gettext which was 
>> missing on my machine.
>> Should glib install dependent packages such as gettext?
>> Maybe I'm wrong here.
>
> It is already depend on gettext.

Yeah, I know that. I meant, should making glib install gettext if 
gettext is not installed on the system?

thanks,

Ganbold


>
> Cheers,
> Mezz
>
>> thanks,
>>
>> Ganbold
>>
>> Ganbold wrote:
>>> Hi,
>>>
>>> When I'm trying to install mc from ports in today's CURRENT machine 
>>> I've got following errors:
>>> It fails in glib20 configure script. Also I saw a lot of "sh: 
>>> environment corrupt; missing value for"
>>> messages.
>>>
>>> ..
>>> sh: environment corrupt; missing value for LC_ALL
>>> sh: environment corrupt; missing value for LC_NUMERIC
>>> i486-portbld-freebsd7.0
>>> checking for gcc... cc
>>> checking for C compiler default output file name... configure: 
>>> error: C compiler cannot create executables
>>> See `config.log' for more details.
>>> ===>  Script "configure" failed unexpectedly.
>>> Please run the gnomelogalyzer, available from
>>> "http://www.freebsd.org/gnome/gnomelogalyzer.sh", which will 
>>> diagnose the
>>> problem and suggest a solution. If - and only if - the 
>>> gnomelogalyzer cannot
>>> solve the problem, report the build failure to the FreeBSD GNOME 
>>> team at
>>> gnome_at_FreeBSD.org, and attach (a)
>>> "/usr/ports/devel/glib20/work/glib-2.12.12/config.log", (b) the 
>>> output of the
>>> failed make command, and (c) the gnomelogalyzer output. Also, it 
>>> might be a
>>> good idea to provide an overview of all packages installed on your 
>>> system
>>> (i.e. an `ls /var/db/pkg`). Put your attachment up on any website,
>>> copy-and-paste into http://freebsd-gnome.pastebin.com, or use 
>>> send-pr(1) with
>>> the attachment. Try to avoid sending any attachments to the mailing 
>>> list
>>> (gnome_at_FreeBSD.org), because attachments sent to FreeBSD mailing 
>>> lists are
>>> usually discarded by the mailing list software.
>>> *** Error code 1
>>>
>>> Stop in /usr/ports/devel/glib20.
>>> *** Error code 1
>>>
>>> Stop in /usr/ports/devel/glib20.
>>>
>>> And the config.log says:
>>>
>>> configure:3499: $? = 0
>>> configure:3506: cc -V >&5
>>> cc: '-V' option must have argument
>>> configure:3509: $? = 1
>>> configure:3532: checking for C compiler default output file name
>>> configure:3559: cc -O1 -pipe  -I/usr/local/include -L/usr/local/lib 
>>> -lintl conftest.c  >&5
>>> /usr/bin/ld: cannot find -lintl
>>> configure:3562: $? = 1
>>> configure: failed program was:
>>> | /* confdefs.h.  */
>>> | #define PACKAGE_NAME "glib"
>>> | #define PACKAGE_TARNAME "glib"
>>> | #define PACKAGE_VERSION "2.12.12"
>>> | #define PACKAGE_STRING "glib 2.12.12"
>>> | #define PACKAGE_BUGREPORT 
>>> "http://bugzilla.gnome.org/enter_bug.cgi?product=glib"
>>> | #define GLIB_MAJOR_VERSION 2
>>> | #define GLIB_MINOR_VERSION 12
>>> | #define GLIB_MICRO_VERSION 12
>>> | #define GLIB_INTERFACE_AGE 12
>>> | #define GLIB_BINARY_AGE 1212
>>> | #define G_COMPILED_WITH_DEBUGGING "minimum"
>>> | /* end confdefs.h.  */
>>> |
>>> | int
>>> | main ()
>>> | {
>>> |
>>> |   ;
>>> |   return 0;
>>> | }
>>> configure:3600: error: C compiler cannot create executables
>>> See `config.log' for more details.
>>>
>>> Anybody has solved this issue before?
>>>
>>> thanks,
>>>
>>> Ganbold
>
>


-- 
Some men love truth so much that they seem to be in continual fear lest 
she should catch a cold on overexposure. -- Samuel Butler