ports using sdp when mpeg4ip is installed

[Guido Falsi]

Hello,

I maintain a few ports, between those there are gnokii and the ports
package for obexapp, written by Maksim.

I already had to deal with the problem in the subject some time ago
(PR ports/108428) and now that gnokii has sdp support PR ports/131778
has correctly been filed.

As exlained in the PRs the problem is mpeg4ip is installing an sdp.h
file and an libsdp.so library in /usr/local/(include|lib), which
are preferred by the ports systems(especially the autotools) on the
system ones breaking software build.

The solution is doing jumps through hoops to make autotools and
other pieces behave, hardcoding base system paths or the like. I
could not find better ways. Whth gnokii right now I'm having big
problems making libtool behave. I could try patching the system
wide one to manage this situation, but I don't really understand
it's internals, if anyone could point me in the right direction
here that would be very appreciated.

We could just fix the includes problem by moving one of the two
sdp.h files in a subdirectory of include, but the libraries problem
would remain.

How should I act? Doing the hoop jumping is not a big problem to me, but in
the future with more programs taking advantage of bluetooth/sdp
functionality this problem will be even more frequent, and I don't think
fixing every single case by hand to be a good solution.

Could we try to find a system or ports wide solution?

Sorry for the lenghty email, but I wanted to explain the situation
fully.

BTW should I also send a resume of this email to gnats for historic
purposes?

Thanks in advance for any help, opinions, revision or also confort on
this.

--
Guido Falsi <mad@...>
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[Maksim Yevmenkin-2]

On Wed, Feb 18, 2009 at 6:10 AM, Guido Falsi <mad@...> wrote:

> Hello,
>
> I maintain a few ports, between those there are gnokii and the ports
> package for obexapp, written by Maksim.
>
> I already had to deal with the problem in the subject some time ago
> (PR ports/108428) and now that gnokii has sdp support PR ports/131778
> has correctly been filed.
>
> As exlained in the PRs the problem is mpeg4ip is installing an sdp.h
> file and an libsdp.so library in /usr/local/(include|lib), which
> are preferred by the ports systems(especially the autotools) on the
> system ones breaking software build.
>
> The solution is doing jumps through hoops to make autotools and
> other pieces behave, hardcoding base system paths or the like. I
> could not find better ways. Whth gnokii right now I'm having big
> problems making libtool behave. I could try patching the system
> wide one to manage this situation, but I don't really understand
> it's internals, if anyone could point me in the right direction
> here that would be very appreciated.
>
> We could just fix the includes problem by moving one of the two
> sdp.h files in a subdirectory of include, but the libraries problem
> would remain.
>
> How should I act? Doing the hoop jumping is not a big problem to me, but in
> the future with more programs taking advantage of bluetooth/sdp
> functionality this problem will be even more frequent, and I don't think
> fixing every single case by hand to be a good solution.
>
> Could we try to find a system or ports wide solution?
>
> Sorry for the lenghty email, but I wanted to explain the situation
> fully.
>
> BTW should I also send a resume of this email to gnats for historic
> purposes?
>
> Thanks in advance for any help, opinions, revision or also confort on
> this.

thanks for keeping the ports up to date!

i think the only reasonable solution is to move sdp.h (and bluetooth.h
while we at it) into /usr/include/bluetooth/

i will see what can be done here. it should be much easier to move
files now when we have svn :)

thanks,
max
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[Guido Falsi]

Maksim Yevmenkin wrote:

> thanks for keeping the ports up to date!
>

That's a pleasure, when time is available :)

> i think the only reasonable solution is to move sdp.h (and bluetooth.h
> while we at it) into /usr/include/bluetooth/
>
> i will see what can be done here. it should be much easier to move
> files now when we have svn :)

I second this idea and it sure will solve the includes problem.

It will not solve the problem with libsdp.so though.

Look at the following log:

/bin/sh ../libtool  --tag=CC   --mode=link cc -I../include -O2
-fno-strict-aliasing -pipe -march=athlon-xp -Wall -Wno-pointer-sign
-fvisibility=hidden -fno-strict-aliasing   -L/usr/local/lib -o gnokii
gnokii-gnokii.o gnokii-gnokii-calendar.o gnokii-gnokii-dial.o
gnokii-gnokii-file.o gnokii-gnokii-logo.o gnokii-gnokii-monitor.o
gnokii-gnokii-other.o gnokii-gnokii-phonebook.o gnokii-gnokii-profile.o
gnokii-gnokii-ringtone.o gnokii-gnokii-security.o
gnokii-gnokii-settings.o gnokii-gnokii-sms.o gnokii-gnokii-todo.o
gnokii-gnokii-utils.o gnokii-gnokii-wap.o ../common/libgnokii.la -lintl
   -lreadline -lncurses
