Re: configure: error: C compiler cannot create executables

Sounds like something is wrong your package database. There should be a
way to check/repair it in the pkg manpages.

On 07/06/14 12:13 PM, Stefanita Rares Dumitrescu wrote:
> Well, the good news is that doing the rollback, then rebuilding the
> world/kernel worked like a charm.
> 
> The bad news is that i can't seem to get any piece of software to
> upgrade. pkg version shows every package with a ? question mark next to
> them.
> 
> 
> 
> )->portupgrade -r ruby*
> Unknown modifier 't'
> 
> Unknown modifier 't'
> 
> Unknown modifier 't'
> 
> Unknown modifier 't'
> 
> Unknown modifier 't'
> 
> "/usr/ports/Mk/bsd.sites.mk", line 953: Malformed conditional
> (!empty(_PERL_CPAN_ID) && ${_PERL_CPAN_FLAG:tl} == "cpan")
> Unknown modifier 't'
> 
> "Mk/bsd.port.mk", line 2895: Unclosed conditional/for loop
> "Mk/bsd.port.mk", line 2895: Unexpected end of file in for loop.
> 
> "Mk/bsd.port.mk", line 6682: Unclosed conditional/for loop
> "Mk/bsd.port.mk", line 6682: Unexpected end of file in for loop.
> 
> 1 open conditional:
>          at line 1173 (evaluated to true)
> make: fatal errors encountered -- cannot continue
> /usr/local/lib/ruby/site_ruby/1.9/pkgtools/portsdb.rb:237:in `join':
> can't convert nil into String (TypeError)
>         from
> /usr/local/lib/ruby/site_ruby/1.9/pkgtools/portsdb.rb:237:in `index_file'
>         from
> /usr/local/lib/ruby/site_ruby/1.9/pkgtools/portsdb.rb:247:in `db_dir='
>         from
> /usr/local/lib/ruby/site_ruby/1.9/pkgtools/portsdb.rb:167:in `setup'
>         from
> /usr/local/lib/ruby/site_ruby/1.9/pkgtools/pkgtools.rb:242:in
> `init_pkgtools_global'
>         from /usr/local/sbin/portupgrade:530:in `block in main'
>         from /usr/local/lib/ruby/1.9/optparse.rb:882:in `initialize'
>         from /usr/local/sbin/portupgrade:237:in `new'
>         from /usr/local/sbin/portupgrade:237:in `main'
>         from /usr/local/sbin/portupgrade:2371:in `<main>'
> 
> 
> 
> On 06/06/2014 17:30, Jesse Gooch wrote:
>> Hi,
>>
>> I'll spare you a scolding for trying freebsd-update with a custom kernel
>> installed! On a production server to boot! We all make mistakes though.
>>
>> Have you tried rolling back with freebsd-update? I've had similar
>> problems, and I just rolled back and built world from source. This was a
>> while ago so my memory is a little hazy though. Read the man page for
>> freebsd-update for more info on rolling back.
>> _______________________________________________
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to
>> "freebsd-questions-unsubscribe@freebsd.org"
> 
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe@freebsd.org"
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"