Hi,

I have been experimenting with T2 the past few weeks to see if it is feasible to use as the next tool chain for some existing embedded projects. I am getting close to having something usable, but have come across something that I don't understand:

My environment:
I am using the trunk, doing the x86 arch, with a target based on embedded-minimal which was fattened up with glibc & and a few other packages.
This is being built on a Suse 9.2 host.

I am now at the point where it builds successfully with some minor package tweaks (kluges?) here & there. I will post the changes that I have made throughout, in a separate email, just in case there are some valid fixes that others can use. but they were mostly desperate changes just to get the things to compile. I noticed that what I did to get tar to compile was pretty much the same thing as the recent official fix, so perhaps I am on the right track.

Anyway, here is the ssh issue:

Our previous user space had the ssh config files in /etc/ssh. the T2 userspace is generating them in /etc. I looked at the openssh package config file and it looks like it is trying to use /etc/ssh under certain conditions, but those conditions are failing in my case, and I'm not sure why.

The following looks like it should change the sysconfdir to the ssh subdir under etc, but when I run the build, $sysconfdir is "/etc" not $root/etc, so the test fails. I wonder why the test was coded that way?, and also why my $sysconfdir does not contain the root prefix.
[ "$sysconfdir" = "$root/etc" ] && \
       sysconfdir=$root/etc/ssh

confopt="$confopt \
       --sysconfdir=\$sysconfdir \
       --with-md5-passwords \
       --disable-suid-ssh \
       --with-xauth=/usr/X11/bin/xauth"

I was going to change it by getting rid of the first 2 lines, and just changing the 2nd confopt line to:
       --sysconfdir=\$sysconfdir/ssh \
which should work in all cases. is anything wrong with that?

Thanks,

Jan



----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2

Reply via email to