mkdir .libs
cc -I../include -O2 -fno-strict-aliasing -pipe -march=athlon-xp -Wall
-Wno-pointer-sign -fvisibility=hidden -fno-strict-aliasing -o
.libs/gnokii gnokii-gnokii.o gnokii-gnokii-calendar.o
gnokii-gnokii-dial.o gnokii-gnokii-file.o gnokii-gnokii-logo.o
gnokii-gnokii-monitor.o gnokii-gnokii-other.o gnokii-gnokii-phonebook.o
gnokii-gnokii-profile.o gnokii-gnokii-ringtone.o
gnokii-gnokii-security.o gnokii-gnokii-settings.o gnokii-gnokii-sms.o
gnokii-gnokii-todo.o gnokii-gnokii-utils.o gnokii-gnokii-wap.o
-L/usr/local/lib ../common/.libs/libgnokii.so /usr/local/lib/libusb.so
/usr/local/lib/libsdp.so /usr/local/lib/libmp4v2.so
/usr/local/lib/libmp4av.so /usr/local/lib/libmpeg4ip_gnu.so -pthread
-lbluetooth /usr/local/lib/libXpm.so /usr/local/lib/libX11.so
/usr/local/lib/libxcb.so /usr/local/lib/libXau.so
/usr/local/lib/libXdmcp.so -lrpcsvc -lroken -lcrypt
/usr/local/lib/libintl.so /usr/local/lib/libiconv.so -lreadline
-lncurses  -Wl,--rpath -Wl,/usr/local/lib
../common/.libs/libgnokii.so: undefined reference to `sdp_close'
../common/.libs/libgnokii.so: undefined reference to `sdp_error'
../common/.libs/libgnokii.so: undefined reference to `sdp_search'
../common/.libs/libgnokii.so: undefined reference to `sdp_open'
gmake[1]: *** [gnokii] Error 1
gmake[1]: Leaving directory
`/usr/home/mad/src/gnokii/work/gnokii-0.6.27/gnokii'
gmake: *** [all-recursive] Error 1
*** Error code 2

Stop in /usr/home/mad/src/gnokii.
*** Error code 1

Stop in /usr/home/mad/src/gnokii.

After fixing the include(by hardcoding the path for now) I got this
error. As you can see libtool prefers libsdp.so found in localbase.

I'm not sure what a solution to this could be. in fact having two
libraries with the same name looks like a problem anyway.

I don't like the idea of FreeBSD adopting to any software which happens
to name a library like ours...But I don't know who to blame.

--
Guido Falsi <mad@...>
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[Iain Hibbert]

On Wed, 18 Feb 2009, Guido Falsi wrote:

> Maksim Yevmenkin wrote:
>
> > i think the only reasonable solution is to move sdp.h (and bluetooth.h
> > while we at it) into /usr/include/bluetooth/
> >
> > i will see what can be done here. it should be much easier to move
> > files now when we have svn :)

btw don't get too excited, you probably only need to change the Makefile
to get it installed to a different place :)

> I second this idea and it sure will solve the includes problem.
>
> It will not solve the problem with libsdp.so though.

would it make sense to merge the sdp functions into libbluetooth?
IIRC with BlueZ only one library is required..

iain
(I have a massive update to libsdp in the works anyway, perhaps it would
make sense to do that at the same time)
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[Oliver Fromme]

Iain Hibbert wrote:
 > Guido Falsi wrote:
 > > I second this idea and it sure will solve the includes problem.
 > >
 > > It will not solve the problem with libsdp.so though.
 >
 > would it make sense to merge the sdp functions into libbluetooth?
 > IIRC with BlueZ only one library is required..

Either that, or rename it to libbtsdp.

Best regards
   Oliver

--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

"Software gets slower faster than hardware gets faster."
        -- Niklaus Wirth
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."

[Guido Falsi]

On Thu, Feb 19, 2009 at 04:17:45PM +0100, Oliver Fromme wrote:

> Iain Hibbert wrote:
>  > Guido Falsi wrote:
>  > > I second this idea and it sure will solve the includes problem.
>  > >
>  > > It will not solve the problem with libsdp.so though.
>  >
>  > would it make sense to merge the sdp functions into libbluetooth?
>  > IIRC with BlueZ only one library is required..
>
> Either that, or rename it to libbtsdp.

I filed a followup to PR ports/131778 with a fix which works here.

I'm hardcoding paths though, which I do not like too much.

If someone has a better solution please let me know!

Obviously if and when libsdp will be renamed or merged into libbluetooth
I will patch the port to take advantage of this. Just let me know and I
will try to fix is ASAP.

--
Guido Falsi <mad@...>
_______________________________________________
freebsd-bluetooth@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@..."