Re: freebsd upgrade problem

2006-11-28 Thread Jonathan


On Nov 28, 2006, at 7:49 PM, Philip M. Gollucci wrote:

Thats um... bad.  Did you upgrade GCC and put the upgraded one in  
your path before the system one.  on 6.1 you want gcc 3.4.4 on 6.2- 
prerelease you want 3.4.6.  7.1-current is preparing to import 4.x.


If you use any other combination it should ONLY BE FOR LOCAL TESTING.

But hey if it works more power to you.

you also want the one in /usr NOT /usr/local.  gcc is part of the  
base system and ports are tested against the one in the base  
system.  The other ports exist only to aid this testing or related  
testing.


well that um.. sucks.

but it works now.  i'll try rebuilding after i upgrade to 6_1 ( i was  
on 6_0 )


perhaps there's a better way to handle the issue i discovered.
i see now that the GCC line made it use another gcc -- and not use  
another library dir (  which is what i had wanted to accomplish )

i was really just taking stabs at stuff i read in the man pages.

// Jonathan Vanasco

| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
- - - - - - - - - - - - - - - -

| FindMeOn.com - The cure for Multiple Web Personality Disorder
| Web Identity Management and 3D Social Networking
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
- - - - - - - - - - - - - - - -

| RoadSound.com - Tools For Bands, Stuff For Fans
| Collaborative Online Management And Syndication Tools
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
- - - - - - - - - - - - - - - -





Re: freebsd upgrade problem

2006-11-28 Thread Philip M. Gollucci

Jonathan Vanasco wrote:

cd /usr/ports/www/libapreq2
export GCC_EXEC_PREFIX=/usr/local/lib
make install
Thats um... bad.  Did you upgrade GCC and put the upgraded one in your 
path before the system one.  on 6.1 you want gcc 3.4.4 on 6.2-prerelease 
you want 3.4.6.  7.1-current is preparing to import 4.x.


If you use any other combination it should ONLY BE FOR LOCAL TESTING.

But hey if it works more power to you.

you also want the one in /usr NOT /usr/local.  gcc is part of the base 
system and ports are tested against the one in the base system.  The 
other ports exist only to aid this testing or related testing.


--

Philip M. Gollucci ([EMAIL PROTECTED]) 323.219.4708
Consultant / http://p6m7g8.net/Resume/resume.shtml
Senior Software Engineer - TicketMaster - http://ticketmaster.com
1024D/A79997FA F357 0FDD 2301 6296 690F  6A47 D55A 7172 A799 97F

I never had a dream come true
'Til the day that I found you.
Even though I pretend that I've moved on
You'll always be my baby.
I never found the words to say
You're the one I think about each day
And I know no matter where life takes me to
A part of me will always be...
A part of me will always be with you.


Re: freebsd upgrade problem

2006-11-28 Thread Jonathan Vanasco


On Nov 28, 2006, at 1:58 AM, Philip M. Gollucci wrote:


Seems to be a FreeBSD quark / fluke, I'll try and solve this off-list.


Argh.. I finally got it.

Thanks a ton to Philip for some offlist pointers.

error:
cd /usr/ports/www/libapreq2
make install

	cc -shared  .libs/util.o .libs/version.o .libs/cookie.o .libs/ 
param.o .libs/parser.o .libs/parser_urlencoded.o .libs/ 
parser_header.o .libs/parser_multipart.o .libs/module.o .libs/ 
module_custom.o .libs/module_cgi.o .libs/error.o  -Wl,--rpath -Wl,/ 
usr/local/lib/apache2 -Wl,--rpath -Wl,/usr/local/lib/apache2 /usr/ 
local/lib/apache2/libapr-0.so /usr/local/lib/apache2/libaprutil-0.so - 
ldb-4.2 -lexpat -liconv -lm -lcrypt -L/usr/local  -Wl,-soname - 
Wl,libapreq2.so.8 -o .libs/libapreq2.so.8

/usr/bin/ld: cannot find -ldb-4.2
gmake[2]: *** [libapreq2.la] Error 1

fix:

cd /usr/ports/www/libapreq2
export GCC_EXEC_PREFIX=/usr/local/lib
make install

I think this might actually be indicative of a ports problem/quirk,  
so i'm posting it here:


the apache20 port installs the various libs in /usr/local/lib/apache2
	when libapreq2 builds against that, it sets the base lib to  /usr/ 
local/lib/apache2 (this is the libapreq ports and source)
	i think the apache22 port and the apache source will automatically  
install into /usr/local/lib instead -- and not cause this issue to occur
	if you install the apr lib on its own (not the bundled 0.9 branch in  
apache20 ) you get a 1.0 branch in /usr/local/lib -- i think there's  
a way to build that first and have apache20 link against that, but  
i'm not sure.


i could be wrong - and this is all some sort of box specific issue.   
i'm not all that familiar with gcc and ld.  but this is what the  
problem looks to be from my vantage.


in any event, there you go.  so the next person to have this  
nightmare won't have this issue.


// Jonathan Vanasco

| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
- - - - - - - - - - - - - - - -

| FindMeOn.com - The cure for Multiple Web Personality Disorder
| Web Identity Management and 3D Social Networking
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
- - - - - - - - - - - - - - - -

| RoadSound.com - Tools For Bands, Stuff For Fans
| Collaborative Online Management And Syndication Tools
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
- - - - - - - - - - - - - - - -